Switching IT support providers without disrupting the business.

Many businesses stay with poor support because changing feels risky. It does not have to be, if the takeover is planned.

Start with discovery

Before anything changes, record what exists: devices, servers, network equipment, cloud accounts, licences, warranties, backup jobs, and who uses what. This is the baseline the new provider works from, and it is useful whatever you decide.

Secure the access

Make sure you, not the outgoing provider, own the administrator accounts, domain registrar, cloud tenancy, firewall and backup credentials. Rotate shared passwords as part of the handover.

Run in parallel

For a few weeks, the new provider shadows the old one: reading the tickets, learning the quirks, fixing documentation gaps. Responsibility moves on a date agreed in advance, not by accident.

Agree the service before day one

Define support hours, priorities, response targets, reporting and escalation. Write the procedures for the common tasks so the service does not depend on any one person.

Fix the foundations early

Typical first-month items: a tested backup restore, missing patches, expired certificates, an updated asset register and a review of administrator rights.

What to ask the outgoing provider

A polite request for documentation, credentials and a handover meeting is reasonable. If that is refused, it is also useful information about the contract you are leaving.