Converse agora com nosso suporte
Chat com o suporte

On Demand Migration Current - User Guide

About On Demand Migration Working with On Demand Migration Account Migration Mailbox Migration OneDrive Migration Microsoft Teams Migration Microsoft 365 Groups Migration SharePoint Migration Public Folders Migration Power BI Migration Troubleshooting Finalizing the Migration Appendix A: Using PowerShell Appendix B: How Queuing Works

Discovering Teams and Groups

Every team is associated with a Microsoft 365 Group, but there are groups that are not associated with teams. In this topic, the term team means a Microsoft Team and includes its associated group, and the term group means a Microsoft 365 Group that is not associated with a team.

NOTE: This topic explains the process to discover both teams and groups. If you want to discover only teams, see Discovering Teams. If you want to discover only groups that are not related to teams, see Discovering Groups.

In this topic:

Discovering all teams and groups

This is the simplest approach which uses the Discover tasks to inspect the source tenant and discover all the teams.

To start the Discover task:

  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 Discover > Discover All from the Teams dashboard.
  6. The New Teams & Groups Discovery Task wizard starts. Each step is described below:
  7. Discovery Options

    NOTE: The Azure AD administrator account will be added to the discovered Teams and Groups.

    1. All Teams - select this option to discover all Microsoft Teams.
    2. All Groups - select this option to discover all Microsoft 365 Groups without Teams.
    3. All Teams and Groups - select this option to discover Microsoft 365 Groups and Teams.
    4. Click Next.
  8. Notification
    1. Send notification email once the task is completed - select this option to send a notification email when a discovery task completes.
      • Only in a case of failure - select this option to send the email if the discovery task fails to complete successfully.
    2. Recipients - enter the email address of the recipients of this email. You can specify multiple recipient email addresses separated by semicolon.
    3. Click Next.
  9. 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 - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time entered in the corresponding calendar field.
    2. Click Next.
  10. Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. You can specify a custom name. The default name is Discover.
      2. Source tenant - name of the tenant where the statistics will be collected.
      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.

Discovering teams and groups from a file

This step is required if you plan to discover teams and groups using a CSV file. When you have a large set of teams and groups but you want to migrate a subset of the objects, the CSV file lets you specify the teams and groups that you want to discover and ignore the rest. You can then use this file in the New Teams & Groups Discovery Task as described in this topic to discover the teams from the source tenant.

