立即与支持人员聊天
与支持团队交流

On Demand Migration Current - User Guide

About On Demand Migration Working with On Demand Migration Account Migration Mailbox Migration OneDrive Migration Microsoft Teams Migration Microsoft 365 Groups Migration SharePoint Migration Public Folders Migration Troubleshooting Finalizing the Migration Appendix A: Working with PowerShell

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 will 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. Teams in the target tenant may take up to 24 hours to be fully provisioned by Microsoft after they are created during a Teams provisioning task. We recommend that you migrate only those teams which are provisioned at least 24 hours before they are migrated.
  3. When teams are migrated, the SharePoint Contents list is updated, and the Migration 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.
  4. Channels are dedicated sections within a team to keep conversations organized. Channel membership can be Standard, Private or Shared.

In this topic:

Configuring the project

  1. Log in to Quest On Demand and choose an organization if you have set up 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. From the project Dashboard click Open in the SharePoint tile.
  1. Click Configure Project on the Teams project dashboard menu. The Edit Project wizard starts
  2. Step 1: Project Settings
    1. Set Migration Defaults

      Default Target User - Specify a user principal name (UPN) to use as the team owner when the existing owner has no match in the target tenant.

    2. Click Finish.
  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 Teams Migration Task wizard opens.
  7. Step 1. Migration Options

    1. Choose from the following options:
      • Channel Posts(Messages) - select this option to migrate the posts or messages in a channel.
        • Archive - select this option to 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.

          Links to files that are not yet migrated to the target will not work. remigrate Teams using Channel Files to ensure the links work correctly. To learn more, see Remigration.

          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.

      • SharePoint Content - select this option to migrate SharePoint content linked to teams selected for migration.
        • Standard (Channel files only) - select this option to migrate files, OneNote, Word, Excel and PowerPoint tabs added to the channel.
        • Standard and Customized (All SharePoint Content) - select this option to migrate OneNote, Word, Excel, PowerPoint and List tabs added to the channel, and site collections which includes any customized content such as descendant websites and lists.

        NOTE: For better performance and accountability the Get Total File Size task is automatically scheduled to run 24 hours after the migration task completes.

        For each team that is being migrated, the task calculates the total size of files across all channels of the team from the source and the target tenants. These totals are displayed in the Teams List view.

        If you manually start the task before 24 hours of the migration task, you may not get accurate results. The task retains its original schedule and runs 24 hours after the migration task completes.

      • Planner - select this option to migrate the Planner buckets, tasks, comments and the corresponding Planner tabs in teams.

        NOTE: For large Planner task migrations (e.g. 20,000+ tasks), see the KB article How to use ODM to migrate large amounts of Teams Planner items. (339416).

      • Group Mailbox - select this option to migrate the Microsoft 365 Group mailbox.
      • Team Membership - select this option to migrate team members. If this option is not selected, team members will not be migrated. If the team member or owner was not matched or migrated by an account migration task, a warning is reported: Cannot add *** as group ***: User Mapping does not exist. Workaround: Match or migrate the account and then re-run the Teams Provisioning task.
    2. Click Next.
  8. Step 2: File Version Options

    1. Choose the migration option for file versions associated with teams selected for migration.
      • Latest version only - select this option to migrate the most recent version of the file. All other versions will be ignored. This is the default selection.
      • More versions - select this option to migrate additional versions of a file based on the options described below. Large version sets take a significantly long time to migrate.
        • Number of versions - 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 - 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 - 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 dropdown list. 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 - select this option to migrate the latest version of the file, and all previous versions 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 dropdown list. 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 4. Archiving Options

    1. Archive the source team after migration - select this option to archive the source team after migration.
    2. Make source SharePoint site read only - select this option to set the associated SharePoint site to read only for the team members.
    3. Click Next.
  10. Step 4: Notification
    1. Send notification email once the task is completed - select this option to send a notification email when a migration task completes.
      • Only in a case of failure - select this option to send the email if the migration task fails to complete successfully.
    2. Recipients - enter the email address of the recipients of this email. You can specify multiple recipient email addresses separated by semicolon.
    3. Click Next.
  11. Step 5: Reporting

    Select the checkbox Generate detailed report of migration errors to generate a migration error report when you run the migration task.

    You can download the report from the Reports tab of the Teams workspace by clicking the Download link in the Error Log column. If there are no migration errors, a download link is not available. Error reports are retained for 30 days. After 30 days the download link is replaced with the label Expired and you can no longer download the report. For more information about error reports, see Reports.

  12. Step 6: 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 - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time.
        • Start - enter the start time for the task.
      • Priority - select a priority from the dropdown for the objects scheduled for migration with this task . Values are: Highest, High, Medium, Low and Lowest. The default priority is Medium. If the system is busy, the objects are queued (Migration state = Queued). When the system accepts new migration work, objects are taken from the queue based on the assigned priority and age in the queue.
    2. Click Next.
  13. Step 7: Summary
    1. Verify the task specifications as described below:
      • Name - name of the task. You can specify a custom name. The default name is Migrate Teams.
      • Source tenant - name of the tenant in this project.
      • Target tenant - name of the target tenant in this project.
      • Scheduled start - date and time when the task will start. Now indicates that the task will start immediately.
      • Priority - select a priority from the dropdown for the objects scheduled for migration with this task . Values are: Highest, High, Medium, Low and Lowest. The default priority is Medium. If the system is busy, the teams are queued (Migration state = Queued). When the system accepts new migration work, teams are taken from the queue based on the assigned priority and age in the queue.
    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 state in the task list indicates the progress of this task. Completed state 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.

