Guide
How to switch IT support providers without downtime
Switching IT support provider takes about four weeks and, done properly, produces no downtime at all. The work is almost entirely administrative: gathering credentials, documenting what exists, transferring monitoring and backup, and confirming the new arrangement works before the old one stops. The technical risk is low. The risk that stops people is the fear of a difficult handover, and that is manageable too.
By James 11 min read
Why most businesses stay too long
Very few businesses leave an IT provider because of one catastrophe. They leave after eighteen months of small things: response times that drifted, a call-out charge that made them stop asking, a project that never quite finished, and the growing sense that nobody there knows their setup any more.
And then they stay anyway, because the switch feels risky. The provider holds the passwords, the monitoring, the backups and the knowledge, and the prospect of unpicking that while continuing to trade is genuinely off-putting.
It is worth naming that this inertia is priced in. A provider who knows leaving is difficult has less reason to be good. The actual switch is far less dramatic than it feels from the inside, and knowing the sequence removes most of the fear.
What actually has to move
Six things, and only six. Administrative access to your Microsoft 365 or Google tenant. Administrative access to servers, network equipment and any line-of-business systems. The monitoring and management agent on each machine. The endpoint protection product. The backup arrangement. And the documentation, such as it is.
Everything else: your data, your email, your files, your applications, stays exactly where it is and is not touched. That is the single most reassuring fact about switching, and it is the one nobody explains: this is a change of who holds the keys, not a migration.
The two items with genuine sequencing risk are endpoint protection and backup, because you must never be without either, even for an afternoon. Both are handled by running the new alongside the old for a period and only removing the old once the new is verified.
Free, before any money changes hands
Want this looked at properly, for nothing?
Ninety minutes mapping how the work actually flows, then a written plan and a fixed quote you keep either way. A working session, not a sales meeting.
- No obligation, no follow-up sequence
- You keep the plan and the quote
or call 01623 354250
The four-week sequence
-
Step 1
Week 1, audit and document
The new provider audits what you actually have: machines, servers, licences, network kit, accounts, backup arrangements, and every system with a login. Nothing is changed. You get a written picture, which for most businesses is the first one they have ever had.
-
Step 2
Week 2, parallel running
New monitoring and endpoint protection are deployed alongside the existing tools, and a new backup runs in parallel with the old. Nothing is removed. If anything is going to conflict, this is when it surfaces, with the old arrangement still fully in place.
-
Step 3
Week 3, verification and notice
A test restore is performed from the new backup. Administrative access is confirmed by using it, not by being told it works. Once both check out, notice goes to the incumbent: deliberately after verification, not before.
-
Step 4
Week 4, cutover and cleanup
Old agents and old protection are removed, the incumbent’s access is revoked, and the final handover items are collected. The helpdesk number changes and your staff are told once, clearly.
What to gather before you start
Most of this you are entitled to. Ask for it in writing, and ask early. The request itself tells you a lot about how the exit will go.
- Global administrator credentials for Microsoft 365 or Google Workspace
- Domain registrar login, or confirmation of where the domain is registered and who controls it
- DNS hosting access, including a current export of all records
- Local administrator credentials for servers and workstations
- Router, firewall and switch access, plus the broadband account details
- Backup platform access, current retention settings and the location of the offsite copy
- Licence keys and vendor account details for line-of-business software
- The asset register, network documentation and any runbooks that exist
- A list of any services the provider resells to you, so those can be transferred rather than cancelled
What this looks like with us
Everything above is written to be useful whoever you move to, which is the point of it. If the provider you are considering is us, the same four weeks apply and the division of labour is worth knowing in advance: we run the audit, deploy alongside, verify the restore and confirm access, and you give notice once that is done rather than before.
What we do, what you do, and what the overlap costs at each notice period is set out under switching your IT support to SetWeb.
We do the audit before you commit
The free review covers this: what you have, what state it is in, what the risks are, and what switching would actually involve. You keep the written findings whether you move to us or not, and several businesses have used them to get a better deal from their existing provider, which is a perfectly good outcome.
When the incumbent will not cooperate
Most handovers are professional. A minority are not, and it is worth knowing that an uncooperative incumbent slows a switch down without being able to stop it.
If administrative credentials are withheld, Microsoft and Google both have documented processes for a domain owner to recover control of a tenant. If DNS is held hostage, control follows the domain registration, and the registrar will act for the registrant. If the domain itself is registered in the provider’s name rather than yours, which happens more often than it should, that is a harder conversation, and it is a good reason to check the WHOIS record today rather than during a dispute.
Two practical protections. Do not give notice until the new provider has verified access to everything that matters, which is why notice sits in week three rather than week one. And do not withhold a final payment as leverage; it converts an administrative process into a commercial dispute and slows everything down.
Where a provider genuinely refuses to hand over data they hold about your business, that engages your rights under UK GDPR, and pointing that out in writing usually resolves it faster than anything else.
Timing the switch
Avoid your busiest period, obviously, but do not wait for a quiet one that never arrives. For an accountancy practice that means not January; for retail, not the run-up to Christmas; for a school-adjacent business, not September.
Beyond that, the best time to switch is when nothing is on fire. Switching during a crisis is possible and we have done it, but you lose the parallel-running safety net and you make decisions under pressure. If you are currently mid-incident, stabilise first and switch afterwards.
One genuinely good trigger is a hardware refresh or an office move. If machines are being rebuilt or the network is being re-cabled anyway, folding the provider change into that work removes most of the duplicated effort.
What good looks like afterwards
Within the first month you should have documentation you did not have before, a written list of the risks found during the audit, and a tested restore. Those three things are the deliverables of a switch, and if you do not get them the switch has not really happened.
You should also expect the first six weeks to surface problems that were always there. A new provider finding issues is not a sign of a bad handover; it is usually the entire point. What matters is whether they are presented as a list to fix or as a series of chargeable surprises.
What to tell your staff, and when
Switching provider is invisible to most of your team until the day the support number changes, and that is exactly how it should be handled. Announce it once, clearly, close to cutover, and give people one instruction rather than a project update.
What they need: the new number and email address, the date it changes, and a sentence about why. What they do not need: a fortnight of anticipation about an IT change, which reliably produces a spike in tickets from people worried their machine is about to be taken away.
The exception is anyone who has become the unofficial internal IT person. Tell them early and involve them in the audit, because a great deal of undocumented knowledge lives with them and a new provider will need an hour of their time. They are also the person most likely to feel displaced by the change, which is worth handling deliberately rather than accidentally.
Switching without leaving your current provider
Worth naming, because it is a legitimate outcome. A fair number of businesses run the audit, take the written findings to their existing provider, and get the service they wanted without changing anything. That is a good result, and any incoming provider who resents it is telling you how they would behave later.
It works because most poor IT relationships are not caused by incompetence. They are caused by drift: a contract that made sense at eight users and no longer does at twenty-five, a service level nobody has revisited, and a provider who has quietly stopped asking. A written list of specific findings restarts that conversation in a way that a general complaint does not.
If you go this route, put the findings in writing, ask for a dated response, and set a review point three months out. If nothing has changed by then, you already have the audit, the documentation and the list, and the switch takes four weeks rather than four months.
The switch checklist
Print this, tick it off, and nothing important gets left behind with the old provider.
- Audit complete and the written findings received
- Domain registration confirmed as being in your company’s name, not the provider’s
- DNS records exported and stored somewhere you control
- New monitoring and endpoint protection deployed alongside the old, with no conflicts
- New backup running and a full test restore completed successfully
- Administrative access to every system confirmed by using it, not by being told it works
- Licence keys and vendor account details collected and documented
- Notice given in writing, dated, and acknowledged
- Staff told the new support number and email address, once, close to cutover
- Old agents removed, old provider access revoked, final documentation received
Frequently asked questions
If the answer is not here, ask us. You will get a straight one, from someone who does the work.
Mon–Fri, 9am–5:30pm
How long does it take to switch IT support providers?
About four weeks: one week to audit and document, one to run new monitoring and backup in parallel, one to verify restores and access before giving notice, and one to cut over and remove the old tools. Done in that order there is no downtime.
Will switching IT provider cause downtime?
It should not. Your data, email, files and applications are not moved: only the monitoring, protection, backup and administrative access change. The two items with real sequencing risk, endpoint protection and backup, are run in parallel until the new arrangement is verified.
When should we give notice to our current provider?
After the new provider has verified administrative access and completed a test restore, not before. That is usually week three of four. Giving notice first hands the incumbent leverage during the period you most need their cooperation.
What if our current provider will not hand over passwords?
It slows a switch but cannot stop one. Microsoft and Google both have documented processes for a domain owner to recover tenant control, and registrar access follows domain registration. Check today whether your domain is registered in your name rather than your provider’s, that is the one case that gets genuinely awkward.
What should we ask our current provider for?
Global admin credentials, domain and DNS access with a record export, server and network device access, backup platform access and retention settings, licence keys and vendor accounts, and the asset register and documentation. You are entitled to all of it, and how quickly it arrives tells you how the rest will go.
Is there a bad time to switch IT providers?
Your busiest trading period, and the middle of an active incident. Otherwise the best trigger is often a hardware refresh or an office move, because the duplicated effort disappears when machines are being rebuilt anyway.
What should we expect in the first month with a new provider?
Documentation you did not previously have, a written list of the risks found during the audit, and a tested restore. If those three do not arrive, the switch has not really happened yet.
Should we tell our staff before or after we switch?
Close to cutover, and once. They need the new number, the new email address and the date, not a fortnight of anticipation about an IT change, which reliably produces tickets from people worried their machine is about to be taken away. The exception is anyone acting as your unofficial internal IT person, who should be involved early.
Can we use a switch audit to renegotiate with our current provider instead?
Yes, and it is a perfectly good outcome. Most poor IT relationships are caused by drift rather than incompetence, and a written list of specific findings restarts that conversation in a way a general complaint does not. If nothing has changed three months later, you already have the audit and the switch takes four weeks.