Preparing the CSV file

  1. Log in to the Microsoft 365 admin center (https://admin.microsoft.com) with the credentials of your source tenant administrator.
  2. From the navigation pane, click Active groups.
  3. Select Microsoft 365 tab in the Active Groups page
  4. Click Export and then click Export all groups. A Groups.csv file will be downloaded to your computer.

  5. Edit the CSV file and retain the Group ID and Group name columns. Then retain the teams and groups you want to discover and delete the rest.

  6. Save the CSV file. You may rename the file if needed.

Starting the Discover Task

  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 Discover > Discover from file from the Teams dashboard.
  6. The New Teams & Groups Discovery Task wizard starts. Each step is described below:
  7. Discovery Options

    1. Click Browse and select the CSV that contains the Group IDs and Group names of the teams that you want to discover.
    2. Click Next.
  8. Notification
    1. Send notification email once the task is completed - select this option to send a notification email when a discovery task completes.
      • Only in a case of failure - select this option to send the email if the discovery task fails to complete successfully.
    2. Recipients - enter the email address of the recipients of this email. You can specify multiple recipient email addresses separated by semicolon.
    3. Click Next.
  9. 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 - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time entered in the corresponding calendar field.
    2. Click Next.
  10. Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. You can specify a custom name. The default name is Discover.
      2. Source tenant - name of the tenant where the statistics will be collected.
      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.

Reviewing the Discover Task

  1. Open the Tasks tab.
  2. Select the task that you want to review. The default name is Discover.
  3. In the task details pane that opens, the information presented is as described below:
    1. Type - type of the task. The type is discoverteams.
    2. Created - date and time when the task was created.
    3. Modified - date and time when the task was last updated.
    4. State - state of the task.
    5. Last Operation - the action that was most recently performed in this task.
    6. Schedule - date and time when the task started. Now indicates that the task started immediately after the task was created.
    7. Events (number) - number indicates the count of events that the task encountered. The values indicate the type of the events and the event count for each type.

  4. If you select the options to collect statistics in the New Teams & Groups Discovery Task wizard, you will see additional tasks: Collect Plan and Task statistics for Teams and Groups and Collect Message statistics for Teams. Click each task to view the corresponding details in the details pane.
 

Reviewing the Discover Task Events

  1. Open the Tasks tab.
  2. Select the task that you want to review.
  3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events for the selected task.
  4. Select an event that you want to review. In the event details pane that opens, the information presented is as described below:
    1. Object - name of the team or group discovered.
    2. Task - name of the task.
    3. Time - date and time when the event occurred.
    4. Category - type of task. the value is Application.
    5. Source - name of the On Demand Migration service

Managing Groups with Collections

Migrating large numbers of groups requires careful planing. The groups could belong to different offices and geographical locations or sensitive departments. Migrating groups of Finance or Legal departments require special care. Organize the groups into collections to make large group lists more manageable.

Working with the Collection Dashboard

The Collection Dashboard shows the collection-specific summary, allows you to see group added to it, create tasks for them, and monitor the progress of tasks.

  • To view the collection dashboard for an existing collection
    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. From the project dashboard, click Open in the Teams tile to open the Teams migration workspace.
    5. From the top-right corner of the migration workspace, click Select Collection and then select the collection to view. The collection Dashboard is displayed.
    6. Click the M365 Groups tab. You will see the list of groups that belong to the collection.
  • To see the tasks for collection-specific accounts, use the corresponding tile on the collection Dashboard or open the Tasks tab.
  • To see the events related to the collection, use the corresponding widget on the collection Dashboard or open the Events tab.
  • To rename or delete the collection, click the corresponding buttons in the menu.
  • To return to the project dashboard, click the project name in the navigation bar.

Creating a Collection manually

  1. From the project dashboard, click Open in the Teams tile to open the Teams dashboard.
  2. From the top-right corner of the migration workspace, click Select Collection > + New Collection
  3. Enter a collection name and click Save to add this collection to the project.

Adding groups to Collections

You can add groups to collections in several ways:

To add selected groups to a new collection:

  1. From the project dashboard, click Open in the Teams tile to open the Teams dashboard.
  2. Click the M365 Groups tab and select List View if not already selected.
  3. Select the groups you want to add to the collection.
  4. From the actions toolbar, click New Collection. The New Collection dialog opens.

  5. Enter a collection name in the Collection name field and click Save to add the selected groups to the collection.

To add selected groups to an existing collection:

  1. From the project dashboard, click Open in the Teams tile to open the Teams dashboard.
  2. If you need to create a new collection:
    1. From the top-right corner of the migration workspace, click Select Collection > + New Collection
    2. Enter a collection name and click Save to add this collection to the project.
  3. Click the M365 Groups tab.
  4. Select the groups you want to add to an existing collection.
  5. From the actions toolbar, click Add To Collection. The Add to existing collection dialog opens.

  6. Select a collection from the Collection name dropdown and click Save to add the selected groups to the collection.

To add groups from a CSV file to a new or existing collection from the M365 Groups tab:

This is a two-step process as described below to add teams to an existing collection from the M365 Groups tab:

Step 1: Prepare the CSV file

NOTE: CSV file names with non-ASCII characters are not supported. Teams in the CSV that have not been discovered cannot be added to a collection.

Use the format shown below to prepare the CSV file. The minimal set of columns required are shown.

TIP: You can export the selected groups to a CSV file and then add the Collection column and retain the Source MailNickname column. All other columns in the exported CSV file will be ignored so you can remove those columns if you want.

  • Collection - Column header for the collection name
  • Source MailNickname - Email alias of the M365 group. You can get the Source MailNickname property of the teams when you export groups to a CSV file. Source MailNickname values are case-sensitive.

Step 2: Import the CSV 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 the Teams tile, or click Open from the Teams tile to open the Teams migration workspace.
  5. Open the M365 Groups tab.
  6. From the actions toolbar, click More > Import Collections. The Import Collections from File dialog opens.

  7. Select Teams/M365 groups from the Specify kind dropdown.
  8. Click Browse and select the CSV file. The selected CSV file name appears.
  9. Click Import.

NOTE: If a collection in the CSV does not exist, a new collection will be created with the name specified in the CSV.

To add groups from a CSV file to an existing collection from the Teams Collection dashboard:

This is a two-step process as described below:

Step 1: Prepare the CSV file

NOTE: CSV file names with non-ASCII characters are not supported. Groups in the CSV that have not been discovered cannot be added to a collection.

Use the format shown below:

MailNickName - Email alias of the M365 group. You can get the MailNickName property of the groups when you export groups to a CSV file. MailNickName values are case-sensitive.

Step 2: Import the CSV file

  1. From the project dashboard, click Open in the Teams tile to open the Teams migration workspace.
  2. From the top-right corner of the migration workspace, click Select Collection and then select the collection.
  3. Click Fill From File from the Teams collection Dashboard menu. The Fill from File dialog opens.
  4. Click Browse and select the CSV file that you created.
  5. Click Populate to add the groups from the file to the collection.

To verify the addition of the group to a collection:

  1. Check the Collections column in the M365 Groups List View that indicates the most recent collection where the group has been added and the number of additional collections that also contain the group.
  2. Select a group from the M365 Groups List View to open the Group Detail pane. Check the Collections property that lists all the collections where the group has been added.

Removing Groups from Collections

  1. From the project dashboard, click Open in the Teams tile to open the Teams migration workspace.
  2. From the top-right corner of the migration workspace, click Select Collection. Then select a collection to open the collections dashboard.
  3. Select the M365 Groups tab. From the Groups list view, select the groups that you want to remove from the collection.
  4. From the actions toolbar, click Remove from Collection.
  5. In the confirmation dialog click Remove to remove the selected groups from the collection.
  6. To return to the Teams migration workspace, click the collection dropdown at the top-right corner of the page, and select Show All.

Exporting Groups

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

  1. Click Teams from your migration project.
  2. Click the M365 Groups tab. From the M365 Groups List View select the groups you want to export.
  3. From the M365 Groups List View select More 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:

  • Group Name - source Microsoft 365 group name.
  • Workflow - (deprecated) the most recent operation performed on the Microsoft 365 group.
  • Created - date and time the Microsoft 365 group record was created
  • Target Group 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 group.

Provisioning Groups

Before you start, verify that you have discovered all the Microsoft 365 groups without teams. Make sure that all accounts that are members of these groups, have been discovered and matched with accounts in the target tenant. Group members are not added to groups in this step. Use the migration task to migrate group membership.

Considerations

A Group Map task will be automatically created in the Accounts and User Data migration workspace of the project. The purpose of this task is to match the M365 group accounts so that the On Demand Migration for SharePoint service can use the mapping for membership migration.

Starting the provisioning task

  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 the Teams tile, or click Open from the Teams tile to open the Teams dashboard.
  5. Click theM365 Groups tab.
  6. Select one or more groups from the Groups List View.
  7. Click Provision. The New Groups Provisioning Task wizard starts. Each step is described below:
  8. Provision Options

    These options control the actions of the provisioning task if the selected groups already exist in the target tenant. Groups that are not in the target tenant will be automatically provisioned.

    Select and configure the options as described below:

    1. Do not provision the group - The group will be skipped if it exists in the target tenant.
    2. Provision a new group. A suffix will be added to the original name - A new group will be provisioned with the specified suffix appended to the group name
      • New group display name suffix - Specify a suffix to append to the group name. The default suffix is (migrated).
    3. Merge with the existing group - Select this option to set up a mapping between a source and target group with the same name. When members are migrated with the migration task, the accounts that are members of the source group will be added to the same group in the target tenant.
    4. Suppress automatic Group Welcome Message sending - Select the check box to prevent group members from receiving a welcome message.
    5. Multi-geo options: Preferred location - Leave the preferred data location as Nonewhich is the default if the target is a multi-geo tenant and you have already configured a default geo location for the target tenant. All groups will be migrated to the same region. To set up the default geo location, see Configuring the Migration Project. If you change the default settings, please allow at least 5 minutes for the new settings to take effect. Alternatively, select the geo location configured for the target tenant.

    6. TIP: To migrate groups to different regions, the best practice is to create a collection of groups for each region. Example collection names could be "Migrate to EUR", "Migrate to JPN" or "Migrate to NAM". Then use the collection as a filter to create the provision task.

      For more information about multi-geo tenants, see Microsoft 365 Multi-Geo.

  9. Notification
    1. Send notification email once the task is completed - select this option to send a notification email when a provisioning task completes.
      • Only in a case of failure - select this option to send the email if the provisioning task fails to complete successfully.
    2. Recipients - enter the email address of the recipients of this email. You can specify multiple recipient email addresses separated by semicolon.
    3. Click Next.
  10. 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 - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time entered in the corresponding calendar field.
    2. Click Next.
  11. Summary
    1. Verify the task specifications as described below:
      • Name - Name of the task. The default name is Provision Groups. You can specify a custom name.
      • Source tenant - Name of the source tenant in this project.
      • Target tenant - Name of the target tenant in this project.
      • 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 provisioning 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.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação