Teams Private Chat Migration Guide

Discover the enhanced support for Teams Private Chat Rehydration migrations with MigrationWiz, replacing the Teams Private Chat mailbox migration. This comprehensive guide will walk you through each step of your migration project, ensuring a smooth and successful transition.

MigrationWiz

MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they do not sync to the destination, nor do the changes made at the destination sync to the source. We do not have “live” monitoring of changes (as with a sync agent), and we cannot handle scenarios such as conflict resolution without user interaction.

The maximum file size for migration through MigrationWiz varies by migration type and environment but may never exceed 60GB.

Prerequisites

When using MigrationWiz, it's essential to understand the requirements for user roles and security groups for both source and destination connectors.

  • The user for the source endpoint needs to be part of the MigrationWiz security group but does not need an admin role.
  • For the destination endpoint, the user does not need to be part of the security group or to have an admin role. The only prerequisite is to have an active Teams license applied and must be on a cloud-only account.

Licenses

For now, this type of migration does not need any licenses. 

Limitations

Consider the following limitations for this type of migration.

  • The conversations are migrated as chat threads only. 
  • Default user mapping is supported based on the display name and line items only.
  • Only the last 30 days (starting from your migration) are migrated and rehydrated.
  • Teams Private Chat migration does not support IpLockDown.
  • At this time, GCC High migrations are not supported.
  • Project sharing is not supported.
  • Currently, you might have issues when using the Autodiscover feature. In case you do, please get in touch with Support so we can help you out.

Migrated Items

Please review the following list to check the migrated and non-migrated items.

Migrated Not Migrated
The following list shows the migrated items in this type of migration.
  • Meeting chats
  • 1:1 Chats

  • Group chats

  • Chat titles
  • Rich content and styling
  • Chat replies/threads
  • Emojis
  • GIFs
  • Stickers
  • Long texts

Prepare the Source Environment

Verify to grant the requested permissions mentioned below.

  • Verify that the user for the source endpoint is part of the MigrationWiz security group before granting permissions.
  • Make sure that the team application permission has been given. Grant applications permission at source using the MigrationWiz-PCH-FullControl permission level.

Add the User to the Security Group

Besides, complete the steps outlined below to add a user to a security group.

  1. Create a new Security Group named “MigrationWiz” on the Microsoft 365 Admin Portal. If you have not created a security group before, follow Microsoft's instructions.
  2. Create a new user. This user must have an active Teams license applied and must be on a cloud-only account. On-premises and hybrid user account types are not supported.
  3. Add a new user to the previously created security group as a member.

Important

Keep in mind that ADFS and MFA must be turned off for this user.

Prepare the Destination Environment

Double-check to grant the requested permissions mentioned below.

  • Verify that the user account for the destination endpoint has an active Teams license applied and must be on a cloud-only account.
  • Make sure that the team application permission has been given. Grant applications permission at the destination using the MigrationWiz-PCH-DelegateAccess permission level.

Important

Keep in mind that ADFS and MFA must be turned off for this user.

MigrationWiz Steps

Create a Collaboration (Private Chats) Project

Important

Ensure the application approval/consent is given before clicking Verify Microsoft 365 Credentials when setting up your source or destination endpoint. If you do not, you may encounter the Failed to verify Microsoft 365 Credentials error. To resolve the issue, refer to the Teams Private Chat - Failed to Verify Microsoft 365 Credentials article.

  1. Go to Projects.
  2. Click Create Project.
  3. Select Collaboration (Private Chats) Project.
  4. Update the project information.
    1. Add a Project Name.
    2. Select a Customer from the drop-down.
    3. Click Next Step.
  5. Create the source endpoint by following the next steps.
    1. Click New.
    2. Confirm that the Microsoft Teams Private Chat (Source) is selected.
    3. Provide your Microsoft 365 credentials.
    4. Click Verify Microsoft 365 Credentials.
    5. Click Add.
  6. Verify your source endpoint information and click Next Step.
  7. Create the destination endpoint by following the next steps.
    1. Click New.
    2. Confirm that the Microsoft Teams Private Chat (Destination) is selected.
    3. Provide your Microsoft 365 credentials.
    4. Click Verify Microsoft 365 Credentials.
    5. Click Add.
  8. Verify your source endpoint information.
  9. Click Save and Go To Summary.

Add Users

