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 Domain Coexistence Mail Migration OneDrive Migration Resource Processing Public Folders Migration SharePoint Online Migration Microsoft Teams Migration Finalizing the Migration

Discovering Teams

Before proceeding with the migration, retrieve the list of teams 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. Click Discover Teams on the project dashboard to create a new discovery task.
  2. 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 teams summary on the Microsoft Teams Migration Project Dashboard.

Discovery also checks the target tenant for potential conflicts (the identical team names on the source and target tenants.) The conflicting teams are marked with "Target team exists" in the Teams list. To see all conflicts, click Needs your attention on the left.
The conflicts are resolved during the provisioning.

Exporting Mapping for Teams

To export the teams mapping as a comma-separated values (CSV) file, select the required teams on the Teams tab and click Export.

You can customize this file and use it as a base for manual mapping.

Exported data will contain source team name (may be team IDisntead), suggested target team name to provision and MailNickName MailNickName parameter specifies the alias for the associated Office 365 Group. This value will be used for the mail enabled object and will be used as PrimarySmtpAddress for this Office 365 Group. The value of the MailNickName parameter has to be unique across your tenant.

Using Manual Mapping for Teams

In some cases, you might want to rename the teams on target or merge them with the existing teams with different names. To achieve this goal, provide a file with the custom mapping between source and target teams. You might use the exported team mapping as a template.

  1. Export a comma-separated values (CSV) as described in Exporting Mapping for Teamsand edit it to prepare for manual mapping.

Important: When editing a CSV file, the following should be considered:

  • To ensure manual mapping will be completed successfully do not remove any columns from exported csv file.
  • You can edit necessary entries, if necessary. In case any objects are added by mistake, please remove entire rows related to these objects.
  • You can merge multiple source teams to a single target team. Just provide the same target team name in a mapping file.
  • File names with non-ASCII characters are not supported.
  1. Open Teams tab and click Map from File.
    Do not select any teams from the list – you have already specified them in the file created on Step 1.
  2. Click Browse to open the mapping file prepared on Step 1.
  3. Browse for file and click Open. Selected file name appears next to the Browse button.
  1. Schedule when the task will be started. See Task Scheduling for details. Click Next to view task summary.
  2. Check selected options. Click Finish to save or start the task depending on schedule option selected.

The task is created. You can track the progress in the Tasks list or view the summary on the Dashboard.

 

Pre-Migration Assessment for Teams

On Demand Migration analyzes your environment and tracks potential problems, misconfiguration, and risks that might adversely affect the migration. Use Assessment view to see the summary reports on the discovered data and use the automatic filters to quickly select certain items.

The following reports are available for Teams:

  • Workflow - Teams sorted by completed workflow
    • Discovered
    • Processed
    • Migrated
  • Teams- Teams sorted by processing status
  • Idle
  • In progress
  • Needs your attention
  • Teams By Size
  • Teams By Last Activity Time
  • Teams By Channel Count
  • Teams By Member Count

Once you handle the issues, if any, go to List View screen. You are ready to start the migration.

Related Documents