Home > Aviator – Microsoft Teams > Merge Team
Export to PDFThe object types that are not listed in the tables below are not supported.
√ – Supported; × – Unsupported.
Note that 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.
| Object Type | Sub Type | Source App Profile Support Status | Source Service Account Authentication Support Status | Comment |
|---|---|---|---|---|
| Format | Subject | √ | √ | |
| Format | Mention (@) | √ | √ | When migrating from standard channels to private or shared channels, members in mentioned tags cannot be displayed in the destination. |
| Format | Bold | √ | √ | |
| Format | Italic | √ | √ | |
| Format | Underline | √ | √ | |
| Format | Strikethrough | √ | √ | |
| Format | Text highlight color | √ | √ | |
| Format | Font color | √ | √ | |
| Format | Font size | √ | √ | |
| Format | Monospaced | √ | √ | |
| Format | Heading | √ | √ | |
| Format | Paragraph | √ | √ | |
| Format | Decrease indent | √ | √ | |
| Format | Increase indent | √ | √ | |
| Format | Bulleted list | √ | √ | |
| Format | Numbered list | √ | √ | |
| Format | Quote | √ | √ | |
| Format | Insert link | √ | √ | |
| Format | 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. |
| Format | Insert horizontal rule | √ | √ | |
| Format | Insert table | √ | √ | |
| Format | Mark as important | √ | √ | |
| Format | Reply option | × | × | |
| Format | Meeting message | × | Partially Supported | The meeting link in the scheduled meeting message cannot be migrated. However, if the source connection has a service account, 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. |
| Format | Meeting ended message | Partially Supported | Partially Supported | 1. 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. 2. Attendance and transcript under meeting end message cannot be migrated to the destination. 3. The migrated replies to the meeting ended messages in the destination cannot redirect to the original messages. |
| Format | Meeting activities - Start recording | √ | √ | Start recordings will be migrated to the destination as system messages. |
| Format | Meeting activities - Recording link | √ | √ | Recording links will be migrated to the destination as system messages. |
| Format | Meeting activities - Transcript link | × | × | |
| Post in multiple channels | - | × | × | |
| Announcement type post’s specific elements | Background | × | × | |
| Announcement type post’s specific elements | Color scheme | √ | √ | |
| Announcement type post’s specific elements | Subheader | √ | √ | |
| Announcement type post’s specific elements | Headline | √ | √ | |
| Attach | Recent | √ | √ | 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 | Browse Teams and channels | √ | √ | 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 | OneDrive | Partially Supported | Partially Supported | 1. 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. 2. 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 | Upload from my computer | √ | √ | 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. |
| 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. |
| Custom emoji | - | Partially Supported | Partially Supported | 1. The emoji size will be different from that of the source emoji after the migration. 2. Custom GIF emojis can be migrated but the animation cannot work in the destination post conversation. You can view them normally in the HTML file. |
| Giphy | - | √ | √ | |
| Sticker | - | √ | √ | |
| Loop components | - | × | × | |
| News | - | Partially Supported | Partially Supported | In the destination post messages, the app title cannot be migrated. |
| Places | - | Partially Supported | Partially Supported | |
| Stocks | - | Partially Supported | Partially Supported | In the destination post messages, the app title cannot be migrated. |
| Weather | - | Partially Supported | Partially Supported | In the destination post messages, the app title cannot be migrated. |
| Wikipedia search | - | Partially Supported | Partially Supported | In the destination post messages, the app title cannot be migrated. |
| Praise | - | Partially Supported | Partially Supported | In the destination post messages, the app title cannot be migrated. |
| YouTube | - | Partially Supported | Partially Supported | In the destination post messages, the app title cannot be migrated. |
| Voice message | - | × | × | The message can be migrated, but cannot be played in the destination. |
| 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. |
| 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 Edited label of source messages cannot be kept to the destination. |
| Mark as unread | - | × | × | |
| Translate | - | × | × | |
| Turn on/off Notifications | - | × | × | |
| Reaction | - | × | × | |
| Pin | - | × | × | |
| Copy link | Conversation link | √ | √ | 1. The link of the source conversation that is shared by the Copy link action will be migrated as the conversation body. 2. 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. |
| Copy link | Copy tab link | × | × | |
| Copy link | Copy links from other channels | × | × | |
| Copy link | Current Team’s task link | √ | √ | |
| Copy link | Current Team link | √ | √ | |
| Copy link | Current Team’s channel link | √ | √ | |
| Copy link | Current Team’s folder link | × | × | |
| Copy link | File link | Partially Supported | Partially Supported | A SharePoint document is shared with the source conversation by the Share > Copy Link action. After the migration, you cannot be redirected to the shared document by clicking the document link in the destination conversation. |
| Copy link | 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. |
| Unfollow thread | - | × | × | |
| The "Save this message" mark | - | × | × |
| Object Type | Sub Type | Source App Profile Support Status | Source Service Account Authentication Support Status |
|---|---|---|---|
| New | Folder | √ | √ |
| New | Word Document | √ | √ |
| New | Excel Spreadsheet | √ | √ |
| New | PowerPoint Presentation | √ | √ |
| New | OneNote Notebook | √ | √ |
| Upload | - | √ | √ |
| Add cloud storage | SharePoint | × | × |
| Add cloud storage | Dropbox | × | × |
| Add cloud storage | Box | × | × |
| Add cloud storage | ShareFile | × | × |
| Add cloud storage | Google Drive | × | × |
| Object Type | Sub Type | Source App Profile Support Status | Source Service Account Authentication Support Status | Comment |
|---|---|---|---|---|
| Add a tab | OneNote | Partially Supported | Partially Supported | See the comments 1-2 below the table. |
| Add a tab | Document Library | Partially Supported | Partially Supported | See the comments 1-2 below the table. |
| Add a tab | SharePoint | Partially Supported | Partially Supported | See the comments 1-2 below the table. |
| Add a tab | SharePoint Pages | Partially Supported | Partially Supported | See the comments 1-2 below the table. |
| Add a tab | Lists | Partially Supported | Partially Supported | See the comments 1-2 below the table. |
| Add a tab | Tasks by Planner and To Do | Partially Supported | Partially Supported | 1. The plans cannot be migrated if the plan is not shared to the current team. 2. Premium planners are not supported in the migration. |
| Add a tab | Word | Partially Supported | Partially Supported | See the comments 3-5 below the table. |
| Add a tab | PowerPoint | Partially Supported | Partially Supported | See the comments 3-5 below the table. |
| Add a tab | Excel | Partially Supported | Partially Supported | See the comments 3-5 below the table. |
| Add a tab | Visio | √ | √ | |
| Add a tab | √ | √ | ||
| Add a tab | 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. |
| Add a tab | Notes | √ | √ | |
| Add a tab | Website | √ | √ | |
| Add a tab | Channel calendar | × | × | |
| Add a tab | Whiteboard | Partially Supported | Partially Supported | See the comments 6-7 below the table. |
| Add a tab | Forms | Partially Supported | Partially Supported | See the comments 6-7 below the table. |
| Add a tab | 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. |
| Tab configurations | - | √ | √ |
Comment 1: 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.
Comment 2: The Document Library tab cannot be migrated in the following cases:
Comment 3: Only Word, PowerPoint, Excel, Visio, and PDF tabs created with files of the corresponding Team are supported.
Comment 4: If the source shared channels are created before October 2022, the Word, PowerPoint, and Excel tabs cannot be migrated.
Comment 5: If the associated files are moved to other locations in the destination, the tabs cannot be opened.
Comment 6: 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.
Comment 7: Files connected to Whiteboard tabs will not be migrated. Whiteboard tabs migrated to destination cannot connect to those source files.
| Object Type | Sub Type | Source App Profile Support Status | Source Service Account Authentication Support Status | Comment |
|---|---|---|---|---|
| Get email address | - | Partially Supported | Partially Supported | The advanced settings configured under the Get email address setting cannot be kept to the destination. |
| Show for me | - | × | × | |
| Show for members | - | × | × | |
| 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. |
| Privacy | 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. |
| Privacy | Standard channel | √ | √ | |
| Privacy | Shared channel | Partially Supported | √ | 1. The Teams added as members of shared channels cannot be migrated. 2. 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. 3. Shared channels can only be loaded in channel mappings and migrated if they were created by your own Teams. |
| Privacy | Archived channel | Partially Supported | Partially Supported | 1. To successfully migrate channels, the destination channels cannot be archived. 2. Source archived channels of commercial tenants can be migrated, but their Archived status will not be migrated to the destination. Fly will keep the Active status for destination channels. |
| Name | - | √ | √ | |
| Description | - | √ | √ | |
| Stabdard channel settings | Channel moderation - Who are the moderators | × | × | |
| Stabdard channel settings | Allow members to reply to channel messages | √ | √ | |
| Stabdard channel settings | Allow members to pin channel messages | × | × | |
| Stabdard channel settings | Allow Bots to submit channel messages | √ | √ | |
| Stabdard channel settings | Allow connectors to submit channel messages | √ | √ | |
| Stabdard channel settings | Recommended tag | × | × | |
| Stabdard channel settings | Notification settings | × | × | |
| Stabdard channel settings | Anyone can post messages | × | × | Only the first channel has the setting. |
| Stabdard channel settings | Anyone can post; show alert that posting will notify everyone (recommended for large teams) | × | × | Only the first channel has the setting. |
| Stabdard channel settings | Only owners can post messages | × | × | Only the first channel has the setting. |
| Layout | - | × | × |
| Object Type | Source App Profile Support Status | Source Service Account Authentication Support Status |
|---|---|---|
| Store Apps - Add as Bots | √ | √ |
| Store Apps - Add as Tab | √ | √ |
| Custom apps | × | × |
| Object Type | Source App Profile Support Status | Source Service Account Authentication Support Status | Comment |
|---|---|---|---|
| Public | √ | √ | |
| Private | √ | √ | |
| Archived Team | Partially Supported | Partially Supported | 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. |
| org-wide | Partially Supported | Partially Supported |
| Object Type | Source App Profile Support Status | Source Service Account Authentication Support Status | Comment |
|---|---|---|---|
| Member | √ | √ | See the comments 1-3 below the table. |
| Owner | √ | √ | See the comments 1-3 below the table. |
| Update role | Partially Supported | Partially Supported | See the comments 1-4 below the table. |
Comment 1: To migrate source members, select the Membership checkbox in the migration policy and configure user mappings for the source members.
Comment 2: 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.
Comment 3: If the destination user of a source user is blocked from signing in, the user cannot be migrated.
Comment 4: The Team/channel members can be promoted to owners during the migration, but owners cannot be demoted to members due to Microsoft API limitations.
| Object Type | Source App Profile Support Status | Source Service Account Authentication Support Status | Comment |
|---|---|---|---|
| Dynamic user | × | × | See the comments 1-2 below the table. |
| Assigned | √ | √ |
Comment 1: If the membership type of the source Team’s associated group is Dynamic User, and
Comment 2: 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.
| Object Type | Source App Profile Support Status | Source Service Account Authentication Support Status | Comment |
|---|---|---|---|
| Team picture | × | × | The Merge Team job will keep the destination Team’s settings. |
| Member permissions | × | × | The Merge Team job will keep the destination Team’s settings. |
| Guest permissions | × | × | The Merge Team job will keep the destination Team’s settings. |
| @mentions | × | × | The Merge Team job will keep the destination Team’s settings. |
| Team code | × | × | The Merge Team job will keep the destination Team’s settings. |
| Fun stuff | × | × | The Merge Team job will keep the destination Team’s settings. |
| Tags | × | × | The Merge Team job will keep the destination Team’s settings. |
(GCC High tenants do not support shifts.)
| Object Type | Source App Profile Support Status | Source Service Account Authentication Support Status | Comment |
|---|---|---|---|
| Shifts settings | Partially Supported | Partially Supported | The Schedule, Copying shifts, and Time clock settings cannot be kept to the destination. |
| Schedule group | √ | √ | |
| Time off reason | √ | √ | |
| Open shifts | √ | √ | |
| Shifts | Partially Supported | Partially Supported | Make sure the Membership option is selected in the migration policy. |
| Schedule group member | √ | √ | |
| Time off | Partially Supported | Partially Supported | The notes of time off cannot be kept to the destination. |
| Day notes | × | × | |
| Request | × | × |
| Object Type | Source App Profile Support Status | Source Service Account Authentication Support Status | Comment |
|---|---|---|---|
| Schedule message | × | × | |
| Record video clip message | Partially Supported | Partially Supported | The message can be migrated. The record video clip cannot be migrated. |
| Forwarded message | × | × | Only the titles, subjects, and attachments (if any) of forwarded messages can be kept. |
| 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. |
| Chat | × | × | |
| Analytics | × | × | |
| Connectors | × | × | |
| Bookings | × | × | |
| Calendar | × | × | If you want to migrate the individual calendar events for team members, you can run an Exchange Online migration job to migrate the user mailboxes of source users to corresponding destination users. Refer to Perform Exchange Online Migrations for details. |
| Meeting Recordings | √ | √ | Meeting recordings will be migrated to the Recordings folder in the destination channel folder. |
| Meeting Transcript | × | × | |
| Pending Requests | × | × | |
| Tags | √ | Partially Supported | 1. Tags of commercial, Education, and GCC tenants can be migrated if you use the app profile or delegated app profile authentication for both source and destination connections. 2. Tags of GCC High tenants can be migrated if you use the service account and delegated app profile authentication for both source and destination connections. |
| Object Type | Sub Type | Source App Profile Support Status | Source Service Account Authentication Support Status | Comment |
|---|---|---|---|---|
| Notebook | - | √ | √ | |
| Planner | - | √ | √ | |
| Description | - | √ | √ | |
| Settings | Let people outside the organization email this team | × | × | The Merge Team job will keep the settings of destination Team’s associated Groups. |
| Settings | Send copies of team emails and events to team member's inboxes | × | × | The Merge Team job will keep the settings of destination Team’s associated Groups. |
| Settings | Don’t show team email address in Outlook | × | × | The Merge Team job will keep the settings of destination Team’s associated Groups. |
| Settings | External file sharing | × | × | The Merge Team job will keep the settings of destination Team’s associated Groups. |
| Object Type | Source App Profile Support Status | Source Service Account Authentication Support Status |
|---|---|---|
| Mails | √ | √ |
| Calendar | √ | √ |
| Object Type | Source App Profile Support Status | Source Service Account Authentication Support Status | Comment |
|---|---|---|---|
| File | √ | √ | |
| Site | √ | √ | The Microsoft Teams Migration will not run Power Platform jobs to migrate Power Platform data related to the Team sites. |