Teams Migration Interface Walkthrough
New Migration UI
Using this new intuitive interface you can:
- Keep track of your location within project and quickly return to the main project dashboard using breadcrumbs on the top of the pane
- View list of discovered teams with last information, completed workflows, team information, and last events related to the teams
- Switch to assessment view to track potential problems, misconfiguration, and risks that might adversely affect the migration
- Quickly navigate to the event lists
- Quickly navigate to the tasks list
- Create discovery task, provision tasks, and teams migration tasks
- Organize the teams into collections that act as “projects within project”. The collections allow you to structure teams.
- Export feature data into comma-separated file and use this file for manual mapping
- Search teams
- Filter teams by workflow, team state or size
- Select team to view details on the right pane. Refer to this pane for extended details related to the selected object .
Assessment View for Microsoft Teams
Refer to the Pre-Migration Assessment for Teams for the complete list of available reports.
Verify the following requirements are met before starting the migration. If these actions are not performed, discovery, provision and migration tasks will fail or some data might be lost!
- Consents are already granted for source and target tenants.
The following consents should be granted before Teams migration feature can be used
- Migration - Basic,
- Migration - Mailbox Migration
- Migration - SharePoint,
- Migration - Teams.
TIP: If the admin consents are not granted or expired, Discover Teams action is disabled and the following notification is displayed: Grant admin consent to the following Migration sub modules on the Tenants page for both source and target tenants: Basic, SharePoint, and Teams. Open Tenants page and grant the necessary permissions so that the product can access the source and target tenants. You will be redirected to the Microsoft web site for granting admin consent. Once admin consent is granted, you can start discovering Teams.
- It is recommended to create or use dedicated (not added as owner or member to any team) source and the target Azure AD administrative accounts.
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.
- Azure AD administrative accounts should have Teams license.
- It is not recommended that you change your Azure AD administrative accounts before completing the migration project.
- Azure AD administrative accounts should be granted Global Administrator role on the tenants for which these account are used.
- Azure AD administrative accounts should be granted Application Impersonation role on the tenants for which these account are used.
- Accounts joined to existing teams should be matched and/or migrated in the migration project.
Before proceeding with the migration, retrieve the list of teams and Microsoft Office 365 groups from the source tenant.
Caution: Don’t start the migration before the discovery is finished. It might result in incorrect processing of migrated objects.
- Go to the main migration project Dashboard in case you use new migration UI. In case you are using classic experience or you are already on the Teams migration Dashboard, go to step 3.
- Click Teams widget.
- Click Discover on the dashboard to create a new discovery task.
- Select objects to discover:
- All Office 365 Groups and Teams ( select this option to discover all Office 365 Groups including groups without Teams functionality)
- All Teams and associated Office 365 Groups
- Office 365 Groups without Teams functionality only
- Schedule when the task will be started. See Task Scheduling for details. Click Next to view the task summary.
- Check scheduled start of the task and name the task. Click Finish to save or start the task depending on schedule option selected.
TIP: Give informative names for the tasks. It will greatly simplify the project management and event filtering in the future.
- Click Finish. You can monitor the task status using task widget on project dashboard.
- Click the task name on the widget to see the details or use Show all link.
Once the discovery task is complete, you will see the source tenant’s teams summary on the Microsoft Teams Migration Project Dashboard.
Discovery also checks the target tenant for potential conflicts (the identical team names on the source and target tenants.) The conflicting teams are marked with "Target team exists" in the Teams list. To see all conflicts, click Needs your attention on the left.
The conflicts are resolved during the provisioning.
Using Collections for Teams
You can use collections to streamline the provision and migration process. There are two approaches:
- You can select discovered teams and create a new collection for them
- You can create a new empty collection and then populate it with discovered teams using comma-separated CSV file.
To create a new collection based on selected teams:
- Click Teams on necessary migration project
- Select teams you want to combine into the collection. You can use search for filtering out the teams by certain criteria or simply hand-pick the individual teams from the grid.
- Click +New Collection in the top right corner of the list view and enter the informative collection name. Click Save to add this collection to the project.
To create a new empty collection and then populate it with teams:
- On the dashboard click Add To Collection.
- Enter the informative collection name. Click Save to add this collection to the project.
- Populate it using comma-separated values (CSV) file as specified in Populating Collections.