Tagged: Tenant Migration
12/31/2020 at 6:31 AM #359534
Mostly in the business acquisition scenarios, the need to perform tenant to tenant migration rises. Or for any reason, if you are performing tenant-to-tenant migration it is not as straightforward a task as it seems. To manually execute the migration, you have to do many preparations, following prerequisites, and need expertise for the task. To get rid of migration hurdles, using a third-party professional tool is always a wise decision. Shoviv Exchange Server Suite is an advanced and efficient utility for migration. Using it, a user can effortlessly migrate from tenant to tenant. There is no limit in terms of mailbox size, and it executes migration without any restriction. Multiple user-centric features are also within the software. Any user can check the working of the software using the free trial version.
For more information visit – https://www.shoviv.com/blog/tenant-to-tenant-migration/01/09/2021 at 12:40 PM #362699
Step 1. Domain Preparation
Prepare the domain with the following steps:
Ensure that you have enough licenses for the target Office 365.
Create admin accounts in both the source and target to perform the migration smoothly.
Create user mailboxes, room/resource mailboxes, and distribution groups in the target.
If needed, perform AD DS consolidation using AD DS tools and sync source domain with the target domain manually or using synchronization.
Train your end users regarding the post-migration use of Office 365.
Step 2. Domain verification
Start verification of target tenant domain in Office 365.
Add a source domain in the target Office 365 admin center and create TXT records in DNS.
Make sure the domain is in use only one tenant. Otherwise, the verification will fail.
After performing these steps, it will take around 72 hours for the change to be seen.
Step 3. Migration Scheduling
Generate a list of user mailboxes that are to be migrated and create a CSV file for mapping.
Note the lowest value of TTL on MX record (of the primary email domain).
Disable directory sync for source tenant (from Office 365 admin center).
Step 4. Migration Stage
Stop inbound mail flow
Stop inbound mail flow to the source tenant by changing the primary MS record to an unreachable value or by using a third-party service. As you have noted the lowest value of TTL on MX record (of primary email domain) in your preparation step, you can plan the time of this step easily.
Source tenant preparation
Before moving the Office 365 mailbox to another tenant, the primary mail domain should be erased from all objects in the source tenant.
Reset the default email address to the initial email address of office 365.
Remove all the Lync licenses from the source tenant with the help of Lync Admin Portal.
Reset the default email address of distribution lists, rooms, resources to the initial domain.
Remove the secondary email address from all tenant objects.
In the Windows PowerShell, run the command Get-MsolUser -DomainName xyz.com that will retrieve all the objects still using the primary email address or refusing the removal.
Preparing the target domain
It involves verifying the source tenant in the target domain (do one hour after the previous step).
Configure the auto-discover CNAME.
When you use AD FS, you’ll have to configure a new domain in target tenant for AD FS.
Activate the new user accounts in the target domain and assign licenses.
On the new users, set the source domain as the primary email address (done using Windows PowerShell). Also, decide on communicating the passwords to end users.
When the user mailboxes are active, change the mail routing and point the MX record to the new Office 365 email address.
Test the mail flow in and out of the target tenant.
You must be logged in to reply to this topic.