Migrate One Exchange Organization to Two Microsoft 365 Tenants
Question details
Two companies sharing one Active Directory forest and Exchange organization need to migrate their mailboxes to separate Microsoft 365 tenants while accounting for existing directory synchronization.
- Product
- Microsoft Exchange Server, Exchange Online, and Microsoft 365
- Device & OS
- not provided
- Scenario
- Users from each company are already synchronized to their respective Microsoft 365 tenants through separate Azure AD Connect configurations.
- Observed behavior
- The desired outcome is to move each company's mailboxes into its own tenant without disrupting identity synchronization, mail routing, or recipient management.
Review each Azure AD Connect configuration's synchronization scope and map every mailbox, SMTP domain, and target tenant. Confirm that your Exchange version and proposed hybrid topology meet Microsoft's current requirements before running the Hybrid Configuration Wizard.
Plan and execute a phased hybrid migration for each company
Use this approach to account for users who are already synchronized, rather than attempting a cutover migration alongside Azure AD Connect.
The proposed approach is to migrate the first company using Minimal Hybrid, then retire or reconfigure that hybrid setup when appropriate before migrating the second company. Validate the sequence against Microsoft's current multi-tenant hybrid guidance; removing a hybrid configuration does not automatically make synchronized users cloud-managed.
In each tenant's Microsoft 365 admin center, open Settings > Domains and check the domains assigned to that company. In each Azure AD Connect configuration, review domain and OU filtering to confirm that the intended users synchronize to the correct tenant. Resolve overlapping synchronization scopes before proceeding.
Run the Exchange Hybrid Configuration Wizard and sign in to the first company's target tenant. Select Minimal Hybrid if it is available and appropriate for your migration requirements. Confirm the selected Exchange servers, credentials, and migration connectivity before completing the wizard.
In the first tenant's Exchange admin center, open Migration and create a migration batch for the first company's mailboxes using the configured hybrid migration endpoint. Complete the batch after synchronization, then test mailbox access, internal and external mail flow, and Autodiscover.
Open the on-premises Exchange admin center and review the hybrid configuration, connectors, and organization relationships against Microsoft's hybrid-removal guidance. Remove or adjust only components that are no longer needed, preserving anything required by remaining mailboxes or shared services. Then run the Hybrid Configuration Wizard for the second tenant using a supported topology.
In the second tenant's Exchange admin center, open Migration and create and complete the appropriate mailbox migration batches. After validating both companies, inventory remaining on-premises mailboxes, SMTP relay dependencies, and recipient-management requirements. Follow Microsoft's Exchange decommissioning guidance before removing servers or changing directory synchronization.
Validate third-party migration tools before replacing hybrid mailbox moves
Use this option when considering BitTitan, SkyKick, or another migration provider instead of native Exchange mailbox moves.
Organize Your Microsoft 365 Migration Plan with WPS Office
WPS Office is a free, lightweight alternative to Microsoft Office productivity apps, with a familiar interface and Microsoft Office file compatibility for an easy transition. Use it to maintain mailbox inventories, migration checklists, and handover documents; it does not migrate Exchange mailboxes or configure Microsoft 365 tenants.
Frequently Asked Questions
Can I use a cutover migration when users are already synchronized through Azure AD Connect?
Do not use cutover migration alongside the existing Azure AD Connect setup for this scenario. Plan hybrid mailbox moves instead, beginning with a review of synchronization scopes and the supported topology before running the Hybrid Configuration Wizard.
Does removing hybrid make all migrated users cloud-managed?
No. Removing Exchange hybrid configuration does not turn off directory synchronization or automatically change the source of authority. Review Azure AD Connect and Microsoft's identity-management guidance separately before making changes.
Should I change remote mailbox attributes after migration?
Do not clear or rewrite remote mailbox attributes as a routine cleanup step. If directory synchronization continues, use supported Exchange recipient-management tools and follow Microsoft's guidance for your chosen management model. Incorrect attribute changes can affect addresses, routing, or recipient provisioning.
Can both tenants use the same custom SMTP domain?
A custom domain generally cannot be verified in two Microsoft 365 tenants at the same time. Check Settings > Domains in each Microsoft 365 admin center and establish a supported domain and mail-routing plan before moving mailboxes.
Can WPS Office perform this Exchange migration?
No. WPS Office can help you create the migration inventory and runbook, but mailbox moves require Exchange migration tools or a supported third-party service. Start native mailbox moves from Migration in the target tenant's Exchange admin center after configuring the required connectivity.
