将您的 Google Workspace 组织迁移到 Google Chat
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
本页面简要介绍了可帮助 Google Workspace 组织从其他即时通讯平台迁移到 Google Chat 的 Google Chat 应用。
作为 Google Workspace 管理员,您可以创建一个 Chat 应用,用于从其他即时通讯平台导入即时通讯数据。为了导入数据,Chat 应用会根据贵组织中现有的消息、附件、回应、成员资格和聊天室创建 Chat API 资源。
为什么在迁移到 Chat 时导入数据
将数据导入 Chat 可为贵组织中的用户提供更好的体验,因为他们可以保留自己所用现有即时通讯平台中的历史记录和上下文。与将源数据复制到常规聊天室相比,使用导入模式聊天室具有以下优势:
- 保留资源创建时间戳。您可以为聊天室和消息资源的创建时间设置历史时间,让 Chat 应用在用户采用 Google Chat 期间保留历史上下文。如需了解详情,请参阅将即时通讯数据导入 Google Chat。
- 最终用户无法在导入模式下查看或访问聊天室。为防止用户干扰正在导入数据的工作区,或避免用户因查看正在进行的数据导入而感到困惑,系统会向最终用户隐藏处于导入模式的工作区。聊天室完成导入模式后,您就可以向聊天室中添加用户了。
- Chat 会在导入模式下关闭通知,以免用户收到有关迁移的不必要提醒。
您可以创建的 Google Chat API 资源,用于导入即时通讯数据
如需导入即时通讯数据,您可以根据其他即时通讯平台中的数据创建 Chat API 资源。您可以在导入模式 Chat 聊天室中创建这些资源。您只能在导入过程中使用导入模式聊天室。
您可以在导入模式聊天室中创建以下 Chat API 资源:
将来源数据映射到 Google Chat 资源
将数据从源通讯平台导入 Google Chat 时,请查看您可以在 Chat 中创建的受支持资源。然后,确定要导入的来源实体,并将每个实体映射到一个 Chat 资源。规划资源映射后,从来源消息传递平台读取实体,并将其写入导入模式聊天室。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2024-12-03。
[null,null,["最后更新时间 (UTC):2024-12-03。"],[[["\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,["# Migrate your Google Workspace organization to Google Chat\n\nThis 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--------------------------------------\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----------------------------------------------------------------------\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----------------------------------------\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\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)."]]