Download Buy Now

Microsoft Teams to Microsoft Teams Migration Guide

Moving Microsoft Teams data between Microsoft 365 tenants requires careful preparation because Teams brings together collaboration content across teams, channels, files, and other connected Microsoft 365 services. EdbMails Microsoft Teams Migration Tool helps administrators migrate supported Teams data from a source Microsoft 365 tenant to the required teams in the target tenant.

EdbMails supports the migration of multiple teams and provides source-to-target mapping to help administrators direct Teams data to the appropriate destination. Incremental migration can be used for subsequent migration runs to transfer new or modified supported content without unnecessarily processing previously migrated data.

Microsoft Teams Migration

This guide explains how to prepare the source and target Microsoft 365 environments, connect the tenants, select and map the required teams, perform the migration, monitor its progress, and review the migration results.

Microsoft Teams pre-migration activities
Complete the following requirements for the source and target Microsoft 365 tenants before starting the Teams migration.
On the source tenant
1. Keep the SharePoint source server URL, SharePoint Admin Center URL, and Microsoft 365 Global Administrator account ready.
2. Complete the required manual application registration in Microsoft Entra ID for the source Microsoft 365 tenant.
  Steps to manually register the EdbMails application in Microsoft Entra ID
3. Grant the Global Administrator account access to each source Team site that you want to migrate. To configure the required access manually, follow the steps below:
  Steps to add a Global Administrator as a member of each Team site
On the target tenant
1. Keep the SharePoint target server URL, SharePoint Admin Center URL, and Microsoft 365 Global Administrator account ready.
2. Complete the required manual application registration in Microsoft Entra ID for the target Microsoft 365 tenant.
  Steps to manually register the EdbMails application in Microsoft Entra ID
3. Make sure the required Team sites are available on the target tenant. EdbMails can automatically create the required target Team sites during migration. If you prefer to create the sites manually, follow the instructions below:
  Steps to create a Team site
4. Grant the Global Administrator account access to each required target Team site. To configure the required access manually, follow the steps below:
  Steps to add a Global Administrator as a member of each Team site
Microsoft Teams Migration Steps
Step 1: Download and Install EdbMails
- Download and install the EdbMails Microsoft Teams migration software on your computer.
- Launch the EdbMails software, enter the email address & password and click the ‘Login’ button or click the ‘Start Your Free Trial’.
- Click the 'SharePoint, OneDrive, Documents, Sites, Teams, Chats & Channels Migration' tab, then select 'Teams & Channel Migration'.
- Select ‘Teams Migration’.
- You can either keep the default job name or click the ‘New Job’ button to change the job name.
Step 2: Connect to the source Microsoft Teams environment
- Enter the source SharePoint server url, admin center url, and Office 365 Global admin account email address.
  For the Teams source connection, manually register the EdbMails application in Microsoft Entra ID of your source Microsoft 365 tenant.
  Learn how to manually register the EdbMails application in Microsoft Entra ID.
- Enter the Application (Client) ID, Directory (Tenant) ID, and Client Secret that you copied from the Microsoft Entra admin center.
- Authenticate on the Microsoft sign-in page using a Global Administrator account.
- Select one of the methods to load the Teams sites. EdbMails will automatically load the available sites. If you have additional sites that are not listed, you can load them using a CSV file.
Step 3: Select the Team sites for migration
- Select the Teams sites you want to migrate and click ‘Next’ to continue.
Step 4: Connect to the target Microsoft Teams environment
- Enter the target SharePoint server url, admin center url, and Office 365 Global admin account email address.
  For the target Teams connection, manually register the EdbMails application in Microsoft Entra ID of your target Microsoft 365 tenant.
  Learn how to manually register the EdbMails application in Microsoft Entra ID.
