To switch MSPs safely, secure company-owned admin access and copies of your backups first, read the exit terms in your contract, then run the old and new providers side by side until the new one has proven it can support you. The biggest risk in a switch is not the new provider. It is discovering, after the old one leaves, that it held the only keys to your domain, your Microsoft 365 tenant, your firewall, or your backups.
Most switches go wrong in the same places, so they are easy to plan for. This guide covers the order to do things in, what to collect, and how to cut over without a gap in support. If you are moving IT in-house rather than to another provider, use our MSP transition checklist instead.
Key takeaways
- Secure ownership before you give notice: domain registrar, DNS, Microsoft 365 or Google Workspace admin, firewall, and backups.
- Read the contract for notice periods, auto-renewal, termination terms, and what offboarding help the provider owes you.
- Plan an overlap of a few weeks, with the new provider onboarding while the old one still answers tickets.
- After cutover, remove every trace of the old provider's access: admin accounts, delegated access, remote tools, and connected apps.
- A good outgoing provider makes this easy. A difficult one is the best argument that you made the right call.
Is it time to switch?
Common reasons businesses change IT providers:
- The same problems keep coming back and nobody fixes the cause.
- Response times have slipped, or you can never reach the same person twice.
- Security incidents happen and the provider cannot explain why.
- You get no clear reporting on what is being done or what is at risk.
- The provider has not kept up with your growth, new locations, or compliance needs.
If the problem is a gap rather than the whole relationship, such as security, you may not need to switch everything. Some businesses keep their MSP for daily support and bring in a second company for cybersecurity, as long as the responsibilities are written down and do not overlap.
Step 1: Read your contract
Find the agreement and look for:
- Term and auto-renewal. When the contract ends and whether it renews automatically.
- Notice period. How much notice you must give, and how.
- Termination terms. Any fees or conditions for ending early.
- Offboarding obligations. What the provider must hand over, and whether transition help is included or billed.
- Ownership. Who owns licenses, hardware, software, and documentation the provider bought or created for you.
Step 2: Secure ownership before you give notice
Do this quietly, and before any conversation about leaving. Confirm that someone at your company can sign in to each of these with their own account:
- Domain registrar and DNS. If the provider registered your domain in its own account, transfer it.
- Microsoft 365 or Google Workspace. At least one company-controlled global administrator, protected with MFA. Note how licenses are billed; if they come through the provider, plan the license transfer.
- Firewall, Wi-Fi, and switches. Admin credentials and current configuration backups.
- Backups. Where they are stored, under whose account, and how you would get a copy if the provider's system were switched off.
- Line-of-business software and vendor portals. Admin access for your accounting, practice management, phone, and internet accounts.
- Password vault. If credentials live in the provider's vault, get a secure export.
If you find little or no documentation at all, follow our 90-day plan for an inherited IT setup.
Step 3: Choose the new provider
Pick the next provider before you leave the current one. Our guide on how to choose an MSP has a 12-point checklist. Ask each candidate to describe its onboarding process in detail, including what it needs from you and from the outgoing provider. A provider that cannot explain onboarding clearly will not handle it well.
Step 4: Plan the overlap
Give notice so that the old provider's last day comes a few weeks after the new provider starts. During the overlap:
- The new provider documents your environment, installs its tools, and learns how your business works.
- The old provider keeps answering tickets and completes the handoff.
- You agree on a cutover date when support officially moves.
Step 5: Run the handoff
Ask the outgoing provider for documentation, network diagrams, asset lists, open tickets, recurring problems, vendor contacts, license details, and anything scheduled to renew. Our MSP transition checklist lists every item to request. Test the important pieces before cutover: sign in as administrator to each system, restore a file from backup, and confirm you can reach every vendor.
Step 6: Cut over and clean up
On cutover day, employees start calling the new provider. Then remove the old provider's access completely:
- Disable or delete its admin accounts in Microsoft 365 or Google Workspace, and remove any delegated admin relationships.
- Uninstall its remote management and monitoring agents from every device.
- Review and remove apps connected to your tenant that belonged to the old provider.
- Change shared passwords, firewall credentials, and service account passwords it knew.
- Update vendor contacts so carriers and software companies stop calling the old provider.
Unused vendor connections are a real risk. The ConnectWise SkyKick breach showed how a provider's app access into Microsoft 365 can be abused, so do not leave old access in place "just in case."
What a good handoff looks like
We supported a 35-person North Jersey medical lab for three years, rebuilding its network from a consumer-grade "server" into a properly managed environment. When the company was acquired, the contract ended, and we treated the exit as a final project: credentials, network documentation, hardware inventory, and configurations, all handed to the acquiring company's internal IT team. They called it one of the easiest IT transitions they had done. Read the medical lab case study. That is the standard to expect from an outgoing provider, and from the next one when your turn comes.
How Spot On Tech can help
When we take over from another provider, we run the onboarding, coordinate the handoff with the outgoing MSP, secure company-owned access, and keep the overlap orderly. If you are considering moving some IT in-house instead, Compass covers that transition. We support businesses across New York and New Jersey. Talk to us before you give notice, and we will help you plan the order.
Frequently asked questions
How do I switch IT providers?
Read your contract's exit terms, secure company-owned admin access and backup copies, choose the new provider, give notice so the two overlap for a few weeks, run a documented handoff, and remove all of the old provider's access after cutover.
How long does it take to switch MSPs?
Plan on the notice period in your contract plus a few weeks of overlap for onboarding. Larger or poorly documented environments take longer, which is why securing access and documentation early matters.
What if my MSP will not hand over passwords or documentation?
Check what your contract requires, then put the request in writing. Many accounts, such as Microsoft 365 and your domain, can be recovered through the vendor with proof of ownership. This is why securing access before giving notice is the first step.
Can we keep our current MSP and use another company for cybersecurity?
Yes. Some businesses keep their MSP for daily support and hire a separate security provider. It works when each company's responsibilities, tools, and escalation paths are written down so nothing overlaps or falls between them.
Should we tell our MSP we are leaving before we have a new provider?
Usually not. Secure your access and choose the new provider first, then give notice so the two can overlap.
