How to switch IT providers without downtime (a step-by-step transition plan)

The outages keep coming back. Tickets sit for days. Every fix comes with a project quote. You've known for months it's time to leave your managed service provider (MSP). What keeps you there isn't loyalty. It's fear of what breaks on the way out.

Here's the plain version. Switching often feels harder than staying, but switching is routine when it's planned. Downtime comes from rushed, unplanned exits, not from the change itself.

Below, you'll find the warning signs, what to collect before you say a word, a 30-60-90 day plan, and the mistakes that cause downtime.

When is it time to switch IT providers?

It's time to switch when the same problems keep coming back, response times slip, every fix comes with a project quote, security is sold as an add-on, nobody can show you documentation, and you only hear from your provider when there's an invoice. If three or more of those sound familiar, it's time.

Eight warning signs to check against your current provider

• Recurring issues. The same problems get "fixed" every month and never actually go away.
• Slipping response times. Tickets take longer than your SLA (service level agreement) promises, and nobody explains why.
• Surprise project quotes. Every improvement or fix becomes a separate bill.
• Security sold as an add-on. Basic protection is priced as an upgrade instead of being part of the service.
• No documentation. Nobody can produce a network diagram, a list of managed systems, or a record of what's been changed.
• Invoice-only contact. You hear from your provider when the bill is due, not when something needs attention.
• No clear picture of coverage. You can't say with confidence which systems the provider actually manages.
• Vendor lock-in. Admin passwords, domains, or licenses sit in the provider's name instead of yours.

Most of these signs trace back to the same root cause, which is how the agreement is structured. You buy a slice of coverage, every improvement becomes a quote, and the gaps only surface at the worst possible moment.

That's not a people problem. It's how the agreement was designed.

Why do businesses stay with an IT provider they've outgrown?

Most businesses stay because of fear of downtime, an old provider holding the admin passwords, missing documentation, long auto-renewing contracts, and not knowing what the provider actually manages. Every one of these can be fixed with planning, and most can be fixed before you ever announce you're leaving.

• Fear of downtime. Counter. Downtime comes from unplanned exits. Overlapping both providers removes the gap.
• The provider holds the admin passwords. Counter. Secure your own global admin and emergency access accounts before you give notice.
• No documentation. Counter. You paid for that work. Request it in writing, and a capable new provider can rebuild what's missing during discovery.
• Long, auto-renewing contracts. Counter. Find the notice period and termination terms now so the renewal date doesn't decide for you.
• Not knowing what's being managed. Counter. A device inventory and license review answers that question in days, not months.

Vendor lock-in usually comes from who holds the keys.

When the provider controls the passwords, the domain, and the documentation, leaving feels dangerous. Take those pieces back and the fear goes with them.

Thinking about leaving your current provider?

What should you collect before you tell your current provider?

Before giving notice, quietly secure what you own. That means global admin access to Microsoft 365 or Google Workspace, domain registrar and DNS logins, firewall and network credentials, software license records, backup locations, a device inventory, and the current contract with its exit terms. Ownership first, conversation second.

Start with the global administrator account, the top-level login for your Microsoft 365 or Google Workspace environment (your "tenant"). Whoever holds it controls email, files, and users.

Your business should also hold a break-glass account. That's an emergency access account with global admin rights, kept locked away and used only when normal admin logins fail. Microsoft recommends creating at least two of them, and they should belong to you, never to any provider. See Microsoft's guidance on managing emergency access accounts in Microsoft Entra ID.

On Microsoft 365, your provider likely manages your tenant through GDAP (granular delegated admin privileges), a partner connection that lets them administer your environment from their own accounts. Remove it from the old provider at cutover under Settings > Partner relationships in the Microsoft 365 admin center. Microsoft explains how in customer-led removal of a granular admin relationship.

Then gather your license records, backup details, and asset inventory so your documentation handoff doesn't depend on the old provider's goodwill.

How long does it take to switch MSPs?

Most small and mid-sized businesses can switch MSPs in roughly 30 to 90 days. The timeline depends on company size, number of locations, how complete the documentation is, the old contract's notice period, and whether compliance requirements like CMMC (Cybersecurity Maturity Model Certification) are in scope. That range is typical, not guaranteed.

Here's what surprises most people. The notice period in your old contract often sets the timeline more than the technical work does.

The technical cutover can move quickly. A 60- or 90-day notice clause can't. Read the exit terms first, not last.

What is the step-by-step plan for switching IT providers?

The plan runs in phases. Secure ownership, review the contract and give notice, run discovery with the new provider, overlap both providers, cut over tools one at a time (monitoring, EDR, backups, help desk), remove the old provider's access, then verify and close out. Never remove the old security or backup tools before the new ones are confirmed running.

Days 1-30. Secure and plan

1. Secure admin ownership. Confirm your company holds global admin, break-glass, domain registrar, and DNS access.
   • Who does it. You, with help from the new provider
   • Done when. Every critical login is in your company's name and tested
