Converse agora com nosso suporte
Chat com o suporte

On Demand Migration Current - User Guide

About On Demand Migration Before you Start Working with On Demand Migration Account Migration Mailbox Migration OneDrive Migration Microsoft Teams Migration Microsoft 365 Groups Migration SharePoint Migration Public Folders Migration Troubleshooting Finalizing the Migration Appendix A: Working with PowerShell

Microsoft 365 Groups Migration

On Demand Migration for Teams securely migrates content for Microsoft 365 Groups without Teams functionality across Microsoft 365 tenants. You can also use this dashboard for migration of Microsoft Teams and associated Microsoft 365 Groups migration (see Microsoft Teams Migration). Microsoft Teams migration requires additional licensing.

The basic Microsoft 365 Groups (without associated Teams) migration process consists of the following steps:

# Step
1 Create a new migration project or open an existing project.
2 Grant necessary permissions in case these permissions are not already granted.
3

Discover Microsoft 365 Groups (without associated Teams) in the source tenant. These groups are not provisioned in the target tenant at this stage.

4

Provision groups in the target tenant.

  • The temporary Migration Manager account in the source tenant will be added to all source Microsoft 365 Groups as a member
  • The temporary Migration Manager account in the target tenant will be added to all migrated target Microsoft 365 Groups as a member and owner.

These accounts can be removed from groups after the migration is completed.

5

Migrate Microsoft 365 Groups without Teams functionality

6

Automatically migrate files associated with content. All files associated with content are transferred to the target according to the options, selected in the migration task.

7 Monitor the progress by tracking tasks and events.

What We Migrate

The following content associated with Microsoft 365 Groups without Teams functionality can be migrated:

  • Inbox folder and Calendar from the group mailbox (this content is always migrated, this option cannot be cleared)
  • SharePoint site as a whole (this is optional)
  • Planner (this is optional)
  • Group settings
Limitations
  • Microsoft 365 group migration between tenants with different default language is not supported.
  • Microsoft 365 group cannot be migrated in case the target group already exists. For all such groups the Target group exists warning message is displayed in the grid. As a workaround, you can rename the source group and re-create migration project.

Prerequisites

Verify the following requirements are met before migrating Microsoft Teams. If these actions are not performed, discovery, provision and migration tasks will fail or some data might be lost!

  • The following consents are granted before Teams migration can be started
    • Migration - Basic,
    • Migration - Mailbox Migration
    • Migration - SharePoint,
    • Migration - Teams.

TIP: If the consents are not granted or expired, Discover Teams action is disabled and the following notification is displayed: Grant admin consent to the following Migration sub modules on the Tenants page for both source and target tenants: Basic, SharePoint, and Teams. Open Tenants page and grant the necessary Consents and Permissions so that the product can access the source and target tenants. You will be redirected to the Microsoft web site for granting admin consent. Once admin consent is granted, you can start discovering Teams.

  • User must be matched or migrated before using the On Demand Migration for Teams service.
  • Images, media files and documents referenced in one-on-one or group chats are stored in your OneDrive for Business folder. They must be migrated using the On Demand Migration for OneDrive service, before you migrate the chats.
  • It is recommended to create or use source and the target temporary Migration Manager accounts.
  • The temporary Migration Manager accounts in the source and target tenant should have Teams license.
  • Do not change your temporary Migration Manager accounts before completing the migration project.
  • The temporary Migration Manager accounts should be granted the Global Administrator or Teams Administrator role on the tenants for which these account are used.
  • The temporary Migration Manager accounts should be granted Application Impersonation role on the tenants for which these account are used.
  • Accounts joined to existing teams should be matched or migrated in the migration project.

IMPORTANT: It is recommended to remove the source and target temporary Migration Manager accounts for safety reasons after the migration is completed. These accounts can be removed from teams as described in Finalizing the Migration.

Required permissions

Feature Required permissions
Migrate conversations Read all channel messages
  Have full access to the Chat Service Aggregator
  Have full access to the Skype Teams Service
  Create chat and channel messages with anyone's identity and with any time stamp
Migrate private chats Read all chat messages
  Read and write user chat messages
Provision groups and teams Read and write directory data
  Read and write all groups
Migrate files and OneNote items Read and write all OneNote notebooks
  Read and write items in all site collections
  View and modify notes for all users
Migrate groups and teams membership Read all users' full profiles
  Read or write user region
  Add and remove members from all teams
  Add and remove members from all channels

Temporary Migration Manager accounts

It is strongly recommended to create source and target temporary Migration Manager accounts. These accounts should not be an owner or member of any team. For security reasons it is recommended to remove these accounts once the migration is complete.

The target temporary Migration Manager account use is in and not limited to the following scenarios:

  • The target temporary Migration Manager account that is used to perform Teams provisioning creates and owns these provisioned target teams.
  • The target temporary Migration Manager account is added to all target teams and Microsoft 365 Groups as a member and an owner, and to all target private channels as an owner.
  • The target temporary Migration Manager account is used to perform the Teams migration and displayed as the owner of all migrated conversation and chat messages and planner tasks on the target.
  • The target temporary Migration Manager account is added to all the chats (both group chats and private chats) as a participant during chats migration, and then removed from the migrated chats as soon as the chat migration is complete. All migrated chats of the target temporary Migration Manager account are hidden when the chat migration is complete.