- Enter the Application (Client) ID, Directory (Tenant) ID, and Client Secret that you copied from the Microsoft Entra admin center.
- Authenticate on the Microsoft sign-in page using a Global Administrator account.
- Select one of the methods to load the Teams sites. EdbMails will automatically load the available sites. If you have additional sites that are not listed, you can load them using a CSV file.
Step 5: Map the source and target Team sites
- Select an option to map the Teams sites between the source and the target servers.
- EdbMails automatically maps the Teams sites between the source and the target servers. Also, you can manually map the sites or select the option to map using previous migration mapping.
Step 6: Start Microsoft Teams Migration
- Verify the sites mapping between the source and target servers, then click the ‘Start Migration’ button to initiate the migration.
- During the migration, you can monitor the progress in real-time. EdbMails also allows you to pause and resume the migration whenever needed. Once the migration is complete, a message will appear prompting you to review the migration status.
- Click the ‘View Log’ button to verify the migrated items from each folder with the items count.

Best practices for Microsoft Teams migration

Use these practices to manage Microsoft Teams migrations more effectively, especially when transferring multiple Team sites between Microsoft 365 tenants.

Start with a pilot migration: Migrate a small number of Team sites first to verify the migration workflow and expected results before proceeding with larger batches.
Migrate in manageable batches: Organize larger Teams environments into smaller migration batches to simplify monitoring and troubleshooting.
Review migration logs: Check the migration results for completed, skipped, or failed items and investigate items that require attention.
Run incremental migration: Perform subsequent migration runs to transfer new or modified supported data before completing the final transition.
Validate migrated Team sites: Review the required teams and migrated content in the target tenant to confirm that the expected data is available.
Verify user access: Confirm that the required users can access the appropriate Teams resources in the target Microsoft 365 tenant after migration.

Benefits of EdbMails for Microsoft Teams migration

EdbMails provides practical features for migrating Microsoft Teams data between Microsoft 365 tenants while giving administrators control over Team site selection, mapping, and migration.

Simultaneous Teams migration: Migrate multiple Team sites simultaneously to handle migrations involving larger Teams environments efficiently.
Selective migration: Select the required Team sites and migrate only the data needed in the target Microsoft 365 tenant.
Automatic and manual mapping: Automatically map matching source and target Team sites, with the option to modify the mapping manually when required.
Incremental migration: Use incremental migration to transfer new or modified supported data in subsequent migration runs without unnecessarily processing previously migrated content again.
Migration logs: Review migration results to identify completed, skipped, or failed items that may require attention.
No PowerShell scripts required: Perform the Teams migration through the EdbMails interface without writing or running PowerShell scripts.
24/7 technical support: Get assistance from the EdbMails support team throughout the Microsoft Teams migration process.

Frequently asked questions

What should I prepare before migrating Microsoft Teams to another tenant?
Prepare the source and target Microsoft 365 environments, required Global Administrator accounts, application registration details, Team site access, and the required target Team sites. Review the pre-migration requirements in this guide before starting the migration.
Can I migrate Microsoft Teams between two different Microsoft 365 tenants?
Yes. EdbMails supports Microsoft Teams migration between source and target Microsoft 365 tenants. Administrators can select the required Team sites, map them to the appropriate destination sites, and perform the migration.
What happens if the source and target Team site names are different?
You can review the source-to-target mapping in EdbMails and manually map a source Team site to the appropriate target Team site when automatic mapping does not match the required destination.
How can I check whether the Teams migration completed successfully?
After the migration, use the ‘View Log’ option in EdbMails to review the migration status and item counts. You should also verify the required Team sites and migrated content in the target Microsoft 365 tenant.
Can users continue working in Microsoft Teams during a staged migration?
If the source environment remains active during the migration project, users may continue creating or modifying content. A subsequent incremental migration can be used to transfer new or modified supported data before the final transition.

Additional resources:

In this manual

Introduction Pre-Migration Activities Teams Migration Steps Best Practices EdbMails Benefits

Microsoft Teams Migration

Just 10 Sites $80 Only

Buy Now

Need help?

24/7 Customer support

Personalized Demo

Book a personalized demo

Still need help?

Email us / Call us