How to switch IT support provider: signs it's time, notice periods and a step-by-step handover

Most businesses stay with an underperforming IT provider for a year or two longer than they should, because switching feels risky and the problems feel tolerable. This guide covers the three parts of the decision in order: how to tell it is time, what your contract lets you do and when, and the handover itself, step by step, including exactly what to ask the outgoing provider for.

Signs it is time to switch

Occasional problems are normal. These patterns are not.

• Slow response has become normal. You wait hours for acknowledgement and days for fixes, and you have started chasing as a matter of routine.
• The same faults keep coming back. Wi-Fi drops, printers vanish, Outlook prompts for passwords, and each fix is a workaround rather than a root cause.
• Nothing is proactive. You have never seen a patching report, a backup test result or a review of hardware age. The provider only appears when something breaks.
• Security has not been discussed. No MFA rollout, no EDR, no email filtering, no awareness training, and no answer when you ask about Cyber Essentials.
• Your staff have become the helpdesk. People fix their own problems or ask the office manager because it is faster than logging a ticket.
• Costs rise, service does not. Annual increases with no explanation, invoices for things you thought were included, and no reporting to show what you are paying for.
• Communication is poor. Jargon, vague updates, or silence during incidents.
• You have outgrown them. You have added staff, sites or remote working and the provider's processes have not changed.
• You feel like an account, not a client. No named contact, a different engineer each time, no understanding of your business.
• Engineers keep changing. High turnover at the provider means your systems are relearned from scratch each time.

A fuller list, with the questions to ask, is in the signs of bad IT support.

What staying actually costs

Delay feels free because the bill for it does not arrive as an invoice. It arrives as staff time, risk and missed opportunities.

Productivity. A team of 30 losing 30 minutes a week each to IT problems loses around 750 hours a year. At any realistic hourly cost that is a multiple of the support fee.

Security exposure. Unpatched systems, no MFA and untested backups are exactly what turns a phishing click into a ransomware event. The GOV.UK Cyber Security Breaches Survey consistently finds phishing the most common attack on UK businesses.

Emergency spend. Hardware bought the day it fails costs more than hardware replaced on a plan, and emergency call-outs are billed at premium rates.

Compliance. A provider that cannot show you where your data is, who has access, and when backups were last tested cannot help you answer an ICO enquiry or a client's supplier questionnaire.

Growth friction. New starters wait for laptops, the second office is improvised, and every new tool is bolted on without a plan.

The arithmetic is worked through in why unresolved IT issues become expensive.

Before you serve notice: read the contract

Do this first, because the contract determines your timeline.

1. Find the minimum term and the renewal mechanism. Many contracts auto-renew for another full term unless notice is served in a window before the anniversary. Missing the window can commit you for another year.
2. Find the notice period. Ninety days is common. Note whether it runs from the day you give notice or from the next anniversary.
3. Check the exit clause. What the provider must hand over, by when, and at what cost. If the contract is silent, you will rely on goodwill and on your rights as the owner of the accounts and data.
4. Check for termination-for-breach. If SLA targets have been missed repeatedly, you may be able to leave sooner with a formal notice and cure period.
5. Gather evidence. Ticket histories, response times, unresolved problems and any written complaints. You may need them.

What a fair contract looks like on each of these points is set out in what to look for in an IT support contract.

Choose the new provider before you give notice

The most common mistake is serving notice first and shopping second. The right order is:

1. Shortlist and choose the new provider. Use how to choose an IT support company for the questions to ask.
2. Agree the new contract, with a start date that overlaps the end of the old one, so there is never a gap.
3. Serve notice on the outgoing provider in writing, in the correct window, and ask for written acknowledgement of the end date.
4. Tell the outgoing provider who the new one is and that you expect cooperation on handover, as the contract requires.

This way the new provider is in place, under contract and installing monitoring while the outgoing one is still obliged to deliver.

The handover, step by step

A well-run handover follows roughly this sequence. The new provider drives it, but you should know what is happening.

Stage 1: access and discovery.

• The new provider is granted global administrator access to Microsoft 365 and other cloud tenants, with its own named accounts.
• It collects credentials for the domain registrar, DNS, firewall, switches, Wi-Fi controllers, servers, NAS, backup systems and any remote-access tools.
• It runs discovery tools to inventory devices, users, licences and software, whether or not documentation exists.
• It reviews backup jobs and performs a test restore.

Stage 2: monitoring and security.

• Monitoring agents are installed on every computer and server, and the outgoing provider's agents are scheduled for removal.
• Endpoint security is reviewed and, if necessary, replaced.
• MFA status, admin accounts, leavers with live access and sharing permissions are audited.
• Patching status is assessed and a catch-up schedule agreed.

Stage 3: helpdesk and documentation.

• Staff are told how to log tickets: phone, email, portal. A short briefing or a one-page guide is enough.
• Priority definitions and the SLA are explained to whoever manages IT internally.
• Network diagrams, device inventory, configurations and recovery procedures are written up and shared with you.

Stage 4: cut-over and clean-up.

• The outgoing provider's accounts, agents and remote-access tools are removed, and you confirm this in writing.
• Any backups held by the outgoing provider are handed over or their deletion confirmed.
• The new provider presents its findings: what is at risk, what is out of warranty, what to fix first.

The same process from the new provider's side is described in the first 30 days with a new IT provider.

What to ask the outgoing provider for

Send this list in writing with your notice, and chase it against the contract's handover clause.

If the outgoing provider refuses or stalls, you still own the accounts and the data. The new provider can recover access through Microsoft, the registrar and the hardware vendors. It is slower, but it is not a reason to stay.

Common mistakes when switching

Four things go wrong often enough to be worth naming.

Serving notice before choosing. It creates a gap, or a rushed choice, and it removes the outgoing provider's incentive to cooperate before the new one is ready.

Switching mid-incident. If the server is down today, get it fixed under the current contract and switch afterwards. Handover during a crisis is how credentials get lost.

Not confirming removal. The outgoing provider's remote-access tool stays installed for a year because nobody checked. Ask for written confirmation and have the new provider verify it.

Assuming documentation exists. Often it does not. Budget the new provider's time to rebuild it through discovery rather than waiting on a handover pack that never arrives.

Telling your staff

Keep it short. One email a week before cut-over saying who the new provider is, the new phone number and portal, and that nothing about their systems changes. A second on the day. The new provider will usually supply the wording. Businesses that switch well find that staff notice the difference within a fortnight, mostly because tickets get answered.

What to do next

If you have recognised several of the signs above and read your contract, the next step is a conversation about what a handover would involve for your particular setup. Our switching IT provider page explains how we run it, including the overlap period and what we ask the outgoing provider for on your behalf.