Table of contents

Microsoft Teams migration

With SharePoint migration software, you can migrate Teams channels including all their data such as messages, files, tabs, apps, members etc. from one tenant to another. Here’s a step-by-step process that guides you on how to do it.

Step 1: Launch Kernel Migration for SharePoint, go to the Source pane.

Step 2: Right-click Microsoft Teams and select Add Teams to add your teams account to it.

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

Step 3.1: For Basic Authentication (Recommended method), input a Global Admin User Id and its password. Click Register and Connect.

It will now take you to a wizard where you need to select the Login type one more time. You can choose from the given options:

Step 3.1 [A]: Basic Authentication (Recommended) : The process with Basic Authentication is straightforward, and it will directly connect the tool to the source.

Step 3.1 [B]: Modern Authentication (MFA/2FA) : To select Modern Authentication to log in, click OK and follow the steps given below to complete app registration and then add Teams to the source:

Step 3.1 [B-I]: Sign in to your Microsoft account that has the role of “Global Administrator.”

Step 3.1 [B-II]: Now, it will ask you to sign in to the Microsoft Azure with the same Microsoft Office 365 account.

Step 3.1 [B-III]: It will take you to the Sign in to your account wizard, here copy the given URL.

Step 3.1 [B-IV]: Now open Incognito window in your web browser and paste the URL in the search bar.

Step 3.1 [B-V]: It will then provide you with a URL of the visual studio, copy it from there.

Step 3.1 [B-VI]: Now paste this authorization URL in the “Sign in to your account” window and click Ok.

Step 3.1 [B-VII]: This opens the Application Role Assignment window, from here, copy the client ID and follow the given instructions.

Step 3.1 [B-VIII]: Once done with the process of Role Assignment, click Ok. This will open a prompt with message “Have you completed the Role assignment process?” Click Yes if done.

With this, Microsoft Teams account is added to the Source with Modern Authentication under Basic Login Type.

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

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 4: 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. 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.1: If you choose Basic Authentication, enter a Global Admin User Id and its password. Click Register and Connect. Follow the same procedure as we did to add Source with Basic Authentication (Basic login and Modern login). This will add the Microsoft Teams in the destination.

Step 5.2: Modern Authentication: Enter Tenant ID, Client ID, Client Secret Value, and User Name as available in the App Registration in Azure Active Directory.

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. Enter a User Name or display name starting with "Migration" to allow users join and leave all personal and group chats.

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

Step 5.2 [B]: 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.2 [C]: Copy the new visual studio URL from the Incognito window.

Step 5.2 [D]: 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 6: As both source and destination are connected, now, there are two options to move the Teams data from tenant to another, Copy-Paste and Migrate.

Step 6 [A]: Copy-Paste method

Step 6 [A-I]: When you right-click Teams and then Copy on the connected team with project you created above. This will copy the content (channel, chats, files, members, etc.) from the source account.

Step 6 [A-II]: In the destination pane, right-click on Microsoft Teams and choose Paste option to take data you copied from source to destination tenant.

Step 6 [B]: Migrate method : Just like we did in the copy-paste method in previous steps, right click on the connected Teams, and then select Migrate.

Step 7: The tool will start fetching users and the respective data.

Step 8: In the next window, select users whose data you want to migrate to Teams at the destination. The items appearing in red color indicates that the Teams from the source are not available in the destination and blue means they’re present at the destination.

Step 9: Make sure you map all the Teams from Source with the destination before starting the migration. You can also search for a particular team by entering the name into the search bar above every column. Once done, click Start Migration.

Step 10: This will begin the process of migrating team objects between the tenants. The new popup appearing on the screen will share the progress of the process.

Step 11: Once completed, you’ll see the completion message, “Migration completed successfully.” Click OK to finish the process.

Step 12: When the data is completely moved to the destination, the migration summary will explain the detailed status of each selected team. You can download the migration logs as a CSV file for getting insights of the process later.

Table of contents

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.

Source Tenant

This is how 1:1 chat between two users at the Source Tenant that we will migrate looks.

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

Destination Tenant

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

