Home > Microsoft Teams Chat Migration > Migration to Microsoft Teams Chat
Export to PDFMicrosoft Teams Chat Migration supports migrating from/to the following tenants:
Microsoft 365 Commercial tenant
Microsoft Education Environment
Microsoft 365 Government GCC High tenant
Microsoft 365 Government GCC tenant
21Vianet tenant
Refer to the table below to view the supported and unsupported object types for Microsoft Teams Chat Migration.
The object types that are not listed in the table below are not supported.
√ – Supported; × – Unsupported.
| Object Type | Sub Type | Support Status | Comment |
|---|---|---|---|
| Group chat | - | √ | The changes of chat profile pictures cannot be migrated. Fly will use the original profile picture for the migrated chats in the destination. |
| Meeting chat | - | Partially Supported | 1. Meeting chats will be migrated as group chats in the destination. 2. Meeting organizers will be migrated as group chat members. 3. Meeting members cannot exceed 200. Otherwise, the migration of meeting chats will fail. |
| One-on-one chat | - | Partially Supported | 1. One-on-one chats will be migrated as group chats in the destination. 2. One-on-one chats deleted from the source may be also migrated to the destination. |
| External chat | - | × | External chats are chats created by users from other tenants. |
| Self-chat | - | × | Self-chats are chats in which the user chats with itself. |
| Just me chat | - | √ | |
| Chat with app | - | × | |
| Chat message | Format - Mention (@) | √ | |
| Chat message | Format - Bold | √ | |
| Chat message | Format - Italic | √ | |
| Chat message | Format - Underline | √ | |
| Chat message | Format - Strikethrough | √ | |
| Chat message | Format - Text highlight color | √ | |
| Chat message | Format - Font color | √ | |
| Chat message | Format - Font size | √ | |
| Chat message | Format - Monospaced | √ | |
| Chat message | Format - Heading | √ | |
| Chat message | Format - Paragraph | √ | |
| Chat message | Format - Decrease indent | √ | |
| Chat message | Format - Increase indent | √ | |
| Chat message | Format - Bulleted list | √ | |
| Chat message | Format - Numbered list | √ | |
| Chat message | Format - Quote | √ | |
| Chat message | Format - Insert link | √ | |
| Chat message | Format - Code snippet | Partially Supported | If the source or destination is other tenant, code snippets will be migrated as texts in the destination chats. The font color and background of the code snippets cannot be migrated. |
| Chat message | Format - Insert horizontal rule | √ | |
| Chat message | Format - Insert table | √ | |
| Chat message | Set delivery options - Standard | √ | |
| Chat message | Set delivery options - Important | √ | |
| Chat message | Set delivery options - Urgent | √ | |
| Chat message | Attach files - OneDrive | Partially Supported | 1. If the file is from the Microsoft Teams Chat Files folder, the file can be migrated in Microsoft Teams Chat migrations. If the file is from other folders, you need to run OneDrive migrations to migrate the file. 2. The file format in messages can be kept to the destination. |
| Chat message | Attach files - Upload from my computer | Partially Supported | If the destination has files with the same name, files in migrated chats cannot be opened in the destination. |
| Chat message | Emoji | Partially Supported | Some emojis cannot be migrated and will be replaced with a square box in the destination. Other emojis can be migrated, but their styles in the destination will differ from their original form in the source. |
| Chat message | Custom emoji | Partially Supported | 1. The emoji size will be different from that of the source emoji after the migration. 2. Custom GIF emojis can be migrated but the animation cannot work in the destination post conversation. You can view them normally in the HTML file. |
| Chat message | Giphy | Partially Supported | If the source or destination is a 21Vianet tenant, Giphy cannot be migrated. |
| Chat message | Sticker | Partially Supported | If the source or destination is a 21Vianet tenant, stickers cannot be migrated. |
| Chat message | Loop components | × | |
| Chat message | Record a video clip | × | |
| Chat message | App message | Partially Supported | The app titles of app messages cannot be kept to the destination. Fly only migrates the body content for the app messages. |
| Chat message | Voice message | × | Voice messages can be migrated, but cannot be played in the destination. |
| Chat message | Picture | √ | |
| Chat message | Reply | √ | |
| Chat message | Forwarded message | × | Only the titles, subjects, and attachments (if any) of forwarded messages can be kept. |
| Chat message | System message | Partially Supported | Messages to notify of meeting started, meeting ended, XX added YY to the chat, and meeting recording link can be migrated. |
| Chat message | Edit message/reply | Partially Supported | If you edit a source message that has been migrated to the destination and run a migration job after your edits, the edited message will be posted to the destination again with the Edited label. |
| Chat message | Send at scheduled time | × | |
| Chat message | Pin | Partially Supported | The sender in the pinned message will be replaced with the destination delegated app profile's consent user after the migration. |
| Chat message | Mark as unread | × | |
| Chat message | Translate | × | |
| Chat message | Reaction | × | |
| Chat message | Unfollow thread | × | |
| Chat message | The "Save this message" mark | × | |
| Chat message | Copy link - File link | Partially Supported | If the link is copied via the Copy link button, the link to the file cannot be redirected to the corresponding file. |
| Chat message | Copy link - Tab link | Partially Supported | Tab links copied from other chats or included in forwarded messages cannot be opened in migrated chats in the destination. |
| Post messages | - | Partially Supported | The messages will be merged and posted by the delegated app profile's consent user. The content of messages will be the same as the source. |
| Archive messages as HTML file | - | √ | |
| Files | OneDrive | Partially Supported | If the file is from the Microsoft Teams Chat Files folder, the file can be migrated in Microsoft Teams Chat migrations. If the file is from other folders, you need to run OneDrive migrations to migrate the file. |
| Files | Upload from my computer | √ | |
| Tab | Visio | √ | See the comments 1-3 below the table. |
| Tab | PowerPoint | √ | See the comments 1-3 below the table. |
| Tab | Excel | √ | See the comments 1-3 below the table. |
| Tab | OneNote | √ | See the comments 1-3 below the table. |
| Tab | Website | √ | |
| Tab | Word | √ | See the comments 1-3 below the table. |
| Tab | √ | ||
| Tab | Shared | × | |
| Apps | Store Apps - Add as Bots | × | |
| Apps | Store Apps - Add as Tab | × | |
| Apps | Custom apps | × | |
| Bookings | - | × | |
| Calendar | - | × | If you want to migrate the individual calendar events for team members, you can run an Exchange Online migration job to migrate the user mailboxes of source users to corresponding destination users. Refer to Perform Exchange Online Migrations for details. |
| Meeting recordings | - | × | |
| Chat members | - | Partially Supported | 1. To migrate chat members, configure user mappings for source members in the migration policy. 2. Members that are not Microsoft 365 users cannot be migrated. |
Comment 1: Only website tabs can be migrated to 21Vianet tenants due to Microsoft API limitations.
Comment 2: If you do not migrate tabs, links to the tabs in migrated messages will be unavailable in the destination.
Comment 3: The tabs for files that are not in the Microsoft Teams Chat Files folder will be displayed as the file types (Excel, Word, PowerPoint, etc.) in the destination and cannot be opened. You can run a OneDrive job to migrate these files and then the tabs can be opened.
| Object Type | Sub Type | Support Status | Comment |
|---|---|---|---|
| Files | Microsoft Teams Chat Files | √ | |
| Files | Other folders in OneDrive | × | Microsoft Teams Chat migrations will not migrate files outside the Microsoft Teams Chat Files folder. |