How to switch IT support provider without the horror stories

The most common reason businesses stay with an IT provider they are unhappy with is not the contract. It is fear: fear of downtime during the handover, fear of what the outgoing provider might do, fear of discovering the new provider is no better. That fear is worth taking seriously, because it is doing real work in the market. It is the reason mediocre providers keep clients for years.

We onboard businesses from other providers regularly, so we see both sides of every switch: what the leaving process looks like when it is done properly, and what turns up when it has not been. This article is the honest version of both.

First, find out whether you are a customer or a hostage

Before you think about switching, ask your current provider four questions. The answers tell you how much freedom you actually have, and you want to know that before you need it, not after.

Who owns your Microsoft 365 or Google Workspace tenancy and licences? The licences should be in your organisation's name, or transferable to you on demand. If your provider has bought them in their own name and "manages them for you", moving providers means migrating your entire environment rather than simply changing who administers it. That difference is weeks of work and it is not an accident.

Who is the registrant of your domain names? Your website and your email both hang off your domain. It should be registered to your business. It is remarkable how often it turns out to be registered to a provider, or to an employee of a provider who left years ago.

Do you have your own admin access? You do not need to use it day to day, but a global administrator account belonging to your organisation, credentials held by you, is the difference between a provider you employ and a provider you depend on. Any provider who resists this has told you something important.

Where is your documentation? Network diagrams, asset lists, passwords, licence records, renewal dates. If the answer is "in the provider's systems" with no copy you can access, your organisation's operational knowledge is an asset on someone else's balance sheet.

If you got four good answers, switching is straightforward whenever you want it. If you got bad answers, do not panic and do not serve notice yet: the right move is to quietly fix ownership first, and any decent incoming provider will help you sequence that.

What a proper switch actually looks like

A competent onboarding is a project with a plan, not a leap of faith, and it runs in phases. Discovery first: the incoming provider audits what you actually have, which is frequently different from what anyone believed, and documents it. Then ownership and access: licences, domains, admin credentials and backups confirmed as yours or transferred to you. Then a period of parallel running around the cutover date, where the new provider takes over monitoring, support and management while the environment itself stays exactly as it was. The golden rule of a good switch is that nothing about your technology needs to change on day one. Change the provider first; improve the technology afterwards, deliberately, once the new provider knows your environment. Any incoming provider proposing to rebuild everything during the handover is creating risk to invoice against.

Done this way, the downtime a switch causes is somewhere between minimal and none, because nothing is being rebuilt. What users notice is a new number to ring.

Our COO Darren Sunley, who runs these transitions, sees the fear from the other side of it: "Clients do worry about how streamlined a handover will be, and some choose to stick with their current provider even though they know the service is not great. Our approach is simple. We have done exactly this for hundreds of clients over two decades, we have seen it all, and we handle the full transition for you. One guarantee: we will sort it."

The contract check before you serve notice

Read your current agreement before you signal anything, and look for four things. The notice period and how it interacts with the renewal date, because many agreements renew automatically for a year and require notice a set period before renewal, so missing the window by a week can cost you twelve months. Any exit or offboarding fees, and what they actually buy. What the contract says the provider must hand over at exit, because silence here is where disputes live. And who owns anything the provider built or configured for you.

To be clear, notice periods themselves are not a trap: ours has them too, because a proper offboarding takes work and both sides need time to do it well. The trap is the combination of a long automatic renewal with a narrow notice window and no defined exit obligations. That structure is designed to make leaving expensive, and it tells you the provider expects clients to want to.

What you should never hear

There are things an outgoing provider may legitimately do: invoice for genuine offboarding work, hold you to a contractual notice period, decline to support systems after the exit date. And there are things that should set off alarms regardless of the contract: withholding admin passwords or refusing to transfer domains until disputed invoices are settled, refusing to export your data or documentation, or making the environment mysteriously worse in the final weeks. Your passwords, your data and your domains are yours. A provider using them as leverage is not negotiating, and if it happens, put everything in writing, involve your solicitor early, and know that the incoming provider can often work around more than the incumbent expects.

The better test happens earlier, though. Watch how a prospective provider talks about the exit before you have signed: ask them directly what happens if you ever want to leave them. A confident provider describes their offboarding process. An evasive one has just answered a different, more useful question. We publish our own answer plainly: everything named in this article as yours, is yours, documented and handed over, because a client who stays out of fear is not a client, they are a liability waiting to review us.

The switch, in order

The sequence that works: check your contract dates quietly. Ask the four ownership questions and fix any bad answers. Choose the incoming provider and let them plan the transition with you, including the timing of notice, because serving notice is a step in the plan, not the start of it. Run discovery and documentation before cutover. Cut over with parallel support in place, change nothing on day one, and schedule the improvements for the months after, when they can be done deliberately and securely rather than in a scramble.

If you are somewhere in that sequence now, even at the "quietly wondering" stage, talk to us. The first conversation is a confidential look at your contract position and your ownership answers, and you will leave it knowing exactly how movable you are, whatever you decide to do next.

Frequently asked questions

How long does switching IT provider take?

For an environment where the client owns its licences, domains and admin access, a well-run switch typically completes within the contractual notice period, with discovery and documentation running in parallel before cutover. Where ownership needs untangling first, add time for that, which is one reason to check ownership before you need it.

Will switching IT provider cause downtime?

It should not. A proper switch changes who supports and manages your systems, not the systems themselves, so users experience a new contact route rather than an outage. Downtime during handover is usually a sign the incoming provider is rebuilding during the switch, which is the wrong order.

Can my old IT provider withhold passwords or my domain?

Your admin credentials, data and domain registrations belong to your organisation, and withholding them as leverage in a commercial dispute is a serious red flag that should go straight to written correspondence and, if needed, legal advice. A provider can hold you to notice periods and invoice for genuine exit work; holding your access hostage is a different thing entirely.

When should I tell my current provider I am leaving?

After you have checked your contract's notice and renewal dates, confirmed what you own, and agreed a transition plan with the incoming provider. Serving notice is a scheduled step in the switch, not the first move.