Home > Microsoft Teams Migration > Migration to Microsoft Teams > Microsoft 365 Commercial Environment / 21Vianet to 21Vianet Environment Migration
Export to PDFMicrosoft 365 Commercial Environment / 21Vianet to 21Vianet Environment Migration
Refer to the table below to view the supported and unsupported object types of 21Vianet Environment.
√ – Supported; × – Unsupported.
| Object Type | Object Type | Object Type | Object Type | Object Type | Object Type | Object Type | App Profile Support Status | App Profile Support Status | Service Account Authentication Support Status | Comment |
|---|---|---|---|---|---|---|---|---|---|---|
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Subject | Subject | Subject | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Mention (@) | Mention (@) | Mention (@) | √ | √ | √ | When migrating from standard channels to private or shared channels, members in mentioned tags cannot be displayed in the destination. |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Bold | Bold | Bold | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Italic | Italic | Italic | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Underline | Underline | Underline | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Strikethrough | Strikethrough | Strikethrough | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Text highlight color | Text highlight color | Text highlight color | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Font color | Font color | Font color | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Font size | Font size | Font size | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Monospaced | Monospaced | Monospaced | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Heading | Heading | Heading | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Paragraph | Paragraph | Paragraph | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Decrease indent | Decrease indent | Decrease indent | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Increase indent | Increase indent | Increase indent | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Bulleted list | Bulleted list | Bulleted list | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Numbered list | Numbered list | Numbered list | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Quote | Quote | Quote | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Insert link | Insert link | Insert link | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Code snippet | Code snippet | Code snippet | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Insert horizontal rule | Insert horizontal rule | Insert horizontal rule | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Insert table | Insert table | Insert table | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Mark as Important | Mark as Important | Mark as Important | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Reply option | Reply option | Reply option | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Meeting message | Meeting message | Meeting message | × | Partially Supported | Partially Supported | The meeting link in the scheduled meeting message cannot be migrated. However, if the source connection has a service account/delegated app profile, the meeting time in the link can be kept as a text to the destination. Additionally, the time zone and time format of the time text in the destination follow the configured DateTimeFormat and TimeZone customized feature strings.Replies to the meeting message, such as meeting ended notification and recording started notification, cannot be migrated. |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Meeting activities | Meeting activities | Start recording | √ | √ | √ | Meeting activities will be migrated to the destination as system messages. |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Meeting activities | Meeting activities | Recording link | √ | √ | √ | Meeting activities will be migrated to the destination as system messages. |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Format | Format | Meeting activities | Meeting activities | Transcript link | √ | √ | √ | Meeting activities will be migrated to the destination as system messages. |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Post in multiple channels | Post in multiple channels | Post in multiple channels | Post in multiple channels | Post in multiple channels | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Announcement Type Post’s Specific Elements | Announcement Type Post’s Specific Elements | Background | Background | Background | Partially Supported | Partially Supported | Partially Supported | Background images of announcements cannot be migrated to the destination. |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Announcement Type Post’s Specific Elements | Announcement Type Post’s Specific Elements | Color Scheme | Color Scheme | Color Scheme | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Announcement Type Post’s Specific Elements | Announcement Type Post’s Specific Elements | Subheader | Subheader | Subheader | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Announcement Type Post’s Specific Elements | Announcement Type Post’s Specific Elements | Headline | Headline | Headline | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Attach*Note: If a conversation contains more than 10 attachments, the conversation will be migrated as an HTML file and the attachments will be displayed as links in the file. You can click the corresponding link to download the attachment. | Attach*Note: If a conversation contains more than 10 attachments, the conversation will be migrated as an HTML file and the attachments will be displayed as links in the file. You can click the corresponding link to download the attachment. | Recent | Recent | Recent | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Attach*Note: If a conversation contains more than 10 attachments, the conversation will be migrated as an HTML file and the attachments will be displayed as links in the file. You can click the corresponding link to download the attachment. | Attach*Note: If a conversation contains more than 10 attachments, the conversation will be migrated as an HTML file and the attachments will be displayed as links in the file. You can click the corresponding link to download the attachment. | Browse Teams and channels | Browse Teams and channels | Browse Teams and channels | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Attach*Note: If a conversation contains more than 10 attachments, the conversation will be migrated as an HTML file and the attachments will be displayed as links in the file. You can click the corresponding link to download the attachment. | Attach*Note: If a conversation contains more than 10 attachments, the conversation will be migrated as an HTML file and the attachments will be displayed as links in the file. You can click the corresponding link to download the attachment. | OneDrive | OneDrive | OneDrive | √ | √ | √ | If you share the link of a OneDrive attachment via a conversation message, the conversation message can be migrated, but the file linked by the conversation cannot be previewed in the destination.If you upload a copy of a OneDrive attachment via a conversation message, the conversation message can be migrated, and the file copied by the conversation can be opened in the destination. |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Attach*Note: If a conversation contains more than 10 attachments, the conversation will be migrated as an HTML file and the attachments will be displayed as links in the file. You can click the corresponding link to download the attachment. | Attach*Note: If a conversation contains more than 10 attachments, the conversation will be migrated as an HTML file and the attachments will be displayed as links in the file. You can click the corresponding link to download the attachment. | Upload from my computer | Upload from my computer | Upload from my computer | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Emoji | Emoji | Emoji | Emoji | Emoji | Partially Supported | Partially Supported | 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. |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Custom emoji | Custom emoji | Custom emoji | Custom emoji | Custom emoji | Partially Supported | Partially Supported | Partially Supported | The emoji size will be different from that of the source emoji after the migration.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. |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Giphy | Giphy | Giphy | Giphy | Giphy | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Sticker | Sticker | Sticker | Sticker | Sticker | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Loop components | Loop components | Loop components | Loop components | Loop components | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | News | News | News | News | News | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Places | Places | Places | Places | Places | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Stocks | Stocks | Stocks | Stocks | Stocks | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Weather | Weather | Weather | Weather | Weather | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Wikipedia Search | Wikipedia Search | Wikipedia Search | Wikipedia Search | Wikipedia Search | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Praise | Praise | Praise | Praise | Praise | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | YouTube | YouTube | YouTube | YouTube | YouTube | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Form | Form | Form | Form | Form | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Voice message | Voice message | Voice message | Voice message | Voice message | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Picture | Picture | Picture | Picture | Picture | Partially Supported | Partially Supported | Partially Supported | Pictures or screenshots that are pasted to the source conversation are blob contents.In migrations using the Advanced method, such migrated data in the destination cannot be previewed. If the source connection has a service account/delegated app profile, Fly will create a MigratedHostedContent folder under the destination File tab to ensure users can find those data.If you select to migrate conversations as the HTML file in the migration, you need to run a full migration job to make sure the SharePoint data can be migrated; otherwise, the picture cannot be viewed in the destination.After you post a picture to the source conversation and then move the picture from the current channel folder to a private channel folder in the source, after the migration, the picture cannot be previewed in the destination conversation. |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Reply | Reply | Reply | Reply | Reply | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Edit post/Reply | Edit post/Reply | Edit post/Reply | Edit post/Reply | Edit post/Reply | Partially Supported | Partially Supported | 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. |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Mark as unread | Mark as unread | Mark as unread | Mark as unread | Mark as unread | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Translate | Translate | Translate | Translate | Translate | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Turn on/off Notifications | Turn on/off Notifications | Turn on/off Notifications | Turn on/off Notifications | Turn on/off Notifications | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Reaction | Reaction | Reaction | Reaction | Reaction | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Pin | Pin | Pin | Pin | Pin | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Copy link | Copy link | Conversation link | Conversation link | Conversation link | √ | √ | √ | The link of the source conversation that is shared by the Copy link action will be migrated as the conversation body.The source service account/delegated app profile’s consent user must have permissions to the Team / shared channel / private channel to be migrated or the source connection must have an app profile at the same time. Otherwise, the conversation links to messages from another Team / shared channel / private channel cannot be migrated as the conversation body. The conversation link will be migrated to the destination, but cannot link to the conversation message. |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Copy link | Copy link | Current Team link | Current Team link | Current Team link | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Copy link | Copy link | Current Team’s channel link | Current Team’s channel link | Current Team’s channel link | √ | √ | √ | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Copy link | Copy link | File link | File link | File link | Partially Supported | Partially Supported | Partially Supported | If the file link is copied via the Copy link button, the link to the file cannot be redirected to the corresponding file.If the file link is copied from another team site, the link to the file cannot be redirected to the corresponding file. |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | Unfollow thread | Unfollow thread | Unfollow thread | Unfollow thread | Unfollow thread | × | × | × | |
| Microsoft Teams Data | Conversations(Conversations will be migrated as the HTML file of the destination channel and/or messages posted in the destination channel based on your configuration.In migrations using the Classic method, migrating conversations as messages is not supported when only the app profile authentication is used for the destination.) | The “Save this message” Mark | The “Save this message” Mark | The “Save this message” Mark | The “Save this message” Mark | The “Save this message” Mark | × | × | × | |
| Microsoft Teams Data | Forwarded message | Forwarded message | Forwarded message | Forwarded message | Forwarded message | Forwarded message | × | × | × | Only the titles, subjects, and attachments (if any) of forwarded messages can be kept. |
| Microsoft Teams Data | Post messages | Post messages | Post messages | Post messages | Post messages | Post messages | × | √ | √ | |
| Microsoft Teams Data | Files | Files | New | New | Folder | Folder | √ | √ | √ | |
| Microsoft Teams Data | Files | Files | New | New | Word Document | Word Document | √ | √ | √ | |
| Microsoft Teams Data | Files | Files | New | New | Excel Spreadsheet | Excel Spreadsheet | √ | √ | √ | |
| Microsoft Teams Data | Files | Files | New | New | PowerPoint Presentation | PowerPoint Presentation | √ | √ | √ | |
| Microsoft Teams Data | Files | Files | New | New | OneNote Notebook | OneNote Notebook | √ | √ | √ | |
| Microsoft Teams Data | Files | Files | Upload | Upload | Upload | Upload | √ | √ | √ | |
| Microsoft Teams Data | Files | Files | Add cloud storage | Add cloud storage | SharePoint | SharePoint | × | × | × | |
| Microsoft Teams Data | Files | Files | Add cloud storage | Add cloud storage | Dropbox | Dropbox | × | × | × | |
| Microsoft Teams Data | Files | Files | Add cloud storage | Add cloud storage | Box | Box | × | × | × | |
| Microsoft Teams Data | Files | Files | Add cloud storage | Add cloud storage | ShareFile | ShareFile | × | × | × | |
| Microsoft Teams Data | Files | Files | Add cloud storage | Add cloud storage | Google Drive | Google Drive | × | × | × | |
| Microsoft Teams Data | Office Tab | Office Tab | Office Tab | Office Tab | Office Tab | Office Tab | × | × | × | |
| Microsoft Teams Data | Website Tab | Website Tab | Website Tab | Website Tab | Website Tab | Website Tab | √ | √ | √ | |
| Microsoft Teams Data | Whiteboard | Whiteboard | Whiteboard | Whiteboard | Whiteboard | Whiteboard | × | × | × | |
| Microsoft Teams Data | YouTube | YouTube | YouTube | YouTube | YouTube | YouTube | × | × | × | |
| Microsoft Teams Data | Channel | Channel | Get email address | Get email address | Get email address | Get email address | × | × | × | |
| Microsoft Teams Data | Channel | Channel | Show for me | Show for me | Show for me | Show for me | × | × | × | |
| Microsoft Teams Data | Channel | Channel | Show for members | Show for members | Show for members | Show for members | × | × | × | |
| Microsoft Teams Data | Channel | Channel | Email message in channel | Email message in channel | Email message in channel | Email message in channel | × | × | × | |
| Microsoft Teams Data | Channel | Channel | Privacy | Privacy | Private channel | Private channel | Partially Supported | Partially Supported | √ | If you want to create private channels in the destination and you only use app profile authentication in the destination connection, the private channels can be created in the destination, but data under the source Posts cannot be migrated. |
| Microsoft Teams Data | Channel | Channel | Privacy | Privacy | Standard channel | Standard channel | √ | √ | √ | If the SharePoint Pages/SharePoint tab links to a page that is not the Home or News page of the current team site, after the migration, the tab cannot be opened in the destination. You need to manually link the tab to that page in the destination. |
| Microsoft Teams Data | Channel | Channel | Privacy | Privacy | Shared channel | Shared channel | × | × | × | |
| Microsoft Teams Data | Channel | Channel | Name | Name | Name | Name | √ | √ | √ | |
| Microsoft Teams Data | Channel | Channel | Description | Description | Description | Description | √ | √ | √ | |
| Microsoft Teams Data | Channel | Channel | Channel settings | Channel settings | Channel settings | Channel settings | Partially Supported | Partially Supported | Partially Supported | Recommended tag and notification settings are not supported. |
| Microsoft Teams Data | Layout | Layout | Layout | Layout | × | × | × | |||
| Microsoft Teams Data | Chat | Chat | Chat | Chat | Chat | Chat | √ | √ | √ | Refer to Microsoft Teams Chat Migration for support details. |
| Microsoft Teams Data | Analytics | Analytics | Analytics | Analytics | Analytics | Analytics | × | × | × | |
| Microsoft Teams Data | Connectors/Workflows | Connectors/Workflows | Connectors/Workflows | Connectors/Workflows | Connectors/Workflows | Connectors/Workflows | × | × | × | |
| Microsoft Teams Data | Apps | Apps | Store Apps - Add as Bots | Store Apps - Add as Bots | Store Apps - Add as Bots | Store Apps - Add as Bots | × | × | × | |
| Microsoft Teams Data | Bookings | Bookings | Bookings | Bookings | Bookings | Bookings | × | × | × | |
| Microsoft Teams Data | Calendar | Calendar | Calendar | Calendar | Calendar | 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. |
| Microsoft Teams Data | Privacy | Privacy | Public | Public | Public | Public | √ | √ | √ | |
| Microsoft Teams Data | Privacy | Privacy | Private | Private | Private | Private | √ | √ | √ | |
| Microsoft Teams Data | Privacy | Privacy | Archived Team | Archived Team | Archived Team | Archived Team | Partially Supported | Partially Supported | Partially Supported | To successfully migrate Teams, the destination Teams cannot be archived.Source archived Teams can be migrated, but their Archived status will not be migrated to the destination. Fly will keep the Active status for destination Teams. |
| Microsoft Teams Data | Members | Members | Member | Member | Member | Member | √ | √ | √ | To migrate source members, select the Membership checkbox in the migration policy and configure user mappings for the source members.If a source member is blocked from signing in, the member can be migrated, but the Shift schedules of groups that contain the user cannot be migrated.If the destination user of a source member is blocked from signing in, the member cannot be migrated. |
| Microsoft Teams Data | Members | Members | Owner | Owner | Owner | Owner | √ | √ | √ | To migrate source members, select the Membership checkbox in the migration policy and configure user mappings for the source members.If a source member is blocked from signing in, the member can be migrated, but the Shift schedules of groups that contain the user cannot be migrated.If the destination user of a source member is blocked from signing in, the member cannot be migrated. |
| Microsoft Teams Data | Members | Members | Update role | Update role | Update role | Update role | Partially Supported | Partially Supported | Partially Supported | To migrate source members, select the Membership checkbox in the migration policy and configure user mappings for the source members.If a source user is blocked from signing in, the user can be migrated, but the Shift schedules of groups that contain the user cannot be migrated.If the destination user of a source user is blocked from signing in, the user cannot be migrated.The Team/channel members can be promoted to owners during the migration, but owners cannot be demoted to members due to Microsoft API limitations. |
| Microsoft Teams Data | Membership Type | Membership Type | Dynamic user | Dynamic user | Dynamic user | Dynamic user | × | × | × | |
| Microsoft Teams Data | Membership Type | Membership Type | Assigned | Assigned | Assigned | Assigned | √ | √ | √ | |
| Microsoft Teams Data | Pending Requests | Pending Requests | Pending Requests | Pending Requests | Pending Requests | Pending Requests | × | × | × | |
| Microsoft Teams Data | Settings | Settings | Team picture | Team picture | Team picture | Team picture | × | × | √ | |
| Microsoft Teams Data | Settings | Settings | Member permissions | Member permissions | Member permissions | Member permissions | Partially Supported | Partially Supported | Partially Supported | The Allow members to upload custom apps and Allow members to create, edit, and delete tagssettings cannot be migrated to the destination. |
| Microsoft Teams Data | Settings | Settings | Guest permissions | Guest permissions | Guest permissions | Guest permissions | √ | √ | √ | |
| Microsoft Teams Data | Settings | Settings | @mentions | @mentions | @mentions | @mentions | √ | √ | √ | |
| Microsoft Teams Data | Settings | Settings | Team code | Team code | Team code | Team code | × | × | × | |
| Microsoft Teams Data | Settings | Settings | Fun stuff | Fun stuff | Fun stuff | Fun stuff | √ | √ | √ | |
| Microsoft Teams Data | Settings | Settings | Tags | Tags | Tags | Tags | √ | √ | √ | |
| Microsoft Teams Data | Tags | Tags | Tags | Tags | Tags | Tags | √ | √ | Partially Supported | Tags can be migrated if you use the app profile or delegated app profile authentication for both source and destination connections. |
| Microsoft Teams Data | Shifts | Shifts | Shifts | Shifts | Shifts | Shifts | × | × | × | |
| Microsoft 365 Group | Notebook | Notebook | Notebook | Notebook | Notebook | Notebook | √ | √ | √ | |
| Microsoft 365 Group | Planner | Planner | Planner | Planner | Planner | Planner | × | × | × | |
| Microsoft 365 Group | Description | Description | Description | Description | Description | Description | √ | √ | √ | |
| Microsoft 365 Group | Settings | Settings | Allow external senders to email this group | Allow external senders to email this group | Allow external senders to email this group | Allow external senders to email this group | × | × | √ | |
| Microsoft 365 Group | Settings | Settings | Send copies of group conversations and events to group members | Send copies of group conversations and events to group members | Send copies of group conversations and events to group members | Send copies of group conversations and events to group members | × | × | √ | |
| Microsoft 365 Group | Settings | Settings | Sensitivity label | Sensitivity label | Sensitivity label | Sensitivity label | × | × | × | |
| Microsoft 365 Group Mailbox | √ | √ | √ | |||||||
| Microsoft 365 Group Mailbox | Calendar | Calendar | Calendar | Calendar | Calendar | Calendar | √ | √ | √ | If you enable the Replace the meeting links with the destination information setting in the Microsoft Teams migration policy to replace the source meeting link with a destination link, make sure you have configured user mappings for the source meeting organizers, and there are some notes that need your attention. Refer to the Notes when Replacing Meeting Links section under Microsoft 365 Commercial Environment to Microsoft 365 Commercial Environment Migration for details. |
| Team Site | File | File | File | File | File | File | √ | √ | √ | |
| Team Site | Site | Site | Site | Site | Site | Site | √ | √ | √ |
On this page