How to Perform Microsoft 365 Tenant-to-Tenant Migration for Email and OneDrive
Question details
The user needs to migrate users, emails, and OneDrive data from one Microsoft 365 tenant to another due to an acquisition involving different domains and subscription plans.

- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Post-acquisition IT integration requiring data migration from a Microsoft 365 E5 tenant to a Business Standard tenant with a different domain.
- Observed behavior
- Users and data currently reside in the source tenant and need to be fully transferred and accessible in the destination tenant under new organizational boundaries.
Ensure you have Global Administrator privileges in both the source and destination Microsoft 365 tenants, and verify that the destination tenant has sufficient licenses for the incoming users.
Use Microsoft Native Cross-Tenant Migration Tools
Microsoft provides native cross-tenant mailbox and OneDrive migration capabilities designed specifically for mergers and acquisitions.
Cross-tenant migration allows you to seamlessly move Exchange Online mailboxes and OneDrive files between two different Microsoft 365 environments. This process requires careful planning, identity mapping, and PowerShell configuration to ensure a smooth transition across domains.
Verify both the source and destination domains in your Microsoft 365 admin center. Configure Microsoft Entra ID (formerly Azure AD) cross-tenant access settings to establish trust between the two organizations.
Prepare the user identities by synchronizing users from the source tenant to the destination tenant. They must be created as Mail Users in the destination tenant before migration.
Open Exchange Online PowerShell and set up the migration endpoints. Configure the organizational relationships and sharing policies between the two tenants to authorize the data transfer.
Navigate to the Exchange admin center, or use PowerShell, to create migration batches for mailboxes and OneDrive accounts. Start the batches to begin copying data in the background.
Once the initial data synchronization is complete, verify the transfer. Complete the final cutover for the migration batches and assign the appropriate Microsoft 365 Business Standard licenses to the newly migrated users.

Switch to WPS Office for a Seamless Post-Migration Experience
Managing licenses during a Microsoft 365 tenant migration can be complex and costly. WPS Office provides a lightweight, highly compatible, and free alternative to Microsoft Office, allowing your team to open, edit, and save Word, Excel, and PowerPoint files without the heavy subscription fees.
- 1. Download the software: Visit the official WPS Office website and download the free installation package for your operating system.
- 2. Install WPS Office: Run the installer and follow the quick on-screen instructions to set up the software on your newly migrated devices.
- 3. Access your files: Open WPS Office and instantly access, edit, or save your migrated OneDrive and local documents without formatting issues.

Frequently Asked Questions
Does a cross-tenant migration transfer my Microsoft Teams data?
Native cross-tenant mailbox and OneDrive migration tools do not automatically transfer Microsoft Teams chat history or channel data. You will need to use third-party migration tools or specific Teams migration APIs for complete Teams integration.
Can I migrate from an E5 license to a Business Standard license directly?
Yes, the data migration itself is independent of the license type. However, you must ensure the destination Business Standard licenses have enough storage capacity (typically 1TB for OneDrive and 50GB for mailboxes) to accommodate the data coming from the larger E5 accounts.
Will users experience downtime during the tenant migration?
Users may experience a brief interruption when the final cutover occurs and DNS records (like MX records) are updated. However, the initial data synchronization happens in the background without affecting their current workflow in the source tenant.




