Tchater maintenant avec le support
Tchattez avec un ingénieur du support

On Demand Migration Current - User Guide

About On Demand Migration Before You Start Account Migration Mail Migration Public Folders Migration OneDrive Migration SharePoint Migration Microsoft Teams Migration Microsoft 365 Groups Migration Troubleshooting Finalizing the Migration

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:

  1. Click Teams on necessary migration project
  2. 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.
  3. 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:

  1. On the dashboard click Add To Collection.
  2. Enter the informative collection name. Click Save to add this collection to the project.
  3. Populate it using comma-separated values (CSV) file as specified in Populating Collections.

Populating Collections

You can populate any existing collection using a comma-separated values (CSV) file with team attributes.

NOTES:
  • CSV file can contain one or more columns. There are no special requirements for header names.
  • One of column must contain case sensitive mail nickname data that will be used for matching.
  • File names with non-ASCII characters are not supported.

To populate collection from CSV file

  1. Prepare a comma-separated values (CSV) file with data of discovered teams you want to add to the collection. File can contain teams that have not been discovered, but these teams won't be added to the collection. One of the columns should contain the mail nicknames. For example:

MailNickname, ...

SampleName,...

  1. Select a collection you want to populate on Dashboard and click it to open the Collection Dashboard.
  2. Click Fill from File to populate the collection with discovered objects you specified in the file created on Step 1.
  3. Click Browse to open the comma-separated CSV file created on Step 1.
  4. Browse for file and click Open. Selected file name appears next to the Browse button.
  1. Click Populate to populate the collection.

The collection is populated. You can see added objects on the Collection Dashboard.

NOTE: The objects that do not exist in the source or target tenants and the source teams that are not enumerated during the Discovery are ignored without producing an event.

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.

  1. 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.
  2. 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.
  1. 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.
  2. Click Browse to open the mapping file prepared on Step 1.
  3. Browse for file and click Open. Selected file name appears next to the Browse button.
  1. Schedule when the task will be started. See for details. Click Next to view task summary.
  2. 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
  1. 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

Example_Name,SampleName

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.

 

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation