Short answer
Most Microsoft 365 tenant-to-tenant migrations for SMB and mid-market organizations take 6 to 16 weeks from kickoff to final cutover. Small tenants under a few hundred users can finish in 4 to 8 weeks. The schedule depends on data volume, domain moves, Teams and SharePoint complexity, identity design and how many waves the business can absorb. A firm date is set after discovery.
Key facts
- Typical range: 6 to 16 weeks for SMB and mid-market tenants, after a 1 to 3 week discovery.
- Discovery and planning usually take 20 to 30 percent of the total schedule.
- Users are normally moved in waves of 50 to 300, with a pilot wave first.
- Moving a primary email domain forces a coordinated cutover window that shapes the whole plan.
- SharePoint, OneDrive and Teams content, not mailboxes, is usually what stretches the timeline.
Typical timelines by size
Timelines below assume a dedicated project team, a decided target identity design and business owners who can approve wave schedules quickly. They run from project kickoff to final cutover and exclude post-migration cleanup.
These are ranges, not quotes. Two tenants with the same user count can differ by weeks because one has 200 GB of SharePoint data and the other has 8 TB.
| Tenant size | Typical duration | Usual wave pattern |
|---|---|---|
| Under 250 users | 4 to 8 weeks | Pilot plus 1 to 2 waves, or a single weekend cutover |
| 250 to 1,000 users | 6 to 12 weeks | Pilot plus 3 to 5 waves |
| 1,000 to 3,000 users | 10 to 16 weeks | Pilot plus 5 to 10 waves |
| 3,000+ users or multiple source tenants | 4 to 9 months | Phased by business unit or region |
The phases and how long each takes
Every tenant-to-tenant project follows roughly the same arc. The length of each phase varies, but skipping one usually costs more time than it saves.
- Discovery, 1 to 3 weeks: inventory mailboxes, shared mailboxes, groups, Teams, SharePoint sites, OneDrive volumes, domains, apps using Entra ID sign-in and devices.
- Design, 1 to 2 weeks: target identity model, UPN and domain plan, licensing, coexistence approach, tool choice and wave plan.
- Build and pilot, 1 to 3 weeks: create or sync target accounts, configure cross-tenant trust or tooling, set up free/busy sharing and run a pilot wave of IT and friendly users.
- Waves, 2 to 10 weeks: pre-stage content days ahead, then run delta syncs and cut users over in planned windows.
- Domain cutover and cleanup, 1 to 2 weeks: move the email domain, update MX and Autodiscover, fix stragglers and decommission source services.
What makes a migration take longer
Most delays come from decisions and dependencies, not data transfer speed.
- Large SharePoint and OneDrive estates, especially with deep folder structures, long paths or broken inheritance.
- Teams with heavy private and shared channel use, which need more planning than standard channels.
- Undecided identity design, for example whether users keep their old UPN or adopt the acquirer's domain.
- On-premises Active Directory in the source or target, which means Entra Connect or Cloud Sync changes and attribute matching.
- Line-of-business apps that use Entra ID sign-in, SMTP relay or hardcoded mailbox addresses.
- Legal holds, retention policies and eDiscovery cases that must be preserved or recreated.
- Change freezes around quarter-end, payroll or seasonal peaks that limit cutover windows.
What can shorten it
A clean source tenant, an early decision on the target domain and a business sponsor who can approve wave dates without long review cycles all compress the schedule.
Pre-staging is the biggest technical lever. Copying mailbox and file content days or weeks ahead means cutover night only moves recent changes. Archiving or deleting stale SharePoint sites before migration also cuts volume, sometimes by a large share.
Closing date pressure is real in M&A, but compressing the plan by skipping the pilot wave tends to push problems into production waves, where they are slower to fix.
How the domain move shapes the schedule
A verified domain can only exist in one Microsoft 365 tenant at a time. If users keep their existing email domain, the domain must be removed from the source and added to the target during a planned window, and every object using it in the source must be renamed first.
That makes the domain move a single coordinated event, usually on a weekend, and it often defines the final wave. Projects that let users adopt the acquirer's domain can move users in flexible waves and avoid that constraint, which is one reason some organizations rebrand addresses during the move.
How Accred Consulting approaches it
Accred Consulting starts every tenant-to-tenant project with discovery, then issues a proposal with clear scope, a fixed price and a timeline built around your wave plan and business calendar. Our US-based specialists run the pilot and every production wave directly, with structured check-ins at each stage. In one engagement we consolidated about 1,200 users after an acquisition in 8 weeks across 6 waves with no all-hands outage. Handover includes documentation and knowledge transfer, and optional support retainers cover the weeks after cutover.
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
Want this scoped for your environment?
Book a free consultation. After discovery you get a written plan with scope, a fixed price and a timeline.
Book a free consultation