How to Switch IT Support Provider: A Step-by-Step Guide for UK Businesses

The short answer

Switching IT support provider is more straightforward than most businesses expect — if it is managed properly. The process is: check your notice period, let a new provider audit your estate before anything changes, formally request credentials and documentation from your incumbent, take over monitoring and helpdesk, then migrate remaining services on a planned timetable. A well-managed transition completes in a few weeks without your team losing a day of support.

The reason switching feels hard is not that it is technically complicated — it is that businesses do not do it often, do not know what to expect, and sometimes encounter an incumbent who makes it deliberately awkward. This guide covers all of it.

Step 1: Check your notice period before you do anything else

Your current IT support contract will specify a notice period — typically 30 to 90 days, though some contracts run to 180 days or include auto-renewal clauses that can catch businesses out. Read the termination clause carefully before you engage a new provider, because the notice period determines your timeline.

Things to look for in the termination clause:

• Notice period length — how many days or months you must give in writing.
• Auto-renewal provisions — some contracts roll over for a full year if you miss the notice window by even a day. Check whether you are inside or outside that window now.
• Notice method — most contracts require written notice, often by recorded post or email to a specific address. A phone call is not notice.
• Early termination fees — if you are mid-contract, check whether a penalty applies and how it is calculated. For most SME contracts it is the remaining months of the minimum term; worth knowing before you commit.

The good news: the transition can run in parallel with your notice period. You do not need to wait until notice expires before starting work with a new provider — in fact, the overlap is intentional, and a new provider should build this into their onboarding plan.

Step 2: Let your new provider audit your estate first

Before any formal handover begins, a competent new provider will want to audit what they are taking on: every device, server, licence, backup configuration, security tool, and third-party vendor relationship currently managed by your incumbent.

This matters for two reasons. First, it means your new provider quotes against what you actually have — not what your incumbent has documented, which may differ. Second, it surfaces anything that needs fixing before the transition (a backup that has not been tested, a licence in the wrong name, a server running an unsupported operating system). Discovering those things after handover is significantly more disruptive than before it.

A thorough pre-handover audit typically covers:

• All endpoints — laptops, desktops, servers — including operating system versions and patch status
• Microsoft 365 or Google Workspace tenant configuration, licences assigned, and admin accounts
• Backup configuration and the last verified restore test
• Security tooling — antivirus, endpoint detection, MFA status across users
• Network infrastructure — routers, switches, firewalls, VPN configuration
• Third-party vendor relationships and contact details your IT provider manages on your behalf
• Documentation — network diagrams, asset lists, password vaults, support runbooks

If a prospective new provider does not want to audit your estate before quoting, that is itself a warning sign.

Step 3: Formally request your documentation and credentials

Once notice is served and your new provider is ready to begin, the formal handover request goes to your incumbent. This is a standard, routine process — your Microsoft tenancy, your domain, your licences, and the admin credentials to all of those belong to you, not to your IT provider. They have always belonged to you.

A standard handover pack from an outgoing provider should include:

• Global administrator credentials for your Microsoft 365 or Google Workspace tenant
• Domain registrar login or confirmation of transfer settings
• All admin passwords managed on your behalf — firewall, router, switches, servers
• Network documentation — IP schemes, VLAN configurations, VPN settings
• Vendor and ISP account details and contact information
• Asset register with hardware serial numbers and warranty status
• Licence keys and software documentation
• Any backup credentials or recovery keys

Your new provider should send this request on your behalf and manage the chase — you should not be making these calls yourself.

What to do if your incumbent is being uncooperative

Most IT provider handovers are professional and uneventful. But some providers do use credentials as leverage — delaying documentation, claiming passwords have been "lost", or drip-feeding access in a way designed to slow your departure. This is more common than it should be, and it is worth knowing how to handle it.

Step one: put everything in writing

Every request, every response, every deadline — email, not phone. You want a paper trail that shows you made reasonable requests and gives dates on which your incumbent failed to respond. This matters if the situation escalates.

Step two: escalate formally within their business

If your day-to-day contact is unresponsive, write to a named director or the company's registered contact. Keep it factual: you are the customer, the credentials belong to you, and you are requesting their return in writing by a specific date.

Step three: invoke your contract

Most IT support contracts include an obligation to return client data and access credentials on termination. If your contract does not, UK case law on data ownership is generally clear: your business data and your Microsoft tenancy are yours. Check whether your contract references this, and if your incumbent is plainly in breach, say so in writing.

Step four: Microsoft direct recovery

If a Microsoft 365 tenant is genuinely inaccessible because credentials have been withheld, Microsoft has processes to verify ownership and restore admin access to the legitimate account holder. This is a last resort and requires identity verification, but it is available. Your new provider should have handled this before, and can guide you through it.

Step five: legal notice

In the rare case of a genuine refusal to return credentials after formal written requests, a solicitor's letter — or a formal complaint referencing the Data Protection Act 2018 if personal data is involved — usually resolves matters quickly. Most providers fold well before this point.

The practical point: do not be intimidated into staying with a provider because they are slow releasing your own credentials. It is your data.

Step 4: Take over monitoring and the helpdesk

Once your new provider has sufficient access, they will deploy their monitoring agent across your estate — this is a lightweight piece of software that sits on servers and workstations and feeds telemetry back to the provider's platform. Your team begins raising support tickets with the new provider from this point.

During the overlap period, your new provider will run their monitoring in parallel with whatever your incumbent still has deployed, until confidence that coverage is complete. Most handovers run this overlap for two to four weeks before formally terminating the incumbent's access.

Step 5: Migrate remaining services on a planned timetable

