Guide

Office 365 tenant migration UK cost: why tenant to tenant costs more

Updated

Both sides are already Microsoft 365, so it sounds simplest. It is usually the most involved, because identity and domains move as well as data.

Get migration quotes Two minutes of questions; up to three IT support and cloud migration providers scope your environment and quote you directly. Free, no obligation.

Tenant migration challenges

  • 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.

Microsoft tenant to tenant migration: what Microsoft charges for

Microsoft's own cross-tenant tooling is not free. It states that "Cross-Tenant migrations require a per user license (one-time fee)": a Cross Tenant User Data Migration add-on that also covers OneDrive migration.

Migrations fail without it, and Microsoft offers no exceptions. Its article does not state the price (Microsoft Learn, cross-tenant mailbox migration, read 2 November 2026).

  • What moves. Only user-visible mailbox content: email, contacts, calendar, tasks and notes. After a successful move the source mailbox is deleted.
  • What blocks a move. A mailbox on any type of hold is not migrated, and a user not set up correctly in the target tenant fails.
  • What breaks after. Microsoft lists Teams in the source tenant losing access to the migrated mailbox as a known issue.

The sequencing that drives the plan

  1. Discovery on both sides. Users, mailboxes, shared and resource mailboxes, groups, sites, licence position and any application dependency on the source tenant.
  2. Target preparation. Accounts created with the attributes the migration tooling needs, licences assigned, policies aligned.
  3. Pre-seeding. Data copied ahead of cutover so that the final synchronisation is short, which is what keeps the cutover window survivable.
  4. 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.
  5. 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.

Get quotes from Microsoft 365 migration partners

Two minutes of questions; up to three IT support and cloud migration providers scope your environment and quote you directly. Free, no obligation.

Where you are moving from

Current email platform

Include shared and resource mailboxes: this partly sets the route.

  • Free, no obligation
  • Your details go to at most three partners
  • Takes about two minutes

Questions, answered directly

What drives the cost of an Office 365 tenant migration in the UK?

Identity and domains moving as well as data, the workloads in scope (mail, OneDrive, SharePoint, Teams), and how long both tenants coexist. Add Microsoft's per-user Cross Tenant User Data Migration licence, a one-time fee whose price its article does not state. No UK partner in our index publishes a tenant to tenant fee; it is quoted per project.

Why does tenant-to-tenant migration cost more than moving from Exchange?

Because identity and domains move as well as data. Accounts must be created and matched in the target tenant. A domain is released by one tenant and verified in the other in a sequenced cutover. Mail flow and calendar lookup must work across both tenants during coexistence. An on-premises move has none of these workstreams.

How long does a tenant-to-tenant migration take?

It is driven by discovery quality, the number of workloads in scope and how quickly the source organisation acts, rather than by data volume alone. Pre-seeding data ahead of the cutover is what keeps the actual switch short; the elapsed project around it is normally measured in weeks to months.

Can users keep their email addresses in a tenant-to-tenant move?

Yes, where the domain itself moves. A domain can only be verified in one tenant at a time, so there is a defined cutover moment, not a gradual transition. A quote should set out how that release and re-verification is sequenced.

Is Microsoft Bookings included in a tenant to tenant migration?

Microsoft's cross-tenant mailbox migration article names only user-visible mailbox content, meaning email, contacts, calendar, tasks and notes, as what moves, and describes no process for Microsoft Bookings. Treat Bookings calendars and their services as a separate line in the scope and ask the partner how they will be rebuilt in the target tenant.

Sources

This site's own datasets, every figure quoted from its source and dated:

  • The M365 Licence Price Table carries 52 published figures read from 9 sources' own pages; the 36 published figures given by plan run from 1.73 to 49 GBP, read 14 November 2026.
  • The M365 Migration Price Index carries 3 published figures read from 3 sources' own pages, from 9.78 to 20 USD, read 14 November 2026.
  1. Microsoft Learn, ways to migrate multiple email accounts to Microsoft 365
  2. Microsoft Learn, Exchange Online migration best practices
  3. Microsoft Learn, cross-tenant mailbox migration
  4. Microsoft, compare Microsoft 365 business plans and current pricing

Get your migration scoped, then priced.

Two minutes of questions; up to three IT support and cloud migration providers scope your environment and quote you directly. Free, no obligation.

Get migration quotes