Microsoft Teams Chat Migration Guide

• When an organization moves to a new Microsoft 365 tenant, private and group chats often contain important decisions, discussions, and shared content that needs to move along with the rest of the collaboration data.
• During a company merger or acquisition, employees from both organizations may need access to past conversations in a single unified tenant, making chat migration a necessary part of the transition.
• When teams are reorganized or employees change roles, migrating chat history ensures continuity so that relevant context and prior conversations aren't lost.
• Compliance and record-keeping requirements may make it necessary to consolidate chat data into a primary tenant for auditing or archiving purposes.

On the source tenant:

1. Have the SharePoint source server URL, Admin Center URL, and a Global Admin account with credentials ready.
2. To migrate private chats (1:1 chats) and group chats, manually register the application in Microsoft Entra ID (formerly Azure Active Directory) of your source Microsoft 365 tenant.

     Click here to learn how to manually register the EdbMails application in Azure AD.

On the target tenant:

1. Have the SharePoint target server URL, Admin Center URL, and a Global Admin account with credentials ready.
2. To migrate private chats (1:1) and group chats, manually register the application in Microsoft Entra ID (formerly Azure Active Directory) of your target Microsoft 365 tenant.

    Click here to learn how to manually register the EdbMails application in Azure AD

Step 1: Download and Install EdbMails

• Download and install the EdbMails Microsoft Teams Migration Tool.

  

• Launch EdbMails, enter your email address and password, then click ‘Login’ or click ‘Start Your Free Trial’.

  

• Select 'Microsoft 365, Exchange, SharePoint, OneDrive, and Teams Migrations', and then choose 'SharePoint Sites, OneDrive, Teams Migration'.

  

• Select 'Private (1:1) and Group Chat Migration'.

  

• Keep the default job name or click 'New Job' to set a custom name.

  

Step 2: Connect to the Source Tenant

• Enter the source SharePoint server URL, Admin Center URL, and your Global Admin credentials, then click 'Next'.

  

  For private and group chats, register the EdbMails application in Microsoft Entra ID (Azure AD) of your source Office 365 tenant.

   Learn how to manually register the EdbMails application in Microsoft Entra ID.

• After the application registration, enter the Application (Client) ID and Directory (Tenant) ID that you have copied from Microsoft Entra Admin Center. Then click the ‘Import’ button.

  

• Browse the PFX file, enter the ‘Password’ (the password you set when exporting the PFX file using PowerShell Commands), and then click the ‘Continue’ button.

  

   Note: You can also directly copy the value for the certificate thumbprint from the ‘Entra admin center’ under the ‘Certificates & secrets’ section.

• Click the ‘Login’ button to continue.

  

• Click the ‘Load Users Automatically’ button; EdbMails will load and display the user list automatically. Then, click ‘Next’ to proceed.

  

Step 3: Select Users

• Select the users you want to include in the chat migration, then click 'Next' to continue.

  

Step 4: Connect to Target Tenant

• Enter the target SharePoint server URL, Admin Center URL, and Global Admin credentials, then click Next.

  

  Register EdbMails app on the Target Office 365 Entra ID.

   Click here to learn how to manually register the EdbMails application in target Office 365 Entra ID.

• After app registration on the target Tenant, enter the Application (Client) ID and Directory (Tenant) ID that you have copied from Microsoft Entra Admin Center. Then click the ‘Import’ button.

  

• Browse the PFX file, enter the ‘Password’ (the password you set when exporting the PFX file using PowerShell Commands), and then click the ‘Continue’ button.

  

• Click the ‘Login’ button to continue.

  

• Click the ‘Load Users Automatically’ button; EdbMails will load and display the target user list automatically. Then, click ‘Next’ to proceed.

  

Step 5: Source and Target Users Mapping

• Select an option to map users between the source and target servers. EdbMails can automatically map users between the servers. Alternatively, you can manually map the users or use the mapping from a previous migration.

  

Step 6: Start the Teams Chat Migration

• Review the source-to-target site mapping and click 'Start Migration' to begin.

  

• Migration progress is displayed in real time. You can pause and resume the process at any point. Once migration completes, a status prompt will appear.

  

• Click the ‘View Log’ to review migrated items and message counts per chat.