CartMicrosoft Teams Divestiture Migration
Microsoft Teams divestiture migration is the controlled movement of selected Team sites from one Microsoft 365 tenant into another environment during a business separation or carve-out. The EdbMails Teams workflow provides the technical controls needed to move selected Team sites between source and target tenants: site selection, mapping, multiple-Team migration, incremental migration, progress monitoring and logs.
Because a divestiture usually moves only part of the source organization, the migration scope must be tightly controlled. Broad Team-site migration, Channel Migration and Private/Group Chat Migration should be treated as separate workload scopes and validated independently where they are included in the separation project.
Define the divestiture scope
Identify the Team sites that belong to the divested business unit and the destination tenant for each site. Exclude Teams that remain with the source organization and record any shared or ambiguous Teams that require a business decision before migration.
Separate Teams workloads before migration
Determine whether each Team requires only the broad Team-site migration workflow or also needs Channel Migration or Private/Group Chat Migration.
EdbMails documents these as separate workflows with their own migration paths.
Prepare the target Microsoft 365 tenant
Confirm the target SharePoint server URL, SharePoint Admin Center URL, administrator access and Team-site readiness. Resolve target naming or structural differences before the migration window opens.
Prepare Microsoft Entra access
Complete the required source and target Microsoft Entra application registration for the Teams migration workload. Keep source and target application credentials separate and aligned with the corresponding tenant.
Map only the Team sites that are transferring
Load the available Team sites, select the sites that belong to the divestiture scope and review the source-to-target mapping carefully. Manual mapping should be used where target names or structures differ from the source.
Use a pilot before the main carve-out
Migrate a representative set of Team sites first. Review logs, destination structure and user access before moving the remaining divested Teams in production waves.
Keep source changes synchronized during the transition
If users continue working in the source tenant during the separation period, run a later incremental migration for supported new or modified data. Preserve the documented migration computer for previously migrated Team sites where the incremental check depends on locally stored encrypted metadata.
Validate the separated environment
Review EdbMails logs and verify representative Team sites and user access in the destination. Confirm that only the intended Teams moved and that any required Channel or Chat migration has been completed separately.
Document unresolved shared dependencies
Teams shared between the retained and divested organizations can require a separate business decision about ownership, duplication or target-side recreation.
Record these exceptions explicitly rather than treating them as automatically resolved by the broad migration.
Frequently Asked Questions
What is Microsoft Teams divestiture migration?
It is the controlled movement of selected Team sites from one Microsoft 365 tenant into another environment during a business separation or carve-out.
How do I define the divestiture scope?
Identify the Team sites that belong to the divested business unit and the destination for each, exclude Teams that remain with the source organization, and record shared or ambiguous Teams that require a business decision before migration.
Do channels and chats need separate handling in a divestiture?
Yes. Determine whether each Team needs only the broad Team-site migration workflow or also Channel migration or Private or Group Chat migration, which EdbMails documents as separate workflows.
How do I prepare the target Microsoft 365 tenant?
Confirm the target SharePoint server URL, SharePoint Admin Center URL, administrator access and Team-site readiness, and resolve target naming or structural differences before the migration window.
How do I prepare Microsoft Entra access?
Complete the required source and target Microsoft Entra application registration for the Teams migration workload, keeping source and target credentials separate and aligned with the corresponding tenant.
How do I map only the Team sites that are transferring?
Load the available Team sites, select the sites in the divestiture scope and review the source-to-target mapping carefully, using manual mapping where target names or structures differ.
Should I run a pilot before the main carve-out?
Yes. Migrate a representative set of Team sites first and review logs, destination structure and user access before moving the remaining divested Teams in production waves.
Can source users stay active during the transition?
Yes. Run a later incremental migration for supported new or modified data and preserve the documented migration computer for previously migrated Team sites.
How do I validate the separated environment?
Review the EdbMails logs and verify representative Team sites and user access in the destination, confirming only the intended Teams moved and any required Channel or Chat migration is completed separately.
How do I handle Teams shared between the retained and divested organizations?
Shared Teams can require a separate business decision about ownership, duplication or target-side recreation, so record these exceptions explicitly rather than treating them as automatically resolved.
Is divestiture migration the same as cross-tenant migration?
A divestiture is a cross-tenant scenario focused on moving only the separated unit's Team sites, using the same EdbMails site selection, mapping and migration controls with tightly controlled scope.
