Changing IT provider sounds daunting because so much depends on it. Email, files, phones, security and every member of staff’s ability to do their job all run through the same relationship. It’s understandable that people put it off for years.
In practice, a well-planned handover is mostly organisation and sequencing. Here is how it usually works, and the things that make the difference between a smooth switch and a stressful one.
Start by reading your contract
Before you do anything else, find your current agreement. You’re looking for the notice period, any minimum term, and what happens on exit. In particular, check who owns the licences, hardware and domain names, and whether there are charges for handing over documentation. If anything is unclear, ask for it in writing or take advice.
This isn’t about picking a fight. It’s about knowing your timeline, so the new arrangement starts when the old one ends, with no gap in between.
Make sure you hold the keys
You should be able to log in as an administrator to the systems your business depends on. In practice that usually means:
- Your Microsoft 365 or other email and productivity tenant
- The registrar account where your domain names are registered
- Your firewall, router and internet service accounts
- Backup consoles and the encryption keys for them
- Software licences and support contracts
- Any websites, hosting and DNS control panels
If any of these are held only by your provider, requesting access is your first job. It’s entirely reasonable to expect your business’s systems to be accessible to you.
Get an independent picture of what you have
A good new provider will begin with an assessment: a list of devices, users, servers, applications, licences and risks. This serves two purposes. It gives them what they need to take over safely, and it often reveals things nobody knew about, such as unsupported software, missing backups or accounts for people who left years ago.
Treat the findings as useful, not as an accusation. Every environment has loose ends. The point is to know about them.
Plan the handover, don’t improvise it
A sensible transition plan covers the dates, the order of work and who is responsible for what. Most businesses benefit from a short overlap, with the old provider available while the new one takes over monitoring, support and administration in stages.
- Agree a start date for the new provider and an end date for the old one.
- Hand over documentation and administrator access.
- Move monitoring, patching and security tooling across.
- Test your backups before and after the move.
- Switch the support route: where staff go when they need help.
- Review everything after the first few weeks.
Tell your team what is changing
From a member of staff’s point of view, most of this is invisible. What they care about is who to call and whether their email still works. Give them a short, clear message: the date the change happens, the new contact details, and what (if anything) they need to do. Keep it simple.
If something will change on their devices, such as a new support tool or a password reset, say so in advance. Surprises are what cause disruption, not the change itself.
The first ninety days
The first few weeks are when a new provider earns its place. You should expect to see issues dealt with promptly, a clear picture of your environment, and a short list of recommended improvements ranked by priority. A good provider will want to review progress with you after the first couple of months and show what has changed.
If you’re considering a move and want to talk it through, there’s no obligation. Often the most useful first step is simply a conversation about what isn’t working and what a better arrangement would look like.