Switching IT providers feels risky because you are handing the keys to a new team while the old one still has access. Done wrong, it causes downtime and a messy handoff. Done right, it is a controlled transition that your staff barely notices.
Here is the sequence we use to make the switch clean, including the traps that cause most failed transitions.
- Get admin credentials and documentation from the old provider before you give notice.
- Never cut off the old provider until the new one has full access and the first backup is verified.
- A written runbook is the difference between a smooth handoff and a scramble.
- Plan for a 30 to 60 day overlap, not an overnight cutover.
1. Inventory and credentials first
Before you tell the old provider anything, collect every password, admin credential and piece of documentation you are entitled to. This includes domain registrar access, Microsoft 365 or Google Workspace admin, firewall and switch credentials, and any vendor logins.
2. Get the documentation in your name
This is the step most businesses skip and regret. Confirm that your documentation, licenses and admin accounts are in your company's name, not the provider's. If the old provider owns your licensing or domain, get that transferred early.
3. Run both providers in parallel
Bring the new provider on board while the old one is still active. The new team documents the environment, deploys monitoring and verifies backups while the old team keeps day-to-day support running. This overlap is usually 30 to 60 days.
4. Cut over in stages
- Deploy the new security baseline (MFA, EDR, backup) and confirm it works.
- Move support and monitoring to the new provider.
- Verify a successful backup restore before any switch is final.
- Then, and only then, remove the old provider's access and credentials.
The phases at a glance
| Phase | Duration | What happens |
|---|---|---|
| Inventory | Week 1 | Collect credentials and documentation |
| Parallel run | Weeks 2-4 | New provider documents, old provider supports |
| Cutover | Week 5 | Move support, verify backups |
| Offboard | Week 6 | Remove old access, rotate passwords |
The checklist for a clean handoff
- All admin credentials collected and documented
- Domain, licensing and Microsoft 365/Google tenant in your name
- New monitoring deployed and alerting tested
- First backup completed and a restore verified
- Old provider access removed and passwords rotated
What can go wrong, and how to avoid it
The two classic failures are losing access to a system the old provider controlled, and cutting over before the new backup is proven. Both are avoidable with the staged approach above. The NIST Cybersecurity Framework recommends treating a provider change as a controlled risk, not a surprise.
What to do if the old provider is uncooperative
Some providers make it hard to leave. The fix is to assert your rights early: you own your data, your licenses and your credentials. If the old provider will not release admin access, your new provider can often recover it through the vendor (Microsoft, your domain registrar, your firewall vendor) with proof of ownership. Do not sign a contract that makes you ask permission to leave.
If you are considering a switch, book a free assessment and we will walk you through a transition plan for your specific environment, with zero pressure and a written roadmap.