This page provides an overview about Google Chat apps that help Google Workspace organizations migrate to Google Chat from other messaging platforms.
As a Google Workspace administrator, you can create a Chat app that imports messaging data from other messaging platforms. To import data, the Chat app creates Chat API resources based on existing messages, attachments, reactions, memberships, and spaces in your organization.
Why import data when migrating to Chat
Importing data to Chat provides a better experience for users in your organization because they can preserve history and context from existing messaging platforms that they use. In comparison to copying source data into regular spaces, the use of import mode spaces have the following advantages:
- Preservation of resource creation timestamps. You can set a historical time for the creation times of space and message resources, letting Chat apps retain historical context during user adoption of Google Chat. For more information, see Import messaging data to Google Chat.
- End users can't view or access spaces in import mode. To prevent user interference of a space undergoing data import, or to avoid possible user confusion as a result of viewing an in-progress data import, spaces in import mode are hidden from end users. After a space has completed import mode, you can add users to the space.
- Chat turns off notifications during import mode, so that users can avoid unnecessary alerts about the migration.
Google Chat API resources that you can create to import messaging data
To import messaging data, you create Chat API resources based on data from another messaging platform. You create these resources in import mode Chat spaces. You can only use import mode spaces during the import process.
You can create the following Chat API resources in import mode spaces:
- Messages
- Attachments
with the following considerations:
- Attachments can be uploaded to import mode spaces with Google Chat API, however we highly recommend using Google Drive API to upload files and link the file URIs to the respective messages in the import mode spaces instead to avoid hitting Google Chat internal limit for attachment upload.
- Reactions
Memberships with the following considerations:
- Historical memberships must be imported when a space is in import mode. You can't import historical memberships after the space completes import mode.
- Other existing memberships from the source messaging platform must be created after a space completes import mode.
- Members must be users within the same domain.
Spaces. Only
SpaceType.SPACE
is supported.SpaceType.GROUP_CHAT
is supported for members of the Developer Preview program.
Map source data to Google Chat resources
When importing data from source messaging platforms into Google Chat, review the supported resources that you can create in Chat. Then, determine the source entities that you want to import and map each one to a Chat resource. After you've planned the resource mappings, read the entities from the source messaging platform, and write them into import mode spaces.
Related topics
- To learn how to authenticate with Chat API when using import mode spaces, see Authorize Google Chat apps.
- To learn how to start importing resources using import mode spaces, see Import messaging data to Google Chat.