Chat now with support
Chat with Support

NOTICE! We are upgrading our support telephone services, implementing Genesys, starting the week of May 26, 2025

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

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.

In this topic:

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 Collections > 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 Collections > 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 to one or more collection with a CSV file:

Using a CSV file provides the following additional benefits:

  • Multiple collections can be created with the same CSV file.
  • Existing collections can be specified in the CSV file to add additional groups.
  • M365 Groups can be listed in multiple collections.

This is a two-step process as described below to add teams to one or more collections:

Step 1: Prepare the CSV file

  1. From the actions toolbar, click Collections > Import Collections. The New Import Collections from File Task wizard starts.
  2. From the Mapping File step, click Download Example File. A ZIP file is downloaded.
  3. Extract the CSV file and use it to prepare your import file in one of three formats described below:

    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 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. If a collection in the CSV does not exist, a new collection will be created with the name specified in the CSV.
    • 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. Open the M365 Groups tab.
  2. From the actions toolbar, click Collections > Import Collections. The New Import Collections from File Task wizard starts.
  3. Mapping File
    1. Click Browse and select the CSV file. The selected CSV file name appears.
  4. Schedule
    1. Choose from one of three options to schedule the task. The scheduler will be activated 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.
  5. Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. The default name is Import Collections From File. You can specify a custom name.
      2. 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.
    3. Click Finish.

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.

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 Migrate > Projects 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 remove items from a collection:

  1. From the actions toolbar, click Collections > Remove from Collection.
  2. In the confirmation dialog click Remove to remove the selected groups from the collection.

To rename the collection:

  1. Click Collections > Rename Collection in the Actions toolbar of the collections dashboard.

To delete the collection:

  1. Click Collections > Delete Collection in the Actions toolbar of the collections dashboard.

To see the tasks for collection-specific Group objects:

  1. Open the Tasks tab.

To see the events related to the collection:

  1. Open the Events tab.

To return to the Teams migration workspace:

  1. 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 Migrate > Projects 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.

Removing Groups

To manage large lists of M365 groups in a project, you can remove one or more M365 groups from the groups list view that you don't need for migration. The M365 groups that are removed will remain in the source tenant and you must re-discover the groups in the project when you need them for migration.

When 365 groups are removed, all associated items, mappings and migration information will also be removed from the project. When these M365 groups are rediscovered, they will be treated as new M365 groups in the project and the process of provisioning and migration of the M365 groups and related items must be repeated.

If these groups are listed in other projects, they will be displayed in those projects.

  1. Log in to Quest On Demand and choose an organization if you have multiple organizations.
  2. From the navigation pane, click Migrate > Projects 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. Select the Teams tab and select List View if not already selected.
  6. Select the groups you want to clear.

    TIP: Use filters, search or collections to quickly navigate through the list of groups.

  7. Click More and then click Delete.
  8. The Remove Objects confirmation dialog opens.
  9. Click Remove to remove the selected groups from the list.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating