Most companies don’t switch MSPs until something breaks. Then they switch in panic — and pick the next provider too quickly, sometimes ending up with the same problems wrapped in a different logo.
The better path is to recognize the signs early, plan the transition, and run a real evaluation before you commit. This is a guide to when to switch MSPs, what the warning signs actually look like, and how to make a clean transition without a 60-day support gap.
You don’t need a disaster to justify a change
The biggest reason buyers wait too long: they’re confusing stability with quality. Your MSP isn’t failing outright, so it must be fine, right?
The bar is higher than that. A managed IT provider you pay $10,000–$25,000 a month should be making your business measurably more secure, more productive, and more capable every quarter. If they’re not — even if nothing is on fire — you’re paying for stability you could get from a stronger partner.
Here are the eleven signs that experienced operators use to recognize when an MSP relationship is past its expiration date.
The 11 signs you’ve outgrown your MSP
1. The same tickets keep coming back
If your team is opening the same kind of ticket every month — the same printer, the same VPN, the same email rule — your MSP is treating symptoms, not causes. Mature MSPs do root-cause analysis and document recurring issues, then propose changes that eliminate the underlying problem. Reactive ticket-closing is a sign of a help desk that’s measured by speed, not outcomes.
2. You’re the one telling them what’s wrong
You shouldn’t be discovering issues before your MSP does. If you’re finding outages, security alerts, or capacity problems first — and your monitoring is supposedly their job — the monitoring isn’t actually being watched, or the alerts are being silenced. Either way, you’re paying for a service you’re not getting.
3. You can’t get your data, credentials, or documentation when you ask
A simple test: email your account manager and ask for a current copy of your network documentation, the list of admin accounts on your tenant, and an export of your password vault. A healthy MSP can deliver all three within a few business days. A weak one will stall, ask why, or send back partial information. You should own these things outright, and getting them should not feel like a divorce proceeding.
4. Quarterly business reviews disappeared (or never existed)
Real MSPs run a Quarterly Business Review (QBR) — a structured meeting that covers ticket trends, security posture, projects completed, projects upcoming, and budgeting for the next quarter. If you can’t remember the last QBR you had, or you’ve never had one, your MSP is operating reactively and you have no view into the relationship.
5. Their team is constantly turning over
You meet a new technician every other ticket. The vCIO who onboarded you left after six months. Your account manager has changed three times. Staff churn at an MSP shows up as institutional knowledge loss in your environment — repeat issues, lost context, slower resolution. If you’ve worked with five different account managers in two years, your MSP has a structural problem that you’ll keep paying for.
6. Security recommendations are stuck in 2018
Multi-factor authentication everywhere. Endpoint detection and response (EDR), not just antivirus. Conditional access. Privileged access management. Email security beyond Microsoft’s defaults. Phishing simulation and training. If your MSP hasn’t proactively walked you through implementing these in the last 18 months, they’re behind the threat landscape, and your business is wearing the risk for them.
7. The “managed” services you bought aren’t actually managed
This one stings. Many SMBs discover, when they finally check, that their backup hasn’t completed in three weeks, their patch compliance is 62% (not the 98% in the proposal), or the EDR they’re paying for has alerts piled up and unreviewed. The hardest part is that nothing breaks until it does — the gap is invisible until an incident exposes it. Ask for hard reports on every “managed” service. Anything they can’t produce isn’t actually being managed.
8. Projects always slip
A 60-day Microsoft 365 migration becomes 9 months. Firewall replacements get pushed three quarters in a row. Office moves run hot on the day-of with frantic engineer scrambling. Project execution is one of the clearest signals of internal MSP maturity. If your projects always slip, theirs do too — and yours just happens to be in their queue.
9. You’ve grown and they haven’t
The MSP you picked at 25 employees may not be the right MSP at 125. A provider built around small business support often hits a ceiling around the point where you have multiple offices, more sophisticated security needs, compliance requirements (HIPAA, SOC 2, CMMC), and meaningful internal IT staff to coordinate with. The signs: vague answers on compliance, no Tier 3 engineers, no documented process for change management.
10. Your insurance or compliance auditor flagged the gap
If your cyber insurance broker, your auditor, or your compliance partner has flagged a gap your MSP should have closed — and your MSP’s response is “we’ll add that to the roadmap” — they should have raised it first, not last. Insurance and audit findings are an external check on what your MSP should have caught internally. Repeated findings of the same kind mean the MSP isn’t keeping up.
11. You don’t trust them to handle a real incident
The honest gut-check question. If you got a ransomware notification on a Sunday morning, would you call your MSP first, or would you call them second? If the answer is second, you have your answer. A managed IT provider who isn’t your first call in a real incident isn’t fulfilling the core job.
The “is it us or them?” check
Before switching, run a 30-day diagnostic on your own side first. Some “MSP problems” are actually communication problems, and switching providers without fixing them just resets the clock.
- Are tickets being submitted properly, with severity and impact, or are they sneaking in as Slack DMs to a tech?
- Is leadership engaged with the QBR, or are reviews scheduled and never attended?
- Is the MSP being asked for things that weren’t in the original contract, with no scope or fee adjustment?
- Have you outgrown the original SOW without renegotiating it?
If you’ve worked through this list honestly and the issues are still on the MSP’s side, switching is the right move.
How to evaluate an IT provider as a replacement
The biggest mistake on a switch is picking a new provider too fast. The same red flags that hurt you the first time will hurt you again. A repeatable process:
- Document what’s not working in writing, in concrete terms (not “they’re slow” — “average ticket resolution went from 2.4 hours to 6.1 hours over the last year”).
- Build a written list of must-haves for the next provider: industry experience, compliance posture, response time, project delivery track record, references in your size range.
- Get three written proposals that respond to your specific environment, not generic boilerplate.
- Speak to references at the new provider — and ask each one specifically what surprised them in year two of the relationship.
- Read the new contract carefully for the same red flags that may have hurt you the first time: vague pricing, long auto-renewal terms, weak SLAs, soft ownership of credentials.
- Plan the transition for a quiet quarter, not the run-up to year-end or your busy season.
How to switch MSPs without disruption
A clean transition takes 60–90 days and overlaps the providers. The phases:
Days 0–30 — Documentation and discovery. New provider performs a discovery on your environment in parallel with the old provider continuing to deliver service. Insist on documentation handover from the outgoing MSP — administrator credentials, network diagrams, vendor contacts, password vault, license keys, contracts.
Days 30–60 — Tenant access, monitoring, and tooling cutover. New provider takes over monitoring agents, RMM tooling, EDR, backup, and ticketing. Old provider remains as a support backstop for legacy questions.
Days 60–90 — Full cutover. New provider is primary on all support. Old provider is officially terminated (in writing, in their preferred form). Tenants are confirmed under your ownership. Termination assistance fees are paid only if and as the contract requires.
Three actions to take before you commit to switching:
- Document what is not working in measurable terms — average ticket resolution went from X to Y, not just "they are slow."
- Email your account manager and request a current copy of your network documentation, admin account list, and password vault export. The response itself tells you a lot.
- Run a parallel evaluation while still under contract. Discovery calls and proposals do not violate any agreement, and the comparison is sharper with something current to measure against.
What most companies don’t realize
Two things that experienced buyers learn the hard way:
You can run a parallel evaluation while still under contract. You don’t need to terminate your current MSP before talking to alternatives. A discovery call, a reference check, and a written proposal don’t violate any contract — and the comparison is far more useful when you have something current to measure against.
Switching MSPs is the highest-risk operational change a 50–200 employee company makes in any given year. Treat it like one. The reason most switches go badly is rushed timing, missing documentation, and unclear responsibility during the cutover. Done well, it’s smooth and invisible. Done badly, it’s a 60-day support gap your team will remember for a decade.
Frequently asked questions
How long do most companies stay with one MSP?
Average tenure is 3–5 years for SMB and mid-market engagements. Companies that switch sooner usually do so because of severe service issues; companies that stay longer than 7 years often do so out of inertia, not satisfaction. The right cadence is to evaluate the relationship every 18–24 months — even if you don’t change anything.
Can my MSP refuse to hand over our credentials and data?
They cannot refuse what’s yours, but a poorly written contract can let them slow-walk it or charge “transition assistance fees” for the work. The protection is in the contract you sign at the start, not in the conversation at the end. If you’re already in this position, document everything in writing and escalate up the chain — most MSPs will move quickly to avoid a public dispute.
How long does it take to switch MSPs?
A good transition takes 60–90 days end-to-end. Faster than that increases risk; slower than that means one of the providers isn’t moving. The transition should overlap, not gap.
Will my new MSP be cheaper than my current one?
Sometimes. More often, the new MSP is similar in price but provides more value — better security tooling, real QBRs, faster response, higher-tier engineers. Switching to save 10% is rarely worth the operational risk. Switching to get to a meaningfully different service tier usually is.
What if my current MSP has been poaching our employees, mismanaging credentials, or otherwise behaving badly?
Get an attorney involved before you terminate. Most contracts have specific rights and remedies for this kind of conduct, and you want them on record before the relationship ends.
Keep learning
- How to Choose an MSP: The Complete Buyer’s Guide — the buyer’s process applies on the second engagement too
- 12 MSP Red Flags to Watch for Before You Sign — what to watch for in the replacement
- Hidden Costs of Managed IT Services — termination fees and offboarding clauses to negotiate before you’re stuck
To compare replacement providers in your area or industry, browse the MSP directory.