Discovering Groups

In this topic:

Discovering all groups

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

To start the Discover Groups 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 Discover M365 Groups from the Groups tile in the Teams dashboard

    - or -

    Select the M365 Groups tab and select List View if not already selected. Then click Discover Groups > Discover All from the Actions menu.

  6. The New Groups Discovery Task wizard opens.
  7. Step 1: Discovery Options

    1. Collect Plan and Task statistics for Groups - Select this option to start a Collect Statistics Task to count the number of Plans and Tasks in Groups.

      NOTE: When a Collect Statistics Task is started, the temporary Migration Manager for the source tenant will be added to all groups, or the groups specified in a CSV file. The additional information collected by the tasks are used in the migration process for teams and groups, and helps improve the performance of the migration task.

    2. Click Next.
  8. Step 2: 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. Step 3: 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.
        • Start - enter the start time for the task.
    2. Click Next.
  10. Step 4: 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 Groups.
      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 Groups from a File

When you have a large set of groups but you want to migrate a subset of those groups, you can start the discovery process by using a CSV file. The CSV file lets you specify the groups that you want to discover and ignore the rest. This is a two-step process:

Step 1: 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 the Microsoft 365 tab in the Active Groups page.
  4. Click Export and then click Export groups in this list. A Groups.csv file will be downloaded to your computer.

  5. Edit the CSV and retain the groups you want to discover that are not associated with Teamsand delete the rest. You can filter that data based on the Has Teams column to get a list of groups that are not associated with teams. If you retain a row that references a group associated with a team, the group will be ignored during discovery. Then retain the Group ID and Group name columns.

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

Step 2: Starting the Discover Groups 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 the M365 Groups tab and select List View if not already selected. Then click Discover Groups > Discover from file from the Actions menu.
  6. The New Groups Discovery Task wizard opens.
  7. Step 1: Discovery Options

    1. Click Browse and select the CSV that contains the Group IDs and Group names of the groups that you want to discover.
    2. Collect Plan and Task statistics for Groups - Select this option to start a Collect Statistics Task to count the number of Plans and Tasks in groups.

      NOTE: When a Collect Statistics Task is started, the temporary Migration Manager for the source tenant will be added to all groups, or the groups specified in a CSV file. The additional information collected by the tasks are used in the migration process for teams and groups, and helps improve the performance of the migration task.

    3. 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 - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time.
        • Start - enter the start time for 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. The default name is Discover Groups.
      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 Groups Discovery Task

  1. Select 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 discovergroups.
    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 selected the option to collect statistics in the New Groups Discovery Task wizard, you will see and additional task for Collect Plan and Task statistics for Groups. Click the task to view the corresponding details in the details pane.
 

Reviewing the Groups Discovery Task Events

  1. Select 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 group.
    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.

Reviewing the Collect Statistics Task

  1. Select the Tasks tab.
  2. Select the task that you want to review. The default name is M365 Group Collect Statistics Task.
  3. In the task details pane that opens, the information presented is as described below:
    1. Type - Type of the task. The type is discovergroups.
    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) - The number of events that the task encountered.

Reviewing the Collect Statistics Task Events

  1. Select the Tasks tab.
  2. Select the Collect Statistics 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 group.
    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

Reviewing statistics collected

Statistics are collected if the option to collect statistics is selected in the New Groups Discovery Task.

  1. From the Teams dashboard, click the Teams tile.
  2. Select the M365 Groups tab and select List View if not already selected.

The columns are as described below:

  • Group Name - name of the group in the source tenant.
  • Migration State - status of the task in the migration process. Values are as listed below:
    • Discovered
    • Exists in target - team in the source tenant exists in the target tenant
    • Provisioning
    • Provisioned
    • Provisioned with issues
    • Provision failed
    • Migrating
    • Partially migrated
    • Partially migrated with issues
    • Migrated
    • Migrated with issues
    • Migration failed
  • Workflow - (deprecated) the most recent operation performed on the group. Valid values are Discovered, Provisioned, and Migrated.
  • SharePoint - nature of the SharePoint site linked to the team. Values are as described below:
    • <no-value> - SharePoint content has not be discovered yet.
    • Standard - There is at most 1 SharePoint site and 4 Lists in the SharePoint site collection

    • Customized - There are more than 1 site and 4 Lists in the SharePoint site collection

    NOTE: The SharePoint status is available only after the New Teams Provisioning Task is run.

  • Members - number of members in the source tenant group.
  • Plans - number of plans in the source tenant group.
  • Migrated Plans - number of plans migrated to the target tenant group.
  • Tasks - number of tasks in the source tenant group.
  • Migrated Tasks - number of tasks migrated to the target tenant group.
  • Created - date and time the team record was created.
  • Source MailNickname - email alias of the associated Microsoft 365 Group.
  • Target Group Name - name of the corresponding group in the target tenant if it exists.

 

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação