Cross Tenant Migration Microsoft 365: Best Practices & Requirements

“Hi, I need to understand the business side functional requirements for Microsoft 365 cross tenant migration for my business. Can you please suggest any resources? Books, a training module, or a reliable solution? Also, explain any challenges/lessons that I must learn from similar migrations? Thank you very much in advance.”

-Wide Enterpreneur658, r/Microsoft365, Reddit

M365 tenant migrations have become quite common with organizations handling divestitures, M&A, restructuring, and consolidations. Even though it is possible to perform cross tenant migration Microsoft 365 using the native Microsoft solution, the process requires much more. It’s not just about moving tenant mailboxes nowadays but also about preserving the originality, handling mailbox throttling, deduplication, delta syncs, etc. It is possible when you use a specialized solution like the SysInfo Microsoft 365 Tenant to Tenant Migration Tool to identify challenges and deal with them technically without loss or downtime.

Core Architecture of M365 Cross-Tenant Migration

Migrate email between two Microsoft 365 Tenants is a crucial step when transforming businesses. Enterprises need to migrate hundreds or thousands of users with data in TBs and business-critical work across Exchange Online, Mailboxes, SharePoint, and OneDrive. Therefore, it becomes essential to preserve productivity and data fidelity during the migration. 

Hence, to ensure that you can reduce migration risks during a Microsoft 365 tenant transfer, effective solutions are essential. This brings us to the two key migration solutions, i.e.:

  • Native Microsoft Solution: Ideal for users with technical proficiency and expertise in PowerShell cmdlets. 
  • SysInfo Microsoft 365 Migration Tool: A standardized method for large-scale migrations with granular control, better reporting, and automatic handling. 

To find out how to perform the migration appropriately, follow the step-by-step methods as explained here. But before that, ensure to fulfil the prerequisites as stated below. 

Pre-Migration Checklist to Follow

Before proceeding with the complex native tenant-to-tenant migration in M365, ensure the following:

  • Have active Microsoft 365 subscriptions with licensing 
  • Admin access for both tenant accounts (source and target)
  • Exchange Online configured and validated 
  • Reviewed identities, UPNs, SMTP addresses, and other 
  • Determine domains to keep, move, and DNS timelines
  • Assess mailbox size, permissions, status, and policies 
  • Lower TTL value, plan rollback, and run pilot migrations 
  • Mailbox migration and creating organizational relationships

Cross Tenant Migration Microsoft 365: Manual Route 

Microsoft offers native support for cross-tenant data transfers via Exchange Online. Organizations with Microsoft expertise and technical skills can follow this method after fulfilling the above prerequisites. Steps are:

  1. In Exchange Online (Microsoft Entra Admin Center), start by preparing the target tenant
  2. Create the Application Client ID and set the API Mailbox.Migration Permissions
  3. Further, create a new client secret and grant permissions for your target tenant. 
  4. Copy and secure the generated consent URL needed for the source tenant account. 
  5. After that, configure a trust relationship between the source and target tenants to authenticate migration requests. 
  6. Create new endpoints and build organizational relationships to move domain between Office 365 Tenants.
  7. Register the application and grant necessary permissions. Create a CSV with source and target mailbox addresses and identifiers for mapping
  8. Set your source tenant and create a new migration batch in the Microsoft 365 Admin Center. 
  9. Map the source and tenant accounts with the CSV file and run the migration batch with PowerShell commands
  10. Monitor the progress and wait until the migration completes successfully. In the end, remove endpoints and relationships

Note: Update the MX Records and check DKIM and DMARC settings post-migration.

This is a summed-up version of the manual method for the cross-tenant mailbox, OneDrive, or SharePoint migrations. Still, the method is too complex to understand and perform for non-technical users. Moreover, there are many other limitations attached to this method. 

Shortcomings of the Method

  • Admin credentials and tech knowledge are mandatory. 
  • Proper internet connectivity and permissions are required. 
  • Too time-consuming and hectic with very large tenant migrations. 
  • High chances and risk of losing the data due to human errors. 
  • Improper configurations or a wrong step can halt the entire workflow. 
  • Additional plans needed for OneDrive and SharePoint migrations. 

So, what’s the ideal solution to overcome these limitations and even handle mailbox throttling during migration without downtime or issues? It’s none other than a professional software solution, as explained in the upcoming section. 

Cross Tenant Migration Microsoft 365: Expert Route

SysInfo Microsoft 365 Tenant to Tenant Migration Software is a one-stop solution for hassle-free and secure migrations. It instantly connects the source and target tenants via Modern OAuth and Graph API and transfers all mailboxes, SharePoint, and OneDrive data without any difficulties. Additionally, it helps with custom and automated mapping and offers advanced filters for customized migration as desired by the individual, IT professional, or enterprise. Moreover, it preserves the structure and data fidelity, ensuring the business-critical data remains compliant and accessible as in the original tenant. 

