Office 365 Tenant to Tenant Migration: A Comprehensive Guide
Office 365 tenant to tenant migration, also called cross-tenant migration, is the process of moving emails and data from one Microsoft Office 365 account to another. This generally happens when companies combine, acquire, buy another company, rebrand, or go through big changes in how they’re organized. However, in this article, we’ll show you the way to prepare Office 365 accounts for a smooth migration with minimal disruption to business operations.
Microsoft 365 is a tool numerous businesses use all over the world, so when things like merges or any changes needed in an O365 tenant, moving data from one account to another becomes very important. But this kind of migration needs careful planning to make sure everything works right, and that nothing is lost or broken.
Although moving Office 365 data from one account to another might feel hard, it’s possible to do it well with the right preparation.However, you can make the move much easier, If you plan ahead and take it step by step. This guide gives you tips and advice on how to do the migration so everything is set up rightly once the move is complete.
Table of Content
When you need to move mailboxes from one Office 365 account to another, you’re performing a tenant-to-tenant migration. This involves transferring all data from one Office 365 domain to another, including emails, contacts, calendars, and any rules set up. Although, the process can be quite complex and requires knowledge of Windows PowerShell, a tool used to manage and automate tasks within Office 365.
To move data between Office 365 accounts, you’ll use tools like Windows PowerShell, the Microsoft 365 Admin Center, and the Azure Web Portal. It’s really important to follow each step very carefully—
The first thing you need to do is to make sure that you have Global Admin access in both Office 365 accounts. If you don’t have the necessary permissions, it is good to request access from your administrator.
There are various factors that may necessitate cross-tenant migration in Office 365. Some of the primary reasons include:
The Office 365 subscription plan you choose will determine which apps and services are available to you as a Microsoft 365 tenant. For example, the Microsoft 365 Business Basic Plan grants you access to the following services and apps:
When performing an Office 365 tenant to tenant migration, it’s crucial to consider all the apps and services that need to be moved. This means migrating data not only from Outlook 365 mailboxes but also from services like OneDrive for Business, Teams, SharePoint.
There are two main ways to carry out the migration:
Using automated tools is typically more efficient and dependable. To ensure that everything runs properly, plan carefully, test the process before fully transferring, and consider seeking assistance from professional tools or service providers.
Before starting the office 365 tenant to tenant migration, there are several tasks that must be completed in both the source and target tenants. Below, we will outline the necessary steps to help guide you through this process.
Follow the steps below to create a mail-enabled security group in the source tenant.
Your Mail-enabled security group has now been created.
Be sure to copy the group name and email address and save them for later use.
To proceed, you need to locate and save the Tenant ID for both the source and target tenants.
Follow these steps:
You’ll see the application creation process in the top right corner.
Once the registration is complete, you’ll be directed to your application page. Be sure to save the Application name and Application (client) ID, as you will need them later.
The Mailbox.Migration permission will now be assigned to the application.
Set-ExecutionPolicy Unrestricted
Type Y and click enter when asking for permission.
# Enable customization if tenant is dehydrated $dehydrated=Get-OrganizationConfig | select isdehydrated if ($dehydrated.isdehydrated -eq $true) {Enable-OrganizationCustomization} $AppId = "[guid copied from the migrations app]" $Credential = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $AppId, (ConvertTo-SecureString -String "[this is your secret password you saved in the previous steps]" -AsPlainText -Force) New-MigrationEndpoint -RemoteServer outlook.office.com -RemoteTenant "[sourcetenant.onmicrosoft.com]" -Credentials $Credential -ExchangeRemoteMove:$true -Name "[the name of your migration endpoint]" -ApplicationId $AppId
Note: Replace [guid copied from the migration app] with the application ID and [this is your secret password you saved in the previous steps] with the client secret value. Also, replace [the name of your migration endpoint] with the migration endpoint name you wish to use. Be sure to save the endpoint name, as it will be needed later.
$sourceTenantId="[tenant id of your trusted partner, where the source mailboxes are]" $orgrels=Get-OrganizationRelationship $existingOrgRel = $orgrels | ?{$_.DomainNames -like $sourceTenantId} If ($null -ne $existingOrgRel) { Set-OrganizationRelationship $existingOrgRel.Name -Enabled:$true -MailboxMoveEnabled:$true -MailboxMoveCapability Inbound } If ($null -eq $existingOrgRel) { New-OrganizationRelationship "[name of the new organization relationship]" -Enabled:$true -MailboxMoveEnabled:$true -MailboxMoveCapability Inbound -DomainNames $sourceTenantId }
Note: Replace [tenant id of your trusted partner, where the source mailboxes are] with the Source Tenant ID that you copied earlier. Replace [name of the new organization relationship] with the desired name for the Organization Relationship. Make sure to save the relationship name, as it will be needed later.
https://login.microsoftonline.com/sourcetenant.onmicrosoft.com/adminconsent?client_id=[application_id_of_the_app_you_just_created]&redirect_uri=https://office.com
Note: Replace sourcetenant.onmicrosoft.com with your actual source tenant name, and substitute [application_id_of_the_app_you_just_created] with the application ID of the app you created.
$targetTenantId="[tenant id of your trusted partner, where the mailboxes are being moved to]" $appId="[application id of the mailbox migration app you consented to]" $scope="[email address of the mail enable security group we created]" $existingOrgRel = $orgrels | ?{$_.DomainNames -like $targetTenantId} If ($null -ne $existingOrgRel) { Set-OrganizationRelationship $existingOrgRel.Name -Enabled:$true -MailboxMoveEnabled:$true -MailboxMoveCapability RemoteOutbound -OAuthApplicationId $appId -MailboxMovePublishedScopes $scope } If ($null -eq $existingOrgRel) { New-OrganizationRelationship "[name of your organization relationship]" -Enabled:$true -MailboxMoveEnabled:$true -MailboxMoveCapability RemoteOutbound -DomainNames $targetTenantId -OAuthApplicationId $appId -MailboxMovePublishedScopes $scope }
Note: Replace the placeholder [tenant id of your trusted partner, where the mailboxes are being moved to] with the Tenant ID of the Target Tenant. Similarly, replace [application id of the mailbox migration app you consented to] with the Application ID of the migration app. For [email address of the mail-enabled security group we created], input the email address of the mail-enabled security group you set up. Finally, substitute [name of your organization relationship] with the name of the organization relationship created in the Target Tenant.
Create an organization relationship. However, after completing these steps, the next task is to create mail users in the Target Tenant for the cross-tenant migration. Let’s walk through how to do this.
Note: You must create a mail user for each mailbox you intend to migrate to the Target Tenant.
After creating mail users in the Target Tenant, update the ExchangeGuid and ExchangeLegacyDn of the source mailbox in the corresponding mail user in the Target Tenant.
Get-Mailbox [Source Tenant Mailbox Address] | fl Name,ExchangeGuid,LegacyExchangeDN
Note: Replace [Source Tenant Mailbox Address] with the email address of the source mailbox user and run the command for each user to retrieve their ExchangeGuid and ExchangeLegacyDN.
To complete the setup, you need to input the ExchangeGuid and ExchangeLegacyDN of the source user mailbox into the corresponding users in the Target Tenant.
Command:
Set-MailUser -Identity [email address of the Target user] -ExchangeGuid [ExchangeGuid of the source user]
Command:
Set-MailUser -Identity [email address of the Target user] –EmailAddresses @{add="x500:[LegacyExchangeDN of the Source user]"}
Note: Perform these steps for each user in the Target Tenant PowerShell.
Command:
Test-MigrationServerAvailability -EndPoint "[the name of your migration endpoint]" -TestMailbox "[Primary SMTP of Mail User object in target tenant]"
If there are any issues, the status will show as failed, indicating something is missing or incorrect.
The system will take some time to assign the licenses to all selected users.
Once the licenses are assigned, you can proceed to create the migration batch for cross-tenant migration.
All user mailboxes have now been successfully migrated to the Target Tenant. You will also receive an email notification once the cross-tenant migration process is complete.
Office 365 tenant to tenant migration is an important but complicated process that companies often need to do during things like mergers, acquisitions, or organizational changes. To move emails, data, and resources from one Office 365 account to another with as minimum disturbance as possible, it’s essential to follow a clear, step-by-step approach.
The key to a successful transfer is careful preparation, efficient setup, and the use of appropriate tools like PowerShell and the Microsoft 365 Admin middle. The strategy includes a variety of specialized activities, such as establishing mail-enabled security agencies, developing migration endpoints, and maintaining licensing. Each of these activities is crucial to maintaining data security and business continuity. Moreover, you can manage the new tenant more effectively, save money, and grow your business as needed if you plan ahead and have the right tools for a seamless transfer.
Q1. What is Office 365 Tenant Migration?
Ans: Office 365 Tenant to Tenant Migration refers to the process of transferring data, users, and mailboxes from one Office 365 tenant to another. This type of migration is often necessary during mergers, acquisitions, or when an organization switches its Office 365 subscription. It involves careful planning to ensure minimal disruption to services and to maintain data integrity.
Q2. Why Do I Need to Migrate From One Office 365 Tenant to Another?
Ans: There are several reasons for migrating from one Office 365 tenant to another, including business mergers, acquisitions, reorganizations, or changing domain names. Additionally, it may be required for consolidating multiple Office 365 tenants into one or for transferring data between different regions or subscription plans.
Q3. What Are the Challenges of O365 Tenant to Tenant Migration?
Ans: Challenges during Office 365 Tenant to Tenant Migration include data loss, extended downtime, user disruption, and configuration issues. Although, ensuring that all data, settings, permissions, and integrations transfer smoothly requires careful planning and expert execution. Some specific challenges are migrating shared mailboxes, public folders, and custom configurations.
Q4. How Long Does O365 Tenant to Tenant Migration Take?
Ans: The duration of a Tenant to Tenant Migration depends on the volume of data being transferred, the complexity of the migration, and the tools being used. Small-scale migrations may take a few days, while large or more complex migrations could take several weeks. It’s essential to plan and test the migration carefully to avoid unnecessary delays.
Q5. What Are the Best Practices for Office 365 Tenant to Tenant Migration?
Ans: Some best practices for a smooth Office 365 Tenant Migration include:
Email Facebook Twitter Linkedin Tumblr Reddit VK Pinterest Pocket
Manoj Dwivedi is a seasoned Technical Content Analyst with over a decade of experience in the IT industry. He specializes in creating in-depth guides, tutorials, and analyses on cloud computing, data migration, and IT infrastructure. When he’s not writing, Manoj enjoys exploring the latest tech trends and engaging with the IT community through forums and social media.
Your email address will not be published. Required fields are marked *
Comment *
Name *
Email *
Website
Save my name, email, and website in this browser for the next time I comment.
Comments
0 comment