Let's proceed toward the process to learn how to execute Microsoft Teams Chat 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: If you choose Basic Authentication, enter a Global Admin User Id and its password. Click Register and Connect. It is the recommended mode of connection while using the tool.

It will now take you to a wizard where you need to select the Login type again. You can choose:

Step 2-A [I]: Basic Authentication (Recommended): The process with Basic Authentication is straightforward, and it will directly connect the tool to the source.

Step 2-A [II]: Modern Authentication (MFA/2FA): Now, if you select Modern Authentication, click OK and follow the steps given below:

Step 2-A [II-a]: First, log in to your Microsoft account that is “Global Administrator.”

Step 2-A [II-b]: Now, sign in to Microsoft Azure with the same MS Office account.

Step 2-A [II-c]: It will take you to the wizard, here copy the given URL.

Step 2-A [II-d]: Now go to Incognito window of your browser and paste the URL.

Step 2-A [II-e]: It will then provide a URL of the visual studio, copy it from there.

Step 2-A [II-f]: Now paste it in the Sign in to your account window and click Ok.

Step 2-A [II-g]: In the Application Role Assignment window, copy the client ID and follow the instructions.

Step 2-A [II-h]: Once done with the Role Assignment process, click Ok. This will open a prompt with message “Have you completed the Role assignment process?” Click Yes if done.

With this, finishes adding Microsoft Teams account to the Source using Modern Authentication under Basic Login Type.

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

Note: User Should be a Global Admin and should have a valid license of Microsoft 365 and Microsoft Teams.

Click Register and Connect.

Step 3: The Microsoft Teams account is added to the source. You can expand the Project Name to see its further components. Now go to the destination pane and right-click Microsoft Teams to add the destination account the same way you added source.

Step 4: Enter the Project Name and credentials on the basis of Authentication Type chosen and then click Register and Connect to connect with the destination Teams account.

Step 4-A: If you choose Basic Authentication, enter a Global Admin User Id and its password. Click Register and Connect. Then follow the same procedure as we did in the Source, and you’ll be able to add Microsoft Teams in the destination using Basic Authentication.

Step 4-B: Modern Authentication: Provide Tenant ID, Client ID, Client Secret Value, and User Name as available in the App Registration in Azure Active Directory.

Note: Please ensure that the selected user is a global admin with a valid Microsoft 365 and Microsoft Teams license. It is recommended to create a new user in the destination tenant for migration purposes. The user name or display name should be "Migration" so that this user can join and leave all personal and group chats.

Step 4-B [I]: In the Sign in to your account window, Copy the given URL.

Step Step 4-B [II]: Now, go to Private or Incognito window of your browser and paste the same URL in the search bar. If you’re not logged in to your respective MS Office account, it will first ask you to sign in.

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

Step 4-B [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: Now we have two ways of moving chats from one tenant to other.

Copy-Paste method

Step 5-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 5-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).

Migrate method

Step 5-B [I]: The process of adding the source and destination is same in both methods. Now to migrate data, go to the source pane and right-click on Microsoft Teams and then select Migrate.

Step 5-B [II]: Use the dropdowns given below to modify the source and destination Tenants selection.

Step 6: Once you pick the approach, the tool will start fetching users for the mapping.

Step 7: Click on the three dots (...) to map users at the destination to ensure the chats are migrated to the 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: 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.

Step 8: Select users from the list and see which user you want to map with the source.

Step 9: Find out particular user from the list using the search bar to avoid the hassle of looking for the same in the long list.

Note: 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 10: Once done with the user mapping, select users whose chats you want to move. Selecting the checkbox “Remove deleted chats” will restrict the deleted chats from migrating to the destination Teams account.

Step 11: If you select more users than the available number of users’ licenses, the tool will show you a popup with the message “The selected number of users is more than the available license.” Select users again and click Next.

Step 12: The process of migrating 1:1 and group chat has begun. You can check the status of the process in the below Progress window.

Note: You can click on Stop button to stop or abort the process.

Step 13: After the process completion, you’ll see a wizard with message, “Migration completed.” Click OK to end process.

Step 14: You can save the migration summary of process in CSV file format.

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

All the messages and files are migrated to the destination 1:1 user.

Here’s how the group chat on the destination end looks like after migrating the chats.

↑