Switching MSPs is a significant undertaking, but staying with an underperforming provider is more costly long-term. This guide provides a step-by-step migration checklist and realistic timeline.
Phase 1: Planning (Weeks 1-2)
- Review current contract termination terms and notice requirements
- Document all systems, applications, and services currently managed
- Identify and secure all credentials, passwords, and admin access
- Select new MSP through evaluation process
- Sign new MSP contract with transition plan included
- Designate internal project lead for migration coordination
Phase 2: Discovery (Weeks 2-4)
New MSP conducts environment assessment:
- Network infrastructure documentation
- Server and workstation inventory
- Cloud services and licensing audit
- Security posture assessment
- Backup and DR evaluation
- User account and access review
Phase 3: Parallel Operation (Weeks 4-6)
Both MSPs have access during transition:
- New MSP deploys monitoring and management tools
- New MSP begins onboarding users to new helpdesk
- Old MSP maintains current services during overlap
- New MSP assumes responsibility system-by-system
- Testing of all critical systems under new management
Phase 4: Full Transition (Weeks 6-8)
- Old MSP access revoked (all credentials changed)
- New MSP assumes full responsibility
- Remaining systems migrated
- Documentation completed
- Staff training on new processes and helpdesk
Phase 5: Stabilization (Weeks 8-12)
- Address issues discovered during transition
- Optimize configurations
- Complete security hardening
- Finalize documentation
- Post-migration review meeting
Critical Migration Risks
- Credential lockout: Ensure you have all admin credentials BEFORE notifying current MSP of termination
- Data loss: Verify all backups are current and accessible before transition
- Downtime: The parallel operation period minimizes but doesn't eliminate downtime risk
- Knowledge gaps: Document institutional knowledge before the old MSP disengages
- Hostile transitions: Some MSPs make departures difficult — have legal counsel review your contract
Frequently Asked Questions
How long does an MSP migration take?
30-90 days from contract signing to full transition. Complex environments (multi-site, hybrid cloud, compliance requirements) take longer.
What if my current MSP won't cooperate?
If your MSP refuses to provide credentials or documentation, consult legal counsel. Your contract should specify data ownership and transition obligations. In extreme cases, the new MSP can recover most access through vendor resets.
Will there be downtime during the switch?
Minimal if properly planned. The parallel operation period (2-4 weeks) ensures continuity. Brief maintenance windows may be needed for tool migrations, typically scheduled after hours.
How much does switching MSPs cost?
New MSP onboarding fees range from $5,000-$25,000. You may also have early termination fees from your current contract. Factor in staff time for coordination.
Can I switch MSPs without my current provider knowing?
Practically, no. Your new MSP will need to deploy tools alongside existing ones during the parallel period. Professional courtesy also suggests providing your current MSP with contractual notice.
The Bottom Line
Switching MSPs requires planning but should not be avoided out of fear of disruption. A well-executed 60-90 day transition plan minimizes risk while setting you up with a better IT partner.
For more, see our MSP onboarding guide and evaluation framework.
-- The MSP Finder Team