Is a zero-downtime Microsoft 365 migration realistic?

Key facts

• Pre-staging data means cutover only syncs recent changes.
• Mail should queue and deliver, not bounce, during MX changes.
• Users typically see a sign-in, profile or app reconfiguration step.
• Domain moves between tenants have a short window that needs careful planning.
• Waves and after-hours cutovers limit how many people are affected at once.

What downtime really means in a migration

Downtime can mean several different things, and it helps to separate them. Mail loss means messages bounce or disappear; this should never happen in a well-run project. Access interruption means users cannot open mail or files for a period; this can usually be kept to a planned window outside business hours. User friction means people restart Outlook, sign in again, register MFA or find files in a new place; some of this is almost always unavoidable.

When a provider promises zero downtime, ask which of these they mean.

Techniques that keep disruption minimal

Low-impact migrations combine several methods.

• Pre-stage mailboxes, OneDrive and SharePoint content days or weeks before cutover
• Run final delta syncs during the cutover window
• Lower DNS TTL values ahead of MX and Autodiscover changes
• Use coexistence such as Exchange hybrid or cross-tenant free/busy during waves
• Inventory and reconfigure apps, scanners and devices that relay mail
• Pre-register MFA and test Conditional Access with a pilot group
• Cut over in waves, outside business hours, with help desk ready the next morning

Where some disruption is hard to avoid

Some scenarios carry an unavoidable short window.

Real-world results

In an anonymized acquisition project, about 1,200 users were consolidated into one tenant across six waves in eight weeks with no all-hands outage. In an Exchange Server exit, an inventory of applications relaying mail found dependencies that would otherwise have broken at cutover. Both outcomes came from planning and inventory, not from a particular tool.

Questions to ask about downtime

Ask the migration team to describe exactly what users will see on cutover day, how long each step takes, what happens to inbound mail during DNS changes, and what the rollback plan is if a wave fails. Ask for this in the runbook, not just in a sales call.

Preparing users for cutover

Most perceived downtime is really confusion. Send users a short notice a week before their wave and a reminder the day before. Tell them what will change, what they need to do, and where to get help. Include simple steps for Outlook, mobile mail and Teams, and explain any new sign-in or MFA prompt.

Ask users to finish large uploads before the cutover window and to avoid creating new shared folders during it. Have help desk staff, or floor support at larger sites, ready on the first morning. A short pilot wave with friendly users helps refine these instructions before the main waves.

How Accred Consulting approaches it

Accred Consulting plans for minimal disruption rather than promising zero impact. Discovery inventories mail flow, relay apps, identity and devices so cutover surprises are found early. The Proposal sets scope, a fixed price and a timeline with wave dates. Delivery uses pre-staged data, planned cutover windows and structured check-ins. Handover includes documentation and knowledge transfer. Clients work directly with US-based specialists. One anonymized consolidation moved about 1,200 users in six waves over eight weeks with no all-hands outage.

Track record: 400+ client projects, 2,000+ migration workstreams and 150,000+ users migrated by a US-based team. Company facts · Case studies

Related questions