Switch IT support providers and you take on two risks in the same moment: the outgoing team stops caring the day they learn they have lost the account, and the incoming team does not yet know where anything is. Between those two facts sits your business, still expected to answer phones, take payments and close the month end. Most transition horror stories are not caused by technical difficulty. They are caused by a fortnight in the middle when nobody was genuinely responsible for anything.
The reassuring news is that this is a solved problem. A move between managed IT services partners has a definite shape: an exit audit, an overlap period, a credential handover, a single cutover date and a thirty-day review. Businesses that switch IT support providers to that pattern find the disruption is close to zero. Run the move as an email saying “we are moving on the first of September” and you will spend October explaining to your board why the finance server was unavailable for two days.
This guide is for UK businesses of roughly ten to three hundred staff who have decided to switch IT support providers, or suspect they probably should. It works through the exit audit, choosing the incoming partner, the overlap period, what actually has to move, cutover week, staff communications, the first thirty days and the true cost of the exercise.
One principle runs through all of it. Businesses that switch IT support providers well treat the handover as a transfer of knowledge rather than a transfer of paperwork. Contracts move themselves. Knowledge — passwords, quirks, undocumented workarounds, the reason that one server must never be rebooted before ten — only moves if somebody makes it move.
Table of contents
- Why businesses switch IT support providers — and why they wait too long
- Before you switch IT support providers: audit your exit position
- Choosing the incoming partner without repeating the mistake
- How to switch IT support providers without a coverage gap
- Credentials, data and licences: what has to move
- Cutover week: sequencing the switch so nothing breaks
- Telling staff, suppliers and customers about the change
- The first thirty days after you switch IT support providers
- What it costs to switch IT support providers — and the mistakes that inflate it
- Switch IT support providers: frequently asked questions
Why businesses switch IT support providers — and why they wait too long
Very few companies change partners because of a single catastrophe. The decision to switch IT support providers is almost always the end of a long, quiet accumulation of small frustrations that nobody wrote down.
The slow drift into a bad relationship
The service that felt attentive in year one becomes a ticket queue in year three. Response times stretch. The engineer who knew your estate leaves. Projects you asked about last spring are still “in the roadmap”. Nothing is bad enough to justify the upheaval on any given Tuesday, so the drift continues. By the time anybody seriously proposes that the business should switch IT support providers, the decline has usually been running for a year. Recognising drift early is the cheapest possible intervention — our guide to the warning signs of an underperforming IT provider exists precisely because the pattern is so consistent.
The trigger events that force a decision
There is usually a moment. A failed restore during a real incident. A security question the provider cannot answer. A renewal quote with a twenty per cent uplift and no explanation. An acquisition that changes who you are actually dealing with. Trigger events do not create the problem; they simply make it impossible to keep ignoring, and they are the reason most firms switch IT support providers in the same quarter as a contract anniversary.
Why fear of disruption keeps bad contracts alive
The most common reason businesses stay too long is not loyalty or price. It is the belief that changing will hurt more than staying. That fear is rational — a badly managed transition genuinely is painful — but it is also the incumbent’s best commercial asset. Every month you delay because you are frightened of the move is a month of service you have already decided is not good enough.
What actually goes wrong in a badly run transition
The failure modes are predictable and short in number: credentials that were never handed over, monitoring that lapsed between contracts, a backup nobody owned for three weeks, a firewall change request with no route to approval, and staff still emailing a service desk that has stopped reading. Every one of them is a planning failure, not a technical one, which is precisely why a written plan removes most of the risk. Businesses that switch IT support providers to a documented sequence rarely meet any of these failures at all.
Before you switch IT support providers: audit your exit position
The work that decides whether a transition is calm or chaotic happens before you sign with anybody new. Audit your exit position first — you can only switch IT support providers safely when you know exactly what you are holding.
Read the contract before you read any proposals
Find the notice period, the minimum term, the auto-renewal clause and the exit or offboarding charges. Ninety-day notice periods are common and thirty-day ones are not universal, so a firm that decides in June may not be free until October. Nobody can switch IT support providers faster than their own notice period allows, and discovering that after signing with somebody new is an expensive way to learn it. Check what the service-level agreement obliges the provider to do during the notice period, because “reasonable assistance” written without definition is worth very little at the point you need it.
Find out what your provider actually holds
Ask for a written inventory: administrative accounts, domain registrar access, firewall and switch configurations, backup platform ownership, licence tenancy, documentation and the remote monitoring agents installed across your estate. Firms with disciplined IT asset management can answer this in an afternoon. Everyone else discovers that the honest answer is “we are not sure”, which is itself the most valuable finding of the whole audit.
Establish what “your data” means in practice
Documentation, ticket history, network diagrams and configuration backups are frequently held in the provider’s own tooling, and their contractual status is rarely obvious. Our companion guide on leaving an IT provider covers the detail, but the summary is simple: assume nothing transfers automatically, and get the position agreed in writing before notice is served rather than after.
Score the incumbent honestly before you move
Write down the last six months of failures with dates. If the list is thin, you may have a communication problem rather than a provider problem, and changing partners will not fix it. If the list is long and repetitive, you have your business case — and the evidence you will need if the incumbent responds to notice with a retention offer. The firms that switch IT support providers with real confidence are the ones holding a dated list rather than a general feeling.
Choosing the incoming partner without repeating the mistake
The point of the exercise is a better service, not merely a different logo on the invoice. Nobody wants to switch IT support providers twice in three years, so the selection deserves as much rigour as the transition itself. This is where disciplined vendor management earns its keep.
Buy the transition, not the sales deck
Ask every shortlisted provider to describe, in writing, how they run a transition: what they do in week one, who does it, what they need from you and what “complete” looks like. Vague answers here reliably predict vague delivery later. Ask how many clients they have helped switch IT support providers in the past year and what went wrong on the most recent one; the firms who do this well have a documented method and no hesitation about describing it.
Ask for a named transition plan in writing
You want dates, owners and deliverables — discovery report, asset register, monitoring coverage, backup verification, documentation pack and a day-thirty review. Our IT provider onboarding checklist sets out what a competent incoming provider should be doing in that window without being asked twice.
Check the shape of the service, not the headline price
Compare what is genuinely included: on-site visits, out-of-hours cover, project hours, security tooling, licence management and the escalation path. A cheaper monthly figure with everything meaningful billed as a project is not cheaper. Reviewing published support plans side by side is more informative than any comparison spreadsheet a salesperson builds for you.
Reference calls that are worth making
Ask for two references of your size and sector, and ask both the same question: what happened during your transition, and what took longer than promised? Every provider can supply a happy customer. Very few can supply one who remembers the move fondly, and the ones who can are the ones you want.
How to switch IT support providers without a coverage gap
This is the heart of it. Almost all genuine disruption comes from a window in which the outgoing provider has disengaged and the incoming provider is not yet operational. Businesses that switch IT support providers without incident are simply the ones who refused to allow that window to exist.
The overlap period is not optional
Plan for two to four weeks in which both contracts are live and you are, briefly, paying twice. It feels wasteful. It is the cheapest insurance available, it costs a fraction of one day of unplanned downtime, and it is the only mechanism that lets you switch IT support providers without a period in which nobody owns the estate. If your notice period allows, serve notice with the overlap built into the dates rather than trying to negotiate it afterwards.
Who owns a P1 during the overlap
Write down, before the overlap begins, who answers a priority-one incident on each day of it. A single sentence — “the outgoing provider retains P1 ownership until 09:00 on the fourteenth, after which the incoming provider owns all incidents” — prevents the single most damaging failure mode, which is two providers each assuming the other is handling it.
Run discovery before the old contract ends
The incoming team should complete estate discovery, deploy monitoring agents and produce a findings report while the outgoing provider is still contractually obliged to answer questions. Businesses that switch IT support providers before discovery is complete turn every unknown into an archaeology project, and archaeology is billed by the hour.
Set a single cutover date and defend it
One date, communicated everywhere, for the moment support responsibility formally transfers. Rolling cutovers by department sound cautious and behave chaotically, because nobody can remember which team is on which service desk this week. Firms that switch IT support providers with the least friction pick a Tuesday, tell everybody twice and hold the line.
Credentials, data and licences: what has to move
The mechanics of the handover are unglamorous and entirely decisive. Almost every transition that goes wrong goes wrong here, and the businesses that switch IT support providers cleanly are simply the ones who worked through this list item by item.
Administrative accounts and the privileged access list
Build a list of every administrative credential in the business: Microsoft or Google tenant, firewall, switches, wireless controllers, backup platform, line-of-business applications, domain registrar and DNS. Hand them over through a password manager with an audit trail, never by email. The incoming provider should create its own named accounts with multi-factor authentication rather than inheriting a shared login.
Documentation, monitoring and the RMM estate
Remote monitoring and management agents belonging to the outgoing provider must be removed, and the incoming provider’s agents deployed, without leaving a period where the estate is unwatched. Reconcile the deployment against your asset register device by device. “Mostly deployed” is an acceptable week-one position and an unacceptable cutover one.
Licences, subscriptions and who owns the tenancy
Check whether your Microsoft 365 licences, antivirus subscriptions and backup capacity sit in your own tenancy or the provider’s. Licences bought through a provider’s agreement may need a formal transfer of billing partner, which takes days rather than minutes and cannot be rushed on cutover morning. Providers who resell under their own agreement should tell you this early; ask directly if they do not, because licensing is the item most likely to delay the date you switch IT support providers.
Backups and the restore you must test yourself
Before the outgoing provider leaves, insist on a real restore test of a real file and a real system, witnessed by you. A backup job with a green tick is a claim, not evidence. This is the single check most likely to find something serious while somebody is still contractually obliged to fix it.
Cutover week: sequencing the switch so nothing breaks
By cutover you should be executing a plan, not making decisions. The order in which you switch IT support providers matters considerably more than the speed, and the sequencing below is what keeps a business covered from one hour to the next.
Freeze changes for the week either side
No infrastructure projects, no firmware updates, no optional migrations for seven days before and after. Everybody involved should be doing one thing only, so that when something does behave oddly there is exactly one recent change to investigate.
The order that keeps you covered
Deploy new monitoring, verify it is reporting, confirm backups are running under the new arrangement, transfer the service desk contact details, then — and only then — remove the outgoing provider’s access. Reversing the last two steps is how businesses end up unmonitored for a weekend without anybody noticing until Monday.
Removing the old provider’s access safely
Revoke access on an agreed date, verify it, and document the verification. Shared administrator passwords surviving a transition is the most common finding in post-incident reviews, and dormant credentials belonging to a firm you no longer pay are a genuine cybersecurity exposure rather than an administrative untidiness. Change every shared password regardless of assurances.
Keep a manual fallback for the first week
Publish a direct mobile number for one named engineer at the incoming provider for the first seven days. Ticket systems are correct and portals are tidy, but the first time something urgent breaks under a new arrangement, somebody needs a number that a human answers. In the week after you switch IT support providers, that number is worth more than the entire service catalogue.
Telling staff, suppliers and customers about the change
Internal communication is the part most transition plans forget, and it is where employees form their opinion of whether the move was a good idea. Staff never see the technical work; they see the day you switch IT support providers and the fortnight that follows it.
One message, sent before the rumours start
Send a short note a week ahead explaining that the business is about to switch IT support providers: who the new partner is, when the change happens, how to raise a ticket from that date, and who to contact internally if anything looks wrong. Then send it again on the morning of the switch. Two clear messages prevent a fortnight of confused forwarding.
Retraining the reflex to email the old service desk
Staff will email the old address for months. Ask the outgoing provider to set an auto-reply pointing at the new one, put the new details on the intranet, in the email signature block and on a sticker on the reception phone. Assume the habit takes eight weeks to break, because it does.
Third parties who also need the new details
Your line-of-business software vendors, telecoms supplier, alarm and door-entry maintainer, and often your insurer all hold a support contact for your business. Update every one of them in the same week. External parties still calling a provider you no longer use is a slow, invisible failure that surfaces at the worst possible moment.
The first thirty days after you switch IT support providers
The transition is not finished at cutover. It is finished when the new provider knows your estate as well as the old one did — and that takes about a month of deliberate effort.
Convert goodwill into documentation
The first month after you switch IT support providers is the only period in which you have real leverage and the provider has real attention. Requests made now get done; the same requests in month seven join a queue. Spend that goodwill on a network diagram, an asset register, an application owner list and a written description of how your backups work.
Measure the first tickets, not the promises
Raise something genuine and moderately urgent in week one and watch what happens end to end. One real ticket tells you more about response times, communication style and internal escalation than any service level table. Log the result; it becomes the baseline for the review.
The day-thirty review that closes the transition
Hold a formal review against the transition plan: monitoring coverage as a percentage, patch compliance, backup verification, documentation delivered, outstanding exceptions and their owners. Businesses that switch IT support providers and never hold this review typically discover eighteen months later that discovery was never actually completed.
What to do if the new provider is already slipping
If deliverables are late in the first month, say so immediately and in writing. The behaviour you accept during onboarding sets the standard for the whole term. A provider who cannot meet commitments while trying to impress you will not improve once the relationship is routine — and you now have recent, documented evidence of what a transition looks like.
What it costs to switch IT support providers — and the mistakes that inflate it
The cost of moving is real but usually smaller than the cost of staying somewhere unsuitable for another two years. Budget for it honestly, because the businesses that switch IT support providers badly are almost always the ones who assumed the move would be free.
The real cost lines of a transition
Expect the overlap month of double running, any contractual exit or offboarding fee, internal time from your own staff — typically two to five days spread across the project — onboarding or setup charges from the incoming provider, and occasionally new agent or security licensing. For most businesses of this size the total lands between one and three months of the monthly fee.
Mistakes that inflate the bill
The expensive errors repeat across every transition we see, and they are the reason some firms switch IT support providers for twice what the exercise should have cost: serving notice before the incoming provider is contracted, skipping the overlap to save one month, treating discovery as optional, allowing the outgoing provider to define what constitutes “your data”, and running the whole exercise without a named internal owner. Each of these converts a planned project into an unplanned one.
When to stay and fix instead of moving
Sometimes the honest answer is that the provider is adequate and the relationship is under-managed — no service reviews, no roadmap, no named contact, requests raised inconsistently. If the last six months of failures are thin on the page, fix the governance and reassess in one quarter. Moving IT outsourcing arrangements has a real cost, and it should buy a genuine improvement rather than a change of scenery.
Switch IT support providers: frequently asked questions
How long does it take to switch IT support providers?
Plan for eight to twelve weeks from decision to day-thirty review for a typical business of ten to three hundred staff. That breaks down as two to four weeks selecting and contracting, the notice period running in parallel where the contract permits, a two to four week overlap, then thirty days of onboarding. Firms that switch IT support providers in under a month usually do so because something has already gone badly wrong.
Can I switch IT support providers mid-contract?
Sometimes, but rarely for free. Check the minimum term and any early termination charge, and weigh it against the cost of another year of poor service. Where the provider has materially failed to meet the agreed service levels there may be grounds to exit early; take the documented evidence to a solicitor rather than relying on a strongly worded email.
Will we lose data or ticket history when we change providers?
Ticket history and documentation held in the outgoing provider’s tooling are the items most often lost when businesses switch IT support providers, because their ownership is ambiguous in many contracts. Request exports in a readable format before notice expires. Your business data — files, mailboxes, databases and their backups — should never move at all in a well-run transition; only who administers it changes.
Should we tell the old provider before we sign with the new one?
Contract with the incoming provider first, then serve notice. Serving notice while still shortlisting leaves you with a disengaged incumbent, no replacement and no leverage. Expect a retention offer; treat it sceptically, because a discount offered only under threat of leaving is an admission about how the account was priced and managed all along.
What if our provider will not hand over administrative passwords?
Ask formally and in writing, citing the relevant contract clause and giving a deadline. Most disputes resolve at this stage. This is the single most common reason a plan to switch IT support providers slips by a fortnight. Where credentials genuinely cannot be recovered, the incoming provider can usually rebuild access to firewalls, switches and tenancies through vendor recovery processes — slower and more expensive, which is precisely why the exit audit and its written inventory come first. Maintaining independent ownership of your identity platform and following recognised standards such as Cyber Essentials prevents the situation arising at all.
Do we need to change our email or domain when we move?
No. Your domain, DNS and mailboxes belong to your business and stay exactly where they are; only the administrative access to them changes hands. If a provider suggests otherwise, or holds your domain registration in their own name, treat that as a serious finding in the exit audit and resolve it before cutover rather than after.