The final phase is migrating services that are still connected to your incumbent — email routing, backup destinations, security tooling subscriptions, and any third-party vendor relationships being managed through them. Each migration is scheduled and tested before cutover, and your team should notice nothing beyond a brief notification that a service has moved.

A typical migration timetable looks like:

• Week 1–2: Audit complete, monitoring deployed, helpdesk live with new provider
• Week 2–3: Security tooling transitioned, backup destination confirmed and tested
• Week 3–4: Vendor relationships and domain/DNS management transferred
• End of notice period: Incumbent access formally terminated, handover complete

For more complex environments — multiple sites, on-premise servers, or heavily customised configurations — allow longer. The timetable should be in writing and signed off by both your business and your new provider before anything starts moving.

Red flags to watch for in a new provider's contract

Before you sign with anyone new, read the contract with switching in mind as well as onboarding. Specifically, look for:

Credential and data ownership

The contract should explicitly state that admin credentials, your Microsoft tenancy, domains and licences are documented in your name and returned on termination without condition. If this is absent — or if the contract implies the provider "manages" these on your behalf without confirming your ownership — ask for it to be added in writing before you sign.

Minimum term and auto-renewal

12-month minimum terms are common and reasonable. 24-month minimums are increasingly common; they are not necessarily a red flag, but understand what you are signing. Auto-renewal provisions that roll over for a full year without written cancellation are worth resisting — push for 30 days' rolling after the initial term if the provider will agree.

Notice period on termination

30 to 90 days is the normal range. More than 90 days of notice required after the minimum term — without a proportional reduction in commitment — is worth negotiating.

Project work and hidden scope

Look carefully at what the monthly fee includes and what is classified as a "project" — billed separately. Some providers treat almost everything beyond basic helpdesk as a project (migrations, new user setups beyond a small number per month, hardware changes). Ask for a worked example of what the previous year's project charges looked like for a client of similar size.

Service level agreements in plain numbers

Response time commitments should be expressed as actual times — "response within 15 minutes for priority 1 issues" — not adjectives like "fast" or "urgent". If response targets are vague or entirely absent from the contract, they are not enforceable.

Data processing agreement

Your IT provider handles personal data — your staff's accounts, email, potentially client files — which makes them a data processor under UK GDPR. A written Data Processing Agreement (DPA) should be provided and signed before access begins. If a provider has never heard of this or cannot produce one, that is a compliance risk on your side as the data controller, as well as a sign of how they operate generally.

How long does switching IT provider take?

For a typical 10–50 user business without unusual complexity, a well-managed transition from first contact with a new provider to completion takes 4–8 weeks from the point you serve notice. The planning and audit phase often runs during the first two weeks of the notice period, so the effective disruption to your business is minimal — usually zero, if the transition is handled properly.

Larger environments (multiple sites, legacy on-premise infrastructure, complex vendor relationships) take longer by design. 8–12 weeks is normal for those. The question to ask any prospective provider is not "how fast can you do it?" but "how do you plan a transition for a business like ours, and what does the timetable look like?"

Questions to ask before switching IT provider

Beyond the contract terms, the conversations you have during the sales process will tell you a great deal about how a provider actually operates. Useful questions:

• "Walk me through your last three handovers — what went wrong and how did you handle it?" A provider with real experience has a genuine answer to this. Vague reassurances are not.
• "Who specifically will handle our account — and what happens when they are on leave or leave the company?" Single-engineer dependency is a risk you are trying to get away from.
• "Can I speak to two or three clients of a similar size who switched to you in the last two years?" References at the point of switching are more relevant than long-standing clients.
• "Are our admin credentials documented in our name from day one? Can I see where in the contract it says so?" A direct question deserves a direct answer with a contract reference.
• "What does your offboarding process look like if we leave you?" A provider confident in their service will answer this clearly and without hesitation.

Frequently asked questions

Can I switch IT provider mid-contract?

Yes, but you may be liable for an early termination fee — usually the remaining months of your minimum term. Read the termination clause and calculate the cost before deciding. In some cases, the service has deteriorated to the point where the contract is in breach, which changes the calculation; take legal advice if you think that applies.

What happens to my Microsoft 365 data when I switch provider?

Your Microsoft 365 tenancy, emails, files and data remain exactly where they are — in your tenant. Switching provider does not move or delete any data. What changes is who holds the global administrator credentials; that is transferred to your new provider (and ideally documented in your own secure location) as part of the handover.

Do I need to tell my staff when switching IT provider?

Yes, and sooner rather than later. Staff need to know who to raise support tickets with, how to contact the new provider, and what (if anything) will look different day to day. A brief email from leadership, ideally co-authored with your new provider, handles this. Plan it as part of the cutover — not an afterthought.

Can I switch provider if my IT is a mess?

Yes — and in many cases, poor documentation or an unmaintained environment is precisely why businesses switch. A good incoming provider will audit what they are inheriting, identify the gaps, and produce a remediation plan. The estate does not need to be tidy before you start the process; that is often the new provider's first project.

What if my current provider holds domain registrar access?

Your domain should be registered in your business's name — not your IT provider's. If it is registered in the provider's name, this is a serious problem to address as a priority. Most domain registrars have a transfer process; your new provider should initiate this as part of the handover. If the incumbent is uncooperative, domain registrars including Nominet (for .co.uk domains) have dispute resolution processes for exactly this situation.

Will switching IT provider cause downtime?

A well-managed transition should cause zero downtime for your team. Monitoring and helpdesk overlap during the transition period, services migrate outside business hours or during agreed windows, and your team's only experience of the change is a new email address for raising tickets. If a prospective provider cannot explain how they achieve this, ask them to walk you through their transition plan in detail.