iSectra — Believe IT
IT Department

What Actually Happens When You Switch IT Providers

The step-by-step reality of moving to a new IT provider — what to get from the outgoing one, how long it takes, and what to check before you give notice.

Brian Martins Aug 4, 2026 8 min read
What Actually Happens When You Switch IT Providers

Switching IT providers is a documented process that a competent incoming provider can run in two to four weeks for a typical small or mid-size business, with little or no downtime for end users. The work happens mostly in parallel with your current setup, and the actual cutover is scheduled outside hours.

What makes companies hesitate is not the process itself but the vagueness around it — lost data, an angry incumbent, credentials held hostage. This article removes the vagueness by walking through the transition step by step, including the parts that are genuinely awkward.

Free IT Risk Assessment

See how your IT actually stacks up.

Twelve questions, about four minutes, and your score appears on screen immediately — no sales call required.

Take the assessment

What does a provider transition actually involve?

At a high level, a transition runs in six stages: discovery and documentation, credential and access transfer, tooling changeover, parallel running, cutover, and stabilization. Discovery comes first, because nothing else can be planned until the incoming provider understands what exists. Credential and access transfer is the stage most likely to stall, and it's the one worth preparing for. Tooling changeover is where the incoming provider's monitoring, ticketing, and security agents replace the outgoing provider's. Parallel running means both providers' systems operate side by side for a short window, so nothing is unmonitored during the handover. Cutover is the single scheduled event where the new provider becomes primary. Stabilization is the first weeks after, where the incoming provider fixes the small things nobody documented.

What do you need to get from your outgoing provider?

This is the most useful section in the article, so I'll be specific. Before you give notice — or at the very least, the moment you do — you need the following in hand:

  • Domain registrar and DNS access. Your domain is the root of your entire online presence; if the outgoing provider holds it in their account, you need it moved to an account you control before the relationship ends.
  • Microsoft 365 or Google Workspace global admin. Whoever holds global admin holds the keys to your email, file storage, and identity. If that's your provider's tenant rather than yours, that's the first problem to solve.
  • Firewall and network device credentials. Administrative access to the devices that protect and route your traffic.
  • Backup system access and retention history. Not just the login — the history of what was backed up, how often, and whether restores have been tested.
  • License ownership records. Whose tenant are the licenses in? If they're in the provider's, you may need to re-procure to keep them.
  • Documentation of the environment. Network diagrams, server inventories, configuration baselines. If it doesn't exist, that's useful to know now.
  • Warranty and support contract details. So you know what's covered and when it expires.
  • Vendor relationships held in their name rather than yours. Rebates, partner pricing, and sometimes the ability to renew at all may travel with the provider.

If that list feels long, it's because it is. But each item is something you're entitled to, and getting it before notice is far easier than getting it after.

Who owns what?

This is the uncomfortable part. Licenses purchased through a provider often sit in the provider's tenant, not yours — which means on paper the provider owns them, and moving them to your own tenant isn't always possible. Monitoring and security agents installed by the provider belong to them; when they leave, those agents are removed, which is fine as long as you knew they were there. Some documentation may never have existed — there is no network diagram, no inventory, no password safe, just knowledge in someone's head who is about to leave.

The way to find out before you give notice is to ask for an asset and license inventory in writing. A provider that can't produce one is telling you something about how your environment has been run. The cost of finding out after notice is that you lose negotiating leverage; the cost of finding out after the provider is gone can be days of downtime while you rebuild access from scratch.

How long does it take?

For a typical small or mid-size business — one office, a Microsoft 365 tenant, a handful of line-of-business applications — a clean transition takes two to four weeks from signed agreement to stable operations. Larger environments, multiple sites, or heavily customized setups take longer; I've run transitions that ran six weeks and ones that ran ten days.

Week one is discovery and documentation: the incoming provider maps the environment, confirms credential access, and identifies anything missing. Week four is stabilization: the new provider is primary, monitoring is in place, and the small undocumented things are being cleaned up. The middle two weeks are credential transfer, tooling changeover, and parallel running. What can be accelerated: discovery, if your documentation is good, and tooling changeover, if the environment is standard. What can't: the parts that depend on your outgoing provider's responsiveness, which is exactly why you want the handover terms agreed in writing.