Cross-Tenant Mailbox Migration Working Procedure 

  1. Run the Office 365 Tenant to Tenant Migration Tool. Hit Copy Mailboxes.
    Run the Office 365 Tenant to Tenant Migration Tool. Hit Copy Mailboxes
  2. Then, select the source tenant after opting for modern authentication mode and sign in. 
    select the source tenant after opting for modern authentication mode and sign in
  3. Further, pick the tenant user IDs and tap Continue to migrate emails.
    pick the tenant user IDs and tap Continue to migrate emails
  4. Afterward, use Saved Credentials or Add New as desired, and complete authentication for the target tenant.
    use Saved Credentials or Add New as desired, and complete authentication for the target tenant
  5. Later, verify the selected source mailboxes that you want to migrate and hit Continue to proceed.
    verify the selected source mailboxes that you want to migrate and hit Continue to proceed
  6. Next, use the drop-down and map the source and target tenant accounts. Verify the mapping status. 
    use the drop-down and map the source and target tenant accounts. Verify the mapping status
  7. Finally, apply filters, pick the way to save the data in the target tenant, and tap Start Migration.
    apply filters, pick the way to save the data in the target tenant, and tap  Start Migration

Later, you can check the migration progress in the Active Tasks window, and after completion, browse to All Reports. There, you can find a detailed report for the entire Microsoft 365 cross tenant mailbox migration. 

How SysInfo Handled A Client Who Needed to Migrate Microsoft 365 Mailboxes Larger than 100 GB

A multinational company acquired two firms operating in separate Microsoft tenants. They needed to combine 6,000 users, 5500+ mailboxes of more than 100 GB, 65 TB OneDrive data, and 1,300 SharePoint sites. 

Rather than executing a complex migration task with PowerShell scripts, they decided to use the SysInfo Office 365 Tenant Migration Tool and found wonders. It immediately migrated their entire data with complete deduplication before migration with 100% precision. 

The migration downtime was reduced, and high-speed processing completed the migration in minimal time with no scope for loss. The incremental sync feature ensured that no data was replicated, and activity logs provided a comprehensive overview of the entire process. With minimal disruption, the company was able to resume operations with ease. 

Conclusion 

Achieve a successful cross tenant migration Microsoft 365 by managing dependencies and choosing a reliable solution. Both native Microsoft PowerShell and Admin Center, and the SysInfo M365 Migration Tool work for a correct migration between the tenant accounts. It ensures all mailboxes, domains, identities, permissions, OneDrive content, and SharePoint sites are transferred securely. Ensure simplified migration of your data with pilot tests, throttling management, and comprehensive logs for guaranteed outcomes. 

Frequently Asked Questions

Q1. How does Microsoft 365 cross-tenant mailbox migration work?

Ans. The M365 cross tenant mailbox migration works by managing source tenants as MailUsers for target tenants, building relationships, mapping profiles, and transferring data with PowerShell scripts. Or, use the SysInfo Office 365 Tenant Migrator for immediate migrations with utmost data security and accuracy. 

Q2. Can I migrate multiple Microsoft 365 mailboxes simultaneously?

Ans. Yes, you can migrate multiple Microsoft 365 tenant mailboxes, but monitor the API throttling limits. Or, best use a professional software like SysInfo Tenant to Tenant Migrator, which can handle very large volumes of mailboxes simultaneously, depending on the licences. 

Q3. Can I migrate OneDrive and SharePoint along with mailboxes?

Ans. Yes, of course. Migrating OneDrive and SharePoint with mailboxes is possible with the dedicated O365 Tenant to Tenant Migrator. However, malicious OneDrive files, SharePoint custom lists, workflows, permissions, and archive version lists aren’t migrated due to the Microsoft Graph API limits. 

Q4. How do I avoid duplicate emails during cross-tenant migration?

Ans. To avoid duplicate emails during tenant migration between two profiles, use the M365 Tenant Migration Software by SysInfo. It provides staged migration with an incremental sync feature and even has a Remove Duplicate filter to ensure only unique emails are transferred from the primary and shared Tenant mailboxes. 

Q5. How can enterprises migrate thousands of Microsoft 365 users between tenants?

Ans. Large enterprises migrated 1000s of Microsoft 365 users between multiple tenants with the M365 Migration Software, which supports batch transfers, delta sync, pilot migrations, deduplication, selective transfers, and modern authentication. 

Q6. What DNS changes are required during Microsoft 365 cross-tenant migration?

Ans. Repoint MX, SPF, DKIM, and DMARC records to the target tenant account and lower the Time to Live (TTL) value to 300 seconds, appx. 5 minutes at least 48 hours before the cutover of DNS to ensure minimal migration. 

Q7. Is Microsoft 365 cross-tenant migration suitable for global organizations?

Ans. Yes, native tenant-to-tenant migration in M365 is suited for a global organization, but the target tenant must reside in the same or a legally compliant region as the source tenant. Also, it should be executed only after proper planning and technical efficiency. 

Rate this post

About The Author:

Simran Bhatia is a technical content writer engaged in writing clear, concise, and SEO-optimized content. With a background in computer science and a passion for writing, I thrive to deliver complex technical content in simple layman terms.

Related Post