Switch IT support providers badly and the damage is not one bad week. It is a Microsoft tenant nobody can administer, a backup chain with no history behind it, and a list of privileged accounts nobody can prove were ever revoked. Do it well and almost nobody in the business notices that anything happened at all. The distance between those two outcomes is rarely technical skill. It is sequencing, paperwork, and knowing who holds which key on which day.
This guide sets out that sequence. Every deadline, retention window and transfer rule below is read off a source published and checked on 21 August 2026: Microsoft’s Partner Center documentation for CSP subscription transfers and subscription lifecycle states, Acas guidance on TUPE service provision changes, ICO guidance on processor contracts under the UK GDPR, the NCSC supply chain security principles, and the published per-user price bands of UK providers who list them at all.
Where a figure had to be modelled rather than read off a page, it is labelled modelled and the working is shown, so you can drop in your own headcount and rates and watch every downstream number move. The worked example throughout is a 60-user UK professional services firm paying £68 per user per month — £4,080 a month, £48,960 a year.
If you have not yet decided whether to move, our guide to assessing IT support value at renewal covers that decision, and this one covers the execution. What good looks like on the far side is set out in our IT provider onboarding checklist for the first 30 days. The service-design view of what we actually deliver sits on our managed IT services page.
Table of contents
- What Actually Breaks When You Switch IT Support Providers
- The Contract Clock That Decides When You Can Switch IT Support Providers
- Exit Rights That Decide How Much It Hurts to Switch IT Support Providers
- The Asset Register to Build Before You Switch IT Support Providers
- Microsoft 365 Licences When You Switch IT Support Providers
- What Happens If the Outgoing Provider Cancels Instead of Transferring
- Admin Access, GDAP and Revoking the Outgoing Provider
- A 90-Day Plan to Switch IT Support Providers Without Disruption
- The Overlap Window: Why Double-Running Costs Less Than It Looks
- The Cutover Weekend, Hour by Hour
- Backups Are the Biggest Risk When You Switch IT Support Providers
- Monitoring, RMM Agents and the Uninstall Order
- Documentation to Demand Before You Switch IT Support Providers
- Does TUPE Apply When You Switch IT Support Providers?
- Security in the Switch Window
- What the New Provider Must Prove After You Switch IT Support Providers
- What It Costs to Switch IT Support Providers
- When Switching Does Not Pay
- Mistakes UK Firms Keep Making When They Switch IT Support Providers
- How Progressive Robot Helps Firms Switch IT Support Providers
- Switch IT Support Providers: Frequently Asked Questions
- References
What Actually Breaks When You Switch IT Support Providers
Ask anyone who has lived through a bad transition what went wrong and you will almost never hear “the new engineers were not good enough.” You will hear about a licence that lapsed, a firewall nobody had the password for, or a backup job that had been silently pointing at the outgoing provider’s storage account.
The four things that decide how well you switch IT support providers
The first is control: who holds the top-level administrative rights to each platform today. The second is continuity: whether monitoring, patching and backup keep running through the changeover with no gap. The third is knowledge: whether the new team knows what the estate looks like before they own it. The fourth is commercial: whether the paperwork lets you leave on the date you intend to leave.
Why the disruption is almost never technical
Every technical task needed to switch IT support providers is routine on its own. Installing a management agent, pointing DNS somewhere new, re-enrolling a device — none of it is hard. What makes a switch dangerous is that these tasks are only safe in one order, and the person who knows the current order is the person you are leaving. That is why firms who switch IT support providers on a rushed timetable get hurt far more often than firms who switch to a cheaper supplier.
The disruption you can plan for and the kind you cannot
Planned disruption is a Saturday morning where email is read-only for ninety minutes. Unplanned disruption is discovering on the Monday that the line-of-business application’s licence was registered to the outgoing provider’s email address. The first costs almost nothing. The second can cost weeks, and it is the reason the asset register below comes before any plan to switch IT support providers.
The Contract Clock That Decides When You Can Switch IT Support Providers
Before any technical planning to switch IT support providers, read the contract. Not the service schedule — the termination clause. In UK managed services the two numbers that matter are the notice period and the renewal term, and together they create a window that is often only a few weeks wide.
The notice period that decides when you can switch IT support providers
A typical UK managed services agreement runs for twelve months and renews automatically unless one side serves written notice, commonly 90 days before the anniversary. That gives a single 90-day window each year in which a decision to switch IT support providers can actually be acted on. Miss it by one day and the agreement rolls for another full term.
The arithmetic of missing your notice date
For the worked 60-user firm, missing that window commits another £48,960 of fees to a supplier you have already decided to leave. Set against a modelled total switching cost of £17,500 — built up later in this guide — the penalty for a missed calendar reminder is 2.80 times the entire cost of switching. It is the single most expensive administrative error in the whole process.
What to do before you serve notice to switch IT support providers
Do not serve notice first. Serve it when the incoming supplier is contracted, the asset register is complete, and you have written confirmation of what the outgoing supplier will hand over. Notice is the trigger that starts the clock and, in practice, the moment goodwill starts to decline. Serving it early costs you nothing except leverage.
Termination for convenience and termination for cause
Most agreements allow termination for convenience with notice, and immediate termination for cause after a defined breach and cure period. Reach for the second only with legal advice — a disputed exit is the one scenario in which an outgoing provider has an incentive to be slow, and slow is exactly what a plan to switch IT support providers cannot absorb.
Exit Rights That Decide How Much It Hurts to Switch IT Support Providers
An exit clause is the difference between a handover and a hostage negotiation. Most UK agreements have one; very few clients have read it before the week they need to switch IT support providers.
What a usable exit clause says when you switch IT support providers
It names the artefacts, the format and the deadline. Documentation, network diagrams, asset inventories, licence records and credentials, supplied in a machine-readable format, within a stated number of working days of termination. Anything vaguer than that is a promise of “reasonable assistance”, which in practice means whatever the outgoing provider considers reasonable while their staff are already working on other accounts.
The UK GDPR clause you already have
Even where the commercial exit terms are thin, data protection law is not. ICO guidance on processor contracts is explicit that at the end of the contract the processor must, at the controller’s choice, delete or return all the personal data it has been processing on your behalf. That is a legal obligation on your outgoing supplier regardless of how their service schedule is worded, and it is the strongest lever most firms do not realise they hold.
Transition assistance, and who pays for it
Expect chargeable transition assistance and budget for it rather than fighting it. A defined block of hours at a stated rate, with a scope, is far safer than free help with no commitment behind it. The NCSC’s supply chain security principles make the same point from the security side: contracts should set out clearly what happens to your information and assets when a supplier relationship ends.
The Asset Register to Build Before You Switch IT Support Providers
This is the step firms skip when they switch IT support providers, and later regret. Before a single agent is uninstalled, you need a written record of every asset, who holds the top-level rights to it, and how those rights move.
Ownership is not the same as administration
Your business may own a firewall outright while the outgoing provider holds the only administrator account on it. You may pay for Microsoft 365 while the subscriptions sit under the provider’s CSP agreement. Ownership and control diverge constantly in managed IT, and it is the control column that determines whether you switch IT support providers in a fortnight or a quarter.
| Asset | Often controlled by | How it moves | Risk if missed |
|---|---|---|---|
| Microsoft 365 tenant | You, via a partner relationship | Partner transfer plus GDAP change | No admin access on day one |
| Microsoft licences | Outgoing provider’s CSP | Partner-to-partner transfer | Subscription expiry and data loss |
| Domain names | Provider’s registrar account | IPS tag change or auth code | Email and website outage |
| DNS zone hosting | Provider’s DNS platform | Zone export and re-delegation | Silent mail delivery failure |
| Firewalls and switches | Provider admin accounts | Credential handover and reset | Unmanageable network edge |
| Backup platform | Provider’s tenant and storage | Rarely transfers — rebuild | Loss of retention history |
| RMM and EDR agents | Provider’s platform | Uninstall and re-deploy | Unmonitored, unpatched estate |
| Line-of-business apps | Vendor, via provider contact | Change of registered contact | No support entitlement |
| Documentation | Provider’s own system | Export on termination | Knowledge starts from zero |
The four rows that hurt most when you switch IT support providers
Licences, domains, backups and documentation. The first three can each stop the business outright, and the fourth quietly doubles the cost of everything the new supplier does for the next six months. Every other row on that table can be rebuilt in an afternoon.
Microsoft 365 Licences When You Switch IT Support Providers
For most UK SMEs this is the single highest-risk element of any decision to switch IT support providers, because the licences that run email are usually bought through the outgoing provider’s Cloud Solution Provider agreement rather than by you directly.
How a licence transfer works when you switch IT support providers
Microsoft’s documented process has a specific shape. You accept a relationship request from the incoming partner, which gives you two partner relationships at once. The incoming partner then sends a transfer request to the outgoing partner, who must open it and approve the subscriptions to be moved. Microsoft will not override a CSP transfer without the source partner’s approval, and does not mediate disputes between partners.
The three deadlines inside that process
A transfer request that nobody acts on expires after 30 days. An approved transfer takes up to 72 hours to complete, with failed line items retried across that same 72-hour window before the transfer settles as partially complete. And a single transfer carries a maximum of 25 licence line items per billing plan, so a larger estate has to be split across several requests.
What does and does not change
The transferred subscription is created new under the incoming partner at the original subscription’s price, with a new subscription ID, and promotions carry across. User counts, renewal settings and scheduled changes are preserved. There is no new cancellation window, because a transferred subscription is not treated as a new term — which means the incoming provider inherits your existing commitment dates, not a fresh set.
| Factor | Partner-to-partner transfer | Cancel and re-purchase |
|---|---|---|
| Service interruption | None | Possible, and hard to reverse |
| Needs outgoing provider to act | Yes — they must approve | No |
| Time to complete | Up to 72 hours | Minutes to purchase, then re-assign |
| Request validity | Expires after 30 days | Not applicable |
| Line item limit | 25 per billing plan | None |
| Pricing | Original subscription price carries over | Current list price applies |
| Commitment dates | Inherited, no new cancellation window | New term begins |
| Best used when | The exit is cooperative | The exit is not |
Start the licence conversation first, not last
Because the transfer request expires after 30 days and needs an action from a supplier who is losing the account, this is the workstream to open on day one of a plan to switch IT support providers — not in the final fortnight. If the outgoing partner will not engage, you need to know that with weeks in hand, not days.
What Happens If the Outgoing Provider Cancels Instead of Transferring
This is the scenario worth understanding before you need it, because the timeline is fixed by Microsoft and no amount of escalation shortens it.
The lifecycle after a cancellation
When a new commerce subscription’s term ends without renewal, it moves into a 30-day expired state in which users can still access files and services. After those 30 days it moves to a 90-day disabled state in which users cannot access anything and only administrators can reach the data. After that the subscription is deleted and is not recoverable.
The 90-day repurchase window
There is one safety net. Microsoft documents a 90-day window after a cancellation during which purchasing the same product or an equivalent SKU automatically restores customer data and user licence assignment settings — including where the new purchase covers fewer licences. After 90 days, that restoration is no longer available and the data is removed.
Together those states give a 120-day total window from the end of the term to deletion, of which only the first 30 days are business as usual.
Why this belongs in your risk register
Nobody plans for this outcome, and it is not usually malicious — it happens when a cancellation is processed on schedule because a transfer request sat unopened. Knowing the 30-day and 90-day figures turns a panic into a recovery plan, and it is a strong argument for starting the licence workstream early.
Admin Access, GDAP and Revoking the Outgoing Provider
Delegated access is the part of the handover most likely to be left half-finished, because nothing breaks when you forget it. That is exactly what makes it a governance problem.
How delegated partner access works now
Microsoft partners hold administrative access to customer tenants through granular delegated admin privileges. A GDAP relationship is created with a defined duration of between 1 and 730 days, and can be set to auto-extend. Critically, the customer can terminate a GDAP relationship at any time — you do not need the outgoing provider’s cooperation to remove their access.
The revoke list
Removing the GDAP relationship is one item on a longer list. Every standing administrator account, every break-glass credential, every VPN certificate, every shared mailbox delegation, every remote access tool and every third-party portal where the outgoing provider is the registered contact needs an owner and a completion date.
Do it on a date, not “when convenient”
Set the revocation date in the plan and hold it. The NCSC’s guidance on supply chain security is direct on this point: when a contract ends there should be an effective offboarding process that shuts down the supplier’s access to your systems. An unrevoked admin account belonging to a company you no longer pay is a finding waiting to happen at your next audit.
A 90-Day Plan to Switch IT Support Providers Without Disruption
Ninety days is the number that keeps appearing when firms switch IT support providers, because it matches the typical notice period and gives every dependency room to move. It can be done in 45 days, and it is done badly in 30.
| Phase | Days | Main work | Exit criteria |
|---|---|---|---|
| 0 — Prepare | Before notice | Asset register, contract review, supplier selected | You know what moves and who holds it |
| 1 — Notice | Day 1 | Written notice served, exit rights invoked | Termination date fixed in writing |
| 2 — Discovery | Days 1–21 | New provider audits estate, licence transfer opened | Documented estate, transfer request sent |
| 3 — Build | Days 22–50 | New tooling deployed alongside, backups started | Two backup sets, agents co-existing cleanly |
| 4 — Overlap | Days 51–75 | Both providers live, tickets routed to the new team | Two weeks of clean service data |
| 5 — Cutover | Days 76–80 | Ownership moves, old access revoked | Revoke list complete and evidenced |
| 6 — Prove | Days 81–90 | Restore test, patch report, security baseline | Evidence, not assurances |
Phase 0 is the one that cannot be compressed
Everything in phase 0 happens before you serve notice, while relations are still normal and information still flows. Firms that switch IT support providers successfully spend longer here than anywhere else. Firms that get hurt start at phase 1.
Why the overlap sits before the cutover
The overlap phase exists so that the new provider is already answering tickets while the old one is still contractually obliged to help. It converts the riskiest hour of the project — the moment ownership changes — into an administrative event rather than a technical one.
The 30-day way to switch IT support providers, and what you give up
A 30-day switch is possible when the estate is small, the licences are already owned directly, and the exit is cooperative. You give up the overlap window, the restore test and most of the discovery. That is a reasonable trade for a ten-person business and a poor one at sixty users.
The Overlap Window: Why Double-Running Costs Less Than It Looks
The instinct is to make the handover instantaneous to avoid paying twice. It is the most expensive instinct in the whole project.
What the overlap buys when you switch IT support providers
Roughly one month of parallel cost buys you a live rehearsal: the incoming team learning the estate while the outgoing team is still answerable for it, and any surprise surfacing while there is still somebody contractually obliged to explain it. For the worked 60-user firm at £72 per user with the incoming supplier, that is a modelled £4,320 for a single month.
The comparison that settles it
£4,320 is 8.82% of the outgoing annual fee of £48,960. One serious cutover failure — a day of lost email across sixty people, plus emergency engineering — comfortably exceeds that. Buying the overlap is buying an insurance policy priced at under nine per cent of one year’s support.
What the overlap must deliver, in writing
Agree beforehand which team owns which queue, who has authority to change production systems, and how an escalation crosses between them. An overlap with no rules is just two suppliers pointing at each other, and it is worse than no overlap at all.
The Cutover Weekend, Hour by Hour
By the time the cutover arrives, almost everything should already be done. If the cutover weekend contains discovery, the plan to switch IT support providers has failed somewhere upstream.
Friday evening
Confirm the last successful backup from both platforms and record the job identifiers. Freeze all non-essential change. Confirm that the licence transfer has already completed — the cutover weekend is far too late to be inside a 72-hour transfer window.
Saturday
Move ownership of DNS, domains and third-party portals. Complete the GDAP change so the incoming provider holds delegated access and the outgoing provider does not. Work through the revoke list and tick items off with evidence, not memory.
Sunday
Validate mail flow end to end, including external senders and any application that sends through your tenant. Run a restore test from the new backup platform. Confirm monitoring, patching and endpoint protection are reporting on every device that should be reporting.
Monday morning
Staff the helpdesk heavily for the first two hours. Nearly every genuine post-switch issue surfaces between 08:00 and 10:00 on the first working day, and the difference between a good switch and a bad one is often just how many people are waiting for the phone to ring.
Backups Are the Biggest Risk When You Switch IT Support Providers
Of everything on the asset register, backup is the item that most reliably does not move when you switch IT support providers, and the one whose failure is invisible until you need it.
Retention history does not move when you switch IT support providers
Your backups usually live inside the outgoing provider’s platform, under their tenant and often their storage contract. When the relationship ends, that history typically ends with it. The new provider can start protecting you from day one, but they cannot inherit twelve months of restore points that were never yours to move.
The parallel backup rule
Start the new backup platform during the build phase, weeks before the cutover, and let both run in parallel. It costs a little and removes the single scenario nobody recovers from gracefully: a data loss event during the changeover window with no usable restore point on either side.
Get the retention position in writing
Ask the outgoing provider two direct questions: how long will existing backup data be retained after termination, and can any of it be exported. Their answers belong in the risk register alongside your compliance retention obligations, and they should be agreed before notice is served.
Monitoring, RMM Agents and the Uninstall Order
Two remote monitoring and management agents on the same endpoint is a recipe for conflicting patch policies, duplicated alerts and a support call that neither provider can diagnose.
Agents can co-exist, briefly and deliberately
In the build phase, deploying the incoming provider’s agent alongside the existing one is normal and safe if patching authority is explicitly assigned to one platform. What is not safe is leaving both live with both configured to patch, reboot and enforce policy.
The order that avoids a gap
Deploy the new agent, verify it reports on every device, assign patching authority to it, and only then remove the old one. Removing first creates a window of unmanaged, unmonitored endpoints — the very state you set out to avoid when you switch IT support providers. Endpoint protection follows the same order, with the added rule that two security products should never both be in active enforcement mode.
The devices you will forget
Laptops belonging to people on long-term leave, kiosk machines, meeting room hardware and any server nobody has logged into since the last audit. Reconcile the agent list against the asset register before signing off the phase, not after.
Documentation to Demand Before You Switch IT Support Providers
Documentation is the cheapest thing to ask for and the most expensive to reconstruct. A new provider without it spends its first quarter rediscovering things your last provider already knew, and that is the hidden cost of every rushed decision to switch IT support providers.
The minimum documentation set before you switch IT support providers
Network diagrams and IP addressing, an asset inventory with warranty and licence status, a list of every third-party vendor with account references, backup configuration and retention settings, a firewall rule base export, and a record of every scheduled task or automation running against the estate.
The undocumented dependency
Every estate has one: a script on a server that nobody owns, a mail rule that routes something important, a certificate that expires in eight months. Ask the outgoing provider directly for a list of known exceptions and workarounds. It is a question they can answer in an hour and one the new provider would take months to answer.
Make the format part of the request
Ask for exports in a portable format rather than screenshots or a read-only portal that closes when the contract does. This is exactly the sort of requirement the NCSC expects a contract to state explicitly for the return of your information and assets on termination.
Does TUPE Apply When You Switch IT Support Providers?
Sometimes, and it surprises firms who assume it only applies to buying a business. In the UK, TUPE covers service provision changes, including a service being reassigned from one contractor to another.
When TUPE is likely to apply if you switch IT support providers
TUPE is most likely to bite where there is an organised grouping of employees dedicated to your account — a named on-site engineer, or a small team assigned principally to you. It is far less likely where you are one client among many in a shared helpdesk pool, which describes most SME managed services arrangements.
The 28-day rule and the £500 exposure
Where TUPE does apply, the outgoing employer must give employee liability information to the incoming employer at least 28 days before the transfer, covering identities, ages, employment particulars, live disciplinary and grievance records from the last two years, collective agreements and outstanding claims. Failure carries compensation of at least £500 per employee for whom information was missing or wrong.
Ask the question early
Put it to both suppliers in writing during phase 0. If either believes TUPE applies, you need employment advice and a longer timeline — 28 days of statutory information exchange has to fit inside your notice period, not after it.
Security in the Switch Window
A decision to switch IT support providers creates a period of elevated privilege, unusual activity and distracted administrators. It is the one window in which a suspicious change is most likely to be waved through as “probably the new provider”.
Why the window is riskier when you switch IT support providers
During a switch, credentials are being shared, new administrative accounts appear, mail rules change, and unfamiliar tooling connects to your tenant. Every one of those is also what a real intrusion looks like, which is why cybersecurity controls should tighten during a transition rather than relax.
Controls to hold through the change
Keep multi-factor authentication enforced for every administrator on both sides. Log privileged actions and keep the log outside both providers’ platforms. Note that Microsoft Entra retains sign-in and audit logs for 7 days on the free tier and 30 days with a P1 or P2 licence, so anything you may need later should be exported before it ages out.
A clean baseline afterwards
After the cutover, have the incoming provider produce a current security baseline: conditional access policies, administrator inventory, MFA coverage, patch compliance. Comparing that against the pre-switch position is the only reliable way to know that nothing was quietly dropped in transit.
What the New Provider Must Prove After You Switch IT Support Providers
The project does not end on the day you switch IT support providers. It ends on the day the new supplier produces evidence that the estate is genuinely under management.
Evidence, not assurances
Ask for four artefacts in the first 30 days: a successful restore test with a timestamp, a patch compliance report by device, an administrator inventory with MFA status, and a backup job report covering every protected workload. All four are routine to produce and impossible to fake convincingly.
The 30-day review meeting
Book it before the switch begins. Its agenda is the exit criteria from the plan above, and its purpose is to catch the items that were quietly deferred during cutover week — the three unpatched laptops, the one server outside monitoring, the shared mailbox nobody re-permissioned.
Where the onboarding guide takes over
From here the work becomes ordinary onboarding rather than transition, and the detail of what month one should contain is set out in our IT provider onboarding checklist. The switch is finished when there is nothing left on the register marked “the old provider used to handle that”.
What It Costs to Switch IT Support Providers
Here is the modelled total for the worked example: a 60-user firm leaving a £68 per user contract for one at £72 per user, with a cooperative exit and a one-month overlap. Every line is modelled, and every line is one you can price yourself.
| Cost line | Basis (modelled) | Amount |
|---|---|---|
| Transition project fee | 8 consultant days at £650 | £5,200 |
| Overlap month | 60 users at £72 for one month | £4,320 |
| Internal project time | 16.25 days at £240 a day | £3,900 |
| Cutover weekend engineering | 2 engineers, 12 hours, £95 an hour | £2,280 |
| Tooling and backup bridging | 60 users at £30 one-off | £1,800 |
| Total one-off cost | Sum of the five lines | £17,500 |
The largest single line is the transition project fee, and the smallest is the one most often cut first.
What the total actually represents
£17,500 is 35.74% of one year’s outgoing fee of £48,960. That is a real number and a large one, and it is why the decision to switch IT support providers should never rest on the per-user rate alone.
The rate you should compare against
UK managed IT support is published at roughly £40 to £150 per user per month, with most SMEs in the £60 to £80 band. A supplier quoting well below that range is not necessarily cheaper — they have usually removed something, and finding out what during your first month under new management is an expensive way to learn.
When Switching Does Not Pay
There is one scenario where the arithmetic argues clearly against a decision to switch IT support providers, and it is the scenario firms are in most often when they start looking.
Why firms who switch IT support providers on price alone rarely gain
Suppose the move saves £8 per user per month: 60 users × £8 × 12 = £5,760 a year. Against a £17,500 one-off cost, payback arrives after 3.04 years, or roughly 36.5 months — longer than most managed services contracts run before the next renewal decision.
The reasons that do justify it
Capability gaps, security failures, unmanaged risk, a provider who cannot support a platform you now depend on, or a relationship where nothing is proactive. Those reasons are worth £17,500 on their own, they do not need a payback calculation to defend them, and they are why firms who switch IT support providers for capability rarely regret it.
Renegotiate first, then decide
Take the quote you have been given and put it to the incumbent alongside a specific list of what is not working. Some firms fix the problem for the cost of one meeting. If nothing changes after that conversation, you have both a clear answer and a much better-documented case for moving.
Mistakes UK Firms Keep Making When They Switch IT Support Providers
These are the recurring ones, in the order they usually appear when firms switch IT support providers.
Serving notice before anything is ready
It feels decisive and it costs you every remaining piece of leverage. Notice is the last step of preparation, not the first step of the project.
Assuming the licences will simply follow
They will not. A CSP transfer requires an action from the supplier you are leaving, within a 30-day request window, and Microsoft will not force it.
Treating the overlap as waste
Cutting the parallel month to save one invoice is the most common false economy in the entire process, and the one most likely to produce the outage the project was designed to avoid.
Skipping the restore test
An untested backup is a belief, not a control. The restore test is the single most informative hour in the whole switch, and it belongs before sign-off rather than after the first incident.
Never finishing the revoke list
Six months later, the old provider still has a global administrator account and a VPN certificate. Nothing has broken, which is precisely why nobody noticed.
How Progressive Robot Helps Firms Switch IT Support Providers
We treat a decision to switch IT support providers as a defined project with a named owner, a written asset register, and exit criteria for every phase rather than a start date and good intentions.
What we do before notice is served
We audit the estate, read the outgoing contract, and produce the register of what moves, who controls it and how. That work is the reason our transitions are quiet, and it happens while your existing arrangement is still fully in force.
What we commit to at cutover
A parallel backup platform running before cutover, a restore test on the weekend itself, a completed and evidenced revoke list, and a 30-day review with the four artefacts named above. If you want to talk through a move, our contact page is the fastest route to a conversation.
Switch IT Support Providers: Frequently Asked Questions
How long does it take to switch IT support providers?
Ninety days is the comfortable figure and matches a typical notice period. Forty-five days is achievable for a cooperative exit on a small estate. Thirty days means giving up the overlap window, the discovery phase and the restore test.
Will our email go down when we switch IT support providers?
It should not. Email risk comes from licence subscriptions lapsing and from DNS changes, both of which are scheduled work with known lead times. A licence transfer completes in up to 72 hours and should be finished long before cutover weekend.
Can our current provider block us from leaving?
They cannot stop you terminating in line with the contract, and they cannot withhold your personal data — ICO guidance requires processors to delete or return it at the end of the contract. They can decline to approve a CSP licence transfer, which is why that workstream starts on day one.
Do we lose our backup history when we switch IT support providers?
Usually yes, if backups sit in the outgoing provider’s platform. Run the new backup platform in parallel from the build phase and ask in writing how long the old data is retained after termination.
Does TUPE apply when we switch IT support providers?
Only where an organised grouping of employees is dedicated principally to your account. It rarely applies to shared-pool SME helpdesk arrangements, but where it does, the 28-day employee liability information deadline has to fit inside your notice period.
What is the biggest cause of disruption when you switch IT support providers?
Sequencing. Removing something before its replacement is verified — an agent, an admin account, a DNS record — causes far more incidents than any technical shortcoming in the incoming team.
References
Subscription lifecycle states — Partner Center
Granular delegated admin privileges (GDAP) introduction
Microsoft Entra data retention
What a TUPE transfer is — Acas
Employee liability information — Acas
What needs to be included in the contract — ICO
The principles of supply chain security — NCSC
Managed IT Support Costs UK 2026: What Businesses Actually Pay
