Cross tenant Migration Microsoft 365 Mailbox, SharePoint, OneDrive and Teams Chats without data loss

Hi @E.M. Nimesh Kavinda Amarasinghe, 

Thank you for posting your question in the Microsoft Q&A forum.    

I understand you’re planning a cross-tenant migration and want to confirm which features are fully supported. Here’s an overview: 

• Exchange Online mailboxes (including folder structure, calendar, contacts, and rules)?  The folder structure, calendar, contacts are able to move to the target tenant.   You could refer to this article: Cross-tenant mailbox migration - Microsoft 365 Enterprise | Microsoft Learn 
• OneDrive for Business (including version history and sharing permissions)?  Version history of files is preserved, and file sharing permissions are retained by mapping users/groups to the target  You could refer to this article : Cross-tenant OneDrive migration overview - Microsoft 365 Enterprise | Microsoft Learn 
• SharePoint Online sites and libraries?  SharePoint site collections (including document libraries, lists, pages, and site metadata) can be moved to another tenant  You could refer to this article : Cross-tenant SharePoint site migration overview - Microsoft 365 Enterprise | Microsoft Learn 
• Microsoft Teams chat history (including private chats, group chats, and channel messages)?  Teams chat history is not migrated by Microsoft’s native tools.
  
• Are there any unsupported scenarios or data types (e.g., Teams private chats, mailbox audit logs, SharePoint metadata)?  Other M365 content areas (e.g. Azure AD accounts, Exchange Online archives, SharePoint workflows, Planner tasks, etc.) may require separate handling. The SharePoint migration preview extends support to sites and group content, but Yammer, Stream, Planner, and other services are outside the scope of these features and might need separate migration strategies if applicable 

But if you want the process to be smoother I strongly recommend you to raise for a support request in the Microsoft 365 Admin Center. A Microsoft support engineer can assist with advanced diagnostics and remote guidance. 

The Global Admin should create a service request with Microsoft support to get advanced technical assistance and diagnostics. For detailed instructions on how to get support, please refer to Get support - Microsoft 365 admin.   

Thank you again for your time and understanding. While my initial response may not resolve the issue immediately, I’d like to gather more details about your situation so I can assist you more effectively.    

I really appreciate your patience, and I’m here to help. Looking forward to your response!    

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

The Cross-Tenant User Data Migration feature provides support for migrating various data types within Microsoft 365, but there are specific limitations and considerations to keep in mind:

1. Scope of Coverage:
   • Exchange Online Mailboxes: The migration supports user-visible content in mailboxes, including emails, contacts, calendars, tasks, and notes. However, mailbox audit logs and certain settings may not be migrated.
   • OneDrive for Business: The migration includes user files, but it does not explicitly mention version history or sharing permissions. You should verify these aspects separately.
   • SharePoint Online: The migration of SharePoint sites and libraries is not explicitly covered in the provided context, so further investigation may be necessary to confirm capabilities.
   • Microsoft Teams Chat History: The migration does not support Teams chat folder content, including private chats and group chats. However, once the mailbox is migrated, Teams chat content can be searched and exported by the source tenant administrator.
2. Limitations or Exclusions: Unsupported scenarios include:
   • Teams private chats and chat history.
   • Mailbox audit logs.
   • SharePoint metadata may also be excluded, but this should be confirmed based on specific requirements.
3. Tooling and Process:
   • The migration utilizes Microsoft tools like Exchange Online PowerShell and MRS for mailbox migrations. However, specific integration details for SharePoint and Teams are not mentioned.
   • Recommended pre-migration steps include ensuring that source accounts are set to Read/Write and that no service encryption is enabled on the source tenant.
4. Post-Migration Validation:
   • Recommended verification steps include checking the integrity of migrated data and ensuring service continuity. Automated reports or logs for stakeholder review are not mentioned in the context, so this may require additional tools or processes.
5. Licensing and Support:
   • The Cross-Tenant User Data Migration feature requires a per-user license, and you must ensure that the proper licenses are in place before migration. There is no specific mention of support for troubleshooting or escalation during migration, so contacting your Microsoft account team may be necessary for assistance.

To ensure a successful migration without data loss, it is crucial to thoroughly plan and validate each step of the process, particularly focusing on unsupported data types and pre-migration configurations.

References:

• Cross-tenant mailbox migration
• Cross-tenant OneDrive migration