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 Mail Migration Public Folders Migration OneDrive Migration SharePoint Migration Microsoft Teams Migration Content Migration for Office 365 Groups Troubleshooting Finalizing the Migration

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.

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.

The 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 before you create the provision task.

NOTE: When using Microsoft Teams for Education, use On Demand Migration for Teams to discover and migrate the EDU group. If you use On Demand Account Migration to discover and migrate the EDU group, then provisioning the EDU teams will fail with a “Request failed with BadRequest status code (Bad Request)” event error.

 

Create the provision task

Open the New Provision Task dialog

From the OnDemand Migration for Teams, teams tab

  1. Check 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.

  2. Click provision to open the New Provision Task dialog.

 

Fill in the New Provision Task dialog

 

Provision Options: Does a team with the same name already exist on the target?

The default option is to Provision a new team on the target with the original name plus suffix. The default suffix is "Migrated". You can change the suffix via the New team display name suffix field.

 

The alternative is to Merge to the existing team on target. When selected, new fields become available. By default On Demand will Provision a new channel on the target with the original name plus suffix. You can change the default suffix "Migrated" via the New channel display name suffix field.

Alternatively, select Merge source channel conversations with the target channel. Select this option if the target channel is empty. If conversations already exist in the target channel then selecting this option will result in mixing the conversations from the source and the target on the target and is not revertible.

Provision Options: Target multi-geo tenant preferred teams location

Leave the preferred data location as Default if the target tenant is a multi-geo tenant (see Microsoft 365 Multi-Geo). All teams and groups will be migrated to the same region as the target admin.

Alternatively, select the geolocation configured for the target tenant.

TIP: To migrate teams/groups to different regions, best practice is to create a collection for each region (see Using Collections for Teams) and add the teams/groups to the appropriate collection. Example collection names are "Migrate to EUR", "Migrate to JPN" and "Migrate to NAM". Use the collection as a filter to create the provision task.

 

Provision Options: Suppress automatic Group Welcome Message sending

When selected users will not be disturbed by automatic Microsoft messages regarding adding to the provisioned Teams.

NOTE: 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.

 

Fill in the New Provision Task dialog: Schedule

Schedule when the task will be started. See Task Scheduling for details.

 

Verify the New Provision Task dialog: Summary

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 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 - could take a long time to complete.
    • Migrate messages only - recommended for fast synchronization of teams.
    • Use previously migrated files - use when On Demand Migration has already migrated files to the target. Teams messages migrated in this task will have access to files on the target.
    • Migrate group mailbox only - use to correct group mailbox issues.

When migrating Teams using Migrate messages only, message links will not work for files not yet migrated to the target. Re-migrate Teams using Migrate messages and files to correct this issue. To learn more, see Re-migrating messages and files.

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 migrate OneNote including all related content. This option is selected by default.
  2. Select whether to migrate Planner including all related content. This option is selected by default.
  3. Select whether to migrate Word, Excel, and PowerPoint tab apps in the team channels. This option is selected by default.
  4. Select whether to migrate the Group Mailbox. 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.

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.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating