How to Switch IT Providers Without a Bad Month
A 30-day transition plan for changing managed service providers, including the credentials to secure first and the bargaining power you lose after you give notice.
The short answer
Most of a successful IT provider switch happens before notice is given: confirming you own your domain, DNS, tenant, licenses, backup data, and phone numbers, obtaining current documentation, reading the contract, and creating a break-glass admin account you control. The transition itself runs about 30 days in four stages.
Most businesses stay with an IT provider they have lost confidence in for six to eighteen months past the decision point. The reason is almost never loyalty. It is that switching feels dangerous, nobody knows what is involved, and the current provider holds everything.
The danger is real and it is manageable. The sequence below is what we use, and most of it happens before anyone gives notice.
Before you give notice
This phase determines whether the transition is smooth or ugly, and it is the phase companies skip.
Confirm what you own. Domain registration, DNS, Microsoft or Google tenant, line of business software licenses, backup data, and your phone numbers. Each one should be registered to your company with a company email as the administrative contact.
If any of these are registered to your provider, that is your first task and it is much easier to fix while the relationship is friendly. A domain registered to a former provider is the single most disruptive thing to recover, and there are firms in this market who will not respond quickly to that request after termination.
Get your documentation. Ask for the current network diagram, asset inventory, license list, and vendor account list as part of a normal review. A good provider hands it over without comment. A provider who hesitates has just told you something important, and you now know to plan for a harder exit.
Read the contract. Term, renewal date, notice period, auto-renewal language, and any offboarding provision. Note the date by which notice must be given, and note whether offboarding assistance is included or billable.
Secure the crown jewels. Ensure you have, in your own possession, administrative access to your identity platform, your domain registrar, and your DNS. Not shared with the provider, yours. A break-glass admin account in your own tenant with credentials in a safe is standard practice and it should exist regardless of whether you are switching.
Selecting the replacement
Run the 3AM Test audit on candidates and on your incumbent, so you are comparing rather than reacting. A provider that scores 20 points better on paper may still be the wrong fit if they have no experience with your industry's core application.
Three questions worth asking every candidate. Describe your onboarding process for a company our size, with a timeline. What have you learned from a transition that went badly. What would you need from our current provider, and what do you do if they do not cooperate.
That last answer separates the experienced from the optimistic. Uncooperative transitions are common and a good provider has a playbook for them.
The 30-day transition
Week one, discovery and access. The new provider documents the environment independently rather than trusting the handover. They deploy their monitoring and management agents alongside the incumbent's, which is safe, and they begin building their own documentation.
Week two, parallel operations. Both providers have visibility. The new one is learning, the old one is still responsible. Any gaps in the documentation surface here, while there is still someone to ask.
Week three, cutover. Support routing moves to the new provider. Announce it to staff clearly, with the new phone number and email, more than once. Credentials are rotated systematically: administrative accounts, service accounts, network device passwords, wifi keys, and anything the outgoing provider's technicians could reach. This is a security requirement and not a comment on anyone's character.
Week four, cleanup and verification. Remove the outgoing provider's tools, agents, remote access software, and accounts. Verify with an independent scan that nothing was left behind. Confirm backups are running under the new configuration and test a restore. Confirm every vendor relationship has been transferred or documented.
The things that go wrong
Backup gaps at cutover. If the old backup stops before the new one is verified, there is a window with no protection. Overlap them deliberately and pay for the extra month.
Orphaned remote access. Old tools left installed and phoning home. Audit for this explicitly.
License ownership. Licenses purchased through the provider's agreement may not transfer, and may need to be repurchased. Find this out in week one, not on the last day.
Institutional knowledge. The undocumented workaround for the quirky application everyone depends on. Ask the outgoing team directly, politely, and early. Most technicians will tell you, because most technicians are professionals who like their work.
On the relationship
Leave well. Give the notice the contract requires, pay the final invoice, and say what did not work without theatrics. Phoenix's business community is smaller than it looks, you may want a reference from them someday, and an outgoing provider treated decently is far more likely to answer the phone in week three when you need the one password nobody wrote down.
Get the plan
The MSP Transition Plan is a week-by-week workbook with the pre-notice ownership audit, the contract review checklist, the candidate evaluation scorecard, the full 30-day task list with owners, the credential rotation register, and a post-transition verification checklist.
Run the ownership audit even if you have no intention of leaving. Knowing you could is worth having.
Frequently asked questions
What should I do before firing my IT provider?
Confirm you own your domain registration, DNS, Microsoft or Google tenant, line of business licenses, backup data, and phone numbers, with your staff as administrative contact. Get current documentation as part of a normal review. Read the contract for notice period. All of this is far easier while the relationship is still friendly.
How long does switching IT providers take?
About 30 days for the transition itself, plus the preparation before notice. Week one is discovery and access, week two is parallel operations with both providers visible, week three is cutover and credential rotation, and week four is cleanup and verification.
Should I rotate passwords when changing IT providers?
Yes, systematically: administrative accounts, service accounts, network device passwords, wifi keys, API keys, and anything the outgoing provider's technicians could reach. This is a standard security requirement and not a comment on anyone's character.
What goes wrong most often during an MSP transition?
Backup gaps at cutover when the old backup stops before the new one is verified, orphaned remote access tools left installed and phoning home, license ownership discovered on the last day, and undocumented workarounds for the quirky application everyone depends on.
Related reading
- Score Your IT Provider: The 40-Point 3AM Test Audit
- Your Backups Are Not a Recovery Plan
- Run a 60-Minute Ransomware Drill With Your Leadership Team
- Build an IT Budget From Operating Priorities
- Read Your Cyber Policy Before You Need to Use It
- The Quarterly Technology Review Every Owner Should Demand
Keep the transition factual
Provider changes can become emotional. I prefer a written inventory, named owners, dated handoffs, and a daily issue log. That keeps the outgoing provider, incoming team, and client focused on the same evidence.
The goal is continuity. Save the postmortem for after access, backups, vendors, and support are stable.