You already know it's time: the tickets sit for days, the invoice is a mystery, and you've started fixing the printer yourself. What usually stops people from switching IT providers isn't loyalty but the worry that leaving will break something, and that you'll be the one explaining it. The good news is that a planned switch is mostly a paperwork and sequencing job, and most of the technical work belongs to the incoming provider. This checklist is for the owner, CFO or office manager who owns the decision.
Key takeaways
- Write down why you're leaving before you give notice. That list becomes the test your new provider has to pass.
- Your organization should own every important account. Your IT provider should be a guest in them, not the landlord.
- Plan a short overlap where both providers know exactly who handles what, and on which date.
- Close the old provider's access on purpose. It's the easiest step to forget.
Before day one: three things only you can do
An incoming provider can handle the technical handover. These three jobs can't be delegated to them, and they take an afternoon, not a month.
Write down why you're leaving
Be specific. "Bad service" won't help anyone. "Password resets take two days" will. So will "we found out about the email outage from a client" or "nobody has given us a plan for the laptops that are five years old."
Keep it to three to five items. You'll hand this list to the new provider during the first conversation, and you'll check it again in week four. It also keeps the switch honest: if the problem is really an internal gap, such as nobody owning IT decisions on your side, a new provider alone won't fix it.
Read the contract for the exit terms
Find three things: the notice period, the end date, and what the agreement says the provider owes you when you leave (documentation, help with the handover, return of equipment). If any of it is unclear, bring in whoever signs your contracts before you say anything to the current provider.
Name one internal owner
Choose the person who will hold the checklist and give the final sign-off. What matters is authority, not technical skill: they need to be able to say "yes, that's done" and have everyone accept it.
Week 1: make sure you own your own accounts
This is the part of switching IT providers that matters most, and it's simpler than it sounds. For each item below, the question is: is this account registered to us, and can someone on our staff log in as an administrator?
- Your domain name (the "yourcompany.com" part of your email and website), held at a domain registrar.
- Microsoft 365 or Google Workspace, where your email, files and user accounts live.
- Your firewall and internet service, the box and the contract that connect the office to the outside world.
- Your backup service, and where the backups are actually stored.
- Software subscriptions and licenses, including who is billed for them.
- Hardware warranties, especially for laptops and servers.
Start with the domain. ICANN, which oversees domain names, sets out the rights and responsibilities of the registrant, the person or organization the domain is registered to. Make sure that's you.
You'll often find that an account was set up years ago under the provider's name or a former employee's email. That's common and fixable. Note it, and ask the incoming provider to plan the transfer rather than doing it in a hurry.
Microsoft 365 has one extra wrinkle worth knowing. IT providers can be connected to your account as a "partner" with administrator rights, and Microsoft lists these on a Partner relationships page in the admin center. Take a look now so there are no surprises later.
Week 2: collect what the old provider knows
Your current provider carries knowledge about your setup that may not be written anywhere else. Ask for it in writing, with a date it's due:
- A list of every device they manage: computers, servers, printers, network equipment.
- Network diagrams and configuration notes.
- Contacts for your other vendors: internet service, phone system, copier lease, line-of-business software.
- Open tickets and known problems, so the new team doesn't rediscover them the hard way.
- Backup details, and the date of the last successful test restore.
Credentials deserve their own plan. Agree in writing how admin passwords and recovery codes will be handed over (a shared password manager is one good option; an email attachment is not), and who on your side will hold a copy.
A professional handover is part of doing the job well, even on the way out. If something stalls, go back to what the contract says and keep the request polite and written.
Week 3: the overlap and the cutover
The overlap is the short stretch when both providers are involved. It's where switches go wrong, usually because each side assumes the other is covering something. Agree on a few dates in writing:
- The day staff start calling the new help desk instead of the old one.
- The day the new provider's monitoring and security tools go on your computers, and the old ones come off.
- The day backups move to the new arrangement, and the day someone confirms a test restore actually worked.
- The day the old provider's access ends, including a change of any shared admin passwords they knew.
That last one is easy to skip because nothing visibly breaks when you forget it. A 2022 joint advisory from CISA and allied cybersecurity agencies tells customers to disable provider accounts once the provider is no longer managing their systems, and notes this "can be overlooked when a contract terminates". Ask the new provider to remove the old one's admin accounts, remote access tools and Microsoft partner roles, change the shared admin passwords and recovery details the old team knew, and tell you in writing when it's done. Changing those passwords can affect connected systems, so it should be planned, not rushed.
If you're also moving email or files to a new platform during the switch, treat that as its own project with its own date. Combining a provider change with a Microsoft 365 or cloud migration is possible, but it's two jobs, not one.
Week 4: test the new provider against your list
Take out the list from before day one. For each item, ask a plain question: has this changed? If password resets were the problem, submit one and time it. If nobody had a plan for aging laptops, ask to see a draft.
It's fair to expect a few things from any good provider by the end of the first month:
- An accurate inventory of your devices, accounts and licenses.
- Confirmation that backups ran and that a restore was tested.
- A short list of what they found that worries them, ranked, with a plain explanation of each. A security review of what you inherited belongs here.
- A date for the first proper planning conversation.
Then the internal owner signs off, and the switch is done.
Telling your staff
Your team doesn't need the whole plan. They need three facts: who to call starting on what date, what (if anything) will look different on their computer, and who to ask if something feels off. Send it a few days before the help desk changes and again on the morning it does.
Picture a 40-person office where that note never goes out. On Monday, half the staff email the old provider, the other half email the office manager, and nobody emails the new help desk. A two-paragraph note prevents all of it.
Common questions
How long does it take to switch IT providers?
For a small or mid-sized office with a cooperative outgoing provider, about a month of active work is a reasonable plan. Your notice period may stretch the calendar, and a platform migration adds time of its own.
Should I talk to the new provider before giving notice?
Yes. Bring them in early so they can review what you own, help sequence the handover, and line up the overlap with your contract dates. Give notice once you know the start date.
What if we have our own IT person?
Then the switch looks different, because some of the knowledge already sits in-house. A co-managed arrangement, where your IT person and an outside team split the work, may suit you better than a full replacement. Our guide to when co-managed IT makes sense walks through the split.
The relief is in the order of things
Switching IT providers feels risky mostly because it's unfamiliar. Done in order (your reasons, your accounts, their knowledge, a clean cutover, then a test), it's a month of steady work rather than a leap. If you'd like a second set of eyes on your list before you give notice, read about our managed IT services or talk it through with us.