Remigration

To remigrate messages, planner tasks and files, start a new teams migration task and follow the steps outlined in Migrating Teams. Select whether to migrate messages with attachments from the various options.

 

NOTE:

  • Do not reuse a previous migration task because the task options you need may be different.
  • See What We Migrate to review the Teams objects that are supported.
  • An incremental query is used automatically to find messages, tasks and files that were added or changed.
  • The initial synchronization must have completed successfully for the incremental synchronization to succeed.
  • Perform a remigration before you switch from the source to the target tenant.
  • Do not delete teams in the target tenant after migration.

 

Messages

Messages that were previously migrated successfully will not be remigrated. Messages are remigrated as follows:

  • New messages that are added since the last synchronization will be migrated.
  • Messages that were partially migrated, for example the attachment was unavailable during a previous migration, will be migrated. Updates to these messages by users in the target tenant will not be overwitten.

Planner Tasks

Planner Tasks in the target tenant that are created or updated will not be impacted. Planner Tasks from the source tenant will be remigrated as follows:

  • Previously migrated Planner Tasks that are updated on the source tenant will not be migrated to the target tenant.
  • New Planner Tasks will be migrated to the target tenant.

Files

Previously migrated list items and files with the same name and ID will be remigrated from the source tenant as follows:

  • Updates on source will be migrated to the target.
  • Updates to target will be overwritten by the remigrated source items or files.

When Teams files are remigrated an incremental query retrieves files that have been added or changed in the channels since the last synchronization. Follow the steps outlined in Migrating Teams and select Migrate messages and files.

Discovering Chats

On Demand Migration for Teams helps you discover and migrate Microsoft Chats for one or more matched users from a source tenant to a target tenant.

In this topic:

 

Starting a Chats Discovery Task

The Chats discovery task will list all user accounts that are matched with a user in the target tenant. If new users are added to the source tenant after the Chats discovery task completes, you must rerun another Chats discovery task.

NOTE: Chats discovery can also return the number of chats and most recent activity within the last 30 days. To activate this capability, you must configure Microsoft 365 for the source tenant, as described below:

  1. In Microsoft 365 admin center of the source tenant, go to Settings > Org Settings and open the Services tab.
  2. Select Reports, and clear the checkbox Display concealed user, group, and site names in all reports. This setting gets applied both to the usage reports in Microsoft 365 admin center and Teams admin center.
  3. Click Save changes.

 

To discover Microsoft Chats:

  1. Sign in to Quest On Demand and choose an organization if you have set up 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 the Teams tile, or click Open from the Teams tile to open the Teams dashboard.
  5. Select the Teams tab and then select the Chats tab.
  6. From the local toolbar, select Discover. The New Chats Discovery Task wizard opens.
  7. Step 1: Description
    1. Read only. This wizard creates a task to discover chats of source tenant user accounts that are already mapped to corresponding target tenant user accounts.
    2. Click Next.
  8. Step 2: Notification
    1. Send notification email once the task is completed - select this option to send a notification email when a discovery task completes.
      • Only in a case of failure - select this option to send the email if the discovery task fails to complete successfully.
    2. Recipients - enter the email address of the recipients of this email. You can specify multiple recipient email addresses separated by semicolon.
    3. 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 - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time.
        • Start - enter the start time for 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. The default name is Discover chats.
      2. Source tenant - name of the tenant where the statistics will be collected.
      3. Target tenant - name of the target tenant in this project.
      4. Scheduled start - date and time when the task will start. For example, Now indicates that the task will start immediately after you complete the wizard.
    2. Click Back to revise or review a previous step.
    3. Click Finish to complete the task wizard. The task will start as scheduled.

 

Reviewing the Chats Discovery Task

  1. Select the Tasks tab.
  2. Select the Discover Chats task that you want to review.
  3. In the task details pane that opens, the information presented is as described below:
    1. Type - Type of the task. The type is discover teams.
    2. Created - Date and time when the task was created.
    3. Modified - Date and time when the task was last updated.
    4. State - State of the task.
    5. Last Operation - The action that was most recently performed in this task.
    6. Schedule - Date and time when the task started. For example, Now indicates that the task started immediately after the task was created.
    7. Events (number) - Number indicates the count of events that the task encountered. The values indicate the type of the events and the event count for each type.

 

