CartMicrosoft Teams Migration Checklist
Use this Microsoft Teams migration checklist to verify that the source and target Microsoft 365 tenants are prepared, the correct Teams workloads are in scope, Team sites are mapped correctly, migration waves are controlled and target validation is completed before the project is closed.
The checklist follows the EdbMails Teams migration workflow: Microsoft Entra preparation, Team-site selection, source-to-target mapping, multiple Team-site migration, incremental migration, pause/resume controls, migration logs and target-side verification.
Discovery checklist
- List all Team sites in scope.
- Identify business owners and destination Team sites.
- Separate broad Teams migration from Channel Migration and Private/Group Chat Migration.
- Identify pilot Teams and production migration waves.
- Record renamed or restructured target Teams that may require manual mapping.
Source and target readiness checklist
- Confirm source and target SharePoint server URLs.
- Confirm SharePoint Admin Center URLs.
- Confirm Microsoft 365 Global Administrator access.
- Verify the required target Team sites are available or can be created according to the documented workflow.
- Confirm the administrator has the required access to the Team sites in scope.
Microsoft Entra configuration checklist
- Complete the required source and target Microsoft Entra application registration.
- Keep Teams/Channel app registration separate from Private/Group Chat app registration.
- Store the Source Client ID, Tenant ID and Client Secret with the Source app.
- Store the Target Client ID, Tenant ID and Client Secret separately.
- Grant the required admin consent in the corresponding tenant.
Mapping checklist
- Load the required Team sites.
- Review automatic mappings.
- Correct mismatched Team names or target destinations manually.
- Confirm every source Team site maps to the intended target site.
- Preserve the approved mapping for later migration runs.
Pilot migration checklist
- Select representative Team sites.
- Run the pilot migration.
- Review migration progress and logs.
- Validate the target Team sites and user access.
- Record configuration or mapping changes before production migration.
Production migration checklist
- Migrate Teams in manageable waves.
- Monitor progress and Microsoft 365 service behavior.
- Use pause and resume where operationally required.
- Review completed, skipped and failed items after each wave.
- Resolve repeatable issues before the next batch.
Incremental migration checklist
- Confirm whether users continued changing source Teams after the first pass.
- Use the same migration computer for previously migrated Team sites where the documented local metadata is required.
- Reuse the approved source-to-target mapping.
- Run a subsequent migration for supported new or modified data.
- Review logs and target changes after the incremental run.
Post-migration checklist
- Verify representative target Team sites.
- Confirm expected supported content is available.
- Check user access in the target environment.
- Document skipped, failed or manually remediated items.
- Confirm whether separate Channel or Chat migration tasks remain.
- Obtain technical and business sign-off before project closure.
Frequently Asked Questions
What does a Microsoft Teams migration checklist cover?
It covers discovery, source and target readiness, Microsoft Entra configuration, mapping, pilot migration, production waves, incremental migration and post-migration validation.
What goes in the discovery checklist?
List all Team sites in scope, identify business owners and destinations, separate broad Teams migration from Channel and Private or Group Chat migration, identify pilot Teams and waves, and record renamed or restructured targets for manual mapping.
How do I confirm source and target readiness?
Confirm the source and target SharePoint server URLs, SharePoint Admin Center URLs and Global Administrator access, verify the target Team sites are available or can be created, and confirm administrator access to the sites in scope.
What Microsoft Entra steps are in the checklist?
Complete the source and target app registrations, keep Teams and Channel app registration separate from Private or Group Chat app registration, store each app's credentials together and grant admin consent in the corresponding tenant.
What should the mapping checklist confirm?
Load the required Team sites, review automatic mappings, correct mismatched Team names or destinations manually, confirm every source Team site maps to the intended target, and preserve the approved mapping for later runs.
What is in the pilot checklist?
Select representative Team sites, run the pilot, review progress and logs, validate target Team sites and user access, and record configuration or mapping changes before production.
What is in the production migration checklist?
Migrate Teams in manageable waves, monitor progress and Microsoft 365 behavior, use pause and resume where required, review completed, skipped and failed items, and resolve repeatable issues before the next batch.
What is in the incremental migration checklist?
Confirm whether users changed source Teams after the first pass, use the same migration computer for previously migrated sites, reuse the approved mapping, run the subsequent pass and review the logs and target changes.
What is in the post-migration checklist?
Verify representative target Team sites, confirm expected supported content, check user access, document exceptions, confirm whether separate Channel or Chat migration remains, and obtain technical and business sign-off.
Can this checklist be used for tenant-to-tenant and consolidation?
Yes. It follows the EdbMails Teams migration workflow and supports tenant-to-tenant, cross-tenant and consolidation scenarios.
Does the checklist replace a pilot migration?
No. A pilot is part of the checklist and validates the process before production waves begin.
