Note: Copy private chats requires a ShareGate Migration Pro or Migration Ultimate package. It is not available with Migration Essentials Mailbox or Migration Essentials Files.
A few choices you make before and during a Microsoft Teams private chat copy affect which chats arrive and who can see them. These recommendations help you get the most complete results when copying private chats in ShareGate Migrate or with Copy-Chat.
In this article, selected users are those whose chats you copy, whether you select them in ShareGate Migrate or use the -Users parameter in PowerShell.
Mapped users are the source-destination pairs in your user mappings.
Map everyone, not just the users you select
It's best to map every source user to their destination account, including deactivated users.
ShareGate Migrate doesn't copy any chat that includes an unmapped user, because it can't match that user to a destination user. In ShareGate Migrate, a Some users aren't mapped warning lists those users before you continue.
Deleted accounts, external users, and guests can't be mapped. Their messages still copy and appear as Unknown user, with their original name kept.
Select everyone who needs access to a chat in the same run
ShareGate Migrate copies the full chat history of each selected user, including messages from users who weren't selected. You can't exclude messages from specific participants.
At the destination, only selected users become members of a copied chat. Messages from mapped users who weren't selected still show under their real name, but those users can't see the chat.
We recommend selecting everyone who should have access to a chat in a single run, for example, an entire department at once.
Run every copy from the same machine
Run all copies for the same source and destination tenant pair from a single machine, in ShareGate Migrate or with PowerShell, including incremental copies. ShareGate Migrate keeps incremental information on the machine that ran the copy.
Avoid splitting a large copy across several machines, even if each machine copies different users. Users on different machines often share chats, and ShareGate Migrate can't detect chats that another machine already copied. Each shared chat is copied once per machine, resulting in duplicate chats.
To shorten long copies, limit how much history you include.
Limit how much history to copy
By default, ShareGate Migrate copies all chat history, so more history means a longer copy time. To copy only recent messages, choose Last 30 days or From a start date under Select range in ShareGate Migrate. In PowerShell, set a start date with New-ChatCopyOptions. For example, to copy the last 30 days:
$options = New-ChatCopyOptions -ChatStartDate (Get-Date).AddDays(-30)
Migrate OneDrive to keep file attachments
File attachments aren't copied with chats. They stay in each sender's OneDrive, and the copied chat doesn't link to them. If you want users to keep those files, it's best to migrate OneDrive as well.
Ask users to sign out and back in
Copied chats sometimes don't appear in Microsoft Teams right away. This is a display delay in Microsoft Teams, and no data is missing.
We recommend telling users to sign out of Microsoft Teams and sign back in if they don't see their chats.
