#Microsoft 365 Government GCC High Environment to Microsoft 365 Government GCC High Environment Migration

Refer to the tables below to view the supported and unsupported object types of Microsoft 365 Government GCC High Environment.

√ – 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 Type	Sub Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
Format	Add 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	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.
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.
Meeting activities	Start recording	√	√	Meeting activities will be migrated to the destination as system messages.
Meeting activities	Recording link	√	√	Meeting activities will be migrated to the destination as system messages.
Meeting activities	Transcript link	√	√	Meeting activities will be migrated to the destination as system messages.
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	√	√	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	-	×	×
Voice message	-	×	×
Picture	-	Partially Supported	Partially Supported	1. 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. 2. In migrations using the Advanced method, such migrated data in the destination cannot be previewed. Fly will create a MigratedHostedContent folder under the destination File tab to ensure users can find those data.
Reply	-	√	√
Edit post/Reply	-	Partially Supported	Partially Supported	If the source conversation contains attachment and attachment URL replaced, that conversation will have an Edited label.
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	×	×	A subfolder of a channel folder is shared to the source conversation by the Get link of Microsoft Teams action. After the migration, you will be redirected to the channel folder of the subfolder but not the subfolder itself by clicking the subfolder 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.
Copy link	File link	Partially Supported	Partially Supported	1. If the file link is copied via the Copy link button, the link to the file cannot be redirected to the corresponding file. 2. If the file link is copied from another team site, the link to the file cannot be redirected to the corresponding file.
Unfollow thread	-	×	×
The "Save this message" mark	-	×	×

#Files

Object Type	Sub Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
New	Folder	√	√
New	Word Document	√	√
New	Excel Spreadsheet	√	√
New	PowerPoint Presentation	√	√
New	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.
Upload	-	√	√
Add cloud storage	SharePoint	×	×
Add cloud storage	Dropbox	×	×
Add cloud storage	Box	×	×
Add cloud storage	ShareFile	×	×
Add cloud storage	Google Drive	×	×

#Tab

Object Type	Sub Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
Add a tab	Notebook	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	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-4 below the table.
Add a tab	PowerPoint	Partially Supported	Partially Supported	See the comments 3-4 below the table.
Add a tab	Excel	Partially Supported	Partially Supported	See the comments 3-4 below the table.
Add a tab	SharePoint	Partially Supported	Partially Supported
Add a tab	Notes	√	√
Add a tab	PDF	√	√
Add a tab	SharePoint Pages	√	√
Add a tab	Website	√	√
Add a tab	Lists	×	×
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	Visio	×	×
Add a tab	Channel calendar	×	×
Add a tab	YouTube	×	×
Add a tab	Whiteboard	Partially Supported	Partially Supported	1. Besides the tabs listed above, Whiteboard and some other tabs can be migrated, but you need to manually configure the tabs in the destination. 2. Files connected to Whiteboard tabs will not be migrated. Whiteboard tabs migrated to destination cannot connect to those source files.
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:

• 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, and Excel tabs created with files of the corresponding Team are supported.

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

#Channel

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	-	×	×
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. Additionally, the Files tab can be migrated to the destination, but you need to manually initialize the Files tab in the destination and run an incremental job to migrate the data under the Files tab.
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.
Name	-	√	√
Description	-	√	√
Standard Channel settings	Who are the moderators	×	×
Standard Channel settings	Allow members to reply to channel messages	√	√
Standard Channel settings	Allow members to pin channel messages	×	×
Standard Channel settings	Allow Bots to submit channel messages	√	√
Standard Channel settings	Allow connectors to submit channel messages	√	√
Standard Channel settings	Recommended tag	×	×
Standard Channel settings	Notification settings	×	×
Standard Channel settings	Anyone can post messages	×	×	Only first channels have these settings.
Standard Channel settings	Anyone can post; show alert that posting will notify everyone (recommended for large teams)	×	×	Only first channels have these settings.
Standard Channel settings	Only owners can post messages	×	×	Only first channels have these settings.
Layout	-	×	×

#Apps

Object Type	Source App Profile Support Status	Source Service Account Authentication Support Status
Store Apps	√	√
Custom apps	×	×

#Privacy

Object Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
Public	√	√
Private	√	√
Archived Team	Partially Supported	Partially Supported	1. To successfully migrate Teams, the destination Teams cannot be archived. 2. 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.

#Members

Object Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
Member	√	√	See the comment 1 below the table.
Owner	√	√	See the comment 1 below the table.
Update role	Partially Supported	Partially Supported	See the comments 1-2 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.

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

Comment 2: 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 Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
Dynamic user	√	√	See the commenta 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 Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
Team picture	×	√
Member permissions	Partially Supported	Partially Supported	The Allow members to upload custom apps and Allow members to create, edit, and delete tags settings cannot be migrated to the destination.
Guest permissions	√	√
@mentions	√	√
Team code	×	×
Fun stuff	√	√
Tags	√	√

#Other Data

Object Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
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 the destination connection does not have a service account/delegated app profile, post messages are supported only if the destination Teams are newly created during the migration.
Chat	√	√	Refer to Microsoft Teams Chat Migration for details.
Analytics	×	×
Connectors/Workflows	×	×
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 Transcript	√	√
Pending Requests	×	×
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 365 Group

Object Type	Sub Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
Notebook	-	√	√
Planner	-	×	×
Description	-	√	√
Settings	Allow external senders to email this group	×	√
Settings	Send copies of group conversations and events to group members	×	√

#Microsoft 365 Group Mailbox

Object Type	Source App Profile Support Status	Source Service Account Authentication Support Status
Mails	√	√
Calendar	√	√

#Team Sites

Object Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
File	√	√
Site	√	√	1. 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. 2. 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.