On Demand Migration for Teams securely migrates Microsoft Teams and associated Office 365 groups across Office 365 tenants. You can also use this dashboard for migration of content for Microsoft Office 365 groups without Teams functionality. (Content Migration for Office 365 Groups). Microsoft Teams migration requires additional licensing.
IMPORTANT: In case you use classic product UI, the Account Migration project for your source and target tenant should exist before migrating Teams. Account matching /migration should be completed.
Basic Microsoft Teams migration workflow consists of the following steps:
|1||Create Microsoft Teams migration project (created automatically with New Migration UI)|
Grant necessary permissions in case these permissions are not already granted (Prerequisites)
IMPORTANT: It is not recommended to use existing user accounts as source and target Azure AD administrative accounts, because it is recommended to remove them for safety reasons after the migration will be completed. These accounts can be removed from teams as described in Finalizing the Migration.
On this step you can see names, suggested for target teams. In case you need some changes use manual mapping as described below. There are no provision on the target on this step.
TIP: Organize teams in collections to streamline the provision and migration process
|4||Export teams mapping to CSV file|
You can use manual mapping to migrate source team to the target team with another name. If the channel do not exist, it will be provisioned. Also you can use manual mapping to merge several source teams to one target team.
These accounts can be removed from teams as described in Finalizing the Migration.
Migrate / merge all conversations (including inline content) from the source to target channels.
|8||Re-migrate teams to incorporate supported changes made after the migration task (step 7) was started.|
|9||Monitor the progress and track issues|