Switching MSP: Warning Signs and a Clean Handover Plan

You switch MSP by spotting the warning signs early, shortlisting a replacement before you give notice, locking down your own credentials and licences, exporting every scrap of documentation, running a proper overlap period, and getting a signed offboarding checklist from the outgoing provider. Do it in that order and the switch is boring. Do it in any other order and you're gambling with your own infrastructure.

What are the warning signs you need a new MSP?

I've taken calls from three different London businesses this year who all said some version of the same thing: "we didn't realise how bad it had got until we tried to leave." The signs are rarely dramatic. They creep in. Response times stretch from hours to days. Tickets get acknowledged, then go quiet. Nobody on their side can explain what's actually running on your servers anymore, because the engineer who set it up left eighteen months ago and nothing was documented.

If you're asking the question at all, you probably already know the answer. Trust your gut, then go looking for evidence.

How slow response times actually signal a bigger problem

A slow reply to a low-priority ticket isn't the issue. The issue is what slow response reveals about resourcing. MSPs that are overselling capacity, understaffed, or losing engineers faster than they can hire, all show up first as response time drift. By the time you notice it consistently, it's usually been building for months. Check your ticket history rather than your memory. Memory is generous. Timestamps aren't.

Why surprise invoices mean it's time to leave

Unplanned costs are a trust problem, not a billing problem. A good MSP tells you before the work happens, not after. If you're regularly seeing line items you didn't approve, "emergency" hours that weren't discussed, or scope creep dressed up as necessary maintenance, that's not sloppy admin. That's a provider who has stopped treating you as a partner and started treating you as a margin line. Pull your last six months of invoices and compare them against what was actually quoted or agreed. The gap tells you everything.

What does "no roadmap" look like in practice

Ask your current MSP what your infrastructure looks like in twelve months. If the answer is vague, or worse, if there isn't one at all, you're paying for reactive firefighting rather than management. A managed service should mean someone is thinking ahead on your behalf: patch schedules, capacity planning, renewal timing, security posture. If every conversation starts with "so what's broken this week" rather than "here's what we're planning next quarter", you don't have management. You have a very expensive fire brigade.

How can you tell if your credentials are being held hostage?

This is the one that turns a switch into a crisis. Some providers, deliberately or through sheer disorganisation, never give clients full admin access to their own domains, hosting accounts, DNS, or licensed software. If you don't personally hold the keys to your own domain registrar, your DNS panel, and your server root or admin logins right now, stop reading this and go check. Today, not next week.

This isn't paranoia. It's basic operational hygiene, and it's the same principle security bodies push for constantly. The Cybersecurity and Infrastructure Security Agency has published extensive guidance on access control and credential management precisely because handover failures like this are one of the most common ways businesses lose control of their own systems, not through a dramatic hack but through a badly managed offboarding.

How do you shortlist a replacement before giving notice?

Never give notice to your current MSP before you've got a replacement lined up and vetted. This sounds obvious. I've watched businesses ignore it anyway, hand in notice out of frustration, and then spend three tense weeks scrambling to find someone competent while their old provider's enthusiasm for helping them evaporates entirely.

Build a shortlist properly. Use HostList's MSP directory to compare providers on more than a sales call and a logo wall. If location or timezone coverage matters to your team, narrow it down with regional listings like managed service providers in London or managed service providers in Texas so you're comparing like for like on support hours and on-site capability. Don't just take the pitch at face value. Check how the provider is actually ranked and why, not just how loudly they market themselves. Our MRI methodology exists for exactly this reason: it scores trust signals rather than marketing spend, and we've written a full breakdown of how the MRI ranks managed service providers if you want to understand what's actually being measured before you sign anything.

What should a clean offboarding checklist include?

This is the document that saves you. Get it in writing, signed, before the old MSP switches off support. At minimum it needs:

• Full list of admin credentials, transferred to accounts you control, not shared logins the old provider still has copies of
• Domain registrar and DNS access, confirmed in your name
• All software licences, transferred or reissued in your name, with proof of purchase
• Complete network and server documentation, architecture diagrams, IP allocations, firewall rules
• Full backup export, tested and confirmed restorable, not just "we have backups, trust us"
• A written statement of what was and wasn't covered under the old contract, so nothing falls into a gap

If a provider resists handing any of this over, that resistance is itself useful information. It confirms you were right to leave.

How long should the overlap period last?

Long enough that the new MSP has actually seen your systems under normal operating conditions, not just read the documentation. For most small to mid-sized setups that means a few weeks of parallel access, where the incoming provider can observe, ask questions, and flag anything the paperwork missed, while the outgoing provider is still contractually on the hook to answer questions. Don't let the old MSP disappear the day the new contract starts. Overlap is cheap insurance against the stuff nobody wrote down.

If you want the mechanics of the actual cutover, DNS changes, propagation timing, minimising downtime, we've covered that in detail in how to switch web hosting providers without breaking your site. The principles apply whether you're moving hosting, a full MSP relationship, or both at once.

Frequently asked questions

What exactly is MSP offboarding?

MSP offboarding is the formal process of ending a managed service contract in a way that transfers full ownership of your credentials, licences, documentation and backups back to you, confirmed in writing before support access is cut off.

How much notice should I give my current MSP?

Check your contract first. Most have a defined notice period, but treat that as a minimum rather than a target. Give yourself enough runway to have a vetted replacement ready and an overlap period agreed before you formally serve notice.

Can an MSP legally refuse to hand over my credentials?

No reputable provider should refuse access to accounts, domains or systems that belong to you. If a contract genuinely restricts this, get legal advice before signing anywhere else, and treat the refusal itself as a serious red flag about how the relationship has been run.

What happens if my MSP shuts down or becomes unreachable?

Recover what you can directly: domain registrar, hosting control panel, DNS, since those are usually accessible independently of the MSP if you were ever given proper access. This is exactly why holding your own credentials from day one matters. It's the difference between a minor inconvenience and a genuine emergency.