Home > Tenant to Tenant Migration Process > Overview
Export to PDFTenant to Tenant Migration Process
The sections below contain the general migration process from Microsoft 365 tenants to Microsoft 365 tenants. The details outlined in the document can be referred for any projects to perform migrations across Microsoft 365 using Fly.
The tenant migration process can be complex, and we recommend that you understand your Microsoft 365 components to better perform migrations and validate migration results. The table below details whether the Microsoft 365 services and components can be migrated.
| Service | Can be migrated |
|---|---|
| Exchange Mailbox | Yes |
| SharePoint Site Collection | Yes |
| OneDrive | Yes |
| Microsoft 365 Groups | Yes |
| Microsoft Teams | Yes |
| Microsoft Teams Chat | Yes |
| Power Automate | Yes |
| Power Apps | Yes |
| Viva Engage | No |
| Azure Information Protection | No |
| Stream | No |
| Power BI | No |
| Microsoft Intune | No |
According to your business design, the migration process of your tenant can be performed in the following options:
*Note: In the sequential or parallel method, we recommend you migrate same group mailboxes/team sites in only one migration type to improve the migration performance. For example, if you have run Teams Migration/Microsoft 365 Groups Migration first, you do not need to migrate same team sites in SharePoint Online Migration, or migrate same mailboxes in Exchange Online Migration.