Reviewing the Chats Discovery Task Events

  1. Select the Tasks tab.
  2. Select the task named Discover Chats that you want to review.
  3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events for the selected task.
  4. Select an event that you want to review. In the task details pane that opens, the information presented is as described below:
    1. Object - Not applicable for this event.
    2. Task - Name of the task.
    3. Time - Date and time when the event occurred.
    4. Category - Type of task.
    5. Summary - a descriptive statement about the event.

 

Reviewing the Chats list view

The columns are described as below:

User Name - name of the user account.

Migration State - migration status of chats from discovery to successful migration. Values are Discovered, Migrating, Partially migrated, Partially migrated with Issues, Migrated, Migrated with Issues, Migration Failed.

Worklflow - (deprecated) the most recent operation performed on a team. Valid values are Discovered, Partially migrated, and Migrated.

ODM Licensed - indicates whether or not an On Demand Migration user account license has been consumed when the account migration task is started. Values are Yes, No, Not required.

OneDrive Status - migration status of the OneDrive files for this user.

Mailbox Status - migration status of a user's mailbox. It is a best practice to migrate a mailbox before chats are migrated for any user. Values are Discovered, Matched, Migrating, Migrated, Migrated with Issues, Migration Failed, Switched, and Migration Stopped.

Account Matching - (deprecated) indicated whether the user has been matched with another user in the target tenant. Value is Completed.

Migrated Chats - number of chats that have been migrated.

Archived Chats - indicates whether or not the archive option is selected during a chat migration. If the value is Yes, chats belonging to this user cannot be archived again.

Message Count (< 30 days) - number of chat messages generated by the user in the last 30 days. There is a latency of 24-48 hours from the time a message is created.

Last Activity (< 30 days) - most recent activity in the last 30 days. This data is provided by Microsoft based on user activity in Microsoft Teams.

Total Chats - total number of chats in the source tenant.

Source UPN - User Principal Name (UPN) of the source account.

Target UPN - User Principal Name (UPN) of the target account.

Deleting inactive users

You can delete inactive users from the Chats list view to prevent the migration of the inactive user's personal chats.

To delete inactive users

  1. Select one or more users in the list view that you want to delete.
  2. Click More Actions > Delete.
  3. Click Yes in the Delete Objects popup to confirm the action.

Managing Chats with Collections

Migrating large numbers of chats requires careful planning. Organize the user accounts into collections to make large chat lists more manageable.

Adding chats to Collections

You can add user accounts with chats to collections in three ways:

To add selected user accounts to a new collection:

  1. From the project dashboard, click Open in the Teams tile to open the Teams workspace.
  2. Open the Chats tab and select the user accounts that you want to add to a collection.
  3. From the actions toolbar, click New Collection. The New Collection dialog opens.

  4. Enter a collection name in the Collection name field and click Save to add the selected user accounts to the collection.

To add selected user accounts to an existing collection:

  1. From the project dashboard, click Open in the Teams tile to open the Teams workspace.
  2. If you need to create a new collection:
    1. From the top-right corner of the workspace, click Select Collection > + New Collection
    2. Enter a collection name and click Save to add this collection to the project.
  3. Open the Chats tab and select the user accounts that you want to add to the collection.
  4. From the actions toolbar, click Add to Collection. The Add to existing collection dialog opens.

  5. Select your collection from the Collection name dropdown and click Save to add the selected user accounts to the collection.

To create one or more collections with a CSV file:

This is a two-step process as described below:

Step 1: Prepare the CSV file

NOTE: Using a CSV file provides the following additional benefits:

  • Multiple collections can be created with the same CSV file.
  • Existing collections can be specified in the CSV file to add additional user accounts
  • Accounts can be listed in multiple collections

Use the format shown below to prepare the CSV file. The minimal set of columns required are shown.

TIP: You can export the selected user accounts to a CSV file and then add the Collection column and retain the Source UPN column. All other columns in the exported CSV file will be ignored so you can remove those columns if you want.

  • Collection - Column header for the collection name
  • Source UPN - User Principal Name (UPN) of the source account.

Step 2: Import the CSV file

  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 the Teams tile, or click Open from the Teams tile to open the Teams workspace.
  5. Open the Chats tab.
  6. From the actions toolbar, click More Actions > Import Collections. The Import Collections from File dialog opens.

  7. Select Chats from the Specify kind dropdown.
  8. Click Browse and select the CSV file. The selected CSV file name appears.
  9. Click Import.

NOTE: If a collection in the CSV does not exist, a new collection will be created with the name specified in the CSV.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级