How to Merge Microsoft 365 Tenants After an Acquisition
Question details
The user needs to consolidate an acquired Microsoft 365 tenant into an existing tenant without manually transferring each account where possible.

- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- An organization is moving users and data from an acquired tenant into its established Microsoft 365 tenant.
- Observed behavior
- Microsoft 365 does not provide a single built-in tool that merges every service and data set across two tenants.
Inventory users, mailboxes, OneDrive accounts, Teams, SharePoint sites, domains, licenses, permissions, and compliance requirements in both tenants. Confirm administrator access and decide how source users will map to destination accounts before scheduling the migration.
Use a Third-Party Service for a Coordinated Tenant Migration
Use a migration service when you need to move many mailboxes and OneDrive accounts without handling each export and import manually.
In the Microsoft 365 admin center, create or confirm destination users and assign the licenses needed for their mailboxes and OneDrive accounts.
In a service such as BitTitan MigrationWiz, create a migration project and configure source and destination connections using the provider's current setup instructions.
Add or import the source-to-destination user mappings in the migration project, then run a pilot with a small group and check mailbox and file access.
Use the service's migration controls to move the selected workloads. Review its reports and check representative mailboxes and OneDrive files in the destination tenant.
Plan separate procedures for Teams, SharePoint, permissions, compliance settings, and domain cutover. Verify which of these the chosen service supports before migrating them.

Migrate Mailboxes and OneDrive Files With Separate Microsoft Methods
Use workload-specific Microsoft methods when you prefer native tools or have a smaller migration.
Work With Office Files in WPS Office After Migration
WPS Office is a free, lightweight alternative for working with documents after a tenant migration. Its familiar interface and Microsoft Office format compatibility make it easier for users to continue working with existing files. It does not migrate Microsoft 365 tenants.

Frequently Asked Questions
Can Microsoft 365 merge two tenants automatically?
No single built-in tool merges every Microsoft 365 workload. Plan separate methods for Exchange mailboxes, OneDrive, Teams, SharePoint, and tenant settings, or evaluate a third-party migration service.
Can I move mailboxes without exporting each one to PST?
Yes. Microsoft cross-tenant mailbox migration supports migration batches after the required tenant relationships, user mappings, and licensing are in place. A third-party service may also support batch migration.
Will OneDrive sharing permissions move with the files?
Not necessarily. Copying files with the OneDrive sync client or Power Automate may not preserve all sharing permissions or metadata. Test your chosen method and review access in the destination.
When should I move the acquired company's domain?
Plan the domain cutover after checking dependencies and migration timing. A custom domain can be associated with only one Microsoft 365 tenant at a time, so it must be removed from the source before it can be added to the destination.
Do Teams and SharePoint move with Exchange mailboxes?
No. A mailbox migration does not automatically move Teams and SharePoint content. Inventory those workloads and check the capabilities of your chosen migration method separately.




