Switching MSP providers requires a transition plan that maintains business continuity and minimizes downtime. We take a step-by-step approach that fixes the problems you’re having with your existing provider first so that we can build a solid working relationship from the start.
If you plan on an MSP transition, the guide below will help.
First, Be Sure Switching MSPs Is Actually the Right Move
A single bad ticket shouldn’t lead to searching for how to switch MSP companies. Operational problems that continue to happen well past the onboarding process call for a reliable switch to a team that better fits the needs of your company.
We never encourage you to switch companies without being sure that it’s the right move because there are:
Problems Worth Trying to Fix First
Before you change a managed service provider, be sure that the problems are not due to unclear expectations rather than a failed MSP.
Discuss the following:
- Slow response times for some requests. Ask if particular sorts of questions have been added to your service level agreement.
- Poor communication between personnel and technicians. Can you put in a clear escalation process to solve the issue?
- Reporting problems, such as late or sparse monthly reports, due to there being no clear deliverables previously established.
- Discrepancies in the scope of the service, where you assumed that the contract said one thing and not another.
Write each issue down. Once it’s on paper, the contract gives your MSP a measurable target, and a deadline for the fix shows exactly what you expect. That often solves the problem before you have to look for a new IT provider.
Signs the MSP Relationship Has Become a Business Risk
Certain problems with providers are harder to fix than others because of data ownership and control risks. Your partnership with an outgoing MSP has become a serious operational risk if:
- SLA response and resolution times are often missed with no plan in place to correct them.
- Patch management slips, which means high-risk vulnerabilities are not patched within 14 days.
- Backup failure reports go missing, and there’s no restore testing or disaster recovery plans in place.
- Cybersecurity monitoring is part of the core managed IT services offered, but you’re never given alerts, logs or reports.
- Administrative access to your systems remains a mystery, with no one willing to give you a straight answer.
- Staff turnover is high, causing a strain on your working relationship with the company.
End-of-life systems may remain in service with no ownership over who will replace them. If your MSP issues include two or more of the above points, it’s time to silently begin the offboarding process and service handover.
You don’t want to give your existing MSP notice that you’re switching just yet.
Before You Give Notice, Make Sure You Control Your Own IT
Switching MSP provider companies requires a strategic approach because you want to verify ownership and access to critical systems. Your team shouldn’t have to depend on the past provider for the incoming MSP handover.
Use our table below to assist with the transition. You can fill in the last two columns as you go along:
| System | What You Need | Who Controls It | Verified? |
| Microsoft 365 or Google Workspace | Two named internal global admins, a break-glass account stored offline, MFA recovery options, list of delegated MSP access | ||
| Domain registrar | Account in your company’s name, registrant contact details, auto-renew status, transfer lock setting | ||
| DNS hosting | Login to the DNS provider, full export of current records (A, MX, TXT, CNAME) | ||
| Firewall and network | Firewall credentials, saved configuration backup, VPN settings, ISP account and circuit details, network documentation | ||
| Backups | Console access, backup retention settings, encryption keys, date of last successful restore test | ||
| Endpoint management and RMM agent | List of managed devices, what the RMM agent controls, removal plan for the agent | ||
| Endpoint security and cybersecurity monitoring | Admin access to the security console, alert history, exclusions list | ||
| Cloud platforms (Azure, AWS, others) | Owner or billing role on each subscription, list of service principals and API keys | ||
| Software licenses and vendor accounts | License agreements in your company’s name, renewal dates, vendor support contacts for line-of-business apps | ||
| Password vault | Your own admin access to the shared vault, plus a record of who else has it | ||
| IT documentation | Asset inventory, network diagrams, runbooks, onboarding and offboarding checklists for staff |
Check Your Admin Accounts and Credentials
Start with accounts that may allow you to regain control of critical business services, such as administrator Microsoft 365 or Google Workspace accounts. Also, maintain DNS access or ask your current provider to transfer access to you.
Get an Inventory of Devices, Systems, Licenses, and Vendors
Create a device inventory for desktops, laptops, servers, mobile devices and any network equipment that you may have available. Add software licenses and subscription services to the list so that you have every vendor account the MSP manages accessible to you.
Verify Backups Before the Old Service Ends
Small business and enterprise IT managed services both rely on strict backup and restoration processes that are tested and maintained within the written retention period. Record all settings so that disaster recovery matches former settings after the transition period.
Read the MSP Contract Before You Pick a Transition Date
Switching MSP provider companies requires a post-transition review of the contract to look for:
- Notice period and termination clauses
- Auto-renewal terms with specific notice windows
- Early termination fees if cancelling before the end of the contract
- Data and document ownership of network diagrams, passwords, configuration records, etc.
- Cooperation agreements with transition overlap support and how exit assistance is billed
- Backup retention periods after terminating the contract
- Third-party license, software and security handling
Contractual items can affect the timing and cost of the switch. Work with your team to better understand how to handle the terms of the agreement.
Be sure to evaluate the company’s exit process so that you don’t have the same vendor-lock-in problems when signing a new contract.
How to Choose the Right MSP Before You Switch
Don’t choose a new MSP because they promise to fix all of the issues that you’re having with your former provider. You may have transition issues with a slow or uncooperative former company.
We recommend that you follow these recommendations on how to switch MSP companies.
Define What You Want the New MSP to Own
Start with a list of why you plan to switch a managed IT provider, including the systems and outcomes that you want to achieve. You might consider things such as parallel support, endpoint security, patch management and network monitoring.
Clearly define the boundaries you want in place to accept a new provider.
Compare SLAs, Security, Support, and Escalation
Response and resolution time are two terms that companies confuse when choosing a managed service provider. Providers may have a one-hour response time and still take a week to fix issues, which is never ideal.
Most issues should be resolved within one business day, and critical ones – within an hour.
Ask for an SLA that addresses the issue priority and the course of action in case of an SLA breach.
Check if they have ISO 27001 or SOC 2 certifications, which confirm the basic level of security during data processing and information security management procedures; ask about the typical time of a patch implementation and escalation procedures.
Ask How They Onboard — and How They Would Offboard You Later
A staged migration is a good start to your business relationship, but you want to know a few other details:
- How onboarding and offboarding work
- What accounts, documents and licenses you’ll need to provide
- Clauses for auto-renewal and early termination
Ask questions before you sign anything.
Verify Claims Instead of Taking the Proposal at Face Value
Compare the scope of the service and review SLAs, cybersecurity, support coverage, documentation ownership, exit terms, pricing, references and reporting. Ask the provider for testimonials and recommendations that you verify on your own.
Build an MSP Transition Plan Before Anyone Starts Changing Systems
Switching an MSP provider without downtime requires a transition plan with dates, ownership, responsibilities and a rollback plan in place. You don’t want a single-night approach on a Friday unless there’s a single cutover.
Keep the Old and New MSP Overlapping Where Possible
Parallel support to reduce the risk when switching MSPs. Overlap during a transition allows your outgoing provider to offer you support for live systems and makes the process less risky. But be cautious of the costs of keeping both contracts active.
Decide Who Owns Each System During the Handover
Choosing an MSP also includes outlining who owns each system when handing them over, such as a cutover plan that includes:
- Backups
- DNS
- Firewall and network
- Endpoint management
- Microsoft 365 administration
Tell Employees What Will Change — and What Will Not
Staged migrations allow your staff to know what to expect during the transition. You can alert them to potential outages for helpdesk requests, logins, authentication and other services. Allow your employees to prepare ahead of time.
Move Systems in Stages Instead of Changing Everything at Once
What should I look for when I switch MSP companies? The services you want with a defined transition period. You can look at what managed IT services include in your agreement on top of:
- Discovery and documentation
- Identity and access information
- Backup and disaster recovery
- Security and tooling
- Endpoint and patch management
- DNS
- Network and firewall
Your stages may vary, but they often include some or all of the points above.
What If the Current MSP Makes the Handover Difficult?
Switching MSP provider companies may come with delays. You might hear horror stories of dramatic lockouts, but these are rare in our experience. What normally transpires is incomplete documentation arrives, credentials are missing or requests sit unanswered.
Make the handover easy with:
- Requests in writing
- Lists of the exact artifacts you need
- Escalation channels
- Company-owned access
Maintain records of all correspondence to make the handover less difficult.
Don’t Remove the Old MSP Until the New One Can Prove Everything Works
To switch MSP providers, you must have a strategic process in place that includes a verification checklist of:
- Asset inventory, network documentation and software licenses
- Monitored and secured endpoints, patch management and RMM agent information
- Backup process information, retention periods and restoration tests
- Support and escalation information
- Access to all systems
Create a checklist to verify that everything works before dismissing your former MSP.
Budget for the Switch, Not Just the New Monthly MSP Fee
Switching to the new provider usually requires some one-time costs. You should consider and budget for this transition period, including the time when you are paying both companies simultaneously, the onboarding and implementation cost, necessary changes/remediation, and license conversion or other expenses you may incur in the process (e.g., hardware purchases to bring the environment up to date).
Request a detailed breakdown of all these one-time costs from your new provider.
Planning to Switch MSPs? Let Cyber Husky Map the Transition First
Don’t switch MSP providers without a plan in place. At Cyber Husky, we can take control of the transition to make it as hands-off as possible for your team.
Contact Cyber Husky to learn more.

