Project Interface Walkthrough
Project Dashboard
| # | Control | |
|---|---|---|
 |
Breadcrumbs | Keep track of your location within project and quickly return to the previous steps. |
 |
Menu |
Configure, manage, and control every aspect of the migration project. Match and migrate Teams, monitor and troubleshoot the project with Events, and control the flow of the migration with Tasks. |
 |
Action pane | Set up and fine tune the migration with these commands. |
 |
Welcome widget | Don’t know where to start? Check our Quick Help. |
 |
Teams widget | See the summary on teams and quickly navigate to the list of teams |
 |
Tasks widget | See the status summary for the current migration flow and quickly navigate to all tasks |
 |
Errors widget |
See the summary on warnings and errors and quickly navigate to all migration events |
List View for Microsoft Teams
| # | Control | |
|---|---|---|
 |
Teams grid | List of discovered teams with last information, completed workflows, team information, and mapped target team names |
 |
Assessment view | You can quickly switch to assessment view to track potential problems, misconfiguration, and risks that might adversely affect the migration. |
 |
Details pane | Refer to this pane for extended details related to the selected object |
 |
Related event filters | Quickly navigate to the filtered event lists 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.
Prerequisites
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 projects get created:- Migration - Basic,
- Migration - Resource Processing for 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, Process Resources for 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. |
- Azure AD administrative accounts should be granted Global Administrator role on the tenants for which these account are used.
- Log in to Teams under the target Azure AD administrative account used in consents granting, at least once.
- Match and/or migrate the affected accounts in the associated account migration project.
Discovering Teams
Before proceeding with the migration, retrieve the list of teams from the source tenant. The discovery collects all necessary data for your source tenant to prevent possible issues.
- Click Discover Teams on the project dashboard to create a new discovery task.
- 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.
|
|
Caution: Don’t start the migration before the discovery task is finished. It might result in incorrect processing of migrated objects. |
Exporting Mapping for Teams
To export the teams mapping as a comma-separated values (CSV) file, select the required teams on the Teams tab and click Export.
You can customize this file and use it as a base for manual mapping.
Exported data will contain source team name (may be team IDisntead), suggested target team name to provision and MailNickName MailNickName parameter specifies the alias for the associated Office 365 Group. This value will be used for the mail enabled object and will be used as PrimarySmtpAddress for this Office 365 Group. The value of the MailNickName parameter has to be unique across your tenant.