How to switch IT providers without breaking anything
The contract traps to check before you give notice, what to demand on the way out, and how to run a parallel transition.
Short answer
Switching takes two to four weeks and should run in parallel, not as a cutover. The incoming provider takes admin access, documents what exists, deploys their tooling alongside the old, verifies, then removes the old agents. Read your current contract before giving notice — multi-year auto-renewals, termination penalties and provider-owned Microsoft tenants are all common and all much easier to handle before the clock starts.
Before you give notice
1. Read the contract, specifically these clauses
- Term and renewal. Many managed IT contracts run 36 months and auto-renew unless cancelled in a narrow window — sometimes 90 days before the anniversary. Miss it and you're locked in another year.
- Termination for convenience. Is there one, and what does it cost? Some contracts require paying out the remaining term.
- Offboarding fees. "Transition assistance" charges of several thousand dollars appear in contracts more often than you'd expect.
- Data and documentation. What are they obliged to hand over, in what format, and by when?
- Non-solicitation. Occasionally prevents you hiring their engineer — relevant if you're bringing IT in-house.
2. Establish what you actually own
This is the step people skip and regret. Verify, before saying anything:
| Asset | Should be | How to check |
|---|---|---|
| Microsoft 365 tenant | Your company name | Entra admin centre → Properties. Check for a delegated partner relationship. |
| Domain registration | Your company as registrant | Public WHOIS lookup |
| DNS control | Account you can log into | Try logging in yourself |
| Global admin account | At least one you control | Entra → Roles → Global Administrator |
| Software licences | Bought in your name | Invoices — check whose name is on them |
| Backup data | Restorable without them | Ask for a test restore |
If the tenant is under their partner account
It's recoverable but takes longer and needs planning. Microsoft has a process for transferring a tenant out of a partner relationship, but it's smoother with the outgoing provider's cooperation — which you're more likely to get before you tell them you're leaving. Sort this first.
3. Create a break-glass admin account
A global administrator account your company controls, with credentials stored somewhere your provider can't reach, excluded from conditional access policies that could lock it out. Do this at the start of any provider relationship. If you don't have one, create it before giving notice.
The parallel transition
Weeks 1–2 · Discovery, both providers active
The incoming provider gets read access and documents everything: devices, licences, configuration, security posture, applications, vendors. Nothing changes yet. This is also when they find what the previous provider never documented — usually a surprise or two.
Week 2–3 · Parallel deployment
New monitoring and management agents deployed alongside the existing ones. Both run simultaneously. Slight performance overhead for a couple of weeks; worth it to avoid a coverage gap.
Week 3 · Verification
Confirm the new provider can actually see and act on everything — patch status reporting, backups running and restorable, alerts firing to the right place, support channel working. Test a real request end to end.
Week 4 · Cutover
Old agents removed, old provider's admin access revoked, support channel switched, staff told where to go. Revoke access yourself in your own admin centre rather than trusting it was done.
After · Verify removal
Check Entra for lingering delegated partner relationships, service principals and guest accounts. Old access has a way of surviving offboarding.
What to demand on the way out
- Administrative credentials for every system
- Complete environment documentation — network diagram, asset inventory, account list, vendor list with account numbers
- Licence and subscription records with renewal dates
- Backup configuration and documented recovery procedures
- Any custom scripts or automations running in your environment
- Written confirmation their access has been removed
- Outstanding ticket history
Reputable providers hand this over at no charge. Ours is contractual: full documentation, credentials and data in standard formats, access removed within 24 hours, no offboarding fee.
Telling your current provider
Professionally and in writing, referencing the notice clause. You don't owe them a justification, and a detailed critique rarely improves the handover. Keep it short, be specific about dates, and ask for the handover list above.
Expect a retention offer. If the relationship failed on responsiveness or capability, a discount doesn't fix that — the reason you're leaving usually isn't price.
Timing
Avoid switching during your busy season, a major project, or the fortnight before an audit. The best window is a quiet month where a week of minor friction costs nothing. Also avoid December: everyone's short-staffed and vendor support is slow.
About the author
Raymond Payne is the founder of PCR — Managed IT. Thirty years building and running technology for businesses across more than a dozen countries, and author of Mastering Automation with AI. Last updated 14 August 2026.
Thinking about switching?
Send us your current contract before you give notice. We'll read it with you and flag the traps — no obligation.