#Perform Microsoft Teams Chat Migrations

Microsoft Teams Chat Migration allows you to migrate Teams chats for chat users, including one-on-one chats, meeting chats, group chats, chat file attachments, and chat members from Microsoft Teams Chat to Microsoft Teams Chat, or from Microsoft Teams Chat to Google Chat Space.

To understand the supported and unsupported elements in the migration, you can refer to the Support Lists for Microsoft Teams Chat Migration.

#Prepare for Migrations

Before performing Microsoft Teams Chat migrations in Fly, follow the instructions below to prepare for the migration:

1. Fly does not automatically provision new users in Microsoft 365. Make sure the destination users already exist before the migration. The users must have Microsoft 365 licenses. We recommend that you assign Microsoft 365 licenses to all destination users for easy use.

   There are different ways to add new Microsoft 365 users:

   • Adding users individually. See instructions here.

   • Adding users in bulk. See instructions here.

   • Adding users via PowerShell. See instructions here.

   • Synchronizing users from local Active Directory to Microsoft 365 via Microsoft Entra Sync or Microsoft Entra connect. See instructions here.

2. Fly can remove source sensitivity labels and apply destination ones to your chat attachment files with a corresponding option selected in the migration policy. Before using this feature, make sure to review the necessary requirements and additional information. Refer to Information about Managing Sensitivity Labels for details.

3. Please note that there will be a User added notification after chats are created in the destination and destination chat members are added to the chats. Make sure your destination chat users are informed of this information.

   This commonly happens in the following situations:

   • When a full migration job is completed and currently existing users are added to the destination chats.

   • After a full migration job, the source and destination are still in use, and new users are added to source chats. When the next incremental migration job is completed, the newly added users are added to corresponding destination chats.

   For more detailed situations of notifications, refer to Understand when users will receive notifications.