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

Provisioning Teams for Target Tenant

After all source teams are discovered you can start to provision teams on the target tenant.

IMPORTANT: Provisioning of public teams is not supported for migration scenarios from one education tenant to another. Only private teams can be provisioned for these scenarios.

Provision task help you to perform the following:

  • Create Office 365 groups on the target tenant.
  • Resolve naming conflicts.
  • Provision teams to the target tenant.
  • Provision team membership and ownership for provisioned teams.

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 Teams widget.
  1. Open Teams and select the teams to provision associated Office 365 group and teams on the target. Provisioned teams will be owned by target Azure AD administrative account. This account also will be added to the provisioned team as a member along with the members matched with source team 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 search and filtering to quickly navigate through the list of teams.

  1. Click Provision.
  2. Decide what to do if the team with the identical name already exists on the target. You have 3 options:
    • Do nothing. Leave the target team as is.
    • Merge to the existing target team. All users from the source team will be added to the target team during provision. Refer to Merging Considerations below for details of team channel naming after merge.
    • Create a new team. A new team will be created on the target by appending the provided text to the original team name. For example, "HR - Migrated".
  1. Select Merge to Existing Target Team Channels option to merge into existing team current channel instead of creating a new channel.
  2. Select whether automatic Group Welcome Message will be suppressed to avoid disturbing users by automatic Microsoft messages about adding to the provisioned Teams. However, suppressing these messages may result in performance degradation due to issues with Microsoft’s synchronization behavior. We suggest you check the performance during the pilot migration. For teams provisioned by tasks created in previous releases, for which Group Welcome Messages were suppressed by default, these email messages may be received in some cases, depending on stage of processing by Microsoft.
  3. 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.

Merging Considerations

If Merge to the existing target team option is selected in case of conflicting source and target team names the team on the source tenant will be merged into the team in the target tenant. All users from the source team will be added to the target team during provision. Refer to the Renaming and Merging Considerations subsection of Migrating Microsoft Teams for details on how to conflicting channel names are resolved during migration.

Migrating Microsoft Teams

  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 Teams and select the teams with provisioned state you want to migrate. Migration will be skipped for all teams that are not yet provisioned

TIP: It is recommended to select no more than 100 teams for the task to streamline the process. You can create several tasks that will be executed concurrently. Use search and filtering to quickly navigate through the list of teams.

  1. Select whether to migrate messages with attachments. The following options are available:
    • Migrate messages and files
    • Migrate messages only
    • Use previously migrated files
    • Migrate group mailbox only

Migrate messages onlyoption is recommended for fast synchronization of teams. Migrate messages and files could take a long time to be completed. In case Migrate messages and files option is not selected for faster migration, links to the file that are not migrated in previous tasks will be visible in conversations on the target, but these files cannot be opened using these links. It is recommended to use re-migration scenario for synchronization purposes. If necessary, you can re-run migration task later with Migrate messages and files option selected to allow access to these files. In case the files were already migrated in previous tasks, select Use previously migrated files to allow access to these files. Migrate Group Mailbox only option is intended only for the group mailbox migration issues.

TIP: Migration task may hang due to group mailbox migration issue. If this is the case, stop migration task and re-run the team migration with the Migrate messages and files option selected. Then repeat migration of these teams with Migrate Group Mailbox only option selected.

  1. Select whether to merge reply message in threads in one combined message per thread to avoid throttling and improve performance. This option is selected by default.

NOTE:

  • Combined reply will only show first one link preview if there are 2 or more link preview due to Microsoft limitation.
  • Combined messages appear as Important if any reply in the thread is Important.
  1. Select whether to migrate OneNote including all related content. This option is selected by default.
  2. Select whether to migrate Word, Excel, and PowerPoint tab apps in the team channels. This option is selected by default.
  3. Select whether to migrate Planner including all related content. This option is selected by default.
  1. 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 migration 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.

Important: The task status in task list only indicates the progress of this task. Completed status only means this task processing is completed. If the migration has any errors, the flag Migration partially failed will appear in the Teams/Group grid.

Renaming and Merging Considerations

If the channel with the same name already exists on target, the source channel will be migrated to a new one with a name: <source team name> - migrated.

Unique channel names remains unchanged.

 

 

Renamed Channel Migration

When a channel is renamed, Microsoft does not rename the corresponding SharePoint Document folder for this channel, this is a known issue. For example, when Channel “Channel_1” is renamed to “Channel_Renamed”, the folder name under the “Files” tab is still “Channel_1”. After migration is completed, all messages and files can be opened correctly. Consider, that these files cannot be displayed on the target Files tab. This is because all the files are still stored and migrated under ““Channel_1” folder. “Channel_Renamed” folder does not exist until you click the “Channel_Renamed” channel’s Files tab, then the system will generate an empty folder for it. But no files will be stored there. To avoid files and message association breaking it is not recommended to rename folders manually. If necessary, you can copy necessary files to “Channel_Renamed' folder, but these files won't associated with messages.

Re-migration scenario

You can use re-migration to synchronize teams that are already migrated or to allow access to the previously migrated files.

To perform re-migration:

  1. Open Teams and select the teams with migrated state you want to re-migrate.
  1. Select options you need for re-migration:
    • Migrate messages and files in case files were not yet migrated (Migrate messages onlyoption was selected for the migration task for these teams).
    • Use previously migrated files in case files were already migrated (Migrate messages and files option was selected for the migration task for these teams).

The Teams synchronization performance is incremental. Delta query, which retrieves those messages that have been added or changed in the channels since the last synchronization, is used automatically after completing the initial synchronization for further re-migrations.

It is recommended to perform re-migration before the source and target tenants will be switched.

Consider the following:

  • The initial channel synchronization must be completed successfully in order for the delta synchronization to start working for further migrations.
  • If the migration for some messages is not completed, for example, the attachment is not available, such messages will be additionally migrated into new and modified messages.
  • Refer to What We Migrate: Microsoft Teams Migrationto consider what changes are supported to be updated.
Related Documents