How long does it take to switch IT providers?

A well-run transition between managed-IT providers takes between four and eight weeks, depending on the size of the firm and the complexity of the existing environment. The cutover itself — when responsibility formally moves — typically happens over a single weekend with minimal user impact.

Will fee-earners notice when we switch IT providers?

In a competent transition, the only thing fee-earners notice is that the helpdesk number changes — and that calls are now answered differently. Email, files, applications, and devices continue to work. If fee-earners experience real disruption, the transition was rushed.

Do we need to give notice to our existing IT provider?

Yes. Most managed-IT contracts have notice periods of 60 to 90 days. Read your contract carefully — particularly clauses about data return, account credentials, and exit cooperation. The notice period is when most of the transition work actually happens.

What should we ask the new provider before signing?

Ask: who owns our Microsoft 365 tenant after the switch (it should be you); what credentials and documentation do you receive; what does your migration plan look like; what's your fall-back position if something goes wrong; how do you handle the first 90 days; and who specifically will be working on our account.

Switching IT providers: how a law firm changes managed-IT firms without disruption

Most law firms put off switching IT providers far longer than they should. The most common reason isn’t price or contract terms — it’s fear of disruption. Fee-earners don’t have time for a botched migration; partners don’t want to spend two months explaining why the email is down.

The fear is reasonable. Transitions can go badly. But a competent transition is mostly invisible to fee-earners, takes four to eight weeks, and has well-understood failure modes that a good incoming provider will plan around.

This article covers what actually happens, how to evaluate a transition plan, and the warning signs that the new provider won’t deliver one.

What a competent transition looks like

The work falls into four phases.

Phase 1: Discovery (weeks 1-2). The new provider documents your environment from scratch. Every device, every account, every cloud service, every shared mailbox, every server, every contract. They do this even if the existing provider has handover documentation — particularly if the existing provider has handover documentation, since that documentation is often optimistic.

What you should see: a written inventory at the end of week 2. If there isn’t one, the discovery phase didn’t actually happen.

Phase 2: Stabilisation (weeks 2-4). Before any cutover, the new provider standardises baselines. Devices get enrolled in management. Accounts get audited and tidied. Patches that were missing get applied. Backup health is verified end-to-end.

This is the unglamorous phase. It is also where most of the long-term value of switching is captured. A new provider who skips it is selling you a brand change, not a service change.

Phase 3: Cutover (one weekend). Tenant ownership, billing, helpdesk responsibility, monitoring, and 24×7 cover all formally move over. The cutover itself is usually a single weekend — Friday evening to Monday morning. Done well, fee-earners notice nothing on Monday except that the helpdesk number has changed.

Phase 4: Settle (weeks 5-8). First-month tickets, edge cases that surface as people start using the system normally, fine-tuning of policies, and the first vCIO session with the partners. This is when the new relationship actually gets formed.

How to evaluate a transition plan

Ask the prospective new provider to walk you through their plan in detail before you sign. Specifically:

Who does what, week by week? A real plan has named roles and named weeks. A vague plan has neither.
What’s the fall-back if cutover goes wrong? A real plan can roll back to the previous state. A vague plan assumes nothing will go wrong.
What documentation do you produce? A real plan produces a full network and service inventory. Demand to see a sample from a previous transition (with the client name redacted).
What credentials and ownership transfer? Microsoft 365 tenant ownership should be in your firm’s name, not the IT firm’s. If your existing provider holds tenant ownership “for convenience,” that needs fixing during the transition.
What happens to the existing provider’s documentation? It should be requested in writing and reviewed for completeness. Gaps should be filled before cutover, not after.

Warning signs the transition will go badly

The honest list:

The provider promises a transition in less than four weeks for a 50-person firm. This is achievable only by skipping discovery or stabilisation. You’ll feel it in month three.
The provider doesn’t ask to see your existing contract. Contract terms — particularly notice periods, data-return obligations, and exit cooperation clauses — drive the transition timeline. A provider who doesn’t ask hasn’t planned around them.
No named technical lead for your account. “Our team will handle it” is not a plan. A specific named person should own the transition.
The provider proposes to migrate your Microsoft 365 tenant. In almost all cases, you don’t move tenants — you transfer admin access and ownership. A provider proposing tenant migration is either confused or planning to lock you in via their own tenant.
No first-month settle plan. A transition that ends at cutover is half-done. Real transitions have a structured first 30 days post-cutover.

What you should hear from your existing provider

Most managed-IT contracts have exit-cooperation clauses. A reputable existing provider will:

Provide a complete inventory of devices, accounts, services, and credentials
Transfer Microsoft 365 admin ownership to your nominated successor
Cooperate on a knowledge-transfer call covering known issues, custom configurations, and quirks
Honour the notice period without quietly degrading service

If your existing provider becomes uncooperative the moment you give notice, that’s a signal you should have switched sooner — and a signal to be conservative about how much notice you give. Most firms time the notice for the same date they sign with the new provider, so the gap closes immediately.

When not to switch

The transition is real work and not always worth it:

You’ve been with your current provider less than 18 months. Most relationships need that long to find their rhythm. Don’t switch in year one unless something is fundamentally wrong.
The price gap is the only reason. Saving 15% on a managed-IT contract is rarely worth the disruption risk. Switch for fit, capability, or culture — not pricing alone.
You’re about to do something else disruptive — an office move, a merger, a major software rollout. Stack disruptions are rarely well-tolerated. Sequence them.

If none of those apply and the relationship isn’t working, the right time to start the conversation about switching is now. The longer a misaligned IT relationship continues, the harder the eventual unwind.