Migrate your Google Workspace organization to Google Chat
Stay organized with collections
Save and categorize content based on your preferences.
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:
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.
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 and SpaceType.GROUP_CHAT are supported.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eGoogle Chat apps can import messaging data (messages, attachments, reactions, memberships, spaces) from other platforms to Google Chat for Google Workspace users.\u003c/p\u003e\n"],["\u003cp\u003eImporting data preserves historical context and provides a better user experience during migration.\u003c/p\u003e\n"],["\u003cp\u003eImport mode spaces are used for data import and are hidden from end-users until the import is complete to prevent interference.\u003c/p\u003e\n"],["\u003cp\u003eChat apps have 90 days to import data into an import mode space before it's automatically deleted.\u003c/p\u003e\n"],["\u003cp\u003eGoogle recommends using Google Drive API for uploading attachments during import to avoid hitting Google Chat's internal limits.\u003c/p\u003e\n"]]],["Google Workspace administrators can create Chat apps to import data from other messaging platforms into Google Chat. These apps create Chat API resources like messages, attachments, reactions, memberships, and spaces within import mode spaces. This preserves historical context and user experience, hiding spaces during the import process and disabling notifications. Admins map data from the source platform to Chat resources and must complete the import within 90 days; otherwise, spaces are deleted. It is recommended to use the Google Drive API to handle attachment upload.\n"],null,["This page provides an overview about Google Chat apps that help\nGoogle Workspace organizations migrate to Google Chat from other\nmessaging platforms.\n\nAs a Google Workspace administrator, you can create a\nChat app that imports messaging data from\nother messaging platforms. To import data, the Chat app\ncreates [Chat API resources](/workspace/chat/api/reference/rest)\nbased on existing messages, attachments, reactions, memberships,\nand spaces in your organization.\n\nWhy import data when migrating to Chat\n\nImporting data to Chat provides a better experience for users\nin your organization because they can preserve history and context from\nexisting messaging platforms that they use. In comparison to copying source data\ninto regular spaces, the use of import mode spaces have the following\nadvantages:\n\n- 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](/workspace/chat/import-data).\n- 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.\n- Chat turns off notifications during import mode, so that users can avoid unnecessary alerts about the migration.\n\nGoogle Chat API resources that you can create to import messaging data\n\nTo import messaging data, you create Chat API resources based on data\nfrom another messaging platform. You create these resources in *import mode*\nChat spaces. You can only use import mode spaces during the\nimport process.\n| **Warning:** After you've created an import mode\n| space, Chat apps have 90 days to complete the import of data for\n| a space. After 90 days, if the space is still in import mode, it's automatically\n| deleted and will be inaccessible and unrecoverable.\n\nYou can create the following Chat API resources in import mode spaces:\n\n- [Messages](/workspace/chat/api/reference/rest/v1/spaces.messages)\n- [Attachments](/workspace/chat/api/reference/rest/v1/spaces.messages.attachments) with the following considerations:\n - Attachments can be uploaded to import mode spaces with Google Chat API, **however we highly recommend using\n [Google Drive API](https://developers.google.com/drive/api/reference/rest/v3)\n to upload files and link the file URIs to the respective messages in\n the import mode spaces instead to avoid hitting Google Chat internal\n limit for attachment upload.**\n- [Reactions](/workspace/chat/api/reference/rest/v1/spaces.messages.reactions)\n- [Memberships](/workspace/chat/api/reference/rest/v1/spaces.members)\n with the following considerations:\n\n - [Historical memberships](/workspace/chat/import-data#historical_memberships) must be imported when a space is in import mode. You can't import historical memberships after the space completes import mode.\n - Other existing memberships from the source messaging platform must be created after a space completes import mode.\n - Members must be users within the same domain.\n- [Spaces](/workspace/chat/api/reference/rest/v1/spaces).\n Only `SpaceType.SPACE` and `SpaceType.GROUP_CHAT` are supported.\n\nMap source data to Google Chat resources\n\nWhen importing data from source messaging platforms into Google Chat, review\nthe supported resources that you can create in\nChat. Then, determine the source entities that you want to import\nand map each one to a Chat resource. After you've planned the\nresource mappings, read the entities from the source messaging platform, and\nwrite them into import mode spaces.\n\nRelated topics\n\n- To learn how to authenticate with Chat API when using import mode spaces, see [Authorize Google Chat apps](/workspace/chat/authorize-import).\n- To learn how to start importing resources using import mode spaces, see [Import messaging data to Google Chat](/workspace/chat/import-data)."]]