Managed IT procurement
Run a controlled MSP handover from notice to exit
An operational MSP exit runbook sequences the agreed notice, service inventory, secure knowledge transfer, successor validation, staged access changes, service acceptance and closure. Follow the customer agreement and obtain qualified legal advice on contract rights; this is an operational handover checklist, not legal advice.
Inventory services, owners and dependencies
Securely deliver agreed records and evidence
Test successor coverage before access removal
Prepare the operational handover
Confirm the agreed notice and final-service dates, transition owner, critical services, affected sites, business contacts, unresolved incidents, renewal dates, and successor-provider responsibilities. Compare the incoming and outgoing coverage so the change does not silently remove monitoring, backup or escalation.
Use the contract to confirm notice, cooperation, fees and deliverables. Keep legal interpretation with qualified counsel; this runbook does not determine contractual rights.
Transfer records through an approved channel
Inventory customer-controlled accounts, privileged roles, assets, configurations, network diagrams, backup and restore evidence, monitoring, alerts, open tickets, known risks, licences, vendor contacts, scripts and automation. Agree the export format and recipient before transferring sensitive records.
Track each item as requested, delivered, validated, not applicable or unresolved. Record the receiving owner and evidence without putting passwords, recovery codes or secrets into an ordinary checklist.
Validate service, then close access
Have the successor confirm access, service ownership, escalation contacts, alert routing and backup visibility. Test representative workflows and restore evidence under an approved plan before the outgoing provider's access is removed.
After acceptance, rotate shared credentials, remove delegated access and agents as appropriate, return equipment, reconcile licences, document exceptions and obtain the agreed data-deletion confirmation. Preserve a dated handover record.
Primary sources
This page separates sourced facts from North Star's operational guidance. Check the current source before relying on a changing price, rule, list, or technical standard.
Questions businesses ask
What sequence should an MSP handover follow?
Confirm the agreed dates and owners, inventory services, transfer approved records securely, validate successor access and coverage, accept the services, then remove old access and close outstanding items.
When should outgoing MSP access be removed?
Coordinate removal with the agreed transition and security plan. Validate replacement access and recovery first, except where a security incident requires an immediate controlled revocation.
What evidence should the handover retain?
Keep the dated inventory, transfer status, receiving owners, validated access and coverage, open risks, equipment and licence disposition, approved access removal, and agreed data-deletion confirmation.
Turn the research into an operating plan
North Star can help assess the environment, define scope, document ownership, implement controls, and verify the result.
Review North Star managed IT