How to Switch MSPs Without Breaking Anything

Switching MSPs is a little scarier than it needs to be. Most of the drama comes from two things: not having your documentation in hand before you leave, and trying to do everything at once. A clean switch is methodical.

Before you sign with the new MSP

• Request a full inventory from your current MSP: users, devices, licenses, network diagram
• Request credential ownership documentation for every account used to manage your environment
• Request a copy of your documentation (runbooks, configurations, vendor contacts)
• Request export of monitoring data and ticket history
• Note anything your current MSP refuses to provide — you'll need a plan for it

During the 30-day transition

A healthy MSP transition runs 2–4 weeks. Not a weekend. The new provider needs to onboard your environment, stand up their monitoring, install their endpoint agents, inventory your assets, and document everything they find. Rushing this is where things break.

The overlap period

Keep your outgoing MSP engaged through the transition. Don't terminate their contract until the new MSP has confirmed they have everything. This is a $500–$2,000 insurance policy that prevents the 'the old provider already disabled their access and the new one doesn't have it yet' catastrophe.

What the outgoing MSP owes you

• All credentials for accounts you own (Microsoft 365, domain registrar, etc.)
• Full documentation of your environment
• Reasonable cooperation with the new provider during handoff
• Return or transfer of any hardware you own that's in their possession

A professional MSP does all of this without drama. If yours is making it difficult, that itself is useful information about why you were right to leave.

The first 90 days with the new provider

Expect some noise. The new provider will find issues the old one was ignoring. That's normal — and it's the point. Give them 90 days to stabilize the environment before judging results. A healthy MSP transition looks worse before it looks better, because you're now seeing the problems instead of letting them accumulate.

The six-month mark is usually when clients say things like 'this is what IT was supposed to feel like the whole time.' That's the benchmark to aim for.