將 Google Workspace 機構遷移至 Google Chat
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
本頁面將概略說明 Google Chat 應用程式,協助 Google Workspace 機構從其他訊息平台遷移至 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 資源。規劃資源對應後,請從來源訊息平台讀取實體,並將實體寫入匯入模式空間。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2024-12-03 (世界標準時間)。
[null,null,["上次更新時間: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)."]]