Following are the Steps for Teams to Teams Migration
Pre-Requisites
- SysTools Customer Management domain should be whitelisted in users network firewall.
- Create project in Microsoft Azure, Allow Application permission and generate Application ID. Read more.
- Microsoft Visual C++ Redistributable Latest (Visual Studio 2015, 2017, 2019, and 2022) Should Be Installed. Download
Note: Before starting the migration please make sure about the destination domain name(e.g., @domain.com, @domain.onmicrosoft.com, or hosted domains), as this cannot be changed later, because the software licenses will be consumed and these cannot be revoked afterwards.
Download and Launch the migration tool
In case, tool is not activated, see how to activate the product: Activation Steps
Tool provides the help section for the details about each migration mode. Click on "Help" button to view this section.
To enable advance settings for Concurrent migration (optional). Read more: Advance Settings
After selecting the destination platform, choose the required resources and workloads for migration. The available options include:
- Users: Migrate user accounts and their associated data.
- Teams: Migrate Teams data.
- Groups: Migrate group data.
- Sites: Migrate site data.
- Public Folders: Migrate public folder data.
Under the Users tab, you can select individual workloads such as User, User Creation, Category, Email, Document, Contact, Calendar, Task, and Chat based on your migration requirements.
For Calendar migration, the application advises disabling CRA mode for destination users.
Select the Teams tab to configure Microsoft Teams migration. Enable Teams to allow Teams workload migration. The available options include:
- Team Creation: Allows team creation in the destination.
- Channel Creation: Allows channels to be created within teams.
- Channel Message: Allows migration of channel messages.
- Files: Allows migration of documents and message attachments.
Select the required Teams workloads according to your migration requirements.
Now, select the Groups tab to configure group migration.
Enable Groups to allow group workload migration. The available options include:
- Group Creation: Allows groups to be created in the destination.
- Group Member: Allows group member mapping between the source and destination.
Select the required Groups workloads according to your migration requirements and then click Next to continue.
Note: The destination platform cannot be changed once resources have been fetched.
After clicking on the Next button, you will be navigated to the Source panel. Here, Enter the Admin Email and Application ID of the source domain.
After entering the Admin Email and Application ID, click on the Validate button to verify the required permissions for the source account.
After successful validation, the required Permissions are displayed on the right side of the screen. You can verify the permissions granted for the source account, including Read User, Read Team, Read Team Channel, Read Channel Message, Read Team File, Read Group, and Read Group Member.
After verifying the required permissions, click on Next to proceed.
After clicking on the Next button, you will be navigated to the Destination panel. Enter the Admin Email and Application ID of the destination domain.
After entering the Admin Email and Application ID for the destination domain, click on the Validate button to verify the required permissions.
After successful validation, the required Permissions for the destination account are displayed on the right side of the screen. You can verify the permissions required to write data to the destination, including Read User, Write Team, Write Team Channel, Write Channel Message, Write Team File, Write Group, and Write Group Member.
After verifying the required permissions, click on Next to proceed.
After clicking on the Next button, you will be navigated to the Resources panel with "Users" as the selected option. To specify the users for migration, you can fetch users from the source account or import users using the provided template.
Click on Fetch Users to fetch users from the source account, Import Users to import users using a CSV file, or Download Template to download the sample template.
Click on Fetch Users to fetch users from the configured source account. A confirmation window will appear with the steps required to provide destination email addresses.
- Download the user list fetched during this operation.
- Update the destination user's email addresses.
- Upload the updated user mapping file.
Click on Continue to proceed with fetching the users.
If you wish to import users manually, click on Import Users. In the Import Users window, select the User list csv file containing the required user details.
To download the user mapping template, click on Download Template. A save dialog will appear with the template file name UserMappingSample.csv.
Select the required location and click on Save to download the CSV template.
Open the downloaded UserMappingSample.csv file. Enter the source and destination user details in the respective columns.
- Source User: Enter the email address of the user from the source domain.
- Destination User: Enter the corresponding email address of the user in the destination domain.
- MarkForExecution: Specify TRUE for the users to be included in the migration and FALSE for the users to be excluded.
Save the updated CSV file after providing the required user mapping details.
After fetching the users, a confirmation window displays the number of users fetched from the source account. Once the processing is completed, click on OK to close the window and proceed.
After the users are fetched, the user list is displayed under the Users section. Select the users that you want to migrate by using the checkboxes provided next to the respective Source Email addresses.
You can also use the Search option to find specific users. The selected users are highlighted in the list, and the total number of selected users is displayed at the bottom of the screen.
You can filter the users based on their permission status using the dropdown menu. Select All Users, Permission Failed, or Permission Succeed to view the respective users.
You can also enable the Show selected option to display only the users selected for migration.
Enter the corresponding Destination Email address for each selected source user. After providing the destination email addresses, click on Validate to verify the source and destination user permissions.
After entering the Destination Email addresses, click on Validate to validate the selected users. Once the validation process is completed, the number of validated users is displayed.
Click on OK to close the confirmation window.
After successful validation, the permission status of the selected users is displayed under the Source Permission and Destination Permission columns. Verify that the required permissions are available for both source and destination users.
Now, select Teams under the Resources section. To specify the teams for migration, you can fetch the teams from the source account or import teams using the provided template.
Click on Fetch Teams to fetch teams from the source account, Import Teams to import teams using a CSV file, or Download Template to download the sample template.
Click on Fetch Teams to fetch teams from the configured source account. A confirmation window will appear with the steps required to provide destination email addresses.
- Download the team list fetched during this operation.
- Update the destination team's email addresses.
- Upload the updated team mapping file.
Click on Continue to proceed with fetching the teams.
To import teams manually, click on Import Teams. In the Import Teams window, select the Team mapping csv file containing the required team mapping details.
To download the team mapping template, click on Download Template. A save dialog will appear with the template file name TeamMappingSample.csv.
Select the required location and click on Save to download the CSV template.
Open the downloaded TeamMappingSample.csv file. Enter the team mapping details in the respective columns.
- SourceTeamID: Enter the source Team ID.
- DestinationName: Enter the name of the corresponding destination team.
- MarkForExecution: Specify TRUE for the teams to be included in the migration and FALSE for the teams to be excluded.
Save the updated CSV file after providing the required team mapping details.
After fetching the teams, a confirmation window displays the number of teams fetched from the source account. Once the processing is completed, click on OK to close the window and proceed.
After the teams are fetched, the team list is displayed under the Teams section. Select the teams that you want to migrate by using the checkboxes provided next to the respective Team Name.
You can use the Search option to find specific teams. The selected teams are highlighted in the list, and the total number of selected teams is displayed at the bottom of the screen.
Turn on the Show selected option to display only the teams selected for migration.
To create the selected teams in the destination Microsoft 365 domain, click Create Teams.
Review the available Microsoft 365 licenses. If sufficient licenses are available, click Start to create the selected teams in the destination domain.
Review the team creation details and Click Continue to proceed.
Review the instructions and click Start to begin creating the selected teams in the destination Microsoft 365 domain.
If any team creation fails, you can retry the failed teams by clicking Continue.
Once the process is completed, review the confirmation showing the number of teams created successfully.
Click OK to close the confirmation message.
Review the team creation status. The "In migration mode" icon indicates that the team is ready for migration.
Click Close to exit the Teams Creation window.
Click Validate to validate the selected team and verify the destination resources before starting the migration.
Once the validation is completed, review the confirmation message showing the number of teams successfully validated.
Click OK to close the confirmation message.
After validation, verify that the Source Permission and Destination Permission icons are displayed for the selected team.
These icons indicate that the required permissions for the source and destination teams have been validated successfully.
Click on the dropdown arrow and select the required channels for migration by checking the corresponding checkboxes. You can select individual channels or multiple channels as needed.
After selecting the channels, click Start Migration to begin the migration process.
A Start Migration confirmation window appears showing the available license details, including the number of licenses purchased, consumed, and available.
Review the license information and click Start to begin the team migration.
A confirmation message appears stating that Migration started successfully.
Click OK to close the confirmation message and proceed with the migration.
The Status section opens and displays the migration progress under the In Progress tab.
You can monitor the migration status for the selected team and its channels from this screen. While the migration is running, some application features may remain unavailable.
To refresh the migration status, click the Refresh icon in the top-right corner.
Once the migration is finished, open the Completed tab to view the migration results.
Verify that the selected team shows Completed status. The status of each selected channel is also displayed as Completed, along with the number of migrated channel messages.
This confirms that the team and its selected channels have been migrated successfully.
Click Migration Actions to view the available post-migration options.
The menu provides the following options:
- Retry Failed Items – Retry items that were not migrated successfully.
- Re-Run Full Migration – Run the complete migration again.
- Delta Migration – Migrate newly added or updated data after the initial migration.
- Mark Teams Complete – Mark the selected teams as completed.
To retry any items that were not migrated successfully, select the required team from the Retry Failed Items window.
Review the listed Source Email and Destination Email, then click Start to retry the failed migration items.
To re-run the complete migration, select the required team from the Re-Run Full Migration window.
Review the Source Email and Destination Email, then click Start to re-run the full migration for the selected team.
After selecting the channels, click Start Migration to begin the migration process.
To perform a Delta Migration, select the required team from the Delta Migration window.
Review the Source Email and Destination Email, then click Start to begin the delta migration for the selected team.
If you wish to import team mappings, click the Import Teams icon in the Delta Migration window.
In the Import Teams window, upload the prepared team list CSV file using the Team list csv file field.
To download the team execution selection template, click the Download Template icon in the Delta Migration window.
In the Save dialog, choose the desired location, enter a file name if required, and click Save to save the CSV template.
To download the resource list file, click the Download Resource List icon in the Delta Migration window.
In the Save dialog, select the desired location and click Save to save the CSV file.
To mark the selected team as complete, select the required team from the Mark Teams Complete window.
Review the Source Email and Destination Email, then click Start to mark the selected team as complete.
After clicking Start, a warning message appears stating that once the team is marked as migration completed, it cannot be migrated again.
Review the team migration reports before proceeding, then click Yes to confirm and mark the team migration as completed.
After confirming the action, the Team Migration Completed message appears, confirming that the selected team has been successfully marked as migration completed.
Click OK to close the confirmation message.
Once the team migration is marked as completed, the Migration Mode column displays a green check mark, confirming that the team migration has been completed successfully.
Click the Download Report dropdown to view the available reporting options: Migration Summary Report and Detailed Report.
After selecting Migration Summary Report, a save dialog box appears. Choose the desired location and click Save to save the migration summary report as a CSV file.
If you want the detailed report, click on the Detailed Report option and the Download Reports window appears. Select the required team and click Download to download the detailed migration report.
The Report Generation Confirmation window appears. Select the required report options, such as Migration Job Detail Report and Item Reports, and click Generate to generate the reports.
Once the report generation is completed, the Generate Report confirmation window appears. Click Download to download the generated reports.
A save dialog box appears. Choose the desired location and click Save to save the detailed migration report as a ZIP file.
Navigate to Groups under Resources. To start the group migration, fetch groups from the source account or import groups using the provided template.
In the Fetch Groups window, review the instructions and click Continue to fetch the groups from the configured source account.
If you wish to import groups, click on the Import Groups option and in the Import Groups window, upload the prepared Group list CSV file using the upload field. Once the file is selected, click Upload.
If you wish to download the template for Group Mapping, click on the Download Template button and in the Save As window, select the desired location and click on Save to download the group mapping template.
Open the downloaded GroupMappingSample.csv file in Excel. It contains the columns SourceEmailID, DestinationEmailID, and MarkForExecution.
Once the groups are fetched successfully, the Fetch Groups window displays the number of groups fetched and the message Processing Completed. Click OK to proceed.
After the groups are fetched, the Groups screen displays the available source groups. Select the group you want to migrate by checking the box next to it. The selected group's destination group mapping is shown in the Destination Group column.
Use the group filter to view All Groups, Permission Failed, or Permission Succeed groups. You can also enable Show selected to display only the groups selected for migration.
After selecting the required groups, click Validate to validate the selected source and destination resources before starting the migration.
After validation is completed, the Validate Groups window displays the number of groups validated along with the message Processing Completed. Click OK to proceed.
After successful validation, click Start Migration to begin migrating the selected groups from the source to the destination account.
A confirmation message appears stating that the migration has started successfully. Click OK to proceed.
After successful validation, click Start Migration to begin migrating the selected groups from the source to the destination account.
A confirmation message appears stating that the migration has started successfully. Click OK to proceed.
Once the migration is completed, verify the Group Member count and Status column to confirm that all the data has been migrated successfully.
You can switch to the Tile View as well to see the migration details in a different preview format.
Go to Settings > General. Enable the Enable multiple accounts option, set the required number of concurrent users using the slider, and click Save to apply the settings.
Go to Settings > Logs to view the available log files. Select any .log file from the list to preview its contents.
Go to Settings > SMTP and enable Enable email notification. Enter the SMTP server details, including the SMTP Server, Port Number, Username, Password, Sender, and Sender Name. Click Test Connection to verify the SMTP configuration, then click Save to apply the settings.
Go to Settings > Notifications and enable Send notification on start of migration. Enter the Subject and Email content, choose the required email body format, and click Send Test Email to verify the notification settings. Finally, click Save to apply the configuration.
Following are the Steps for Teams Personal Chat Migration
Pre-Requisites
- Application should be registered on both source and destination domain’s Azure platform to get service account credentials. For detailed steps, refer to the SysTools Migrator application.
- Application should be granted all required scopes on the Azure portal.
- Source and destination users must have a valid Office 365 license along with Teams license.
- User mapping for all users must be provided.
What is User Mapping?
The user whose chats you are transferring had conversations with other users. All these users will need to be mapped (source and destination email IDs) and validated in our tool.For Example:
[email protected] chatted with [email protected] and [email protected] on the source side.
He is migrating only [email protected] personal chats to [email protected].
Now, before starting to migration of the [email protected] personal chats.
You need to validate [email protected] to [email protected] and [email protected] to [email protected] in the tool.
After validation (user mapping), you can uncheck [email protected] and [email protected] if you do not want their chat migration.
- A temporary user should be created in the destination domain with a valid O365 license. This account will be used for chat migrations.
- Before migrating personal chats, ensure that other workloads (like document migration with permissions) are complete.
- All users' documents and chats should be migrated from the same server.
- Ensure that the antivirus does not block the application.
- Proxy settings should not block network calls.
- Sleep and Hibernate modes should be disabled on the migration server.
- Internet bandwidth should be a minimum of 100Mbps.
Note: Before starting the migration please make sure about the destination domain name(e.g., @domain.com, @domain.onmicrosoft.com, or hosted domains), as this cannot be changed later, because the software licenses will be consumed and these cannot be revoked afterwards.
Launch the Software, Select Microsoft 365 as both the Source and Destination.
Under the User's Option, mark the checkbox next to Documents and Chat Workloads.
If Chat Migration is your only priority, then don’t apply the Date Filter on Documents.
Note: This is an explicit boundary that is selected from the day you start migration and goes back two months.
After workload selection click on Next.
On the Source Page, add the Admin Credentials and enter the Application ID in their respective spaces.
After putting in the credentials, click on the Validate Button.
The tool will perform the Validation process and show the results Successful or Not in a box next to the credentials area.
The entire process competes in a few minutes.
When the Source side Validation completes successfully, click on Next.
In the Destination area, you must redo the validation steps.
Use the Destination Admin email and the equivalent Application ID.
Press the Validate Button, let the Process complete, and Press Next.
The User Mapping screen is where you can add the list of users whose chat data you want to transfer.
There are three options present to make a list of users.
The Fetch operation can use the Microsoft 365 admin id to pull out a list of users directly from the source.
Use Import CSV option when you have a pre-made list of specific users whose chat you want to transfer.
Download Template provides you with a blank CSV where you can add the user accounts and then upload the CSV in the tool.
After going forward with any of the user addition options, the tool loads in the list in the Preview area.
There you can mark the users whose chat data is to be migrated with the help of a checkbox.
Apply priority marking to specific accounts to move their accounts to the top of the migration order.
The Show Selected toggle filters out the list to display only those accounts which have been selected for migration.
Once the user-level settings are done, add the destination email and press Validate.
A popup appears indicating the Validation process. Press OK once it completes.
Then click on the Start Migration Button at the top right corner.
A popup containing two options becomes visible. As you are yet to migrate Document data, stay with the default selection that says “No, please continue to migrate workloads other than Personal Chat” and click on Start Migration.
Take a look at the license consumption data and press Start.
The popup changes to an alert indicating the start of Document Migration; click on OK.
The details of the current status of migration can be found in one of three tabs.
Pending: Contains the accounts which are still in line for the migration.
In Progress: Keeps the accounts whose data is being migrated in real-time.
Completed: Contains the accounts whose data migration is done.
While the migration is going on, you can end the process midway by hitting the Stop Migration button.
Once hit, a secondary confirmation popup appears on the screen. Click Yes to confirm.
Once all accounts you are migrating come under the Completed tab, the Document Migration is done.
After the Document Migration completes, go back to the Setup Page.
Deselect the Documents workload and continue by only selecting the Chat option.
Perform the re-validation of Source and Destination one after the other.
In the User Preview Section, revalidate for all those accounts which underwent a Document Migration.
No need to change the selections as the tool remembered it for you.
Once all basic steps are done, click on Start Migration.
Inside the Personal Chat Migration box, mark the radio button next to “Yes, document migration is completed, please continue migrating only the Personal Chat workload.”
Add the temporary user ID on behalf of whom the migration takes place.
Note that this should be a new account with no historical chat data with any of the members.
Then press Authenticate.
A sign-in window appears; put in the password of the temp user account and press Sign in.
The sign-in window will close on its own after validating the credentials. Click on the Continue button of the Personal Chat Migration box.
A second pop-up informing you about the Chat creation process appears on the screen. Click on the Create Chat button.
Inside the same popup, a chat creation count will begin. Once it completes, click on OK.
The topmost popup window will close, then click on the Start Migration button of the Personal Chat Migration box.
This produces a license consumption alert. Take a look and click on Start.
The box displays a Migration Started successfully alert. Click on OK to continue.
An account undergoing chat migration can exist in one of three phases.
Pending: Houses those accounts still in line for the Chat Migration.
In Progress: Keeps the Accounts whose chats are being migrated in real-time.
Completed: Contains the accounts whose chat migration is done.
Once every account you selected for chat migration appears in the Completed tab, the migration is done.
If the migration encounters any issues or there is data missing, try the troubleshooting options under the Re-run Migration tab.
Retry Failed Items: Brings in the data that was left out during the initial run.
Re-run full Migration: Use when you believe you have to re-do the entire migration again.
Delta Migration: Migrate the data generated during the first migration cycle.
Once the migration is done, indicate chat completion by expanding Rerun Migration option and clicking Mark Chat as complete.
This opens a new box where every account that has undergone chat migration is pre-selected. Note you can't change selections so just hit the Start button to continue.
A warning alert appears on top of the screen, informing you that once marked as complete, the chat migration option will permanently freeze for that user.
Proceed only when you have double-checked that all chat contents have arrived safely in the destination. Click Yes to proceed.
Once the process completes, the box will indicate that the selected users' status has changed to Migration Completed.
You won't be able to migrate the same chat again.
Chat Migration is now truly completed.
The tool provides an in-built reporting option to document the migration process. Click the Download Report option.
Choose from two options:
Summary Report: Contains overall transfer records of the entire process.
Detailed Report: Makes user-specific reports on the migration data.
Free Download SysTools Microsoft Teams Migrator Download Now