You migrate content with the Copy-Chat command in PowerShell and get the following error:
Copying Teams private chats using ShareGate will be disabled until further notice. This will help us process the valuable feedback and data to bring back an improved version in the future. Don’t worry, you can continue to use all other features as normal. We’ll let you know as soon as we have any updates.
Microsoft Teams private chat copy with the
Copy-Chat command in PowerShell was available as a beta feature in ShareGate's migration tool.
We recently discovered 2 possible issues with the message history at the destination:
- Users who joined a group chat later will have access to messages from before they joined in the Chat history tab at the destination.
- When you recopy the same chat for a different user who joined that chat more recently, all messages from before he joined are removed from the chat history at the destination. This is because each new chat copy overwrites the chat history for that conversation.
To avoid issues with these discoveries and further improve
Copy-Chats with the information we've gathered since its inception, we've decided to remove the command from the migration tool's PowerShell module until further notice.
Caution: Considering the risks involved, we do not recommend using the beta
Copy-Chats command at this time, even if it can still be used with older versions of the migration tool.