How to Migrate Entire M365 Tenant to Another Tenant

Hi Yogeshwaran M1,

Thank you for your update, I'm glad my response helpful to you.

After researching your questions, here's a clear breakdown based on internal documentation and Microsoft sources:

• Does the add-on support migration of Loop components and Viva Engage data?

Unfortunately, no, the Cross-Tenant User Data Migration add-on does not support migration of:

• Loop components or workspaces
• Viva Engage (Yammer) communities and data

The add-on is specifically designed to support Exchange Online mailboxes and OneDrive for Business content only

For Loop, there is currently no native Microsoft tool for cross-tenant migration. Manual recreation or export/import may be required.

For Viva Engage, cross-tenant engagement is possible only through a multitenant organization setup, which requires:

• Microsoft 365 E3 + Microsoft Entra ID P1, or Microsoft 365 E5 (includes Entra ID P2)
• Viva Suite or Viva Communications and Communities license
• All tenants must be in Native Mode and configured in a hub-and-spoke model

Here is some relative links you want to reference Introducing Cross-tenant user data migration

•  Is the Business Basic license sufficient for the entire migration process when paired with the add-on?

Yes, your Microsoft 365 Business Basic license is eligible to use the Cross-Tenant User Data Migration add-on for migrating:

• Exchange Online mailboxes
• OneDrive for Business content

This add-on is available for Business Basic, Business Standard, Business Premium, and other enterprise plans

• would you require any additional licenses or subscriptions to fully complete the operation?

if your migration scope includes Loop or Viva Engage, you will need additional licenses:

• For Loop: No native support exists, so manual handling or third-party tools may be needed.
• For Viva Engage: You’ll need Microsoft 365 E3 or E5 and Viva Suite licenses to enable multitenant organization features

I hope information above helpful to you.

If you're still facing any problems, please feel free to share more details about the current error or steps you're stuck on—I’ll be happy to assist further.   

We are glad that helps. Meanwhile, hope you kindly mark it as an answer and vote it up by your original account which raised this question. Once marked, it will automatically pin on top. As other users will also search information in this community, your valuable marked answer will definitely also help other users who have similar queries easily to find the correct channel and useful information more quickly.

Thank you for your cooperation once again, have a nice day!   Looking forward to your update.Best regards,Darren-Ng | Microsoft Community Support Specialist

Hi Darren,

Thank you for the detailed response and the helpful resources.

At present, I’m using a Microsoft 365 Business Basic license. I understand that I can purchase the Cross-Tenant User Data Migration add-on separately—but I wanted to confirm a few things:

• Does this add-on support the migration of Loop components and Viva Engage data?
• Is the Business Basic license sufficient for the entire migration process when paired with the add-on?
• Or would I require any additional licenses or subscriptions to fully complete the operation?

Please let me know if I’m misunderstanding anything. I appreciate your guidance and look forward to your input.

Best regards,
Yogeshwaran M

Hi,

Thank you for reaching out to our community, I'm glad to be here to support you.

After researching, here are relative information that may be helpful to you:

Microsoft 365 tenant-to-tenant migrations - Microsoft 365 Enterprise | Microsoft Learn

How to migrate mailboxes from one Microsoft 365 or Office 365 organization to another | Microsoft Learn

      **Prerequisites & Dependencies**

1. Global Admin Access on both source and target tenants.
2. Tenant ID of the target tenant.
3. User accounts must be pre-created in the target tenant.
4. Azure AD B2B collaboration may be required for some services.
5. PowerShell scripting is often necessary for automation and customization.
6. OneDrive Specifics
   • Each OneDrive site must have:
     • ≤ 2 TB of storage
     • ≤ 1 million items
   • OneDrive accounts should not be created in the target tenant before migration
   Licensing Requirements

To use Microsoft’s native cross-tenant migration, you need:

• Cross-Tenant User Data Migration licenses.
• These licenses must be purchased and assigned before migration begins.
• Available only to organizations with:
  • An Enterprise Agreement with Microsoft.
  • At least 500 users/devices

If you don’t meet these conditions, you may need to contact Microsoft directly or consider third-party tools.

      **Lessons Learned & Tips**

• Plan thoroughly: Migration can be complex and time-consuming.
• Test in a pilot group before full migration.
• Use Microsoft documentation and PowerShell scripts to automate tasks.
• Coordinate with target tenant admins for permissions and setup.
• Monitor throttling limits during data transfer.

Hope it helps, if you need any other supporting, please feel free to reach out.

If I misunderstand your point, please pardon me

look forward to hearing your update and hope suggestions above can meet your expectation.

Have a nice day!!

Best regards,    Darren-Ng | Microsoft Community Support Specialist

I’m planning a migration from one Microsoft 365 tenant to another and need help navigating the process. Specifically, I’m looking for best practices or a native tool for migrate:

• Exchange Online mailboxes
• OneDrive for Business content
• Loop components or workspaces
• Viva Engage (Yammer) communities and data

In particular, I’d love to hear from anyone who’s done this using native Microsoft tools — what are the key dependencies and licensing requirements (e.g., Cross-Tenant User Data Migration licenses) that I need to be aware of?

If you’ve been through this or can share helpful resources or tips, I’d be truly grateful!

Thanks in advance