#Microsoft 365 Commercial Environment / 21Vianet to 21Vianet Environment Migration

Refer to the tables below to view the supported and unsupported object types of 21Vianet 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	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	×	×
Format	Insert horizontal rule	√	√
Format	Insert table	√	√
Format	Mark as important	√	√
Format	Reply option	×	×
Format	Meeting message	×	Partially Supported	1.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. 2. Replies to the meeting message, such as meeting ended notification and recording started notification, cannot be migrated.
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	Partially Supported	Partially Supported	Background images of announcements cannot be migrated to the destination.
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 you share the link of a OneDrive attachment via a conversation message, the conversation message can be migrated, but the file linked by the conversation cannot be previewed in the destination. 2. If you upload a copy of a OneDrive attachment via a conversation message, the conversation message can be migrated, and the file copied by the conversation can be opened in the destination. 3. 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	-	×	×
Places	-	×	×
Stocks	-	×	×
Weather	-	×	×
Wikipedia search	-	×	×
Praise	-	×	×
YouTube	-	×	×
Form	-	×	×
Voice message	-	×	×
Picture	-	Partially Supported	Partially Supported	There are some notes need your attention. Refer to the notes below the table.
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	Current Team link	√	√
Copy link	Current Team’s channel link	√	√
Copy link	Copy links from other channels	×	×
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
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	×	×

#Channel

Object Type	Sub Type	Source App Profile Support Status	Source Service Account Authentication Support Status	Comment
Get email address	-	×	×
Show for me	-	×	×
Show for members	-	×	×
Email Message in Channel	-	×	×
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	√	√	If the SharePoint Pages/SharePoint tab links to a page that is not the Home or News page of the current team site, after the migration, the tab cannot be opened in the destination. You need to manually link the tab to that page in the destination.
Privacy	Shared channel	×	×
Name	-	√	√
Description	-	√	√
Channel settings	-	Partially Supported	Partially Supported	Recommended tag, notification settings, and first channel settings are not supported.
Layout	-	×	×

#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
Dynamic user	×	×
Assigned	√	√

#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
Forwarded message	×	×	Only the titles, subjects, and attachments (if any) of forwarded messages can be kept.
Post messages	×	√
Office Tab	×	×
Website Tab	√	√
Whiteboard	×	×
YouTube	×	×
Chat	√	√	Refer to Microsoft Teams Chat Migration for details.
Analytics	×	×
Connectors/Workflows	×	×
Store Apps - Add as Bots	×	×
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.
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.
Shifts	√	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	×	√
Settings	Sensitivity label	×	×

#Microsoft 365 Group Mailbox

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

#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:

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

2. The Meeting options link in the calendar cannot be opened. 

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

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

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

6. 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:

• Make sure you have configured an app profile for the source tenant, and the app has the permissions below to publish the source meeting link:

  • Make sure you have assigned the access policy for the AvePoint Fly app or custom Azure app. Refer to access policy for details.

  • If you use a custom Azure app, make sure you have assigned the Microsoft Graph API > OnlineMeetings.ReadWrite.All permission to the app.

• If destination users join the meeting via Teams on the web:

  • Apps, Record and translation, and Meeting notes actions will not be displayed.

  • Source organizer will be displayed as a guest and source attendees will be displayed as external users in the destination.

  • End meeting action will not be displayed.

  • The options in Meeting options and Mute notifications action displayed in More > Settings will not be displayed.

  • Manage permissions, Download attendance list and Lock the meeting actions displayed in Participants will not be displayed.

  • Together mode action in View is not available.

  • Destination users cannot save the meeting recording. The meeting recording saved by the source user will be displayed in the meeting chat of destination users rather than meeting files. When destination users click the recording, a window appears with the recording link. Destination users do not have permissions to access the recording via the recording link since the link is a source link.

• If destination users join the meeting via Teams app:

  • Rooms, Apps, Record and translation, and Meeting notes actions will not be displayed.

  • Source organizer will be displayed as an external user in the destination.

  • End meeting action will not be displayed.

  • The options in Meeting options displayed in More > Settings will not be displayed.

  • Manage permissions, Download attendance list and Lock the meeting actions displayed in Participants will not be displayed.

  • Together mode action in View is not available.

  • Destination users cannot save the meeting recording. The meeting recording saved by the source user will be displayed in the meeting chat of destination users rather than meeting files. When destination users click the recording, a window appears with the recording link. Destination users do not have permissions to access the recording via the recording link since the link is a source link.

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:

• For big bang migrations (migrate all objects at a time), the situations above may not occur, and we recommend that you enable the Replace meeting links with the destination information setting to replace the source meeting link with a destination link.

• For wave-based migrations (split the migration into multiple waves), to avoid the situations above, we recommend that you do not enable the Replace meeting links with the destination information setting and refer to the solutions provided above.

#Team Sites

Object Type	Source App Profile Support Status	Source Service Account Authentication Support Status
File	√	√
Site	√	√