How to hand off cleanly when you're the outgoing MSP

The handoff package

1. 1
   Root access to the client, first and unprompted

   Global admin / super admin on their tenants to an account the client's business controls — offered before anyone asks. This single move defuses the entire adversarial script. (It should have been true all along; if it isn't, fixing it is step zero.)
2. 2
   The documentation export

   Asset lists, configurations, credentials (transferred securely, then rotated), network diagrams, licence inventory, warranty records. Whatever lives in your documentation platform about them is theirs — deliver it in a form the next provider can use.
3. 3
   Licence and billing transition

   If their Microsoft/Google licences run through your CSP relationship, coordinate the move to the new provider's — with dates, so nothing lapses mid-transfer. Same for any subscription you resell: backup, security tooling, phone.
4. 4
   The backup handover

   Where backups live, how to reach them, retention settings — and a joint test restore with the incoming provider. Backups you leave behind but nobody can restore are a liability with your name on it.
5. 5
   Agent and access removal, last and documented

   Your RMM agents, remote-access tools, engineer accounts, VPN profiles, conditional-access exceptions — removed after the new provider is stood up, with a written confirmation of what was removed and when. That letter protects you as much as them.

The 30-day overlap

Offer a fixed, paid transition window: you answer the incoming provider's questions, hold read access for continuity, and handle the in-flight tickets. Paid matters — free overlap breeds resentment and sloppiness; a modest transition fee makes it a professional engagement with defined ends. Most incoming MSPs will sing your praises for it, and incoming MSPs are outgoing MSPs' best referral source in ways nobody admits.

What never to do

• Hold access hostage against invoices. Pursue unpaid bills through the contract, not the tenant — withholding a client's own admin access is reputational self-harm and, depending on jurisdiction and contract, legally reckless.
• Let things lapse 'accidentally' during the notice period. Domains and certificates expiring on your watch during a handoff read as sabotage even when they're negligence.
• Badmouth the incoming provider. Every criticism you voice will be tested against how clean your handoff was.
• Delete your documentation about the client out of spite or 'policy' the week they leave. Export first, always.

The quiet payoff

Clients come back — the new provider disappoints, the acquirer churns them, the ops manager moves on — and the ones who come back are the ones whose exit was painless. Do the offboarding so well it becomes a story they tell, and treat our incoming-MSP checklist (written for the client's side of this same transition) as the standard your package should exceed.