Converse agora com nosso suporte
Chat com o suporte

On Demand Migration Current - User Guide

About On Demand Migration Before you Start 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

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:

 

Discovering Microsoft Chats

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 the Settings > Org Settings, and under Services tab, choose Reports.
  2. Select Reports, and then 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. Select 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.

Last 30 days Message Count - 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 - most recent activity in the last 30 days.

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.

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 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. You can export the selected user accounts to a CSV file and then add the Collections 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 Import Collections. The Import Collections from File dialog opens.
  7. Click Browse and select the CSV file. The selected CSV file name appears.
  8. 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.

Migrating Chats

In this topic:

Reviewing Chats Migration Readiness

Use the following information in the Chats list view to support your decision.

Property Value Description
Workflow Discovered On Demand has discovered the chat.
OneDrive Status Completed The OneDrive migration service has migrated the files for this user. This must be completed for On Demand to migrate chats for this user. You can migrate OneDrive file sharing permissions before or after the Chats migration.
Mailbox Status Migrated User mailbox migration is complete and successful.

In addition to the information that you reviewed, verify the following:

  • The temporary Migration Manager accounts for source and target tenants that you will use to migrate Teams Chat should be granted the Teams license. You should not change your temporary Migration Manager accounts before completing the migration project.
  • The temporary Migration Manager accounts 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, Mailboxes, SharePoint, Teams, etc., is migrated and the user accounts are matched.
  • During migration, the migration task will migrate any new messages added to Chats after completing a Discovery task.
  • Chats can be migrated multiple times. During remigration, new messages are added to previously migrated chats in the target, and new chats that were not migrated before are migrated.
  • Due to Microsoft API limitations, the discovery task is automatically run against all users during a remigration to discover new messages and new chats. Which is why we don't recommend remigration for small users sets.

Starting a Chats 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 open 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 Chats Migration Task wizard opens.
  7. Step 1: Migration Options

    1. Select one or more options as described below:
      • 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: Migration Actions

    NOTE: To experience the full set of chat migration options described below, please contact Quest Technical support to get your Microsoft Teams Private Chat feature added to your Migration subscription. Without the feature subscription, only a limited set of chat migration options are available.

    1. Select one or more action options as described below:
      1. Migrate to live chat - select this option to migrate all or a subset of the chat messages from the source tenant to the live chat in the target tenant. You choose a subset or all messages based the date range option as defined below:
        • Messages within last 15 days - the most recent chats within 15 days discovered after the last migration will be migrated.
        • Messages within last 30 days - the most recent chats within 15 days discovered after the last migration will be migrated.
        • Messages within last 60 days - the most recent chats within 15 days discovered after the last migration will be migrated.
        • All messages - all chats discovered after the last migration will be migrated.

        Messages are merged into manageable sets and then migrated. The effect of merging messages is described in the example below:

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

        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.

      2. Archive remaining messages - select this option to archive the rest of the chat messages. These messages will be available to the user in the Conversation history tab in the target tenant. If you selected to migrate all messages to live chat, then this option is ignored. If the option is not selected, any chat messages that remain will not be migrated to the target tenant.

        You can exercise greater granular control over the remaining messages using the time-range options described below:

        • Last 30 days of remaining messages - the most recent 30 days of messages that remain to be migrated will be archived.
        • Last 60 days of remaining messages - the most recent 60 days of messages that remain to be migrated will be archived.
        • Last 90 days of remaining messages - the most recent 90 days of messages that remain to be migrated will be archived.
        • All remaining messages - all messages that remain to be migrated will be archived.

        IMPORTANT: You can archive chats only once regardless of the time-range that you select.

        Example 1: Assume that you are migrating chats on June 30.

        If you select Migrate to live chat and Messages within 15 days, then all chat messages from June 16 to June 30 will be migrated to the live chat in the target tenant.

        If you also select Archive remaining messages and Last 30 days of remaining messages, any remaining chats from May 17 to June 15 will be archived and available in the Conversation history tab of the user in the target tenant. Chats before May 17 will not be migrated.

        Example 2: Assume that you are migrating chats on June 30.

        If you select Migrate to live chat and Messages within 15 days but there are no chats within the last 15 days, then no chats will be migrated to the live chat in the target tenant.

        If you also select Archive remaining messages and Last 30 days of remaining messages, any remaining chats from May 17 to June 15 will be migrated or archived to the Conversation history tab of the user in the target tenant.

        Example 3: Assume that you migrated all chats previously on June 20 and are migrating chats again on June 30.

        If you select Migrate to live chat and Messages within 15 days, only new chats discovered after June 20 will be migrated to the live chat in the target tenant. The migration service remembers the previous migration.

        If you also select Archive remaining messages and All remaining messagesbut no chats remain, then none will be migrated or archived.

    2. Click Next.
  9. Step 3: 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.
  10. Step 4: 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.
  11. Step 5: 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 Migrate chats.
      2. Source tenant - name of the source tenant for the chats.
      3. Target tenant - name of the target tenant where the chats will be migrated.
      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 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.

Reviewing the Migration Results

Once the migration task is complete, use the information on the Chats tab to verify the success of the migration. The column in the chats migration list view are as follows:

  • User Name - name of the user from the source tenant.
  • Migration State - status of the task in the migration process. Values are as listed below:
    • Discovered
    • Migrating
    • Partially migrated
    • Partially migrated with issues
    • Migrated
    • Migrated with issues
    • Migration failed
  • Workflow - the most recent operation performed on the group. Valid values are
    • 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.
  • Migrated Chats - 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.
  • Archived Chats - indicates whether or not chats have been archived. When chats are migrated and archived, the value changes to Yes for the selected user. Since chats can be archived only once, if you attempt to re-archive migrated chats, a warning message appears in the migration task events.
  • Source UPN - UserPrincipalName (UPN) of the source account.
  • Target UPN - UserPrincipalName (UPN) of the target account.

 

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 rerun 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 rerun the migration task for the same user. If you are unable to address the issues with chat messages, contact Quest Technical Support.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação