Chat now with support
Chat with Support

Welcome, Quadrotech customers to Quest Support Portal click here for for frequently asked questions regarding servicing your supported assets.

On Demand Migration Current - Administrator Guide

About On Demand Migration Before You Start Working with On Demand Migration Starting Migration Project Configuring Connections Sharing Availability Information Collecting Account Information Pre-Migration Assessment Account Migration Hybrid Account Migration Domain Coexistence Mail Migration OneDrive Migration Resource Processing Public Folders Migration SharePoint Migration Microsoft Teams Migration Content Migration for Office 365 Groups Troubleshooting Finalizing the Migration

Prerequisites

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

  • Consents are already granted for source and target tenants.
    The following consents should be granted before Teams migration feature can be used
    • Migration - Basic,
    • Migration - Mailbox Migration
    • Migration - SharePoint,
    • Migration - Teams.

TIP: If the admin 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 Required 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. On Demand for Migration uses the global administrator account to grant consent because the ‘admin consent flow’ which it uses requires it; read more about the admin consent flow experience.

  • It is recommended to create or use dedicated (not added as owner or member to any team) source and the target Azure AD administrative accounts.

IMPORTANT: It is not recommended to use existing user accounts as source and target Azure AD administrative accounts, because it is recommended to remove them for safety reasons after the migration will be completed. These accounts can be removed from teams as described in Finalizing the Migration.

  • Azure AD administrative accounts should have Teams license.
  • It is not recommended that you change your Azure AD administrative accounts before completing the migration project.
  • Azure AD administrative accounts should be granted Global Administrator role on the tenants for which these account are used.
  • Azure AD administrative accounts should be granted Application Impersonation role on the tenants for which these account are used.
  • Accounts joined to existing teams should be matched and/or migrated in the migration project.

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 timestamp
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 OneNotes 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

 

Enumerating Groups

Before proceeding with the migration, retrieve the list of Microsoft Office 365 groups without Teams functionality from the source tenant.

Caution: Don’t start the migration before the discovery is finished. It might result in incorrect processing of migrated objects.

  1. Go to the main migration project Dashboard in case you use new migration UI. In case you are using classic experience or you are already on the Teams migration Dashboard, go to step 3.
  2. Click Teams widget.
  1. Click Discover on the project dashboard to create a new discovery task.
  2. Select Office 365 Groups without Teams functionality only option
  3. Schedule when the task will be started. See Task Scheduling for details. Click Next to view the task summary.
  1. Check scheduled start of the task and name the task. Click Finish to save or start the task depending on schedule option selected.

TIP: Give informative names for the tasks. It will greatly simplify the project management and event filtering in the future.

  1. Click Finish. You can monitor the task status using task widget on project dashboard.
  2. Click the task name on the widget to see the details or use Show all link.

Once the discovery task is complete, you will see the source tenant’s Office 365 groups without Teams functionality summary on the Microsoft Teams Migration Project Dashboard.

Discovery also checks the target tenant for potential conflicts (the identical group names on the source and target tenants.) The conflicting groups are marked with "Target team exists" in the Groups list. You will need to rename these groups in the source and create a new migration project to migrate such groups.

Provisioning Groups

After all source Office 365 groups without Teams functionality are discovered you can start to provision groups on the target tenant.

Make sure that all associated accounts are matched or migrated in account migration project and create the Provision task:

  1. Go to the main migration project Dashboard in case you use new migration UI. In case you are using classic experience or you are already on the Teams migration Dashboard, go to step 3.
  2. Click M365Groups widget.
  1. Select the Office 365 groups to be provisioned on the target. Provisioned groups will be owned by target Azure AD administrative account and with account matched with source group owner in case this account exists. The target Azure AD administrative account also will be added to the provisioned group as a member along with the members matched with source group members. In case any matched account cannot be found on the target, this account cannot be processed and related event will be reported.

TIP: Use Searching and Filtering to quickly navigate through the list of groups.

  1. Click Provision.
  1. Select whether automatic Group Welcome Message will be suppressed to avoid disturbing users by automatic Microsoft messages about adding to the provisioned groups. However, suppressing these messages results in performance degradation due to issues with Microsoft’s synchronization behavior. We recommend do not suppress these messages to avoid issues related to synchronization.
  2. Schedule when the task will be started. See Task Scheduling for details.
  1. Click Next to 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.

Migrating Groups and Associated Content

  1. Go to the main migration project Dashboard in case you use new migration UI. In case you are using classic experience or you are already on the Teams migration Dashboard, go to step 3.
  2. Click Teams widget.
  1. Open M365Groups and select the groups with provisioned state you want to migrate (Provisioning Teams for Target Tenant). Migration will be skipped for all groups that are not yet provisioned

TIP: Use Searching and Filtering to quickly navigate through the list of groups.

  1. Click Migrate. Group Mailbox and Calendar will always be migrated. This option cannot be cleared.
  2. Select whether to migrate associated SharePoint sites including all related content..
  3. Select whether to migrate Planner including all related content. This option is selected by default.
  4. Schedule when the task will be started. See Task Scheduling for details.
  5. Click Next to 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 migration task is created. Consider, additional content migration task will be also created automatically to transfer all associated content. You can track its progress in the Tasks, view the summary on the Dashboard or monitor alerts and notifications in the Events.

Related Documents