"It's not great, but switching would be a nightmare." It is the most common reason we hear for staying with an IT provider that is not working, and it is easy to understand. The current provider holds the passwords, knows where the server is, and is the only one who remembers why the printer works. Leaving feels like a leap into a week of downtime.
While that fear is reasonable, it is mostly built on what a bad handover looks like, not on what a planned one involves. Done in the right order, a switch is a few weeks of quiet preparation and a cutover your staff barely notice. Done in the wrong order, it is exactly the nightmare people picture. The difference is almost entirely sequencing.
Start with your current agreement
Before talking to anyone new, read three clauses in the agreement you already have.
The notice period. Most month-to-month agreements need thirty days of written notice. Some annual agreements renew automatically unless you give notice inside a window before the renewal date, and missing that window can lock you in for another year.
The exit terms. Look for an exit fee, a termination charge, or a clause requiring you to pay out the remaining term. Know the number before you plan the date.
Documentation and data. The agreement should say that your documentation, credentials and data are yours, and that the provider hands them over when the relationship ends. If it is silent, assume you will have to ask for everything specifically and in writing.
We went through these clauses in more detail in what is in a managed IT contract.
Collect what you own before you give notice
Unfortunately, the moment of giving notice is also the moment a provider's goodwill is lowest. Collect what you can first, quietly, while the relationship is still ordinary.
- Administrator access to Microsoft 365 or Google Workspace, in an account that belongs to the business, not to the provider.
- Your domain registrar login. Whoever controls the domain controls your email and website. If the domain is registered in the provider's name, that is the first thing to fix.
- Licence ownership. Find out whether your Microsoft licences were bought through the provider. Annual subscriptions under Microsoft's current licensing generally cannot be cancelled after the first few days, so a new provider may need to take them over rather than replace them.
- A list of every system someone logs into on the business's behalf: accounting software, the firewall, the backup service, the phone system, any vendor portals.
- Any documentation that exists. Network diagrams, passwords stored in a password manager, notes on how the server is set up. Ask for it plainly: "please send us the documentation for our environment."
The order a clean handover follows
Once the new provider is chosen and notice is given, the handover should run in roughly this order. The principle is simple. Nothing gets switched off until its replacement is already working.
- Inventory. The new provider documents everything that exists: devices, accounts, licences, network equipment, backups and the third-party systems from your list.
- Access. New administrator accounts are created for the incoming team, multi-factor authentication is confirmed on every admin account, and the outgoing provider's access is recorded so it can be removed later.
- Backups first. A new backup starts running and a restore is tested before anything else changes. If the handover goes wrong at any later step, this is what protects you.
- Security tools overlap. New endpoint protection and monitoring go onto each device before the old tools come off, so no machine is ever unprotected in between.
- Cutover. Remaining management tools are switched over, and the help desk number your staff call changes on a set date that everyone knows in advance.
- Close out. The outgoing provider's access is removed from every system on the list, their accounts are disabled, and shared passwords they knew are changed.
That last step is the one most often skipped. It matters for the same reason offboarding an employee matters: an account belonging to someone who no longer works for you is an unmonitored door. The same logic, applied to people, is in the offboarding checklist most small businesses skip.
How long it takes
For a business of ten to twenty people, two to four weeks from signing to cutover is typical. Most of that is preparation the staff never see. The visible part, the day the help desk number changes, is usually a non-event. If a new provider promises the whole thing in two days, ask what they are skipping.
When switching is the wrong call
With that being said, not every frustration justifies a move. If the problem is a single unresolved issue, a missed response time, or a technician who has left, raise it in writing first and see what changes. A provider who fixes a problem once it is clearly named may be worth keeping.
Switching makes sense when the problems are structural: response times that are never met, no written scope, documentation that does not exist, or a provider who cannot say who has administrator access to your systems. Those do not improve with a conversation. The twelve questions to ask an IT provider are a quick way to tell which kind of problem you have.
Our verdict
We don't doubt that switching providers takes effort. However, the disruption people fear comes from handovers done in a hurry and in the wrong order, not from switching itself. Collect what you own first, overlap the security and backups, and remove the old access last. Done that way, the riskiest part of the whole exercise is staying with a provider you have already stopped trusting.
We take on the handover from whoever runs things now as part of onboarding, and it is covered by the onboarding fee on our pricing page. Our response times and the credit when we miss one are quoted from the agreement on our commitments, so you can compare them before you decide anything.