When you need it
A merger, acquisition, divestiture or rebrand leaves people in the wrong Microsoft 365 tenant. Their mail, files, chats and meetings have to follow them without losing history and without a week of disruption.
We run the move with Microsoft's native cross-tenant tooling (Migration Orchestrator, Cross-Tenant Identity Mapping, cross-tenant mailbox and OneDrive migration) or with Quest On Demand Migration and SPMT where they fit better, chosen against your workloads, data volume, compliance constraints and cutover window.
What is included
- Read-only discovery of both tenants: users, licences, mailboxes, holds, archives, OneDrive, Teams and domains
- Target design: identities, MailUsers, licensing order, scope groups and the batch plan
- Tenant configuration: migration app and consent, endpoint, organization relationships, Teams and OneDrive trust
- Identity mapping so every source user lands on the right target user
- Pilot batch with written acceptance before any production wave
- Batched production waves with nightly reconciliation and a cutover communication pack
- Hypercare, then cleanup of every permission, relationship and app the project created
How a migration runs
- 1Discover
Read-only assessment of both tenants and a risk-classified findings list.
- 2Plan
Batch plan, CompleteAfter dates, delegate grouping and rollback position, agreed in writing.
- 3Configure
Source and target tenants prepared in Microsoft's documented order.
- 4Pilot
Two or three test users moved end to end and signed off.
- 5Migrate
Production waves, validated before they start and reconciled every night.
- 6Close
Cleanup, handover documentation and a walkthrough with your team.
Limits we plan for, not discover
Mailboxes on hold cannot move until compliance approves the hold change. Target users must not have a mailbox or OneDrive before identity mapping. Delegates have to move in the same batch. OneDrive moves once with no delta. Shared Teams channels and SharePoint sites are out of scope for the orchestrator and need their own plan.
Our engineers run this with the Tenant-to-Tenant Orchestrator, our own app that generates every PowerShell step, checks each result and keeps all of these limits next to the step they affect.
Questions buyers ask
How long does a tenant-to-tenant migration take?
It depends on users, data volume and the cutover date the business needs. Exchange content pre-syncs with no user impact, so we usually submit batches about two weeks before cutover. The plan and dates are agreed in writing after discovery.
Do users lose email history, chats or files?
Mail, calendar, contacts and OneDrive content move with the user. Teams chats are copied, with some content types Microsoft does not migrate (for example reactions and messages over 4 MB). We give you the full list before cutover so nothing is a surprise.
What licences are needed?
Each migrating user needs Microsoft's Cross-Tenant User Data Migration licence on the source or target object, plus Exchange Online and Teams licences in both tenants.
Can you move our domain as well?
Yes, as a separate planned cutover. A domain can live in only one tenant at a time, so the domain move is scheduled with mail routing and user communication.
How is it priced?
Fixed price after a scoped discovery, with written inclusions and exclusions: 40% at start, 40% before production, 20% on acceptance.