Home > Microsoft Teams Migration > Migration to Microsoft Teams > Microsoft 365 Commercial Environment to Microsoft 365 Commercial Environment Migration
Export to PDFMicrosoft 365 Commercial Environment to Microsoft 365 Commercial Environment Migration
Refer to the table below to view the supported and unsupported object types of Microsoft 365 Commercial Environment.
√ – Supported; × – Unsupported.
| Object Type | Object Type | Object Type | Object Type | Object Type | Object Type | 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 | √ | √ | |
| 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 (@) | √ | √ | 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | Partially Supported | Partially Supported | Code snippets will be migrated as texts in the destination conversation. The font color, background, and title of the code snippets 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 | 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | × | × | |
| 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 | Scheduled meeting link | Scheduled meeting link | × | 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. |
| 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 ended message | Meeting ended message | Partially Supported | Partially Supported | The meeting titles of meeting ended messages cannot be migrated due to Microsoft API limitations. Fly will name the title in the format of Meeting in [Channel Name] ended for such messages in the destination.Attendance and transcript under meeting end message cannot be migrated to the destination.The migrated replies to the meeting ended messages in the destination cannot redirect to the original 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 | 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 | 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 | 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 | × | × | |
| 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 | × | × | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | √ | √ | |
| 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 | Partially Supported | Partially Supported | If the file is added via the Upload a copy method in the source, the file can be accessed in the destination after the migration; if the file is added via the Share a link method in the source, the file cannot be accessed in the destination after the migration. |
| 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 | √ | √ | |
| 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 | 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 | 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 | √ | √ | |
| 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 | √ | √ | In migrations using the Advanced method, such migrated data cannot be previewed in the destination HTML file. Fly will create a MigratedHostedContent folder under the destination File tab to ensure users can find those data. |
| 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 | × | × | |
| 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 | Partially Supported | Partially Supported | In the destination HTML file, only the text of these apps can be migrated. In the destination post messages, the app titles of these apps 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.) | Places | Places | Places | Places | Partially Supported | Partially Supported | In the destination HTML file, only the text of these apps can be migrated. In the destination post messages, the app titles of these apps 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.) | Stocks | Stocks | Stocks | Stocks | Partially Supported | Partially Supported | In the destination HTML file, only the text of these apps can be migrated. In the destination post messages, the app titles of these apps 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.) | Weather | Weather | Weather | Weather | Partially Supported | Partially Supported | In the destination HTML file, only the text of these apps can be migrated. In the destination post messages, the app titles of these apps 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.) | Wikipedia search | Wikipedia search | Wikipedia search | Wikipedia search | Partially Supported | Partially Supported | In the destination HTML file, only the text of these apps can be migrated. In the destination post messages, the app titles of these apps 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.) | Praise | Praise | Praise | Praise | Partially Supported | Partially Supported | In the destination HTML file, only the text of these apps can be migrated. In the destination post messages, the app titles of these apps 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.) | YouTube | YouTube | YouTube | YouTube | Partially Supported | Partially Supported | In the destination HTML file, only the text of these apps can be migrated. In the destination post messages, the app titles of these apps 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.) | Voice message | Voice message | Voice message | Voice message | × | × | The message can be migrated, but cannot be played 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.) | Picture | Picture | Picture | Picture | Partially Supported | Partially Supported | 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.In migrations using the Advanced method, such migrated data in the destination cannot be previewed in the destination HTML file. Fly will create a MigratedHostedContent folder under the destination File tab to ensure users can find those data. |
| 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 | √ | √ | |
| 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 | Partially Supported | Partially Supported | If you use the app profile authentication to connect to the destination and the destination Teams are newly created by Fly during the migration, the following cases will occur: ● The Edited label of source messages cannot be kept to the destination.● 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 as a new message.Other situations other than the above: ● 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 | × | × | |
| 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 | × | × | |
| 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 | × | × | |
| 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 | × | × | |
| 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 | × | × | |
| 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 | √ | √ | 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 | Copy tab link | Copy tab 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 task link | Current Team’s task 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 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 | √ | √ | |
| 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 folder link | Current Team’s folder 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 | 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.) | Copy link | Copy link | Link containing other channel ID | Link containing other channel ID | Partially Supported | Partially Supported | Links containing other channel IDs in source conversations can be migrated, but cannot link to the corresponding channels 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.) | 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 | × | × | |
| Microsoft Teams Data | Schedule message | Schedule message | Schedule message | Schedule message | Schedule message | Unsupported | Unsupported | |
| Microsoft Teams Data | Record video clip message | Record video clip message | Record video clip message | Record video clip message | Record video clip message | Partially Supported | Partially Supported | The message can be migrated. The record video clip cannot be migrated. |
| Microsoft Teams Data | 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 | Partially Supported | √ | If you only use the app profile authentication to connect to the destination and the destination Teams are newly created by Fly during the migration, conversations can be migrated as post messages in the destination; if the destination Teams already exist before the migration, conversations cannot be migrated as post messages. |
| Microsoft Teams Data | Files | New | New | Folder | Folder | √ | √ | |
| Microsoft Teams Data | Files | New | New | Word Document | Word Document | √ | √ | |
| Microsoft Teams Data | Files | New | New | Excel Spreadsheet | Excel Spreadsheet | √ | √ | |
| Microsoft Teams Data | Files | New | New | PowerPoint Presentation | PowerPoint Presentation | √ | √ | |
| Microsoft Teams Data | Files | New | New | OneNote Notebook | OneNote Notebook | √ | √ | With the Overwrite content level conflict resolution used, if the default section already exists in the destination and even if the source and destination section names may be different, the source section will overwrite the destination section. |
| Microsoft Teams Data | Files | Upload | Upload | Upload | Upload | √ | √ | |
| Microsoft Teams Data | Files | Add cloud storage | Add cloud storage | SharePoint | SharePoint | × | × | |
| Microsoft Teams Data | Files | Add cloud storage | Add cloud storage | Dropbox | Dropbox | × | × | |
| Microsoft Teams Data | Files | Add cloud storage | Add cloud storage | Box | Box | × | × | |
| Microsoft Teams Data | Files | Add cloud storage | Add cloud storage | ShareFile | ShareFile | × | × | |
| Microsoft Teams Data | Files | Add cloud storage | Add cloud storage | Google Drive | Google Drive | × | × | |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | OneNote | OneNote | Partially Supported | Partially Supported | Only OneNote tabs created with notebooks of the corresponding team site are supported. Only Document Library, SharePoint, SharePoint Pages, and Lists tabs created with SharePoint links to the corresponding team site are supported.The Document Library tab cannot be migrated in the following cases:● If Only the default Documents libraryis selected in the policy for the project, and the Document Library tab is associated with a custom document library that does not exist in the destination, the tab cannot be migrated.● Though All data in SharePoint team site is selected in the policy for the project, if the Document Library tab is associated with a custom document library that does not exist in the destination, the tab cannot be migrated in the first migration. ● If the associated files are moved to other locations in the destination, the tabs cannot be opened. |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | Document Library | Document Library | Partially Supported | Partially Supported | Only OneNote tabs created with notebooks of the corresponding team site are supported. Only Document Library, SharePoint, SharePoint Pages, and Lists tabs created with SharePoint links to the corresponding team site are supported.The Document Library tab cannot be migrated in the following cases:● If Only the default Documents libraryis selected in the policy for the project, and the Document Library tab is associated with a custom document library that does not exist in the destination, the tab cannot be migrated.● Though All data in SharePoint team site is selected in the policy for the project, if the Document Library tab is associated with a custom document library that does not exist in the destination, the tab cannot be migrated in the first migration. ● If the associated files are moved to other locations in the destination, the tabs cannot be opened. |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | SharePoint | SharePoint | Partially Supported | Partially Supported | Only OneNote tabs created with notebooks of the corresponding team site are supported. Only Document Library, SharePoint, SharePoint Pages, and Lists tabs created with SharePoint links to the corresponding team site are supported.The Document Library tab cannot be migrated in the following cases:● If Only the default Documents libraryis selected in the policy for the project, and the Document Library tab is associated with a custom document library that does not exist in the destination, the tab cannot be migrated.● Though All data in SharePoint team site is selected in the policy for the project, if the Document Library tab is associated with a custom document library that does not exist in the destination, the tab cannot be migrated in the first migration. ● If the associated files are moved to other locations in the destination, the tabs cannot be opened. |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | SharePoint Pages | SharePoint Pages | Partially Supported | Partially Supported | Only OneNote tabs created with notebooks of the corresponding team site are supported. Only Document Library, SharePoint, SharePoint Pages, and Lists tabs created with SharePoint links to the corresponding team site are supported.The Document Library tab cannot be migrated in the following cases:● If Only the default Documents libraryis selected in the policy for the project, and the Document Library tab is associated with a custom document library that does not exist in the destination, the tab cannot be migrated.● Though All data in SharePoint team site is selected in the policy for the project, if the Document Library tab is associated with a custom document library that does not exist in the destination, the tab cannot be migrated in the first migration. ● If the associated files are moved to other locations in the destination, the tabs cannot be opened. |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | Lists | Lists | Partially Supported | Partially Supported | Only OneNote tabs created with notebooks of the corresponding team site are supported. Only Document Library, SharePoint, SharePoint Pages, and Lists tabs created with SharePoint links to the corresponding team site are supported.The Document Library tab cannot be migrated in the following cases:● If Only the default Documents libraryis selected in the policy for the project, and the Document Library tab is associated with a custom document library that does not exist in the destination, the tab cannot be migrated.● Though All data in SharePoint team site is selected in the policy for the project, if the Document Library tab is associated with a custom document library that does not exist in the destination, the tab cannot be migrated in the first migration. ● If the associated files are moved to other locations in the destination, the tabs cannot be opened. |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | Tasks by Planner and To Do | Tasks by Planner and To Do | Partially Supported | Partially Supported | The plans cannot be migrated if the plan is not shared to the current team.Premium planners are not supported in the migration. |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | Word | Word | Partially Supported | Partially Supported | Only Word, PowerPoint, Excel, Visio, and PDF tabs created with files of the corresponding Team are supported.If the source shared channels are created in the before October 2022, the Word, PowerPoint, and Excel tabs cannot be migrated.If the associated files are moved to other locations in the destination, the tabs cannot be opened. |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | PowerPoint | PowerPoint | Partially Supported | Partially Supported | Only Word, PowerPoint, Excel, Visio, and PDF tabs created with files of the corresponding Team are supported.If the source shared channels are created in the before October 2022, the Word, PowerPoint, and Excel tabs cannot be migrated.If the associated files are moved to other locations in the destination, the tabs cannot be opened. |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | Excel | Excel | Partially Supported | Partially Supported | Only Word, PowerPoint, Excel, Visio, and PDF tabs created with files of the corresponding Team are supported.If the source shared channels are created in the before October 2022, the Word, PowerPoint, and Excel tabs cannot be migrated.If the associated files are moved to other locations in the destination, the tabs cannot be opened. |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | Visio | Visio | √ | √ | Only Word, PowerPoint, Excel, Visio, and PDF tabs created with files of the corresponding Team are supported.If the source shared channels are created in the before October 2022, the Word, PowerPoint, and Excel tabs cannot be migrated.If the associated files are moved to other locations in the destination, the tabs cannot be opened. |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | √ | √ | Only Word, PowerPoint, Excel, Visio, and PDF tabs created with files of the corresponding Team are supported.If the source shared channels are created in the before October 2022, the Word, PowerPoint, and Excel tabs cannot be migrated.If the associated files are moved to other locations in the destination, the tabs cannot be opened. | ||
| Microsoft Teams Data | Tab | Add a tab | Add a tab | Wiki | Wiki | × | × | Wiki tabs will be retired from Teams. If you want to migrate the content of Wiki tabs for standard channels, you can export the content to Notes tabs first and migrate the content with Notes tabs. For private channels, you can export the Wiki content to somewhere that is easy to access and migrate the content with that object. |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | Notes | Notes | √ | √ | |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | Website | Website | √ | √ | |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | Channel calendar | Channel calendar | × | × | |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | YouTube | YouTube | × | × | |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | Whiteboard | Whiteboard | Partially Supported | Partially Supported | Besides the tabs listed above, Whiteboard, Forms, and some other tabs can be migrated, but you need to manually configure the tabs in the destination.Files connected to Whiteboard tabs will not be migrated. Whiteboard tabs migrated to destination cannot connect to those source files. |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | Forms | Forms | Partially Supported | Partially Supported | Besides the tabs listed above, Whiteboard, Forms, and some other tabs can be migrated, but you need to manually configure the tabs in the destination.Files connected to Whiteboard tabs will not be migrated. Whiteboard tabs migrated to destination cannot connect to those source files. |
| Microsoft Teams Data | Tab | Add a tab | Add a tab | Other tabs | Other tabs | × | × | Other tabs can be created in the destination, but the content under the source tabs cannot be migrated. You can manually configure the content for the destination tabs. |
| Microsoft Teams Data | Tab | Tab configurations | Tab configurations | Tab configurations | Tab configurations | √ | √ | |
| Microsoft Teams Data | Channel | Get email address | Get email address | Get email address | Get email address | Partially Supported | Partially Supported | The advanced settings configured under the Get email address setting cannot be kept to the destination. |
| Microsoft Teams Data | Channel | Show for me | Show for me | Show for me | Show for me | × | × | |
| Microsoft Teams Data | Channel | Show for members | Show for members | Show for members | Show for members | × | × | |
| Microsoft Teams Data | Channel | Email Message in Channel | Email Message in Channel | Email Message in Channel | Email Message in Channel | Partially Supported | Partially Supported | An email is sent to the source channel using the Get email address action, and you can be redirected to the email by clicking Download original email link in the corresponding conversation. After the migration, the Download original email link will not exist in the migrated conversation. |
| Microsoft Teams Data | Channel | Privacy | Privacy | Private channel | Private channel | 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 | Privacy | Privacy | Standard channel | Standard channel | √ | √ | |
| Microsoft Teams Data | Channel | Privacy | Privacy | Shared channel | Shared channel | Partially Supported | √ | The Teams added as members of shared channels cannot be migrated.If you want to create shared channels in the destination and you only use app profile authentication in the destination connection, the shared channels can be created in the destination, but data under the source Posts cannot be migrated.Shared channels can only be loaded in channel mappings and migrated if they were created by your own Teams. |
| Microsoft Teams Data | Channel | Privacy | Privacy | Archived channel | Archived channel | Partially Supported | Partially Supported | To successfully migrate channels, the destination channels cannot be archived.Source archived channel can be migrated, but their Archived status will not be migrated to the destination. Fly will keep the Active status for destination channels. |
| Microsoft Teams Data | Channel | Name | Name | Name | Name | √ | √ | |
| Microsoft Teams Data | Channel | Description | Description | Description | Description | √ | √ | |
| Microsoft Teams Data | Channel | Channel settings | Channel moderation | Who are the moderators | Who are the moderators | × | × | Only standard channels have these settings. |
| Microsoft Teams Data | Channel | Channel settings | Allow members to reply to channel messages | Allow members to reply to channel messages | Allow members to reply to channel messages | √ | √ | Only standard channels have these settings. |
| Microsoft Teams Data | Channel | Channel settings | Allow members to pin channel messages | Allow members to pin channel messages | Allow members to pin channel messages | × | × | Only standard channels have these settings. |
| Microsoft Teams Data | Channel | Channel settings | Allow Bots to submit channel messages | Allow Bots to submit channel messages | Allow Bots to submit channel messages | √ | √ | Only standard channels have these settings. |
| Microsoft Teams Data | Channel | Channel settings | Allow connectors to submit channel messages | Allow connectors to submit channel messages | Allow connectors to submit channel messages | √ | √ | Only standard channels have these settings. |
| Microsoft Teams Data | Channel | Channel settings | Recommended tag | Recommended tag | Recommended tag | × | × | Only standard channels have these settings. |
| Microsoft Teams Data | Channel | Channel settings | Notification settings | Notification settings | Notification settings | × | × | Only standard channels have these settings. |
| Microsoft Teams Data | Channel | Layout | Layout | Layout | Layout | × | × | |
| Microsoft Teams Data | Chat | Chat | Chat | Chat | Chat | √ | √ | Refer to Microsoft Teams Chat Migration for support details. |
| Microsoft Teams Data | Analytics | Analytics | Analytics | Analytics | Analytics | × | × | |
| Microsoft Teams Data | Connectors/Workflows | Connectors/Workflows | Connectors/Workflows | Connectors/Workflows | Connectors/Workflows | × | × | |
| Microsoft Teams Data | Apps | Store Apps - Add as Bots | Store Apps - Add as Bots | Store Apps - Add as Bots | Store Apps - Add as Bots | √ | √ | |
| Microsoft Teams Data | Apps | Store Apps - Add as Tab | Store Apps - Add as Tab | Store Apps - Add as Tab | Store Apps - Add as Tab | √ | √ | |
| Microsoft Teams Data | Apps | Custom apps | Custom apps | Custom apps | Custom apps | × | × | |
| Microsoft Teams Data | Bookings | Bookings | Bookings | Bookings | Bookings | × | × | |
| Microsoft Teams Data | 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 | Meeting Recordings | Meeting Recordings | Meeting Recordings | Meeting Recordings | Meeting Recordings | √ | √ | |
| Microsoft Teams Data | Meeting Transcript | Meeting Transcript | Meeting Transcript | Meeting Transcript | Meeting Transcript | √ | √ | |
| Microsoft Teams Data | Privacy | Public | Public | Public | Public | √ | √ | |
| Microsoft Teams Data | Privacy | Private | Private | Private | Private | √ | √ | |
| Microsoft Teams Data | Privacy | Archived Team | Archived Team | Archived Team | Archived Team | 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 | Privacy | org-wide | org-wide | org-wide | org-wide | Partially Supported | Partially Supported | The source org-wide Team will be migrated as a public Team after the migration. |
| Microsoft Teams Data | 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 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. |
| Microsoft Teams Data | 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 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. |
| Microsoft Teams Data | Members | Update role | Update role | Update role | Update role | 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 | Dynamic user | Dynamic user | Dynamic user | Dynamic user | √ | √ | If the membership type of the source Team’s associated group is Dynamic User, andif the destination Team does not exist before the migration, Fly will create the Team during the migration and create the associated Group in the membership type of Assigned for the Team. After the migration, you can manually update the membership type of the Group to Dynamic User in Microsoft Entra ID.if the membership type of the destination Team’s associated Group is also Dynamic User, to migrate the planner data, make sure the source and destination service accounts/delegated app profiles’ consent users meet the dynamic membership rules of the source and destination Groups.If the membership type of the destination Team’s associated group is Dynamic User, and you only use the app profile as the destination authentication method, to migrate source private channels as newly created private channels in the destination, the destination app profile account must be a member/owner of the destination Group.Manually add the user as the destination group owner/member.Make sure the user meets the destination Group’s dynamic membership rule. Fly will automatically add the user as a member of the destination Group. |
| Microsoft Teams Data | Membership Type | Assigned | Assigned | Assigned | Assigned | √ | √ | |
| Microsoft Teams Data | Pending Requests | Pending Requests | Pending Requests | Pending Requests | Pending Requests | × | × | |
| Microsoft Teams Data | Settings | Team picture | Team picture | Team picture | Team picture | × | √ | |
| Microsoft Teams Data | Settings | Member permissions | Member permissions | Member permissions | Member permissions | 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 | Guest permissions | Guest permissions | Guest permissions | Guest permissions | √ | √ | |
| Microsoft Teams Data | Settings | @mentions | @mentions | @mentions | @mentions | √ | √ | |
| Microsoft Teams Data | Settings | Team code | Team code | Team code | Team code | × | × | |
| Microsoft Teams Data | Settings | Fun stuff | Fun stuff | Fun stuff | Fun stuff | √ | √ | |
| Microsoft Teams Data | Settings | Tags | Tags | Tags | Tags | √ | √ | |
| Microsoft Teams Data | 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 settings | Shifts settings | Shifts settings | Shifts settings | Partially Supported | Partially Supported | The Schedule, Copying shifts, and Time clock settings cannot be kept to the destination. |
| Microsoft Teams Data | Shifts | Schedule group | Schedule group | Schedule group | Schedule group | √ | √ | |
| Microsoft Teams Data | Shifts | Time off reason | Time off reason | Time off reason | Time off reason | √ | √ | |
| Microsoft Teams Data | Shifts | Open shifts | Open shifts | Open shifts | Open shifts | √ | √ | |
| Microsoft Teams Data | Shifts | Shifts | Shifts | Shifts | Shifts | Partially Supported | Partially Supported | Make sure the Membership option is selected in the migration policy when you run full migration jobs. For membership and complete migration jobs, you can run the job without the Membership option selected. |
| Microsoft Teams Data | Shifts | Schedule group member | Schedule group member | Schedule group member | Schedule group member | √ | √ | |
| Microsoft Teams Data | Shifts | Time off | Time off | Time off | Time off | Partially Supported | Partially Supported | The notes of time off cannot be kept to the destination. |
| Microsoft Teams Data | Shifts | Day notes | Day notes | Day notes | Day notes | × | × | |
| Microsoft Teams Data | Shifts | Request | Request | Request | Request | × | × | |
| Microsoft 365 Group | Notebook | Notebook | Notebook | Notebook | Notebook | √ | √ | |
| Microsoft 365 Group | Planner | Planner | Planner | Planner | Planner | Partially Supported | Partially Supported | Premium planners are not supported in the migration. |
| Microsoft 365 Group | Settings | Let people outside the organization email this team | Let people outside the organization email this team | Let people outside the organization email this team | Let people outside the organization email this team | × | √ | Make sure the source and destination service accounts/delegated app profiles’ consent users have the Microsoft 365 Global Administrator or Exchange Administrator role. |
| Microsoft 365 Group | Settings | Send copies of team emails and events to team member's inboxes | Send copies of team emails and events to team member's inboxes | Send copies of team emails and events to team member's inboxes | Send copies of team emails and events to team member's inboxes | × | √ | Make sure the source and destination service accounts/delegated app profiles’ consent users have the Microsoft 365 Global Administrator or Exchange Administrator role. |
| Microsoft 365 Group | Settings | Don’t show team email address in Outlook | Don’t show team email address in Outlook | Don’t show team email address in Outlook | Don’t show team email address in Outlook | × | √ | Make sure the source and destination service accounts/delegated app profiles’ consent users have the Microsoft 365 Global Administrator or Exchange Administrator role. |
| Microsoft 365 Group | Settings | External file sharing | External file sharing | External file sharing | External file sharing | √ | √ | To migrate the setting, data in SharePoint sites must be migrated together with Teams. |
| Microsoft 365 Group | Description | Description | Description | Description | Description | √ | √ | |
| Microsoft 365 Group Mailbox | Mails | Mails | Mails | Mails | Mails | √ | √ | |
| Microsoft 365 Group Mailbox | 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 below for details. |
| Team Site | Files | Files | Files | Files | Files | √ | √ | |
| Team Site | Sites | Sites | Sites | Sites | Sites | √ | √ | In Advanced mode, Fly will not keep the language of the source team site to the destination. The language of the destination team site will be the same as the destination tenant.In Classic mode, if the destination Teams are newly created during the migration, Fly will keep the language of the source team site to the destination. |
Notes when Replacing Meeting Links
If you enable the Replace meeting links with the destination information setting to replace the source meeting link with a destination link, some issues may occur in the following situations:
-
Due to API limitations, some features may be different from the source after users join the meeting with the new links.
-
If destination organizers join the meeting via Teams on the web:
-
Chat, Apps, Record and translation, and Meeting notes actions are not available.
-
The meeting title, date and time, Meeting ID, and Meeting options link will not be displayed in Meeting info.
-
The Turn off incoming video action will not be displayed in More > Settings, but will be displayed in View > More options.
-
Only the current user will be displayed in the meeting.
-
The meeting duration will not be displayed.
-
The options in Meeting options displayed in More > Settings will not be displayed.
-
-
If destination attendees join the meeting via Teams on the web:
-
Chat, Apps, Record and translation, and Meeting notes actions are not available.
-
The meeting title, date and time, Meeting ID, and Meeting options link will not be displayed in Meeting info.
-
The Turn off incoming video action will not be displayed in More > Settings, but will be displayed in View > More options.
-
Only the current user will be displayed in the meeting.
-
The meeting duration will not be displayed.
-
-
If destination organizers join the meeting via the Teams app:
-
Chat, Apps, Record and translation, and Meeting notes actions are not available.
-
Only the current user will be displayed in the meeting.
-
The meeting title, date and time, Meeting ID, and Meeting options link will not be displayed in Meeting info.
-
The meeting duration will not be displayed.
-
The options in Meeting options displayed in More > Settings will not be displayed.
-
-
If destination attendees join the meeting via the Teams app:
-
Chat, Apps, Record and translation, and Meeting notes actions are not available.
-
Only the current user will be displayed in the meeting.
-
The meeting title, date and time, Meeting ID, and Meeting options link will not be displayed in Meeting info.
-
The meeting duration will not be displayed.
-
-
-
The Meeting options link in the calendar cannot be opened.
-
The Join on the web link in the source calendar item cannot be replaced with the destination information. After you map the source meeting attendees to the destination, when the mapped attendees click the Join on the web link and use the meeting ID and passcode to join the meeting via Microsoft Teams on the web, they will wait in the lobby until the meeting organizer allows the user to enter the meeting.
-
The source tenant ID in the meeting link will be replaced with the destination information. If some users in your organization have been migrated to the destination and the meeting participants contain source users and users who have been migrated to the destination, when the source and destination participants click the meeting links in the email, they will enter two different meetings.
-
The source tenant ID in the meeting link will be replaced with the destination information. If the meeting participants contain external users, the destination meeting organizer needs to update the meeting after the migration to update the meeting link for external users. Otherwise, when external users click the link to attend the meeting, they will be redirected to the source meeting.
-
When you enable the Safe Links settings for email addresses in Microsoft 365 Defender for Office 365, the source meeting links cannot be replaced with the destination information. When the external/destination user clicks the source meeting link to attend the meeting, they will wait in the lobby until the meeting organizer allows the user to enter the meeting.
If your meeting meets the situation 4, 5, or 6 above, we recommend that you do not enable the Replace meeting links with the destination information setting and configure the ChangeTeamsMeetingScopeAsEveryone=true customized feature string in the migration policy to publish the source meeting link to everyone. Also, you need to note the following:
For whether to enable the Replace meeting links with the destination information setting in the migration policy, we have recommendations based on different migration methods:
On this page