Home > Microsoft Teams Migration > Migration to Google Chat Space

Export to PDF

Migration to Google Chat Space

Microsoft Teams to Google Chat Space Migration supports migrating from/to the following tenants:

  • Microsoft 365 Commercial tenant

  • Microsoft Education Environment

  • Microsoft 365 Government GCC High tenant

  • 21Vianet tenant

Refer to the table below to view the supported and unsupported object types for Microsoft Teams to Google Chat Space Migration.

NOTE

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

– Supported; × Unsupported.

Microsoft Teams Data

Conversation

Object TypeSub TypeSource App Profile Support StatusSource Service Account Authentication Support StatusComment
Format (Some formats are not supported but content can be migrated normally)SubjectPartially SupportedPartially SupportedConversation subject only shows as bold in the destination, other formats does not support to migrate.
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
Format (Some formats are not supported but content can be migrated normally)Code snippetPartially SupportedPartially SupportedThe title of the code snippet will be placed under the message title and upon the code snippet.
FormatInsert horizontal rule××
FormatInsert table
Format (Some formats are not supported but content can be migrated normally)Mark as importantPartially SupportedPartially SupportedImportant message will be migrated to destination with important note. However, text color and important icon cannot be migrated.
FormatReply option××
FormatScheduled meeting link××
Format (Some formats are not supported but content can be migrated normally)Meeting ended messagePartially SupportedPartially Supported1.Meeting end message can be migrated to the destination with title "Meeting in {destination space name} ended". 2. The meeting titles of meeting ended messages cannot be migrated due to Microsoft API. 3. Attendance and transcript under meeting end message cannot be migrated to the destination. 4. The migrated replies to the meeting ended messages in the destination cannot redirect to the original messages.
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××
AttachRecentPartially SupportedPartially SupportedIf attachment is attached from another Team or OneDrive, URL mapping is required when run Replace attachment URLs job, otherwise destination attachment URL will show source attachment URL.
AttachBrowse Teams and channelsPartially SupportedPartially SupportedIf attachment is attached from another Team or OneDrive, URL mapping is required when run Replace attachment URLs job, otherwise destination attachment URL will show source attachment URL.
AttachOneDrivePartially SupportedPartially SupportedIf attachment is attached from another Team or OneDrive, URL mapping is required when run Replace attachment URLs job, otherwise destination attachment URL will show source attachment URL.
AttachUpload from my computer
Emoji-Partially SupportedPartially SupportedEmojis can be migrated, but their styles in the destination will be different from their original form in the source.
Giphy-
Sticker-
Loop components-××
News-××
Places-××
Stocks-××
Weather-××
Wikipedia search-××
Praise-××
YouTube-××
Voice message-××
Reply-
Edit post/Reply-Partially SupportedPartially SupportedIf 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-Partially SupportedPartially SupportedTo migrate reactions, ensure you have configured user mappings to map source users to destination existing users.
Pin-××
Copy linkConversation linkSource link will be kept at the destination.
Copy linkCopy tab linkPartially SupportedPartially SupportedSource link will be kept at the destination.
Copy linkCurrent Team’s task linkPartially SupportedPartially SupportedSource link will be kept at the destination.
Copy linkCurrent Team linkPartially SupportedPartially SupportedSource link will be kept at the destination.
Copy linkCurrent Team’s channel linkPartially SupportedPartially SupportedSource link will be kept at the destination.
Copy linkCurrent Team’s folder linkPartially SupportedPartially SupportedSource link will be kept at the destination.
Copy linkFile linkPartially SupportedPartially SupportedFiles from another Team or OneDrive, URL mapping is required when run Replace attachment URLs job, otherwise destination files URL will show source files URL.
Copy linkLink containing other channel IDPartially SupportedPartially SupportedThese links will show as source URL in the destination after migration.
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××

Channel

Object TypeSource App Profile Support StatusSource Service Account Authentication Support StatusComment
Get email address-××
Show for me-××
Show for members-××
Email Message in Channel-××
Privacy-××
Name-
Description-
Channel settings-××

Privacy

Object TypeSource App Profile Support StatusSource Service Account Authentication Support Status
Public
Private
Archived Team
org-wide

Members

Object TypeSource App Profile Support StatusSource Service Account Authentication Support StatusComment
MemberThe owner will be Space Manager in the destination.
OwnerThe owner will be Space Manager in the destination.
Update rolePartially SupportedPartially Supported1. The owner will be Space Manager in the destination. 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 TypeSource App Profile Support StatusSource Service Account Authentication Support Status
Dynamic user××
Assigned××

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 recorded video clip cannot be migrated.
Forwarded messagePartially SupportedPartially SupportedOnly the titles, subjects, and attachments (if any) of forwarded messages can be kept.
Post messages
Add a tab××
Standard channel
Private channel
Shared channel1. The Teams added as members of shared channels cannot be migrated. 2. Shared channels can only be loaded in channel mappings and migrated if they were created by your own Teams.
Chat××
Analytics××
Connectors/Workflows××
Apps××
Bookings××
Calendar××
Meeting RecordsMeeting recordings will be migrated to the Recordings folder in the destination channel folder.
Meeting Transcript××
Pending Requests××
Settings××
Tags××
Shifts××

Microsoft 365 Group

Object TypeSource App Profile Support StatusSource Service Account Authentication Support Status
Microsoft 365 Group××

Microsoft 365 Group Mailbox

Object TypeSource App Profile Support StatusSource Service Account Authentication Support Status
Microsoft 365 Group Mailbox

Team Site

Object TypeSource App Profile Support StatusSource Service Account Authentication Support StatusComment
File
SiteSites will be migrated to destination as Shared Drive. Refer to Migration to Google Drive for support details.