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

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

Re-migrating messages and files

To re-migrate messages and files, re-run the task following the steps outlined in Migrating Microsoft 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 Microsoft 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.

Migrating Microsoft 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:

 

Discover Microsoft Chats

The Discovery Task will list all user accounts that have a Teams Chat. If new users are added to the source tenant after the Discovery Task completes, you must re-run another Discovery task.

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 select an existing project.
  4. Click Teams from the project tile. You can also click Open Project to open the project dashboard and then click Open from the OneDrive tile. The Accounts and User Data dashboard opens.
  5. Select the Teams tab and then select the Chats tab.
  6. From the local toolbar, select Discover. The New Discovery Task wizard opens.
  7. Step 1: Discovery Options
    1. Select from the following options:
      • Check all users - every user account will be checked for private chats
      • Check matched users only - user accounts that have a matching tenant UPN will be checked. All other accounts will be ignored.

    2. Click Next.
  8. Step 2: 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.
  9. Step 3: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. Specify an informative name for the task. It will greatly simplify the project management and event filtering in the future.
      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.

To review the Discover Chats 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. Status - 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.

To review the events for the Discover Chat task:

  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.

     

Review Migration Readiness

Use the information on the Chats tab to support your decision.

Property Value Description
Workflow Discovered On Demand has discovered the chat.
Account Matching Completed On Demand Migration for Accounts has migrated this user. This must be completed for On Demand to migrate chats for this user.
OneDrive Status Completed On Demand Migration for OneDrive has migrated files for this user. This must be completed for On Demand to migrate chats for this user. Note that you can migrate OneDrive file sharing permissions before or after the Chats migration (OneDrive Migration).

In addition to the data review, verify the following:

  • The Azure AD administrator account that you will use to migrate Teams Chat should be granted the Teams license. You should not change your Azure AD administrator accounts before completing the migration project.
  • The Azure AD administrator account should be granted the Global Administrator or Teams Administrator role on the tenants for which these account are used.

 

Considerations

  • It is a best practice to migrate Chats after all the content like OneDrive, Mail, SharePoint, Teams, etc., is migrated and the user accounts are matched.
  • You must use dedicated Azure AD administrator accounts for migrating Chats. For more information, see Prerequisites and Azure AD administrator accounts.
  • During migration, the migration task will migrate any new messages added to Chats after completing a Discovery task.
  • When a migration completes successfully, you must remove the Azure AD administrator account from the target tenant. As a result:
    • You can migrate a Chat only once, and the Chat cannot be re-migrated.
    • You cannot migrate new messages added to the Chat in the source tenant after the migration.

 

Migrate Microsoft Chats

Microsoft Chats are migrated with the New Migration Task.

  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 select an existing project.
  4. Click Teams from the project tile. You can also click Open Project to open the project dashboard and then click Open from the OneDrive tile. The Accounts and User Data dashboard opens.
  5. Select the Teams tab and then select the Chats tab.
  6. From the local toolbar, select Migrate. The New Migration Task wizard opens.
  7. Step 1: Migration Options

    1. Select one or more options as described below:
      • Merge Messages - select this option to merge message for faster migration. If you have a large number of messages, they are merged into manageable sets and then migrated

        Example: Consider a set of original messages in the source tenant as shown below:

        When this message set is migrated without merging, it appears in the target tenant as shown below. Each message is a separate entity. Messages retain their chronological order and the time stamp is converted to GMT.

        When the message set is merged and migrated, they appear in the target tenant as shown below. The migration service determines the merge set. Messages retain their chronological order and the time stamp is converted to GMT.

      • Migrate chats with unmatched users - select this option to ignore users in a chat that have not been mapped or matched with user accounts in the target tenant. The information about the user from the source tenant is used to migrate the chat.

        For example, if John chats with Dave, and Dave's user account has not been migrated to the target tenant, then Dave will not be able to view his chats with John in the target tenant even if his user account is migrated to the target at a later time.

        Use this option if there are user accounts in chat messages that are redundant because the user accounts will not been mapped, matched or migrated to the target account.

      • Skip OneDrive status check - select this option to ignore any verification of OneDrive accounts. Chat messages of users will be migrated regardless of their OneDrive status in the target tenant. Links to OneDrive files attached to chat messages will work when the OneDrive account has been migrated and the files are successfully migrated to the OneDrive account in the target tenant.
      • Avoid adding external users to target chats - select this option to avoid adding external users to the chats that are migrated to the target tenant. If this option is not selected, external users must be mapped to external users in the target tenant before migration, otherwise you will receive a warning and the migration will stop.
    2. Click Next.
  8. Step 2: 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.
  9. Step 3: Summary
    1. Note the name of the task. You will need the name of the task to track its progress and locate any issues.
    2. Click Finish to complete the task wizard. The task will start 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.

