Chat now with support
Chat with Support

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

Content Migration for Office 365 Groups

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

Basic Microsoft Office 365 groups without Teams functionality content migration workflow consists of the following steps:

# Step
1 Create Microsoft Teams migration project (created automatically with New Migration UI)
2 Grant necessary permissions in case these permissions are not already granted
3

Discover Office 365 groups without Teams functionality on the source tenant

There are no provision on the target on this step.

4

Provision groups on the target tenant. Target teams will be owned by the target Azure AD administrative account that is used to perform the provisioning.

  • Source Azure AD account will be added to all source Office 365 Groups as a member
  • Target Azure AD account will be added to all target Office 365 Groups as a member and owner.

These accounts can be removed from groups as described in Finalizing the Migration.

5

Migrate Microsoft Office 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 and track issues

What We Migrate for Groups

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

  • Group Mailbox & Calendar (this content is always migrated, this option cannot be cleared)
  • SharePoint site as a whole (this option is optional)
  • Planner (this option is optional)

Please, consider the following:

  • Office 365 group migration between tenants with different default language is not supported.
  • Office 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 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 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.

  • 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.

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.

Related Documents