How to Move a Microsoft 365 Domain Between Tenants and Preserve Email
Question details
The organization needs to transfer a custom domain from one Microsoft 365 tenant to another existing tenant while ensuring all user emails, Teams identities, OneDrive files, and SharePoint sites are securely migrated and preserved.

- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Migrating a custom domain along with all associated workloads (Exchange, OneDrive, SharePoint, Teams) from a source Microsoft 365 tenant to a destination tenant.
- Observed behavior
- The organization wants a seamless transition to the new tenant environment where users retain their original email addresses and data access without long disruptions.
Before initiating the migration, inventory all user mailboxes, SharePoint sites, and Teams data in the source tenant, and ensure you have Global Administrator credentials for both Microsoft 365 environments.
Perform a Manual Tenant-to-Tenant Migration
Use the Microsoft 365 Admin Center to manually transition the domain, configure user identities, and route emails to the new tenant.
A tenant-to-tenant migration requires carefully removing the domain from the source environment before it can be added to the destination. Because a domain can only exist in one Microsoft 365 tenant at a time, expect a brief period of mail routing disruption during the cutover.
Navigate to the Microsoft 365 Admin Center of the destination tenant. Pre-create the user accounts, prepare the necessary Microsoft 365 licenses, and set up target SharePoint sites to receive the data.
In the source tenant's Admin Center, navigate to Settings > Domains. Reassign all user aliases, groups, and resources away from the custom domain to the default '.onmicrosoft.com' domain. Once all dependencies are cleared, select the custom domain and click 'Remove domain'.
Log into the destination tenant's Admin Center, go to Settings > Domains, and click 'Add domain'. Enter your custom domain name and update your DNS host provider records to verify domain ownership in the new tenant.
In the Exchange Admin Center, assign the newly verified custom domain email addresses as the primary SMTP address for your users. This ensures the correct address displays in Microsoft Teams. Finally, test mail flow, sign-in capabilities, and file access.

Utilize a Third-Party Migration Tool
Use specialized migration software to automate the transfer of mailboxes, Teams data, and OneDrive files across tenants.
Looking for a Lightweight Alternative to Microsoft 365?
While Microsoft 365 is built for complex enterprise backend management and tenant structures, many teams and individuals simply need a reliable, affordable way to create and edit documents. WPS Office is a powerful, free alternative that offers seamless compatibility with Word, Excel, and PowerPoint files without the overhead of tenant administration.
- 1. Download WPS Office: Visit the official WPS website and download the installation package for your operating system.
- 2. Install and Launch: Follow the simple on-screen instructions to install the software, then launch WPS Office from your desktop.
- 3. Open Your Documents: Drag and drop any existing Microsoft Word, Excel, or PowerPoint files directly into WPS Office to continue working seamlessly.

Frequently Asked Questions
How long does it take to remove a domain from a Microsoft 365 tenant?
While the domain removal process usually completes within a few minutes in the Microsoft 365 Admin Center, it can take up to 24 hours for the change to fully propagate across all Microsoft backend services before you can add it to a new tenant.
Will emails bounce during a tenant-to-tenant domain migration?
Yes, there is typically a brief downtime window during the cutover phase when the domain is being removed from the source and verified in the destination. Emails sent during this specific window may bounce or be queued depending on the sender's mail server.
Can I keep both domains active in the destination tenant?
Yes. A single Microsoft 365 tenant can host multiple custom domains. You can have users with different primary email addresses (e.g., @abc.com and @def.com) operating within the same administrative environment.
Does Microsoft offer a native tool for tenant-to-tenant Teams migration?
Microsoft offers limited cross-tenant mailbox migration capabilities natively natively, but full Teams and SharePoint migrations typically require utilizing Microsoft's specific Cross-Tenant User Data Migration features (which may require additional licensing) or third-party migration tools.




