Merge Channel

NOTE

The object types that are not listed in the tables below are not supported.

√ – Supported; × – Unsupported.

Microsoft Teams Data

Conversation

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 TypeSub TypeSource App Profile Support StatusSource Service Account Authentication Support StatusComment
FormatBold
FormatBulleted list
FormatDecrease indent
FormatFont color
FormatFont size
FormatHeading
FormatIncrease indent
FormatInsert link
FormatInsert horizontal rule
FormatInsert table
FormatItalic
FormatMark as important
FormatMention @When migrating from standard channels to private or shared channels, members in mentioned tags cannot be displayed in the destination.
FormatMonospaced
FormatNumbered list
FormatParagraph
FormatQuote
FormatStrikethrough
FormatSubject
FormatText highlight color
FormatUnderline
FormatCode snippetPartially SupportedPartially SupportedCode snippets will be migrated as texts in the destination conversation. The font color, background, and title of the code snippets cannot be migrated.
FormatMeeting ended messagePartially SupportedPartially Supported1. 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.
FormatMeeting activities - Start recordingStart recordings will be migrated to the destination as system messages.
FormatMeeting activities - Recording linkRecording links will be migrated to the destination as system messages.
FormatMeeting activities - Transcript link××
FormatScheduled meeting link×Partially SupportedThe 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.
FormatReply option××
Post in multiple channels-××
Announcement type post’s specific elementsBackground××
Announcement type post’s specific elementsColor scheme
Announcement type post’s specific elementsSubheader
Announcement type post’s specific elementsHeadline
AttachRecentIf 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.
AttachBrowse Teams and channelsIf 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.
AttachOneDrivePartially SupportedPartially Supported1. 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.
AttachUpload from my computerIf 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 SupportedPartially SupportedSome 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 SupportedPartially SupportedThe emoji size will be different from that of the source emoji after the migration.
Giphy-
Reply-
Sticker-
Loop components-××
News-Partially SupportedPartially SupportedIn the destination post messages, the app title cannot be migrated.
Places-Partially SupportedPartially SupportedIn the destination post messages, the app title cannot be migrated.
Stocks-Partially SupportedPartially SupportedIn the destination post messages, the app title cannot be migrated.
Weather-Partially SupportedPartially SupportedIn the destination post messages, the app title cannot be migrated.
Wikipedia search-Partially SupportedPartially SupportedIn the destination post messages, the app title cannot be migrated.
Praise-Partially SupportedPartially SupportedIn the destination post messages, the app title cannot be migrated.
YouTube-Partially SupportedPartially SupportedIn the destination post messages, the app title cannot be migrated.
Loop components-××
Voice message-××The message can be migrated, but cannot be played in the destination.
Picture-Partially SupportedPartially SupportedAfter 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.
Edit post/Reply-×
Mark as unread-××
Translate-××
Turn on/off Notifications-××
Reaction-××
Pin-××
Copy linkConversation link1. 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 linkCopy tab link××
Copy linkCopy links from other channels××
Copy linkCurrent Team’s task link
Copy linkCurrent Team link
Copy linkCurrent Team’s channel link
Copy linkCurrent Team’s folder link××
Copy linkFile linkPartially SupportedPartially SupportedA 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 linkLink containing other channel IDPartially SupportedPartially SupportedLinks 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-××
Conversation HTML files-××

Files

Object TypeSub TypeSource App Profile Support StatusSource Service Account Authentication Support StatusComment
NewFolder
NewWord Document
NewExcel Spreadsheet
NewPowerPoint Presentation
NewOneNote NotebookPartially SupportedPartially SupportedOnly custom OneNote notebook files can be migrated.
Upload-
Add cloud storage-××

Tab

Object TypeSub TypeSource App Profile Support StatusSource Service Account Authentication Support StatusComment
Add a tabWebsite
Add a tabOneNotePartially SupportedPartially SupportedSee the comments 1-3 below the table.
Add a tabDocument LibraryPartially SupportedPartially SupportedSee the comments 1-3 below the table.
Add a tabSharePointPartially SupportedPartially SupportedSee the comments 1-3 below the table.
Add a tabSharePoint PagesPartially SupportedPartially SupportedSee the comments 1-3 below the table.
Add a tabListsPartially SupportedPartially SupportedSee the comments 1-3 below the table.
Add a tabTasks by Planner and To DoPartially SupportedPartially Supported1. 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 tabWordPartially SupportedPartially SupportedSee the comments 4-6 below the table.
Add a tabPowerPointPartially SupportedPartially SupportedSee the comments 4-6 below the table.
Add a tabExcelPartially SupportedPartially SupportedSee the comments 4-6 below the table.
Add a tabVisioSee the comments 4-6 below the table.
Add a tabPDFSee the comments 4-6 below the table.
Add a tabWiki××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 tabNotesPartially SupportedPartially SupportedOnly Notes tabs with existing OneNote files can be migrated.
Add a tabChannel calendar××
Add a tabWhiteboardPartially SupportedPartially SupportedSee the comments 7-8 below the table.
Add a tabFormsPartially SupportedPartially SupportedSee the comments 7-8 below the table.
Add a tabOther 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 channel site are supported. For default OneNote tabs, the related files must exist in the destination.

Comment 2: Only Document Library, SharePoint, SharePoint Pages, and Lists tabs created with SharePoint links to the corresponding channel site are supported.

Comment 3: If the associated files are moved to other locations in the destination, the tabs cannot be opened.

Comment 4: Only Word, PowerPoint, Excel, Visio, and PDF tabs created with files of the corresponding Team are supported.

Comment 5: If the source shared channels are created before October 2022, the Word, PowerPoint, and Excel tabs cannot be migrated.

Comment 6: If the associated files are moved to other locations in the destination, the tabs cannot be opened.

Comment 7: 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 8: Files connected to Whiteboard tabs will not be migrated. Whiteboard tabs migrated to destination cannot connect to those source files.

Channel

Object TypeSub TypeSource App Profile Support StatusSource Service Account Authentication Support StatusComment
Get email address-Partially SupportedPartially SupportedThe 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 SupportedPartially SupportedAn 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.
PrivacyPrivate channelPartially SupportedIf 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.
PrivacyStandard channel
PrivacyShared channelPartially Supported1. 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.
PrivacyArchived channelPartially SupportedPartially Supported1. 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-
Channel settings-××Only standard channels have these settings.
Meeting Recordings-Partially SupportedPartially SupportedMeeting recordings will be migrated to the Recordings folder in the destination channel folder.
Meeting Transcript-××
MemberOwner1. If a source user is blocked from signing in, the user can be migrated. 2. If the destination user of a source user is blocked from signing in, the user cannot be migrated.
MemberMember1. If a source user is blocked from signing in, the user can be migrated. 2. If the destination user of a source user is blocked from signing in, the user cannot be migrated.
MemberGuest userOnly private channel support guest users.
MemberExternal userOnly shared channels support external users.
MemberUpdate rolePartially SupportedPartially SupportedThe channel members can be promoted to owners during the migration, but owners cannot be demoted to members due to Microsoft API limitations.

Other Data

Object TypeSource App Profile Support StatusSource Service Account Authentication Support StatusComment
Schedule message××
Record video clip messagePartially SupportedPartially SupportedThe 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×

Channel Site

Object TypeSource App Profile Support StatusSource Service Account Authentication Support Status
Files
Sites