How Cloudiway Uses Google Import APIs

Understanding the technical process behind high-performance Google Spaces migration using Google's Import APIs.

Last updated: 2025-01-15 General Info

Google Import API Migration Process

1️⃣
Create Space
Migration Mode
2️⃣
Create Channel
Migration Mode
3️⃣
Import Messages
High Throughput
4️⃣
Complete
Close Space
5️⃣
Add Members
Finalize

Overview

Cloudiway leverages Google Import APIs to optimize throughput when migrating to Google Spaces. This approach provides significantly better performance than standard APIs and preserves original message metadata including creation dates and creator information.

The migration process consists of five key steps: creating a space in migration mode, establishing channels in migration mode, importing messages, completing the migration, and adding team members.

Migration Mode Prerequisite

Critical Requirement

The Import API can be leveraged only if the Space has been created in Migration Mode. Creating a Space in Migration Mode can only be done programmatically.

Spaces must be created through Cloudiway's platform to access these optimized APIs. If migration targets an existing space not created in migration mode, the system automatically reverts to standard, non-optimized APIs.

Automatic Handling

Cloudiway's preprocessing step automatically creates spaces in import mode. You don't need to manually configure migration mode—it's handled automatically when you start your migration.

Migration Process

Step 1: Create Space in Migration Mode

The preprocessing step automatically creates Google Spaces in import mode. During this phase, spaces are not visible to end users.

Step 2: Create Channel in Migration Mode

Channels are similarly created in import mode when possible, enabling high-throughput message import within the space structure.

Step 3: Import Messages

With spaces and channels in import mode, messages are imported using the optimized Import APIs. This supports thousands of messages per hour with preserved metadata.

Step 4: Complete Migration

Running the Post Migration Job closes the Google Space, making it visible to users and finalizing the migration process.

Step 5: Add Members

Team membership is migrated after the space is closed, allowing users to access their migrated content.

Key Benefits

High Performance

Import thousands of messages per hour, significantly outperforming standard APIs

📅

Preserved Metadata

Original creation dates and creator information are maintained

📊

Correct Order

Messages are automatically reordered chronologically by Google

Delta Passes

During active migration, delta passes allow incremental synchronization of new messages and replies that arrive after the initial migration.

Post-Migration Phase

Once migration is complete, running the Post Migration Job performs several critical steps:

Post Migration Job Actions

  • Executes a final delta pass to capture recent messages
  • Closes the Google Space, making it visible to users
  • Migrates membership to allow user access

API Limitations After Closure

After the space is closed, Import APIs can no longer be used for that space. Subsequent migrations to the same space will use standard APIs, which cannot preserve original timestamps or creator information.

Was this article helpful?

We value your feedback

Help us improve your experience

What would you like to share with us?

Need direct support? Open a ticket