How long does a Microsoft 365 migration take?

Key facts

• Data copy time is rarely the bottleneck; planning, testing and change management are.
• Pre-staging data before cutover keeps cutover windows short.
• Each extra cutover wave adds calendar time but lowers risk.
• Device re-enrollment and identity changes often set the critical path.
• A realistic schedule comes from discovery, not from user count alone.

Typical ranges by migration type

These are typical ranges for SMB and mid-market organizations. Your schedule depends on the drivers in the next section.

What makes it take longer

The calendar is driven by decisions and dependencies more than by copy speed.

• Waiting on decisions: domain ownership, naming, site structure, retention
• Identity changes such as new UPNs or a new Entra Connect configuration
• Many sites or time zones that need separate cutover windows
• Large archives or file shares with broken or deeply nested permissions
• Apps and devices that relay mail and must be reconfigured
• Change freezes, month-end close, or deal-driven blackout dates

The phases and how long each takes

Discovery and planning usually take one to three weeks. Tenant preparation, such as identity, security baselines and mail flow design, runs alongside. Pilot migration with a small group follows, then production waves. Data is pre-staged in the background so each cutover only syncs recent changes. Hypercare after the final wave typically runs one to two weeks.

Compressing the plan is possible, but cutting the pilot or testing is where most outages come from.

Real examples

In anonymized projects, an organization of about 180 people moved mail, calendar and Drive from Google Workspace in five weeks. A professional services firm consolidated about 1,200 users after an acquisition in eight weeks across six waves. An Exchange hybrid free/busy change for about 460 mailboxes took four weeks. Each schedule was set after discovery.

How to shorten the timeline safely

Make decisions early, give the migration team admin access promptly, and assign an internal owner who can approve changes. Clean up stale mailboxes and old file shares before migration so less data moves. Communicate cutover dates to users early. These steps cut weeks without adding risk.

Planning around hard deadlines

Many migrations have a fixed end date: a Google Workspace renewal, an Exchange Server reaching end of support, a hosting contract expiring, or a transition services agreement after an acquisition. Work backward from that date. Leave room for a pilot, at least one buffer week before the deadline, and hypercare after the last wave.

If the date is too tight for the full scope, split it. Move mail and calendars first to meet the deadline, then move files, Teams and devices in a second phase. Many tenants can coexist for a period with free/busy sharing and mail routing in place, which takes pressure off the cutover. Ask for this phasing to be written into the plan rather than improvised late.

How Accred Consulting approaches it

Accred Consulting sets the schedule after Discovery, once mailboxes, data volumes, identity, devices and mail dependencies are inventoried. The Proposal states clear scope, a fixed price and a timeline, including wave dates. Delivery runs with structured check-ins so slippage is visible early, followed by Handover with documentation and knowledge transfer. Clients work directly with US-based specialists. Past anonymized projects include a 1,200-user consolidation in 8 weeks and a 180-person Google Workspace move in 5 weeks.

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