Merge Team

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
FormatSubject
FormatMention (@)When migrating from standard channels to private or shared channels, members in mentioned tags cannot be displayed in the destination.
FormatBold
FormatItalic
FormatUnderline
FormatStrikethrough
FormatText highlight color
FormatFont color
FormatFont size
FormatMonospaced
FormatHeading
FormatParagraph
FormatDecrease indent
FormatIncrease indent
FormatBulleted list
FormatNumbered list
FormatQuote
FormatInsert link
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.
FormatInsert horizontal rule
FormatInsert table
FormatMark as important
FormatReply option××
FormatMeeting message×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. Additionally, the time zone and time format of the time text in the destination follow the configured DateTimeFormat and TimeZone customized feature strings.
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××
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 Supported1. 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 SupportedPartially SupportedIn the destination post messages, the app title cannot be migrated.
Places-Partially SupportedPartially Supported
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.
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.
Reply-
Edit post/Reply-Partially SupportedPartially SupportedIf 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 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-××

Files

Object TypeSub TypeSource App Profile Support StatusSource Service Account Authentication Support Status
NewFolder
NewWord Document
NewExcel Spreadsheet
NewPowerPoint Presentation
NewOneNote Notebook
Upload-
Add cloud storageSharePoint××
Add cloud storageDropbox××
Add cloud storageBox××
Add cloud storageShareFile××
Add cloud storageGoogle Drive××

Tab

Object TypeSub TypeSource App Profile Support StatusSource Service Account Authentication Support StatusComment
Add a tabOneNotePartially SupportedPartially SupportedSee the comments 1-2 below the table.
Add a tabDocument LibraryPartially SupportedPartially SupportedSee the comments 1-2 below the table.
Add a tabSharePointPartially SupportedPartially SupportedSee the comments 1-2 below the table.
Add a tabSharePoint PagesPartially SupportedPartially SupportedSee the comments 1-2 below the table.
Add a tabListsPartially SupportedPartially SupportedSee the comments 1-2 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 3-5 below the table.
Add a tabPowerPointPartially SupportedPartially SupportedSee the comments 3-5 below the table.
Add a tabExcelPartially SupportedPartially SupportedSee the comments 3-5 below the table.
Add a tabVisio
Add a tabPDF
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 tabNotes
Add a tabWebsite
Add a tabChannel calendar××
Add a tabWhiteboardPartially SupportedPartially SupportedSee the comments 6-7 below the table.
Add a tabFormsPartially SupportedPartially SupportedSee the comments 6-7 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 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:

  • If Only the default Documents library is 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.

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.

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-
Stabdard channel settingsChannel moderation - Who are the moderators××
Stabdard channel settingsAllow members to reply to channel messages
Stabdard channel settingsAllow members to pin channel messages××
Stabdard channel settingsAllow Bots to submit channel messages
Stabdard channel settingsAllow connectors to submit channel messages
Stabdard channel settingsRecommended tag××
Stabdard channel settingsNotification settings××
Stabdard channel settingsAnyone can post messages××Only the first channel has the setting.
Stabdard channel settingsAnyone can post; show alert that posting will notify everyone (recommended for large teams)××Only the first channel has the setting.
Stabdard channel settingsOnly owners can post messages××Only the first channel has the setting.
Layout-××

Apps

Object TypeSource App Profile Support StatusSource Service Account Authentication Support Status
Store Apps - Add as Bots
Store Apps - Add as Tab
Custom apps××

Privacy

Object TypeSource App Profile Support StatusSource Service Account Authentication Support StatusComment
Public
Private
Archived TeamPartially SupportedPartially SupportedSource 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-widePartially SupportedPartially Supported

Members

Object TypeSource App Profile Support StatusSource Service Account Authentication Support StatusComment
MemberSee the comments 1-3 below the table.
OwnerSee the comments 1-3 below the table.
Update rolePartially SupportedPartially SupportedSee 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.

Membership Type

Object TypeSource App Profile Support StatusSource Service Account Authentication Support StatusComment
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

  • if 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.

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.

  • 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.

Settings

Object TypeSource App Profile Support StatusSource Service Account Authentication Support StatusComment
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.

Shifts

NOTE

(GCC High tenants do not support shifts.)

Object TypeSource App Profile Support StatusSource Service Account Authentication Support StatusComment
Shifts settingsPartially SupportedPartially SupportedThe Schedule, Copying shifts, and Time clock settings cannot be kept to the destination.
Schedule group
Time off reason
Open shifts
ShiftsPartially SupportedPartially SupportedMake sure the Membership option is selected in the migration policy.
Schedule group member
Time offPartially SupportedPartially SupportedThe notes of time off cannot be kept to the destination.
Day notes××
Request××

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 messagesPartially SupportedIf 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 RecordingsMeeting recordings will be migrated to the Recordings folder in the destination channel folder.
Meeting Transcript××
Pending Requests××
TagsPartially Supported1. 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.

Microsoft 365 Group

Object TypeSub TypeSource App Profile Support StatusSource Service Account Authentication Support StatusComment
Notebook-
Planner-
Description-
SettingsLet people outside the organization email this team××The Merge Team job will keep the settings of destination Team’s associated Groups.
SettingsSend 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.
SettingsDon’t show team email address in Outlook××The Merge Team job will keep the settings of destination Team’s associated Groups.
SettingsExternal file sharing××The Merge Team job will keep the settings of destination Team’s associated Groups.

Microsoft 365 Group Mailbox

Object TypeSource App Profile Support StatusSource Service Account Authentication Support Status
Mails
Calendar

Team Site

Object TypeSource App Profile Support StatusSource Service Account Authentication Support StatusComment
File
SiteThe Microsoft Teams Migration will not run Power Platform jobs to migrate Power Platform data related to the Team sites.