2. Review exit terms and give notice. Check the notice period, data return terms, and termination fees, then give notice in writing.
   • Who does it. You
   • Done when. Notice is delivered and the end date is confirmed
3. Pick a cutover window. Choose dates that avoid your busiest periods.
   • Who does it. You and the new provider
   • Done when. Dates are agreed in writing
4. Start discovery. The new provider maps your devices, systems, licenses, and backups.
   • Who does it. New provider
   • Done when. There's a documented inventory of your environment

Days 31-60. Overlap and cut over

5. Deploy new monitoring. The new provider installs its RMM agent (remote monitoring and management software) on every device.
   • Who does it. New provider
   • Done when. Every device reports into the new monitoring system
6. Swap endpoint protection device by device. New EDR (endpoint detection and response) security software goes on before the old tool comes off each machine.
   • Who does it. New provider, coordinating with the old provider
   • Done when. Every device runs the new EDR and none is left unprotected
7. Migrate backups and run a test restore. New backups run, and a test restore succeeds before old backups are retired.
   • Who does it. New provider
   • Done when. Data has been restored successfully from the new backups
8. Switch help desk routing on a set date. Staff tickets move to the new provider on one announced day.
   • Who does it. You and the new provider
   • Done when. Requests reach the new help desk and nothing lands with the old one

Days 61-90. Close out and clean up

9. Remove the old provider's access. Delete their user accounts and remove partner access (GDAP) in Microsoft 365.
   • Who does it. You or the new provider
   • Done when. No old provider accounts or partner relationships remain
10. Rotate shared passwords. Change every password the old provider knew. This is credential rotation.
    • Who does it. New provider
    • Done when. All shared credentials have been changed
11. Confirm license ownership. Make sure every software license and vendor account is in your company's name.
    • Who does it. You and the new provider
    • Done when. Licenses are verified and nothing is billed twice
12. Document everything and hold a first review. Capture the final state of your environment and review what was found.
    • Who does it. New provider, with your leadership
    • Done when. Documentation is delivered and the review is complete

The most important rule in this whole plan is the no gap rule. New security and backup coverage must be live before the old coverage comes off. Not the same day. Before.

That's what the overlap period is for. Two sets of tools running for a few weeks isn't waste. It's insurance.

Announce the help desk handoff to staff with one simple message covering the new number, new email, and start date. Nothing more.

What are the most common mistakes when switching IT providers?

The mistakes that cause downtime are giving notice before securing admin access, removing old backups before new ones are tested, leaving security tools uninstalled between providers, forgetting the domain registrar, not telling staff where to get help, and leaving the old provider's access active after the cutover.

1. Giving notice before securing admin access. Fix. Lock down global admin and break-glass accounts first.
2. Forgetting the domain registrar. Fix. Move the registrar account into your company's name before anything else changes.
3. Removing old backups before new ones are tested. Fix. Retire old backups only after a successful test restore.
4. Leaving security tools uninstalled between providers. Fix. Install the new EDR before removing the old one, device by device.
5. Not telling staff where to get help. Fix. Send one message with the new help desk contact and start date.
6. Leaving the old provider's access active after cutover. Fix. Remove their accounts and partner access, then rotate shared passwords.
7. Ending the old contract before everything is verified. Fix. Close out only after monitoring, security, and backups are confirmed running.

Illustrative scenario (not a real client). A company gives notice, and email goes down for two days. The old MSP owned the domain registrar account, and nobody at the company had the login.

Removing a departing provider's access is the same discipline as offboarding an employee. You wouldn't leave a former employee's login active. Don't leave your old provider's, either.

What should your new IT provider do in the first 90 days?

A good new provider should document your whole environment, bring every device under management, deploy its security stack with no gaps, verify backups with a test restore, fix the urgent problems first, and give leadership a clear picture of what it found. You should never be quoted extra just to get onboarded.

What you should see in the first 90 days, from any provider

• A documented inventory of your devices, systems, and licenses
• Every device brought under management and monitoring
• The new security stack deployed with no gap in coverage
• Backups verified with a successful test restore
• Urgent problems fixed first, before nice-to-haves
• Old provider access removed and shared passwords rotated
• Scope and response commitments agreed in writing before work starts
• A plain-English summary for leadership of what was found and what's next

Use this list to hold any provider accountable, including us.

At Headway Strategy, transition and cleanup work is part of the agreement, not a separate project quote. One price, $195 per person per month, covers it. Projects aren't extra, scope and response commitments are written down before work starts, and the same toolset applies regardless of company size.

Two case records from our work.

• HS-0906. Standardized equipment and automated setup across 9 clinical sites, resulting in 51% fewer tickets within six months and 99.98% uptime.
• HS-0417. Consolidated four acquisitions and retired 31 systems, lowering running costs by 22%.

Want a transition plan built around your environment?

Frequently asked questions

Ready to switch IT providers?

Secure ownership first. Overlap coverage. Cut over one piece at a time. Close out cleanly.

The hardest part of switching is deciding to. We'll handle the rest.