Exporting Mapping for Teams
To export the teams mapping as a comma-separated values (CSV) file, select the required teams on the Teams tab on Teams migration Dashboard 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 ID isntead), suggested target team name to provision and the Source 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 Source MailNickname parameter has to be unique across your tenant.
Using Manual Mapping for Teams
In some cases, you might want to rename the teams on target or merge them with the existing teams with different names. To achieve this goal, provide a file with the custom mapping between source and target teams. You might use the exported team mapping as a template.
- Export a comma-separated values (CSV) as described in Exporting Mapping for Teams. Alternatively, you can create and use your own CSV file, as described below.
- Edit Target Team Name column only to specify the target team names to create desired matched pairs. Do not change the rest of columns.
Important: When editing a CSV file, the following should be considered:
- To ensure manual mapping will be completed successfully do not remove any columns from exported CSV file.
- You can edit Target Team Name entries only, if necessary. Do not update the Source MailNickname column, this column contains mailnicknames for source tenant, and it is case sensitive. In case any objects are added by mistake, please remove entire rows related to these objects.
- You can merge multiple source teams to a single target team. Just provide the same target team name in a mapping file.
- File names with non-ASCII characters are not supported.
- Open Teams tab and click Map from File.
Do not select any teams from the list – you have already specified them in the file created on Step 1.
- Click Browse to open the mapping file prepared on Step 1.
- Browse for file and click Open. Selected file name appears next to the Browse button.
- Schedule when the task will be started. See Task Scheduling for details. Click Next to view task summary.
- Check selected options. Click Finish to save or start the task depending on schedule option selected.
The task is created. You can track the progress in the Tasks list or view the summary on the Dashboard.
Creating Mapping File
- Prepare a comma-separated values (CSV) file with the matched teams pairs. The first row defines the names of the source and target attribute used for mapping. Subsequent rows list the matching values of the attributes (one pair per row.) This file should have two columns
Target Team Name, SourceMailNickName
Target Team Name specifies team name, e.g., Example_Name, you want your source team ( in this example the source team with SourceMailNickName SampleName) to be matched in target tenant.
SourceMailNickName specifies your source tenant team mail nickname, e.g., SampleName. This field is case sensitive.
|NOTE: File names with non-ASCII characters are not supported.|
Pre-Migration Assessment for Teams
On Demand Migration analyzes your environment and tracks potential problems, misconfiguration, and risks that might adversely affect the migration. Use Assessment view to see the summary reports on the discovered data and use the automatic filters to quickly select certain items.
The following reports are available for Teams:
- Workflow - Teams sorted by completed workflow
- Teams- Teams sorted by processing status
- In progress
- Needs your attention
- Teams By Size
- Teams By Last Activity Time
- Teams By Channel Count
- Teams By Member Count
Once you handle the issues, if any, go to List View screen. You are ready to start the migration.
Provisioning Teams for Target Tenant
After all source teams are discovered you can start to provision teams on the target tenant.
IMPORTANT: Provisioning of public teams is not supported for migration scenarios from one education tenant to another. Only private teams can be provisioned for these scenarios.
The provision task help you to perform the following:
- Create Office 365 groups on the target tenant.
- Resolve naming conflicts.
- Provision teams to the target tenant.
- Provision team membership and ownership for provisioned teams.
Make sure that all associated accounts are matched or migrated before you create the provision task.
NOTE: When using Microsoft Teams for Education, use On Demand Migration for Teams to discover and migrate the EDU group. If you use On Demand Account Migration to discover and migrate the EDU group, then provisioning the EDU teams will fail with a “Request failed with BadRequest status code (Bad Request)” event error.
Create the provision task
Open the New Provision Task dialog
From the OnDemand Migration for Teams, teams tab
Check the teams to provision associated Office 365 group and teams on the target. Provisioned teams will be owned by target Azure AD administrator account. This account also will be added to the provisioned team as a member along with the members matched with source team members. In case any matched account cannot be found on the target, this account cannot be processed and related event will be reported.
TIP: Use search and filtering to quickly navigate through the list of teams.
- Click provision to open the New Provision Task dialog.
Fill in the New Provision Task dialog
Provision Options: Does a team with the same name already exist on the target?
The default option is to Provision a new team on the target with the original name plus suffix. The default suffix is "Migrated". You can change the suffix via the New team display name suffix field.
The alternative is to Merge to the existing team on target. When selected, new fields become available. By default On Demand will Provision a new channel on the target with the original name plus suffix. You can change the default suffix "Migrated" via the New channel display name suffix field.
Alternatively, select Merge source channel conversations with the target channel. Select this option if the target channel is empty. If conversations already exist in the target channel then selecting this option will result in mixing the conversations from the source and the target on the target and is not revertible.
Provision Options: Target multi-geo tenant preferred teams location
Leave the preferred data location as Default if the target tenant is a multi-geo tenant (see Microsoft 365 Multi-Geo). All teams and groups will be migrated to the same region as the target admin.
Alternatively, select the geolocation configured for the target tenant.
TIP: To migrate teams/groups to different regions, best practice is to create a collection for each region (see Using Collections for Teams) and add the teams/groups to the appropriate collection. Example collection names are "Migrate to EUR", "Migrate to JPN" and "Migrate to NAM". Use the collection as a filter to create the provision task.
Provision Options: Suppress automatic Group Welcome Message sending
When selected users will not be disturbed by automatic Microsoft messages regarding adding to the provisioned Teams.
NOTE: Suppressing these messages may result in performance degradation due to issues with Microsoft’s synchronization behavior. We suggest you check the performance during the pilot migration.
For teams provisioned by tasks created in previous releases, for which Group Welcome Messages were suppressed by default, these email messages may be received in some cases, depending on stage of processing by Microsoft.
Fill in the New Provision Task dialog: Schedule
Schedule when the task will be started. See Task Scheduling for details.
Verify the New Provision Task dialog: Summary
View the task summary. Name the task and check selected options.
Click Finish to save or start the task depending on schedule option selected. The provision task is created. You can track its progress in the Tasks, view the summary on the Dashboard or monitor alerts and notifications in the Events.