Screenshots - Microsoft Teams Migration Tool

Microsoft Teams Chat migration

With SharePoint migration software, you can migrate Teams Chat from one tenant to another. Here’s a step-by-step process that guides you on how to do it.

Here’s what the source and destination look like before migrating the chats.

Source Tenant

1:1 chat between two users at the source that we will migrate.

Group chat between multiple users sending texts and files appears like the image below.

Destination Teams is currently empty, and we’ll move our chats here and then see what it looks like after the migration.

Step 1: Launch Kernel Migration for SharePoint, go to the Source pane, and right-click Microsoft Teams. Now click on Add Teams to add your teams account to it.

Step 2: In the Add Teams wizard, provide a Project Name and enter the credentials based on the Authentication you choose from the two.

Step 2-A: Modern Authentication: Enter Tenant ID, Client ID, Client Secret Value, and User Name from the App Registration in Azure Active Directory

Step 2-B: For Basic Authentication (Recommended method), input a Global Admin User Id and its password.

Note: User should be a Global Administrator and possess a valid license of Microsoft 365 and Microsoft Teams to execute the data transfer.

Click Register and Connect.

Step 3: The Microsoft Teams account is added to the source. You can expand the Project Name and see the components of Teams account under the project name you created.

Step 4: Now go to the destination pane and right-click Microsoft Teams to add the destination account with the same process you followed to add source.

Step 5: Enter the Project Name and credentials as per the Authentication Type and then click Register and Connect to connect with the destination Teams account.

Step 5-A: Modern Authentication: Enter Tenant ID, Client ID, Client Secret Value, and User Name as available in the App Registration in Azure Active Directory and proceed as per the instructions on the screen.

Note: Please make sure that the selected user is a Global Administrator with a valid Microsoft 365 and Microsoft Teams license. We recommend creating a new user in the destination tenant for migration.

Step 5-A [I]: In the Sign in to your account window and copy the given URL.

Step 5-A [II]: Now, go to Private /Incognito window of your browser and paste the same URL in the search bar. If you’re not logged in to your Microsoft Office 365 account, it will first ask you to sign in.

Step 5-A [III]: Copy the new visual studio URL from the Incognito window.

Step 5-A [IV]: Paste the URL copied in previous step to Auth URL box and then click OK. This will connect the tool with the destination tenant.

Step 5-B: Basic Authentication: Provide a Global Admin User Id and then enter its password.

Step 6: This will add the Teams to the destination pane. You can expand and see all the Teams within the tenant by clicking on + icon preceding project name.

Step 7: Now we have two ways of moving chats from one tenant to other.

Step 7 [A]: Copy-Paste method

Step 7 [A-I]: Once both the source and destination are connected, click on the connected teams to expand its components and right-click on Chats. Now select Copy to copy chats (1:1 and group both) for the transfer.

Step 7 [A-II]: Once the data is copied from the source, go to the destination pane and right click on Chats and then select Paste to move the user chats (1:1 and group chats).

Step 7 [B]: Migrate method

Step 8: Click on the three dots (…) to map Source User with the Destination User to ensure the chats are migrated to the specific user accounts that you want. Ensure that you do not end up mapping wrong users else the chat will show under the name of other users that’s not intended to.

Note: Use the search box to find users with the User name or email. Items marked in red signifies that the users from the source are not present in the destination. While the green color shows that user are mapped successfully with the users at the destination. The tool also allows you to import CSV file for easy user mapping or you can even export the mapped source and destination users in the form of a CSV file for future use.

Step 9: If some users are left unmapped at the destination and you press Next to proceed, the tool will show a pop-up saying, “Some users are not mapped. Do you still want to process?” Select Yes or No and to proceed.

Step 10: Select users from the list whose chat you want to move to the users at the destination.

Note: Use the search box to find users with user name or email.

Step 11: Select from the given options to migrate selective chats of the users. Click Next.

• Select from Migrate chat attachments to Migration admin’s OneDrive or Migrate chat attachments to the selected destination user’s OneDrive account.
• Mark the checkbox Exclude conversations of unmapped users to avoid migration of unmapped users chat to the destination.

Note: Use Import CSV option to import a CSV file with the pre-mapped source and destination Teams chat users. Download the mapped CSV to your system with the Export CSV option.

Step 12: All the chats stored within the selected users will be listed. These chats are represented with the unique chat id and chat type.

• Chat Id column shows the Id of all the chats within the selected users whether one-to-one, group, or self-chat.
• Check out the Name of the respective chat id as stated in the Teams. It mentions the user and group name to make it easy for the users to identify.
• If any of the chats were finished migrating or aborted earlier, user can view its status under the Migration Status column stating Partially completed or Completed, otherwise Pending. Next time when user try re-migrating same chats, it will only migrate recent items added after last migration.

Click on the three dots in the Members column to select members of the specific group or chat messages.

Step 13: Users can split User Chats using Split into batches button to create multiple batches of the chats in case of bulk migration.

Note: The minimum count to split batches of the chats is 5 while the maximum is 50000.

Step 14: Select Upload Existing Batch checkbox to upload the created files in multiple instances.

Step 15 Select the desired CSV files from the saved location. Click Open.

Step 16: Click OK on the pop-up with the message, “CSV has been imported successfully.”

Step 17: The user whose chats were listed in the chosen batch will be selected mapped with the mapped destination user.

Note: If you select the checkbox “Only new threads will be shown,” it will show the recent threads added to the conversations. This feature will make sure there’s no duplication of data.

Step 18: Selection of User Chats screen shows all the chat ID stored in the batch uploaded.

Step 19: The process of migrating chats has begun. You can check the status of the process in the below Progress window. Use the Stop button to halt the progress of the process before completion.

Step 20: After the process completion, message, “Chat migration has been completed successfully.” Click OK to end process.

Step 21: Click on Save as CSV to save the migration summary of process to a CSV file format. Click Finish to exit.

After the migration process is complete here’s how the sample destination Teams look like.

Step 22 [A-I]: After the migration process is complete here’s how the sample destination Teams look like.

Step 22 [A-II]: Here’s how the group chat on the destination end looks like after migrating the chats.