Guide
Tenant-to-tenant Microsoft 365 migration: why it costs more
Updated
Both sides are already Microsoft 365, so it sounds like the simplest case. It is usually the most involved one, because you are moving identity and domains as well as data.
Why it is harder than an on-premises move
- Identity moves too. Users exist in a source directory and must exist correctly in the target one, with matching attributes so mailboxes attach to the right accounts. Microsoft documents cross-tenant mailbox migration as its own process for exactly this reason (Microsoft Learn).
- A domain can only live in one tenant. Releasing a domain from the source tenant and verifying it in the target is a sequenced operation with a hard cutover moment, not a gradual transition.
- Coexistence has to work in the middle. While some users are in each tenant, mail flow, free/busy calendar lookup and directory search need to work across both, and that is configuration effort in its own right.
- Everything else is in scope by implication. Teams, SharePoint sites, OneDrive content, Power Platform items and any application using the old tenant for sign-in all need a plan.
- Two organisations, two change controls. The commercial reality of a merger or divestment is that the source side may have limited motivation and a fixed end date. That is a project risk, and risk is priced.
The sequencing that drives the plan
- Discovery on both sides. Users, mailboxes, shared and resource mailboxes, groups, sites, licence position and any application dependency on the source tenant.
- Target preparation. Accounts created with the attributes the migration tooling needs, licences assigned, policies aligned.
- Pre-seeding. Data copied ahead of cutover so that the final synchronisation is short, which is what keeps the cutover window survivable.
- Domain cutover. The source releases the domain, the target verifies it, and mail flow switches. This is the irreversible moment and it is normally done out of hours.
- Delta sync and hypercare. Final catch-up of anything that changed, then a supported period while users find the things that did not come across as expected.
What to pin down in the quote
- Which workloads are in scope
- Mail alone, or mail plus OneDrive, SharePoint and Teams. Each addition is a separate workstream with its own tooling.
- Length of coexistence
- How long both tenants run with cross-tenant mail flow and calendar lookup working, and what that costs per week if the date slips.
- Who owns the source side
- Named responsibility for the source tenant's administrative actions, with dates. This is where these projects usually stall.
- Rollback position
- What happens if the domain cutover goes wrong on the night, and how long the agreed recovery window is.
- Licence overlap
- Both tenants are licensed during coexistence. Whose budget carries that, and for how long, should be settled before the project starts, not during it.
Where a divestment has a contractual separation deadline, the deadline itself is a cost driver: compressed timelines mean more people, more out-of-hours work and less room to stage the risk.