Most businesses wait too long to fire their MSP. The relationship decays slowly — tickets a little slower each quarter, invoices a little higher — until an outage or a breach forces the question. Service quality, not price, drives the majority of MSP switches (CompTIA State of the Channel, 2025).
This guide gives you the 9 warning signs that justify a switch, the contract homework to do before you say anything, and the migration checklist that gets you out without losing data or uptime. When you're ready to shortlist replacements, our provider directory is the place to start.
What are the warning signs you need a new MSP?
The firing offenses
-
1. Repeated P1 SLA misses. One slow response is a bad day. Three documented misses in a quarter is a staffing problem. Healthy MSPs hit first response inside 30-60 minutes for critical incidents (Datto Global State of the MSP Report, 2024) — log every incident against your SLA's stated targets.
-
2. Patching has gone stale. Pull a patch-compliance report. If 90%+ of endpoints aren't current within 30 days of patch release, you're carrying breach risk you're paying to avoid. Unpatched vulnerabilities remain a leading ransomware entry vector (Sophos State of Ransomware, 2025).
-
3. Backups aren't tested. Ask for the date and result of the last test restore. No answer means no recovery plan — and the median SMB ransomware recovery ran $1.5 million including downtime (Sophos, 2025).
-
4. Surprise invoices keep appearing. Recurring "out of scope" charges for work you assumed was covered signal either a scope mismatch or deliberate under-quoting. Both end the same way.
-
5. Security recommendations stopped. If your MSP hasn't pushed MFA enforcement, EDR, or security training in the past year, they're operating a 2019 playbook in a 2026 threat environment.
The slow-decay signs
- 6. Your account manager disappeared. No quarterly business review in 6+ months means you're on the neglect tier.
- 7. The same problems recur. Tickets get closed; root causes don't get fixed.
- 8. You've outgrown them. Compliance needs (HIPAA, CMMC), a second site, or 24/7 operations they can't staff.
- 9. Their turnover shows. A new technician on every ticket means knowledge of your environment is evaporating.
Two or more firing offenses, or four-plus slow-decay signs, justify starting the search. One bad month doesn't — raise it at a QBR first, in writing, with dates.
What should you check before giving notice?
Three contract items decide your timing and cost. Pull the agreement before talking to anyone:
| Contract item | What to find | Why it matters |
|---|---|---|
| Renewal window | Notice deadline (30-180 days) and renewal date | Miss it and you're locked another 12 months |
| Early-exit terms | Buyout percentage of remaining months | Mid-term exits can cost 50-100% of remaining value |
| Data + offboarding clauses | Who owns docs/passwords; exit-assistance hours | Decides whether migration is smooth or hostage |
If your renewal is more than 6 months out and exit fees are steep, run the search now and time the switch to the window. Document SLA misses meanwhile — they're negotiation leverage and, in some contracts, a no-penalty exit trigger (contract terms guide).
How do you run the migration? The 30-60 day checklist
A clean MSP-to-MSP migration runs 30-60 days with a 2-4 week overlap period. Here's the sequence.
Phase 1: Before notice (weeks 1-2)
- Select the new MSP using the 15-point evaluation checklist; sign with a start date aligned to your exit window
- Inventory everything: devices, licenses, domains, admin accounts, vendor contacts
- Export or screenshot current documentation from the old MSP's portal while access is friendly
- Verify you hold registrar, Microsoft 365 global admin, and firewall credentials in escrow — not just the MSP
- Confirm backup status independently: when, where, last test restore
Phase 2: Notice and overlap (weeks 3-6)
- Give written notice per the contract's method and window; request the offboarding plan in writing
- New MSP deploys its RMM agents alongside the old (they coexist fine)
- Transfer documentation: network maps, configs, password vault export, runbooks
- Rotate every administrative credential the old MSP held — domain admin, M365, firewall, backup console
- Move monitoring, alerting, and helpdesk routing to the new provider on a named cutover date
Phase 3: Cutover and closeout (weeks 6-8)
- Old MSP's agents and remote-access tools removed from every endpoint — verify with a scan, don't take their word
- Final data export: ticket history, asset records, configuration docs
- Revoke the old MSP's accounts in every system; check M365 enterprise app grants and conditional-access exceptions
- Confirm backup chain ownership transferred (storage accounts, retention, encryption keys)
- Reconcile the final invoice against contract terms before paying
The credential rotation step is the one businesses skip. Departing MSPs retain working admin access in a surprising share of switches — CISA's MSP guidance exists precisely because provider access is a high-value attack path (CISA Advisory AA22-131A, 2022).
What does switching cost?
Budget three items. Onboarding with the new MSP runs about one month's contract value, often waived on longer terms.
Then add the overlap — paying two providers for 2-4 weeks — and any early-exit buyout per your old contract.
Against that: companies that switch for documented service failures typically recover the cost within months through eliminated "out of scope" billing and right-sized contracts. Get the new quote benchmarked against 2026 market pricing — $125-$200 per user per month for a standard stack — before assuming your current rate is the problem.
One cost-control move worth knowing: tell the new MSP you're switching from a competitor, not starting fresh. Many providers discount or waive onboarding for competitive takeaways because your environment is already documented and agent-managed.
The discount is rarely advertised. You have to ask.
Timing also matters. Avoid cutovers during your busy season, quarter-end, or a compliance audit window. The overlap period is cheap insurance; compressing it to save two weeks of double-billing is the most common self-inflicted wound in MSP migrations.
Frequently Asked Questions
How long does it take to switch MSPs?
Plan 30-60 days end to end: 1-2 weeks of selection and inventory, written notice per your contract window, a 2-4 week overlap while the new provider deploys agents and absorbs documentation, then cutover and credential rotation. Complex environments with compliance requirements run toward 90 days.
Can I switch MSPs mid-contract?
Yes, but read the early-termination clause first — buyouts of 50-100% of remaining contract value are standard. Two cheaper paths: documented SLA failures (some contracts allow exit-for-cause), or timing the switch to the renewal window. If the window requires 90+ days' notice, calendar it now.
What should my old MSP hand over when I leave?
Complete documentation (network maps, configurations, runbooks), a full password-vault export, ticket and asset history, backup chain ownership including encryption keys, and removal of all their agents and remote-access tools. Offboarding assistance should be in the contract; 10-20 hours is a normal allowance.
Will switching MSPs cause downtime?
A properly run migration causes none — RMM agents from both providers coexist during overlap, and monitoring cuts over on a scheduled date. The real risks are access-related: credentials not rotated, backup chains orphaned, or licenses lapsing. The checklist's escrow and verification steps exist for those.
How do I know the problem is my MSP and not my budget?
Benchmark first. If you're paying under $100 per user per month for "all-inclusive" service, slow tickets may be the price of a lean contract. Compare your rate and service catalog against market bands ($125-$200/user for a standard stack in 2026), then judge SLA performance within that context.
Related Reading
- How to Switch MSPs: Migration Checklist
- MSP Contracts and SLAs: Red Flags and Typical Terms
- How to Evaluate an MSP: The 15-Point Vendor Selection Checklist
Sources
- CompTIA. "State of the Channel." 2025. https://www.comptia.org/content/research/comptia-state-of-the-channel
- Datto. "Global State of the MSP Report." 2024. https://www.datto.com/resources/global-state-of-the-msp-report/
- Sophos. "The State of Ransomware." 2025. https://www.sophos.com/en-us/content/state-of-ransomware
- CISA. "Protecting Against Cyber Threats to Managed Service Providers and their Customers (AA22-131A)." 2022. https://www.cisa.gov/news-events/cybersecurity-advisories/aa22-131a
- ChannelPro Network. "MSP Pricing Model Survey." 2026. https://www.channelpronetwork.com/2026/02/06/best-pricing-model/
— The MSP Directory Team