Chat now with support
Chat with Support

On Demand Migration Current - User Guide

About On Demand Migration Before You Start Account Migration Mail Migration Public Folders Migration OneDrive Migration SharePoint Migration Microsoft Teams Migration Microsoft 365 Groups Migration 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.

Migrating Teams

When you migrate teams, files stored in the corresponding SharePoint document libraries and OneNote items stored in asset libraries can be migrated. The SharePoint sites associated with teams may contain additional objects that cannot be migrated with the On Demand Migration for Teams service. The following information is made available to you to help you manage the migration of SharePoint objects that cannot be migrated:

  1. When teams are provisioned on the target tenant, a SharePoint New Discovery Task is run. The task discovers the corresponding SharePoint site collection and its contents listed in the SharePoint Contents tab.
  2. When teams are migrated, the SharePoint Contents list is updated, and the Content State of the objects is changed to Migrated. You can review the list and use the On Demand Migration for SharePoint service to migrate additional SharePoint objects.

To migrate Microsoft Teams:

  1. Log in to Quest On Demand and choose an organization if you have multiple organizations.
  2. From the navigation pane, click Migration to open the My Projects list.
  3. Create a new project or open an existing project.
  4. Click Teams from the project tiles, or click Open from the Teams tile to open the Teams dashboard.
  5. Select one or more teams from the Teams List View.

    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.

  6. Click Migrate. The New Migration Task wizard opens.
  7. Step 1. Migration Options

    1. Choose from the following options:
      • Channel Posts(Messages) - Migrate the posts or messages in a channel.
        • Archive - Migrate and archive channel messages as an HTML file for each channel. The HTML file is added to the file list of the team's SharePoint site in the target tenant. A new message from the target tenant Administrator is added to each migrated channel with a link to its HTML file. A new tab called Conversation History is created in the target channel and the archived messages are displayed there.
          • All messages - Migrate and archive all messages across all channels in the team
          • Messages older than 15 days - Migrate and archive messages across all channels in the team that are older than 15 days.
          • Messages older than 30 days- Migrate and archive messages across all channels in the team that are older than 30 days.
          • Messages older than 60 days - Migrate and archive messages across all channels in the team that are older than 60 days.

          NOTE:

          Messages that are more recent than the 15, 30 or 60 days option that is selected will be migrated but not archived.

          If the migration task is successful and the archive HTML file is created in the target tenant, it cannot be modified by subsequent migrations. If you attempt another migration and select the Archive option, the Archive option is ignored. All new and modified channel messages from the selected teams will be migrated and posted to the corresponding team channels in the target tenant. Messages already archived will be skipped unless they were subsequently modified (edited or linked to replies or attachments) in the source tenant.

          If the migration task is unsuccessful and the archive file is not created, subsequent migrations with the Archive option selected will attempt to create an archive HTML file in the target tenant. Archive sub-options like All, Messages older than 15 days, Messages older than 30 days or Messages older than 60 days, are re-evaluated for all messages in the channel. The new set of messages selected for archival may not be the same set of messages identified in the previous archive attempt.

      • Channel Files - Migrate the files, attachments, OneNote, Word, Excel and PowerPoint apps in the channel.
      • Team Membership - Select this option to migrate team members. If this option is not selected, team members will not be migrated.
      • Planner - Migrate the Planner buckets, tasks, comments and the corresponding Planner tabs in teams.
      • Group Mailbox - Migrate the Microsoft 365 Group mailbox.

      When migrating Teams using Channel Posts (Messages), links to files that are not yet migrated to the target will not work. Re-migrate Teams using Channel Files to ensure the links work correctly. 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 Channel Posts and Channel Files options selected. Then repeat migration of these teams with Group Mailbox option selected.

    2. Click Next.
  8. Step 2: Version Options

    1. Choose the migration option for file versions associated with teams selected for migration.
      • Latest version only - This is the default selection. The most recent version of the file will be migrated. All other versions will be ignored.
      • More versions - Additional versions of a file will be migrated based on the options described below. Large version sets take a significantly long time to migrate.
        • Number of versions - The maximum number of version to migrate. The available choices are: 2, 5, 10, 30, 60, 90 and 365. When you specify the number of versions, additional options can be selected.
          • Latest version and preceding versions - The version count includes the latest version and the preceding versions in chronological order restricted to the Size Limit of the latest version. For example, if you choose to migrate 5 versions, then the most recent version and 4 preceding versions will be migrated as long as the most recent version does not exceed the selected size limit specified.
          • Latest version and daily latest from preceding days - The version count includes the latest version and the latest version from each preceding day restricted to the Size Limit of the latest version. For example, if there are many versions of a site and you choose to migrate 5 versions, then the most recent version and the latest version from each of the 4 preceding days will be migrated as long as the most recent version does not exceed the selected size limit specified.
          • Size limit - This setting is available if the Latest version and preceding versions or the Latest version and daily latest from preceding days option is selected. By default, the size limit is 80 MB. You can configure the size limitation by selecting from one of the possible values in the drop down. If the size of the latest file version exceeds the selected size limit, the latest version will be migrated and previous versions will be ignored. If the size of the latest file version does not exceed the selected size limit, then the file and its versions will be migrated based on your selection between Latest version and preceding versions or Latest version and daily latest from preceding days.
      • All Versions - The latest version of the file will be migrated, and all previous versions of the file will be migrated if the latest version does not exceed a specified size limit. This option requires significantly more time to migrate all the versions.
        • Size limit - This setting is available if the All Versions option is selected. By default, the size limit is 80 MB. You can configure the size limitation by selecting from one of the possible values in the drop down. If the size of the latest file version exceeds the selected size limit, the latest version will be migrated and previous versions will be ignored. If the size of the latest site version does not exceed the selected size limit, then the file and its versions will be migrated.
    2. Click Next.
  9. Step 3: Schedule
    1. Choose from one of three options to schedule the task. The scheduler will be activated only after you complete the task wizard.
      • Run now - the task will run immediately.
      • Run later - the task must be started manually.
      • Schedule - specify a future date and time to run the task.
    2. Click Next.
  10. Step 4: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. You can specify a custom name.
      2. Source tenant - name of the tenant in this project.
      3. Target tenant - name of the target tenant in this project.
      4. Scheduled start - date and time when the task will start. Now indicates that the task will start immediately.
    2. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.

The migration task is created. You can track its progress from the Taskstab, view the summary on the Dashboard or monitor alerts and notifications from the Eventstab.

Important: The task status in task list indicates the progress of this task. Completed status means this task processing is completed. If the migration has any errors, the status column in the Teams List View will indicate Migration partially failed.

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-migrating messages and files

To re-migrate messages and files, re-run the task following the steps outlined in Migrating Teams. Select whether to migrate messages with attachments from the various options.

 

NOTE:

  • An incremental query to find messages and files that were added or changed is used automatically.
  • The initial synchronization must have completed successfully in order for the incremental synchronization to start working for further migrations.
  • Previously migrated messages and files will not be re-migrated by this process. We highly recommend you do not delete teams in the target tenant after migration.
  • See What We Migrate to consider what changes are supported to be updated.
  • It is recommended to perform re-migration before the source and target tenants will be switched.

 

Message updates

When Teams messages are re-migrated a delta query retrieves those messages that have been added or changed in the channels since the last synchronization. Messages that did not migrate completely previously, for example the attachment was unavailable, will be additionally migrated into new and modified messages.

File updates

Follow the steps outlined in Migrating Teams and select Migrate messages and files.

NOTE: When Teams files are re-migrated an incremental query retrieves files that have been added or changed in the channels since the last synchronisation.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating