Plan a Microsoft 365 Tenant-to-Tenant Migration After a Merger
Question details
Plan the consolidation of two Microsoft 365 tenants while preserving email addresses, mailboxes, users, and access to existing data.

- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- After a merger, the acquiring company wants its tenant to absorb the acquired company's tenant.
- Observed behavior
- Users should be able to access their migrated mailboxes and data in the acquiring company's tenant and continue receiving mail at their existing addresses.
Confirm administrator access to both tenants and the acquired company's DNS registrar. Inventory domains, users, licenses, mailboxes, and data locations, including SharePoint, OneDrive, and Teams.
Plan and execute a phased Microsoft 365 tenant migration
Use the acquiring company's tenant as the destination and coordinate identity, mailbox, data, and domain cutover.
A custom domain can be associated with only one Microsoft 365 tenant at a time. Plan the domain release and re-verification alongside mailbox migration and mail routing; the exact order depends on the chosen migration method.
Mailbox migration does not automatically migrate all SharePoint, OneDrive, Teams, application, or permission settings. Include each workload in the migration plan.
In the Microsoft 365 admin center for each tenant, review Users, Groups, Billing, and Settings > Domains. Record mailbox addresses and aliases, licenses, domain dependencies, and access requirements.
Review Microsoft's cross-tenant mailbox migration documentation and its licensing and configuration prerequisites. Alternatively, evaluate a specialized migration tool for the required workloads, coexistence, and cutover schedule.
In the target tenant's Microsoft 365 admin center, prepare users and assign appropriate licenses according to the chosen migration method. Map source identities to target identities and plan how users will sign in.
Use the selected migration tool or Microsoft's documented migration process to pilot mailbox moves, then migrate remaining users in batches. Migrate SharePoint, OneDrive, and Teams data separately as needed, and test access and permissions.
In the source tenant's Microsoft 365 admin center, remove the acquired domain from dependent objects and release it. Add and verify it under Settings > Domains in the target tenant, assign the required addresses and aliases, and update MX and other DNS records at the DNS provider according to the cutover plan.
Send test messages to the retained addresses, check mailbox and data access, and confirm users can sign in to the target tenant. Retire the source tenant only after validating the migration and resolving remaining dependencies.
Work with Office Documents in WPS Office After Your Migration
WPS Office is a free, lightweight alternative with a familiar interface and compatibility with common Microsoft Office formats, making it easier to continue working with documents after a migration. It does not perform Microsoft 365 tenant or mailbox migrations.

Frequently Asked Questions
Can both Microsoft 365 tenants use the acquired company's domain at the same time?
No. A custom domain can be associated with only one Microsoft 365 tenant at a time. Remove its dependencies and release it from the source tenant before adding and verifying it in the target tenant.
Will users keep their old email addresses after the migration?
They can keep them if the acquired domain is transferred to the target tenant and the addresses and aliases are assigned to the appropriate accounts. Update mail routing and test delivery after cutover.
Does moving mailboxes also migrate Teams and SharePoint data?
Not necessarily. Inventory Teams, SharePoint, and OneDrive content separately, choose a migration method for each workload, and verify permissions and access in the target tenant.
Is forwarding required after the domain moves?
Not necessarily. Once the domain, addresses, and MX routing point to the target tenant, mail can be delivered there directly. Temporary forwarding or other coexistence routing may be useful during migration.




