立即与支持人员聊天
与支持团队交流

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.

To create a new collection with teams selected from the user interface:

  1. Click Teams from your migration project
  2. From the Teams List View select the teams you want to add to the collection.
  3. Click New Collection from the Teams List View toolbar.
  4. Enter a collection name.
  5. Click Save to add this collection to the project.

To create a new collection with teams from a CSV file

  1. Click Teams from your migration project
  2. Click Select Collectionand then click +New Collection from the top right corner of the Teams List View.

  3. Enter the collection name.
  4. Click Save to add this collection to the project.
  5. Prepare a comma-separated values (CSV) file with the teams you want to add to the collection. If the CSV file contains teams that have not been discovered , the teams cannot be added to the collection.

    NOTE: CSV file names with non-ASCII characters are not supported. MailNickName values are case-sensitive.

  6. Click Dashboard to open the Teams Dashboard.
  7. Click Select Collectionand then select the collection that you created.
  8. Click Fille From Filefrom Teams Dashboard toolbar.
  9. In the Fill from File dialog, click Browse and select the CSV file that you created.
  10. Click Populate to add the teams from the file to the collection.

To add teams selected from the user interface to an existing collection:

  1. Click Teams from your migration project
  2. From the Teams List View select the teams you want to add to an existing collection.
  3. Click Add To Collection from the Teams List View toolbar.
  4. In the Add to Existing Collection dialog, click the Collection Name drop down and select a collection.
  5. Click Save to add the teams to the collection.

To add teams from a CSV file to an existing collection:

  1. Prepare a comma-separated values (CSV) file with MailNickName property of the teams you want to add to the collection. If the CSV file contains teams that have not been discovered , the teams cannot be added to the collection.

    NOTE: CSV file names with non-ASCII characters are not supported. You can get the MailNickName property of the teams when you export teams to a CSV file. MailNickName values are case-sensitive.

  2. Click Dashboard to open the Teams Dashboard.
  3. Click Select Collection from the top right corner of the Teams Dashboard and then select the collection that you created.
  4. Click Fille From Filefrom Teams Dashboard toolbar.
  5. In the Fill from File dialog, click Browse and select the CSV file that you created.
  6. Click Populate to add the teams from the file to the collection.

Exporting Teams

To export teams to a comma-separated values (CSV) file:

  1. Click Teams from your migration project
  2. Click the Teams tab. From the Teams List View select the teams you want to export.
  3. From the Teams List View select More Actions and then select Export.
  4. Open the CSV file by extracting it from the ZIP file that is downloaded to your computer.

The exported data contain the following information:

  • Team Name - source team name
  • Workflow - the most recent operation performed on the team
  • Channel, Members, Messages, Plans, Tasks - counts of various content in the team.
  • Size(MB) - size of all the content in the team.
  • Last Activity - date and time of the last action performed on the team record.
  • Created - date and time the team record was created
  • Target Team Name - suggested target team name that will be provisioned in the target tenant
  • Source MailNickname - alias for the associated Microsoft 365 Group. This value will be used for the mail enabled object and will be used as PrimarySmtpAddress for this Microsoft 365 Group. The value must be unique across your tenant.
  • Last Operation Description - description of the last operation performed on this team.

Mapping Teams

To rename teams or merge one or more source teams to a specific team in the target tenant, a CSV file is used to indicate the mapping between source and target teams as described in this topic.

To creating a mapping file:

  1.  Prepare a comma-separated values (CSV) file with the source and target team names.

    TIP: Export selected teams to a comma-separated values (CSV) and then edit this file. See Exporting Teams for more details.

  2. The header row defines the names of the source and target attribute used for mapping. Subsequent rows list the matching values of the attributes. This file has two columns:
    • SourceMailNickname - the unique name of the source team. This value is case sensitive.
    • Target Team Name - specify the target team name. You can merge multiple source teams to a single target team when you specify the same target team name in a mapping file.

  3. Save the CSV file.

NOTE: File names with non-ASCII characters are not supported.

To upload a mapping file:

  1. Log in to Quest On Demand and choose an organization if you have multiple organizations.
  2. From the navigation pane, click Migration to open the My Projects list.
  3. Create a new project or open an existing project.
  4. Click Teams from the project tiles, or click Open from the Teams tile to open the Teams dashboard.
  5. Click the Teams tab.
  6. Click More Actions and then click Map from File. The New Mapping from File Task wizard opens.
  7. Step 1: Mapping file
    1. Click Browse and select the CSV mapping file. The selected file name appears next to the Browse button.
    2. Click Next.
  8. Step 2: Schedule
    1. Choose from one of three options to schedule the task. The scheduler will be activated only after you complete the task wizard.
      • Run now - the task will run immediately.
      • Run later - the task must be started manually.
      • Schedule - specify a future date and time to run the task.
    2. Click Next.
  9. Step 3: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. You can specify a custom name.
      2. Source tenant - name of the tenant in this project.
      3. Target tenant - name of the target tenant in this project.
      4. Scheduled start - date and time when the task will start. Now indicates that the task will start immediately.
    2. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.

The task is created. You can track its progress from the Tasks tab, view the summary on the Dashboard or monitor alerts and notifications from the Events tab.

 

Provisioning Teams

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 Microsoft 365 Groups on the target tenant.
  • Resolve naming conflicts.
  • Provision teams in the target tenant.

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.

To provision teams:

From the OnDemand Migration Teams tab

  1. 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. Team members are not added to teams in this step. Use the migration task to migrate team membership.

    TIP: Use search and filtering to quickly navigate through the list of teams.

  2. 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 geo location 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 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.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级