Home > Google Chat Migration
Download this articleGoogle Chat Migration
Google Chat Migration supports migrating to the following tenants:
- Microsoft 365 Commercial tenant
- Microsoft Education Environment
- Microsoft 365 Government GCC High tenant
- Microsoft 365 Government GCC tenant
- 21Vianet tenant
Refer to the table below to view the supported and unsupported object types for Google Chat migration.
The object types that are not listed in the table below are not supported.
√ -- Supported; × -- Unsupported.
Chat Type
| Object Type | Support Status | Comment |
|---|---|---|
| Direct Messages | Partially Supported | Refer to comments 1-3 below the table. |
| Spaces | √ | Spaces will be migrated as group chats in the destination. |
Comment 1: Direct messages will be migrated as group chats in the destination.
Comment 2: In one-to-one chats, if only one user post messages, the chat name in the destination will be displayed as Just me.
Comment 3: Chats where the source user chats with app only cannot be migrated.
Chat Settings
| Object Type | Sub Type | Support Status | Comment |
|---|---|---|---|
| Space Name | - | √ | Space name will be migrated as group chat name in the destination. |
| Mark as unread | - | × | |
| Pin | - | × | |
| Mute | - | × | |
| Turn on/off history | - | × | |
| Apps & Integrations | Apps | × | |
| Apps & Integrations | Webhooks | × | |
| Chat Members | Google User | √ | The mapped user of the source workspace user will be updated to the destination chat member after the migration. |
| Chat Members | Google Group | × | |
| Chat Members | External User | √ | To migrate external users to destination chat members, configure user mappings for the external users using their user ID. |
Conversation
| Object Type | Sub Type | Support Status | Comment |
|---|---|---|---|
| Format | Bold | √ | |
| Format | Italic | √ | |
| Format | Underline | × | |
| Format | Text Color | × | |
| Format | Strikethrough | √ | |
| Format | Link | √ | |
| Format | Bulleted List | √ | |
| Format | @user | √ | |
| Format | @space | Partially Supported | The source space that is mentioned in the conversation is migrated as a text link. The text can only link to the source space. |
| Format | Code | √ | |
| Format | Block quote | Partially Supported | The format of some quote data cannot be kept. |
| Format | Code Block | √ | |
| Send By | - | Partially Supported | The messages will be posted by the consent user of the delegated app. |
| Emoji | - | Partially Supported | 1. Custom emojis cannot be migrated. 2. Some emojis cannot be displayed correctly in the destination. |
| Gif | - | √ | |
| Voice Message | - | √ | |
| Video Message | - | √ | |
| Video Meeting | - | × | |
| Calendar Event | - | × | |
| Tasks | - | × | |
| Edit Message/Edit Reply/Edit Quote in Reply Message | - | √ | If you edit a 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. |
| Emails Message | - | × | |
| Huddle Message | - | √ | The destination message will be displayed as a link redirected to the source message. |
| Meet link Message | - | √ | The destination message will be displayed as a link redirected to the source message. |
| Call Message | - | √ | The destination message will be displayed as a link redirected to the source message. |
| Deleted Message | - | × | |
| App Message | - | Partially Supported | Only texts in the app messages can be migrated. |
| Link | Message link | Partially Supported | The message link can be replaced with the destination URL only if the linked message exists in the same chat and has been migrated. |
| Link | Drive file link | √ | Will be replaced with the destination URL. |
| Link | Copy link to the space | Partially Supported | The source space link in the conversation is migrated as a text link. The text can only link to the source space. |
| Reply in thread/Quote in Reply | - | Partially Supported | Refer to the comments 1-3 below the table. |
| Forwarded message | - | Partially Supported | If a forwarded message contains an attachment, the attachment format can only be kept when it is a file or image. |
| Reaction | - | × | |
| Star | - | × | |
| Mark as Unread | - | × | |
| See message views | - | × | |
| Following | - | × | |
| Pin to board | - | × |
Comment 1: After a message is migrated to the destination, if there are new replies sent to the source message, the incremental migration job will only migrate the new replies, and you can click original message with the preview content in the destination to jump to the original message.
Comment 2: If an original message cannot be found in the source, its replies can be migrated. Fly will display a The message was unable to be retrieved from Google Chat. indication above its reply in the destination.
Comment 3: In incremental migration jobs, the newly added or modified source messages will be listed in the bottom of the destination HTML file after they are migrated to the destination.
Files
Files will be migrated to the destination Microsoft Teams Chat Files folder.
The migrated file name in the destination will contain the source file ID.
No matter what permissions source chat users have on the chat file, after the migration, they only have the view permission on the file.
If a chat file is shared with users who are not chat members, their permissions on the file cannot be migrated.
| Object Type | Support Status | Comment |
|---|---|---|
| Attach and create Drive files | Partially Supported | Refer to the comments 1-4 below the table. |
| Attach Drive folders | × | |
| Upload files | √ | |
| Picture | √ | |
| Voice Message Recording | √ |
Comment 1: Google Sites, Google My Maps, and files added via third-party services cannot be migrated.
Comment 2: Google Forms exported content larger than 10 MB cannot be migrated due to Google API limitations. For information on Google API limitations that can affect how Fly migrates Google Forms, see here.
Comment 3: Item versions cannot be migrated to the destination.
Comment 4: The data size may be different after the data type is converted in the destination.