There are three ways to add users to the migration. Either of these may be used, or both. Read through each of the options before beginning your process. 

We recommend you follow the Autodiscover process to find all the user's chats you are moving, then select either Quick Add or Bulk Add.

Generally, Quick Add is used for small migrations, proof of concept migrations, and other tests, while Bulk Add is used for large migrations and full migration passes. 

Important

Autodiscover discovers all users with private chats at the Source tenant. Once Autodiscover is completed, all users discovered will be imported/populated as line items or could be downloaded as a CSV file to manage the user mapping. Once verified, the same CSV file may then be uploaded.

Click Add Bulk Add Autodiscover
This option allows you to add items one at a time. In case you are using administrative credentials, just provide an email address. Otherwise, enter the following user information:
  • Source email address
  • Destination email address

Advanced Options

There is no required advanced option for private chat migrations.

Verify Credentials

After adding the user, verify the credentials.

  1. Open the Project containing items to validate.
  2. Select the items to validate.
  3. Click the Start button in your dashboard.
  4. Select Verify Credentials from the drop-down list.

Once complete, the verification results will be shown in the Status section.​  Wait until the status changes to Completed (Verification). Then you can proceed with the rest of the steps.

Private Chats Migration Summary

Consider the following behavior of the summary of the line items count after verifying your credentials:

  • When only Verify Credentials is run before the migration, the Private Chats Migration Summary shows the count of line items as zero (0) items were migrated.
  • When Verify Credentials is run after performing a Full Migration, the Private Chats Migration retains and shows the Full Migration summary.
  • When new line items are added after a migration and the Verify Credentials is run before performing a subsequent migration, the count of line items shows as zero (0) items were migrated.

Performing a Migration

Keep in mind the following process to start with the migration.

  1. Select the line item to migrate by clicking its checkbox.
  2. Click the start dropdown list and select Full Migration.
  3. Verify that the Private chats checkbox is selected.
  4. Select the Add selected user(s) to hydrated chats checkbox.
    Migrate Chats.jpg

    Warning

    In case you do not select the Add selected user(s) to hydrated chat checkbox, users that have been part of the chat will not be added to it, only the Admin will appear and the name of the chat will still be migrated as UserName1, UserName2, and so on.

  5. Click Start Migration.

Private Chats Migration Summary

Resolve Errors

Errors vary widely, so if you encounter migration errors, refer to the Collaboration error list and follow the steps listed under Resolution. For specific, Team Private Chat migration errors review the Troubleshooting article.

If a migration completes successfully, but not all members show on the Teams destination, the users may take extra time to sync.  

Run Retry Errors

Each error logged represents an item that was not migrated. MigrationWiz contains a mode in which you can resubmit the migration to retry failed items. This mode of operation is always free of charge. You may only submit mailboxes in this mode only if they satisfy all of the following conditions:

  • The last migration was completed successfully.
  • The mailbox contains at least one error.

If your mailbox does not satisfy these conditions, you will receive a warning when submitting the migration in this mode and your request will not be fulfilled.

To submit one or more mailboxes in retry mode, perform the following steps:

  1. Click the Go To My Projects button.
  2. Select the project that contains the line item you want to retry.
  3. Select the items with migration errors.
  4. Click on the Start button.
  5. Select Retry Errors from the menu.
  6. Click the Retry Errors button.

When errors are repaired, they will disappear from the error log. Some errors may not disappear if the Source item was not reprocessed (due to filters, for example), deleted, or moved, or if the item failed again. 

If problems persist contact Support.

Multi-pass Migration

Teams Private Chat allows Multi-pass migration always considering the limitations mentioned above. 

Keep in mind that MigrationWiz migrates only as a second pass for new chats. Please note that new messages in already successfully migrated chats, will not be included in the second pass. Meaning that the migration of new messages is not occurring in subsequent migration passes.

Warning

Remember that Multi-pass migration can only be performed if you have not run the Clean up process.

Post-Migration Steps

After your migration, you may need to perform one or more of the following options. Please review them carefully and follow the steps outlined in each.

Clean Up

The Clean up feature removes the migrating Migration user’s accounts from all the migrated chat threads. To perform it, please follow the steps below click the Start dropdown and select Clean-up Resource.

Warning

Once the Migration User is removed from chats, the user can no longer migrate new messages in subsequent passes. This step is irreversible, please be sure before performing it.

Was this article helpful?
0 out of 0 found this helpful