What about downtime?

The honest answer is that a well-run transition involves essentially none for end users. The work happens in parallel: the incoming provider stands up monitoring, deploys its tools, and verifies access while the outgoing provider's systems are still running. Cutover is scheduled outside hours — usually a weekend window — and on Monday morning your team logs in to the same email, the same files, and the same applications, with a different company answering the help desk.

Parallel running is the mechanism that makes this safe. For a short window both providers' monitoring can see your environment, so there's no gap where nobody is watching. If something breaks during cutover, the fallback is the previous configuration, which still exists until you decommission it. The risk is not downtime; it's the small frictions — a printer that needs reconfiguring, a VPN profile that needs reinstalling — and a good provider triages those in the first week.

What if the outgoing provider is difficult?

Most are professional. The relationship ends, the work is handed over, and both sides move on. Some, though, slow-walk credential handover, bill for documentation that should have existed anyway, or imply that leaving will be more trouble than it's worth. It's worth covering this directly because it's the fear that keeps companies stuck.

Your leverage is straightforward. Your contract has termination and auto-renewal clauses — read them before notice, not after. Your data is yours; a provider cannot withhold it. Your domain is yours; if it isn't in an account you control, that's the first thing to fix. And the timing of notice matters: giving notice at the wrong point in the billing cycle can trigger an unwanted renewal, so check the renewal date and the required notice period and line them up.

What should you do before giving notice?

A short, blunt checklist:

  1. 1.Read the termination and auto-renewal clauses. Know exactly how much notice is required and when renewal triggers.
  2. 2.Confirm who owns the licenses. If they're in the provider's tenant, plan the re-procurement before notice, not after.
  3. 3.Confirm you control the domain registrar. If you don't, move it first — it's the single most important asset to hold in your own name.
  4. 4.Get a written asset inventory from the outgoing provider. Networks, devices, licenses, vendor relationships.
  5. 5.Agree the handover scope in writing with the incoming provider. What they'll do, what they need from you, and how long each stage takes.

None of this is aggressive. It's the diligence any vendor relationship deserves before you change it.

How we run a transition

Briefly, because this section isn't the point. We document first, then deploy monitoring in parallel, schedule cutover outside hours, and run a stabilization period of two to four weeks where we fix the small things. How we deliver managed IT and how we run the help desk your team will actually call are described elsewhere. The structure here is what matters: documentation before action, parallel before cutover, stabilization before "done."

WeekWhat we doWhat your team doesWhat changes for end users
Week 1Discovery, documentation, confirm credential access, identify gapsProvide contacts, confirm priorities, review the inventoryNothing
Week 2Acquire credentials, deploy monitoring in parallel, start tooling changeoverApprove configuration, sign off on the inventoryNothing
Week 3Complete tooling changeover, validate backups, schedule cutoverConfirm the cutover date, communicate the change windowNothing
Week 4Run cutover off-hours, then stabilize — triage small issues, documentReport any issues, attend a wrap-up reviewA different company answers the help desk

The transition is rarely the hard part

The hard part is deciding to have the conversation. Most companies stay with a provider they've outgrown not because the switch is technically risky — it isn't, when it's run properly — but because asking the questions feels confrontational. It isn't. The questions in this article are the ones any competent provider should answer, incoming or outgoing, and the same instinct that makes them worth asking before a switch makes them worth asking now. If you want a parallel on why the economics of a switch can be hard to see, our article on how MSPs earn covers the incentive side. The transition itself is a known process, run by people who've done it many times. Deciding to start it is the part that takes courage.

Hero photo: "A hand holding a key to a door" by Jakub Żerdzicki on Unsplash.

Frequently asked questions

Don't see your question? Email info@isectra.com and we'll answer it directly.

Share
IT Department
BM
Chief Technology OfficerBrian Martins

Brian Martins is Chief Technology Officer at iSectra. He has run dozens of provider transitions and writes about the parts that actually go wrong.

Get the next post in your inbox.

Signal, once or twice a month. No spam — just the posts worth reading.

Let's see what your IT could feel like.

A senior engineer will review your environment and respond within 24 hours. No sales script, no obligation.

(845) 563-0346
Call