Home > Microsoft Teams Migration > Migration to Microsoft Teams > Microsoft 365 Commercial Environment / 21Vianet to 21Vianet Environment Migration
Download this articleRefer to the tables below to view the supported and unsupported object types of 21Vianet Environment.
The object types that are not listed in the table 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 | × | × | |
| 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 | × | × | |
| 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 | See the comments 1-4 below the table. |
| Reply | - | √ | √ | |
| Edit post/Reply | - | Partially Supported | Partially Supported | If you edit a source message that has been migrated to the destination and run a migration job after your edits, the edited message will be posted to the destination again with the 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 / 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 / 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 | - | × | × |
Comment 1: Pictures or screenshots that are pasted to the source conversation are blob contents.
Comment 2: In migrations using the Advanced method, such migrated data in the destination cannot be previewed. If the source connection has a service account/delegated app profile, Fly will create a MigratedHostedContent folder under the destination File tab to ensure users can find those data.
Comment 3: If you select to migrate conversations as the HTML file in the migration, you need to run a full migration job to make sure the SharePoint data can be migrated; otherwise, the picture cannot be viewed in the destination.
Comment 4: 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.
| 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 |
|---|---|---|---|---|
| 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 | - | × | × |
| 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. |
| 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.
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.
| Object Type | Source App Profile Support Status | Source Service Account Authentication Support Status |
|---|---|---|
| Dynamic user | × | × |
| Assigned | √ | √ |
| 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 | √ | √ |
| 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 | × | × |
| 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 | √ | √ |
| 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 under Microsoft 365 Commercial Environment Microsoft 365 Commercial Environment Migration for details. |
| 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. |