Review the Migration Results

Once the migration task is complete, use the information on the Chats tab to verify the success of the migration.

Property Description

Workflow

When the migration task is complete the workflow value changes to

  • migrated - when all discovered chats have migrated.
  • partially migrated - when some chats failed to migrate. The number of migrated chats is fewer than the total number of chats.
Total Chats The number of chats discovered for the user.
Migrated Chats The number of chats migrated for the user. This may be fewer than the total number of chats. If a participant is not matched or OneDrive not migrated then migration of the chat is intentionally skipped and the event documented on the Events tab.

IMPORTANT: You must remove the Azure AD Administrator account that you used to migrate Chats. For more information about removing the account, see Finalizing the Migration.

 

Troubleshooting

Chats may not be successfully migrated due to a variety of reasons. Two example are described below.

Example 1: Members of a chat have not been matched or migrated to the target tenant.

This is a common case where one or more members are not available in the target tenant. In such a case, the chat will not be migrated. In this example, the chat migration for Joni Sherman indicates a failure. The Status column indicates Migration failed. Joni has been chatting with the Administrator. However the Administrator account has not been matched or migrated to the target tenant.

When you inspect the migration task details, it will indicate a failure. You can click the event icons to get more information about the failure.

Resolution: When accounts are missing from the target tenant, you must map or migrate the account and re-run the chat migration task.

Example 2: An error in a chat message prevents all subsequent chat messages from being migrated.

In this example, chats for Joni Sherman indicate a migration problem. The Status column indicates Migration partially failed. There are 36 chat messages but only 3 messages could be migrated. The migration task completes successfully but no more messages are migrated. The service account that is used to migrate the chat remains as a member of the chat in the target tenant.

When you inspect the migration task, you will notice that the task has completed successfully, but there are error events in the task detail.

The Events list will indicate the error event, but more importantly you will notice that no more messages are migrated after the error event.

Resolution: Inspect the chat messages of the user and resolve the issue. Then re-run the migration task for the same user. If you are unable to address the issues with chat messages, contact Quest Technical Support.

Microsoft 365 Groups Migration

On Demand Migration for Teams securely migrates content for Microsoft 365 Groups without Teams functionality across Office 365 tenants. You can also use this dashboard for migration of Microsoft Teams and associated Microsoft 365 Groups migration (see Microsoft Teams Migration). Microsoft Teams migration requires additional licensing.

Basic Microsoft 365 Groups without Teams functionality content migration workflow consists of the following steps:

# Step
1 Create Microsoft Teams migration project (created automatically with New Migration UI) Project Management
2 Grant necessary permissions in case these permissions are not already granted (Prerequisites)
3

Discover Microsoft 365 Groups without Teams functionality on the source tenant (Discovering Groups)

There are no provision on the target on this step.

4

Provision groups on the target tenant. (Provisioning Groups) Target teams will be owned by the target Azure AD administrator account that is used to perform the provisioning.

  • Source Azure AD account will be added to all source Microsoft 365 Groups as a member
  • Target Azure AD account will be added to all target Microsoft 365 Groups as a member and owner.

These accounts can be removed from groups as described in Finalizing the Migration.

5

Migrate Microsoft 365 Groups without Teams functionality

6

Automatically migrate files associated with content

All files associated with content are transferred to the target according to the options, selected in the migration task.

7 Monitor the progress and track issues (Event Management)

What We Migrate

The following content associated with Microsoft 365 Groups without Teams functionality can be migrated:

  • Inbox folder and Calendar from the group mailbox (this content is always migrated, this option cannot be cleared)
  • SharePoint site as a whole (this is optional)
  • Planner (this is optional)
  • Group settings
Limitations
  • Office 365 group migration between tenants with different default language is not supported.
  • Office 365 group cannot be migrated in case the target group already exists. For all such groups the Target group exists warning message is displayed in the grid. As a workaround, you can rename the source group and re-create migration project.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级