Most businesses put off switching IT support provider for far longer than they should. The reason is nearly always the same: a fear that the move will cause disruption, downtime, or some kind of mess that turns out to be worse than the problem they were trying to fix.
In practice, a well-managed handover is much less dramatic than most people expect. This guide explains what actually happens, how long it takes, and how to avoid the few things that genuinely can go wrong.
Contents:
Before you start: what to have in place
The transition runs more smoothly when a few things are lined up before you tell your old provider you are leaving.
- A signed contract or written agreement with your new provider
- A confirmed changeover date
- Any existing IT documentation you hold: network diagrams, asset lists, passwords
- A list of key suppliers: broadband, phones, software vendors, cloud platforms
If you do not have documentation, that is fine. A good incoming provider will build it as part of the onboarding process. It just takes a little longer.
Telling your existing provider
Once your new arrangement is in place, you need to give formal notice to your current provider in line with your contract. Check the notice period before you write the email, and check whether the contract requires written notice in a specific form.
Keep the message professional and brief. There is no need to explain your reasons in detail, and there is nothing to be gained from confrontation. The transition is smoother when both sides act sensibly.
A typical notice email confirms the end date, asks for an offboarding plan, and requests the handover information your new provider will need. Most reputable providers cooperate, even when they are losing the account.
The handover process
With both providers aware of the date, the actual handover typically runs over two to four weeks. The exact length depends on the complexity of your setup. A typical sequence looks like this.
Week 1: Discovery and documentation. Your incoming provider audits your existing systems: hardware, software, cloud platforms, user accounts, and security setup. They document what they find and flag anything out of date or risky.
Week 2: Access transfer. Administrator access is moved from the old provider to the new one. This covers Microsoft 365 or Google Workspace, your domain registrar, firewall, cloud platforms, and any third-party services. It is done in a controlled order so nothing is left unmanaged at any point.
Week 3: Tools and monitoring. Your new provider installs their monitoring software, endpoint security, and remote support tools on your devices. This usually runs in the background without interrupting staff.
Week 4: Final cutover. The old provider’s tools are removed, helpdesk contact details are updated, and your team is briefed on how to log issues with the new provider. After this date, all support goes through the new team.
What about downtime?
In most cases, switching IT support provider causes no downtime at all. The work is administrative rather than technical: it is about who has access to your systems, not about changing the systems themselves.
The exceptions are rare and planned. If your new provider recommends moving to a different backup system, replacing an ageing firewall, or migrating off an old server, those changes will involve a short out-of-hours window. Anything significant will be scheduled, agreed in advance, and timed to avoid your busy periods.
Common problems and how to avoid them
An uncooperative outgoing provider. Most providers behave professionally during a handover, but some drag their feet or withhold information. The defence is to have everything possible in writing, and to make sure your new provider is building their own documentation from day one. If they have to reconstruct everything from scratch, the transition still works.
Missing passwords or access. If your old provider holds administrator access to a service and refuses to hand it over, there are usually direct routes to recover control through the vendor. This is more common than expected and rarely a serious problem.
Surprise contract clauses. Some contracts include exit fees, data retrieval charges, or notice periods longer than the standard 30 days. Read your contract before committing to a date.
Staff confusion. If your team are not told how to contact the new provider, they will keep calling the old one. A short email or team meeting on the cutover day prevents this.
What your new provider should be doing
A capable incoming provider will lead the transition. You should not need to chase them for an onboarding plan or worry about whether the right steps are being taken.
Look for these signs that the handover is being handled properly:
- A named project lead at the new provider
- A written onboarding plan with dates and milestones
- Regular updates during the transition, not just at the start and end
- A documentation pack at the end, summarising your setup as it now stands
- A formal introduction to the helpdesk team your staff will be contacting
If you are not seeing these things, push for them. A provider who is disorganised at the start is unlikely to improve once the contract is signed. For help preparing the right questions before you commit, see our guide on what questions to ask an IT support company.
Local handovers and what they offer
Working with a local provider during a transition has practical advantages. An engineer can be on-site quickly if anything needs hands-on attention, and face-to-face meetings are easier to arrange. Focus Technology Solutions runs a structured onboarding process called Safe Launch, which is designed to get new clients fully operational within two weeks with no disruption to their day-to-day work. Our IT support services in Wigan are built around exactly that kind of reliable, straightforward transition.
Summary
Switching IT support provider is far less disruptive than most businesses expect. A typical handover takes two to four weeks, runs largely in the background, and rarely causes any downtime. The work is mostly administrative.
The things that can cause friction are all manageable with preparation. The bigger risk is staying with a provider who is not doing their job, out of fear of the change itself.
FAQs
How long does it take to switch IT support provider?
Most transitions run between two and four weeks from the signed contract to the final cutover. Simpler setups with mostly cloud-based systems can be quicker. Businesses with on-site servers, multiple offices, or specialist software tend to be at the longer end of that range.
Will switching IT support cause downtime for my business?
In most cases, no. The handover is administrative and runs in the background without affecting your systems. The only exception is if your new provider recommends significant infrastructure changes during the transition, in which case any work will be scheduled outside business hours and agreed with you in advance.
What information do I need to hand over when changing provider?
Anything useful you already hold: IT documentation, asset lists, network diagrams, a list of your key software platforms and suppliers. If you do not have these, your new provider will build them during onboarding. You do not need to do extensive preparation yourself.
What if my old IT provider is unhelpful during the transition?
It does happen, though most providers behave professionally. If your outgoing provider drags their feet or withholds access, your new provider can usually work around it by auditing your systems directly and recovering administrator access through the relevant vendors. The transition takes a little longer but it still completes.
How do I make sure nothing is missed when switching over?
Ask your new provider for a written onboarding plan with clear milestones and a documentation pack at the end of the process. A competent provider will lead this without being chased. If you find yourself following up repeatedly during the handover, that is a useful signal about the service you can expect once you are on contract.