Traditionally, when Exchange Online tenants had to move mailboxes to another tenant within the same service, there was a need to off board them from the source tenant and import data into the target tenant. Such tenant-to-tenant migrations typically involved the use of third-party tools and\/or significant on-premises infrastructure dependency. Microsoft has introduced the new cross-tenant mailbox migration feature with which administrators can move mailboxes across the source and target tenants. This minimizes dependencies in their on-premises systems and eliminates the need to off-board and onboard mailboxes. In this article, we will explain the process involved in cross-tenant mailbox moves.<\/p>\n
The cross-tenant Exchange mailbox migration feature uses an invitation and consent model to establish an Azure Active Directory (Azure AD) application used for authentication between the two tenants. Cross tenant migration moves also require organization relationships, migration endpoints, and other components. Here are the prerequisites for Microsoft 365\/ Office 365 cross-tenant migrations.<\/p>\n
At a high level, the following configuration actions have to be performed in the target tenant for Office 365 cross tenant migration.<\/p>\n
After the target admin setup is complete, the source tenant has to be prepared for cross tenant migration with the Exchange mailbox migration feature.<\/p>\n
The process of performing cross-tenant Exchange mailbox migrations is similar to onboarding migration batches migrating from Exchange on-premises to Office 365\/Microsoft 365. After setting up the necessary prerequisites, such as tenant relationships and configuration settings, admins with the Move Mailbox management role can use the New-MigrationBatch cmdlet to migrate mailboxes between tenants. The admin of the target tenant initiates the move to pull mailboxes after the necessary tenant authorization checks in a process that is similar to on-premises to cloud migrations. Mail users are finally updated with the target tenant address.<\/p>\n
While the cross-tenant Exchange mailbox migration feature simplifies Office 365 tenant-to-tenant migrations significantly, it has its drawbacks. The feature is initially only available with PowerShell as of now and requires technical knowledge to trigger important moves. Additionally, it cannot perform Microsoft Teams tenant-to-tenant migration or migrate Auto Expanded archives.<\/p>\n
As a Tier 1 Microsoft CSP,<\/strong> Apps4Rent offers comprehensive Office 365 tenant-to-tenant migration<\/a> to move Teams, SharePoint, OneDrive, and other components apart from Exchange Online as a part of our managed services. Contact Microsoft-certified Office 365 cloud migration consultants, available 24\/7 via phone, chat, and email for assistance. <\/p>
\n<\/a>
\n\n<\/ul><\/div>\n