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
In this workload selection, select Teams, It will automatically select Teams Creation, Channel creation, channel message & files. Users can also select the group workload as per their needs.
Now, Enter Admin email ID & Application ID of Source tenant & then click on Validate button to validate associated permissions.
Enter the Destination Admin email and Application ID & then click on the Validate button to validate all permission.
Now under Resources tab, in the Users screen, there are several ways in which you can add users from the source Users that needs to be processed.
Fetch Users: It will fetch all the users from Source domain.
Import Users: This will import users through CSV.
Download Template: In this option, you will get a sample CSV file in which you can add source and destination users manually.
Fetch User – This option will fetch all source user accounts, then you have to enter destination user's email addresses.
Click on Continue.
Map sources users emails to the destination user emails by entering destination emails (enter destination email where you want to migrate source Teams).
Click on (…) icon, if you want to import a CSV file containing destination accounts.
Users can also filter out the selected users for migration and also allocate Priority if they have multiple user mailboxes and want to migrate some of them prior to others.
Now, Validate permissions by clicking on Validate button. It's compulsory to validate Users in case of Teams Migration
After successful validation, you will see user icons in green colour.
Now proceed to the Resources tab. In the Teams screen, there are several ways in which you can add Teams from the source account that needs to be processed.
Fetch Teams: It will fetch all the Teams from Source domain.
Import Teams: This will import Teams through CSV.
Download Template: In this option, you will get a sample CSV file in which you can add source and destination users manually.
You need to map destination Team with selected source Team. For this, Click on Create Team button. Now you'll see below screen, Provide the Team name as per your requirement or software will pre-populate destination Team names according to source Team name.
Click on Start button
All required teams will be created in the destination domain. Teams will be created in "In-Migration Mode".
Now, validate permissions by clicking on the validate button.
Now, after successful validation, you'll see all the green icons.
Once the required source and destination permissions are validated, you can expand a particular team to list the channels in that team. Additionally, you can also check / uncheck the channels that you want to migrate.
After successful validation. Click on Start Migration button to initiate the process.
You can see the migration task In-Progess / Pending / Completed tab.
After completion, you can see the green tick icon in front of all the teams that are migrated.
After completion of the migration process, you can click on the drop down button to see the count of the channel names, messages & files that are migrated
Re-Run Migration option is also provided in order to perform the migration again.
- Retry Failed Items: To migrated the data which didn't get migrated.
- Re-Run Full Migration: To perform the entire migration process again.
- Delta Migration: To migrate the newly arrived data in between the migration process
Users can perform these actions before marking Teams as complete. They won't be able to execute these steps after they've clicked on Mark Teams Complete.
The software will show you a prompt screen. Click on Yes. Users can not perform Re-run or Delta Migrtion once marked Teams as complete.
After completion of migration, click on the Download Report button to generate the detailed migration report.
The tool provides two options for downloading the reports:
Summary Report: The summary report will be a single .csv file containing migration reports of all the selected users for migration.
Detailed Report: Here, you get the option to save the detailed migration report of the mailboxes you want to. Select the mailbox and click on Download button.
Choose the destination location where you want to save the Detailed Report.
Now, users need to migrate Teams Groups. Under Resources tab, in the Groups screen, there are several ways in which you can add Groups from the source account that needs to be processed.
Fetch Groups: It will fetch all the Groups from Source domain.
Import Groups: This will import Groups through CSV.
Download Template: In this option, you will get a sample CSV file in which you can add source and destination users manually.
To start migration you have to enter Destination Groups emails (enter destination email where you want to migrate source Groups).
Click on (…) icon, if you want to import a CSV file containing both source and destination accounts.
Destination ID of "Team Group" which Team has been marked as completed will be automatically get mapped.
Note:- “No license will get consumed for Group migration”
After initiating the Microsoft Teams migration, the application automatically opens the advanced Migration Dashboard. The interactive Card View provides real-time tracking and visual analytics to help administrators monitor the migration progress efficiently.
- View the Total Teams Migrated section to track live migration counts for Teams, Channels, Chats, Files, Tabs, and other Microsoft Teams components.
- Analyze the Storage Consumption Overview panel, which displays dynamic graphical insights of migrated Teams data volume, including detailed usage distribution across chats, shared files, and channel content.
The dashboard actively tracks Microsoft Teams migration operations through four dedicated processing queues. The first tile, "Pending", displays all Teams, Channels, chats, and associated workloads that are queued and waiting for migration execution.
The "In-Progress" queue displays Microsoft Teams workloads that are currently undergoing migration, along with live updates for transferred Teams, Channels, chat messages, shared files, and overall data volume.
The "Completed With Error" queue shows Microsoft Teams workloads that completed migration with certain failed or skipped components, while the "Completed" queue contains Teams, Channels, chats, and files that were migrated successfully without any issues.
Click the More Details option on a specific Microsoft Teams workload card to open the Workload Data Insights panel. This section provides a comprehensive breakdown of source data, migrated Teams components, failed items, and skipped content for each Microsoft Teams workload category.
Click the information ("i") icon to access the column glossary, which explains important migration metrics such as "Source Team Count", "Migrated Item Count", and "Failed Component Count" in detail.
To temporarily halt the ongoing Microsoft Teams migration process, click the Stop Migration button available in the top-right corner of the dashboard. A confirmation dialog box will appear, enabling you to immediately pause the migration activity.
After confirmation, a success message will be displayed on the screen, confirming that the Microsoft Teams migration process has been paused successfully.
Select a specific Microsoft Teams workload from the Data Insights window to open the Channel Analysis Details section. This panel displays detailed migration statistics for each Team and Channel, including channel paths, migrated items, failed components, and processed data counts.
Within the same interface, the Storage Insights section displays Source and Destination storage usage through interactive visual charts, allowing users to compare utilized space, remaining storage capacity, and quota consumption during the Microsoft Teams migration process.
Click the Download Report button available in the Channel Analysis window to export a Microsoft Teams workload-specific CSV report. A download prompt will appear, allowing you to save the Teams, Channels, chats, or files migration report directly to your local system.
Open your local File Explorer and browse to the location where the downloaded Microsoft Teams migration CSV report has been stored on your system.
Open the Microsoft Teams migration report in Microsoft Excel to examine detailed migration records, including source and destination identifiers, Team and Channel paths, migration status, and success or failure information for each migrated component.
This reporting process can also be repeated for other Microsoft Teams workloads. From the respective Channel Analysis window, click the Save option to download a workload-specific migration report directly to your local system.
Open your local File Explorer and locate the downloaded Microsoft Teams workload CSV report stored on your computer.
Open the Microsoft Teams migration report in Microsoft Excel to review detailed status updates for Teams, Channels, chats, shared files, and other migrated components within the selected Microsoft Teams workload.
Once the Microsoft Teams migration process is completed, use the Migration Actions dropdown located at the top-right section of the dashboard to manage additional migration tasks and future synchronization operations.
Selecting the Retry Failed Items option opens a configuration window where you can choose specific Microsoft Teams, Channels, users, or workloads to reprocess only the components that failed during the initial migration execution.
Before starting the retry operation, a confirmation prompt will display the current Microsoft Teams migration license usage along with the remaining available license quota.
Selecting the Re-Run Full Migration option enables you to select specific Microsoft Teams, Channels, users, or workloads to execute the entire migration process again from the beginning.
Selecting the Delta Migration option allows you to migrate only the newly added or updated Microsoft Teams data that has been created in the source environment since the last migration cycle.
To generate the final Microsoft Teams migration documentation, click the Download Report dropdown menu and choose the Migration Summary Report option.
A download prompt will appear, allowing you to save the consolidated Microsoft Teams migration CSV summary report directly to your local computer.
Open your File Explorer and browse to the location where the Microsoft Teams Migration Summary Report has been saved on your system.
Open the Microsoft Teams Migration Summary Report in Microsoft Excel to review a comprehensive overview of migration statuses across all mapped source and destination Teams workloads, categorized by workload type and execution status.
For detailed Microsoft Teams migration documentation, select the Detailed Report option from the dropdown menu. A prompt window will appear, allowing you to choose specific Teams, users, Channels, or workloads to include in the generated report.
Next, configure the report generation settings by selecting the required report categories to export, such as Migration Job Details, Channel-Level Details, or Item-Level Details.
Once the reports are generated successfully, click the Download button to save the Microsoft Teams migration reports to your local system.
The generated detailed reports are packaged into a ZIP archive file. Download and save the ZIP package to your local system for future reference, compliance verification, and migration auditing purposes.
Extract the downloaded ZIP archive to access the generated Microsoft Teams migration reports. The files are automatically organized into separate folders based on each processed Team, user, Channel, or workload for simplified management and review.
Open a specific Team or user folder to access detailed CSV report files containing granular migration information for Teams, Channels, chats, shared files, tabs, and other migrated Microsoft Teams components.
Navigate to the Settings section to configure application preferences. Under the General tab, you can adjust concurrent migration execution limits using the slider control and enable support for multiple Microsoft Teams accounts.
The Logs tab provides an integrated Log Visualization feature. Click the "LOG" badge next to migration processes, Teams synchronization activities, or license operations to preview detailed system logs directly within the application interface.
Under the SMTP tab, enable the "Email Notification" feature and provide the necessary SMTP server configuration details to allow the application to send automated Microsoft Teams migration alerts and status updates.
Under the Notifications tab, you can customize the email subject line and message body for automated alerts that are triggered when the Microsoft Teams migration process starts.
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.
