CartMicrosoft Teams Sites Migration
Microsoft Teams sites migration focuses on moving the Team-connected site structure and supported collaboration content from a source Microsoft 365 tenant to corresponding Team sites in a target tenant. The EdbMails Teams workflow is built around loading Team sites, selecting the required sites, mapping source and target sites, and migrating supported content between tenants.
Because Microsoft Teams is connected to SharePoint-backed content and other Microsoft 365 workloads, this page covers the supported Team-site migration workflow. Channel messages, private chats and group chats are handled through separate EdbMails migration workflows, so use those for those workloads.
What does Teams sites migration cover?
The EdbMails workflow documents migration of selected Team sites between Microsoft 365 tenants. Administrators can load the available sites, choose the required Teams, connect the target tenant and map each source Team site to the intended destination.
Prepare source and target Team sites
Before migration, confirm the source and target SharePoint server URLs, SharePoint Admin Center URLs and Microsoft 365 Global Administrator access.
Make sure the required target Team sites exist or can be created according to the documented workflow.
Select only the Team sites required
EdbMails lets administrators choose the Team sites that belong in the migration project. This is useful when only certain departments, projects or business units are moving to the target tenant.
Map source sites to target sites
Use automatic mapping where the source and destination align, and manually correct mappings where Team names, URLs or target structures differ. Previous mapping can also be reused where supported by the migration workflow.
Use Teams site migration in phased projects
For larger environments, migrate a pilot set of Team sites first, review the results and then proceed in controlled waves. This reduces the risk of repeating mapping or target-readiness issues across the full tenant.
Run incremental migration for later changes
If the source Team sites remain active during the project, use a subsequent incremental migration for supported new or modified content. Keep the same migration computer for previously migrated Team sites where the documented local encrypted metadata is required for the incremental check.
Validate migrated Team sites
Review EdbMails migration logs and verify representative Team sites in the target tenant. Confirm the site mapping, expected supported content and user access before the migration wave is considered complete.
Frequently Asked Questions
What is Microsoft Teams sites migration?
It is moving the Team-connected site structure and supported collaboration content from a source Microsoft 365 tenant to corresponding Team sites in a target tenant.
What does Teams sites migration cover?
The EdbMails workflow documents migration of selected Team sites between tenants. Administrators load the available sites, choose the required Teams, connect the target tenant and map each source Team site to the intended destination.
Are channels and chats part of sites migration?
No. Channel messages, private chats and group chats are handled through separate EdbMails migration workflows, so use those for those workloads.
How do I prepare source and target Team sites?
Confirm the source and target SharePoint server URLs, SharePoint Admin Center URLs and Microsoft 365 Global Administrator access, and make sure the required target Team sites exist or can be created.
Can I migrate only selected Team sites?
Yes. EdbMails lets administrators choose the Team sites that belong in the project, which is useful when only certain departments, projects or business units are moving.
How do I map source sites to target sites?
Use automatic mapping where source and destination align, manually correct mappings where Team names, URLs or target structures differ, and reuse previous mapping where supported.
Can I migrate Team sites in phases?
Yes. Migrate a pilot set of Team sites first, review the results, then proceed in controlled waves to reduce the risk of repeating issues across the tenant.
Can source Team sites stay active during migration?
Yes. Use a subsequent incremental migration for supported new or modified content, keeping the same migration computer for previously migrated Team sites.
How do I validate migrated Team sites?
Review the EdbMails migration logs and verify representative Team sites in the target, confirming the site mapping, expected supported content and user access.
Can EdbMails create the target Team sites?
Confirm that the required target Team sites exist or can be created according to the documented EdbMails workflow.
Do I need Microsoft Entra app registration?
Yes. The Teams workflow uses manual source and target Microsoft Entra ID application registration.
