Centerpoint IT provides tenant to tenant Microsoft 365 migrations for organizations throughout Metro Atlanta. Get help from the experts.
Acquisitions, divestitures, merges, oh my! According to Deloitte’s Future of M&A Trends Survey, 61% of C-level executives expect merger and acquisition (M&A) activity to return to pre-COVID levels within the next 12 months. Microsoft Tech Community reports that Office 365 has more than 200 million monthly active users. What do these figures mean to you? Tenant-to-tenant migration is definitely on an upward trend.
With divestitures, M&As, data center relocations, and domain changes, Office 365 infrastructures and environments are consolidating and merging rapidly. This process of transferring data from one Office 365 environment to another is referred to as tenant-to-tenant (T2T) migration, and it’s not necessarily a breeze.
So, why do businesses want to go ahead with T2T migrations when the new infrastructure has the same capabilities and functionality as the source infrastructure? Three words: changing business requirements.
How to do it? T2T migration involves various steps. You’ll find the Pre-migration (preparation) stage and the migration process itself. Let’s show you the nitty-gritty below.
Before diving into the migration process, you need to go through the preparation stage, which involves multiple steps:
Here’s a detailed process of planning a T2T Microsoft 365 migration:
1. Preparing the domain
Domain preparation is all about preparing the target domain—where you want to move the source data. There should be sufficient space in the target domain to make the process a success. Does your target account have enough space? If yes, here’s what else you need to do:
2. Verifying The Domain
What should follow after the preparation stage is verifying the target domain. This is to affirm that you own this new domain.
Begin the verification process of the target tenant account in Microsoft 365. Then add a source domain to the target Microsoft 365 admin center to generate TXT records in DNS.
It’s very important to ensure that only the target tenant account uses the domain. Else the verification will hit a dead end. After following the verification process as required, it will take approximately three days for the changes to take effect.
3. Scheduling The Migration
First off, generate a list of user mailboxes that you want to migrate and a CSV file for mapping.
Secondly, note down the lowest value of Time To Live (TTL) on the MX record (of the primary email domain)
Lastly, you need to disable the Azure directory sync for the source tenant domain.
4. Performing The Migration
If you’ve planned your Office 365 T2T migration up to this point, well, there isn’t much to be performed on the day of the migration.
Broadly, there are three things left:
Still on the final step, here’s what else you need to do:
Congratulations, you’ve reached the end of the pre-migration stage! Time for the actual migration. You can choose between using PowerShell Scripts or third-party migration tools when executing your T2T data migration.
Our honest advice? Pick third-party migration tools as they offer complete control over the data migration process. Kernel Office 365 Migration is arguably the best tool in this regard.
Why Kernel Office 365 and not any other migrating tool? Because it:
Depending on the number of end-users, you can have two different migration methods:
If you have 500 end-users or more, it’s best to go for the multi-pass approach. Here, you transfer the data in multiple batches. This process takes quite some time, so you’re better off migrating calendars, contacts, and emails for a single week.
If you have 500 end-users or less, transfer the contacts, emails, and calendar separately to the target tenant mailbox. You’ll also want to limit the volume of mails transferred if you’re pursuing email migration. To achieve this, set a cut-off date, say six months.
Assuming you decide to use Kernel Office 365 to migrate user mailboxes, here’s the process involved:
It’s prudent to save the migration report in CSV format since it provides huge time-saving benefits during Office 365 T2T migrations.
There you have it!—a complete guide on Office 365 T2T migrations.
We understand how difficult—and costly—it is to a Microsoft 365 tenant to tenant migration. The complexities and nuances involved in migrating corporate data can be too much to handle, especially if your IT team has other equally important commitments.
That’s why our team is devoted to partnering with businesses across Atlanta and North Georgia to make the whole T2T migration process fuss-free, quick, and cost-effective. What are you waiting for? Give us a call today for inquiries or submit a support request online!