Check your contract before anything else
Start by reading the agreement you already have. Find the minimum term, the notice period, any automatic renewal date and any exit or transition fees. Note what the contract says about handing over credentials and documentation. These details decide your timeline, and knowing them before you talk to anyone avoids awkward surprises halfway through.
If the notice window is close, give notice in writing even if you have not finalised the new provider. It is better to have a few weeks of overlap than to roll into another full term. Keep the tone professional; you will need your current provider's cooperation during the handover, and most are reasonable when treated well.
Secure your access quietly first
Before announcing the change, make sure your business already holds working admin access to the critical systems: Microsoft 365 or Google Workspace, your domain registrar, firewall, backups and any line-of-business software. If you do not, request those credentials now as routine housekeeping rather than as part of an exit, which keeps the conversation simple.
Test each login. Confirm the multi-factor sign-in goes to a phone or app that someone in your business controls. Write down which systems you could not access so the new provider can plan around them. This step alone removes most of the risk in a provider change, because everything after it can be done with or without the outgoing provider's help.
Choose the new provider and plan the overlap
Once you have chosen a new provider, agree a start date and a handover period, typically two to four weeks. During that time the old provider continues day-to-day support while the new one documents the environment, installs its own monitoring tools and confirms it can reach every system. An overlap costs a little more but prevents gaps in cover.
Ask the new provider for a written onboarding plan covering discovery, tool installation, security checks, documentation and the formal cutover date. A clear plan lets you see progress and spot anything that is stuck, such as a system nobody can log into or a licence that sits in the old provider's name.
The handover checklist
The outgoing provider should hand over all admin credentials, network diagrams, asset lists, licence records, warranty details, backup configuration, firewall settings, supplier contacts and any open issues or planned work. Ask for anything unusual too: scripts they wrote, scheduled tasks they set up and workarounds that keep a legacy system running.
Licences deserve special attention. If Microsoft 365 or security software is billed through the old provider, the licences need to move without interrupting service. The new provider should handle this carefully, as a botched licence transfer can leave staff unable to sign in. Check that your domain name and any vendor accounts are registered to your business.
Cutover and clean-up
On the cutover date, the new provider takes over support requests, and staff are told how to contact them. Send a short internal email with the new help desk details and what has changed. Keep it simple; most staff only need to know where to send requests from now on.
After cutover, the old provider's tools and access should be removed. That means uninstalling their monitoring agents, deleting their admin accounts and revoking any delegated access to your cloud tenancy. Change shared passwords they knew. The new provider should confirm in writing that this has been done, so no unknown access lingers in your systems.
Common pitfalls to avoid
The biggest mistakes are leaving it too late, announcing the move before securing access, and assuming the old provider will remember everything. Plan for the handover taking longer than you expect, especially if documentation is thin. Do not cancel the old contract so early that there is no cover if the new provider hits a snag.
Watch for forgotten systems. Older offices often have a server in a cupboard, an alarm or door system with a network connection, or a supplier portal nobody has logged into for a year. Ask staff what they use day to day and include it all in the discovery. The more complete the list, the fewer surprises after cutover.
Finally, give the new arrangement a fair settling-in period. The first month with any provider involves learning your quirks, and a few requests will take longer than they will later on. Hold a short review at the end of the first and third months to raise anything that is not working, while it is still easy to adjust how requests, priorities and reporting are handled.
In short
- Read your contract first to find notice periods and renewal dates.
- Secure and test your own admin access before announcing the change.
- Overlap the old and new providers for two to four weeks.
- Remove the old provider's tools and accounts after cutover.