General Info

How Cloudiway Uses Google Import APIs

Understanding how Cloudiway leverages Google Import APIs to optimize throughput and preserve metadata when migrating to Google Spaces.

Overview

Cloudiway utilizes Google Import APIs to significantly enhance migration performance when migrating to Google Spaces. This specialized API enables high-throughput message transfer while preserving critical metadata such as original timestamps and sender information.

Import API Benefits

High Performance

Thousands of messages per hour

Metadata Preserved

Original dates & creators

Delta Pass Support

Incremental updates

Migration Mode Requirement

The Import API only works with Google Spaces created in Migration Mode. Spaces created through Cloudiway preprocessing automatically use this mode.

Migration Process Overview

The migration process follows a specific sequence to maximize performance and ensure data integrity:

1
Create Google Space in Migration Mode
2
Create Channel in Migration Mode
3
Import Messages via Import API
4
Complete Space and Channel Migration
5
Add Team Members

Step 1: Create Google Space in Migration Mode

The first step is creating the Google Space in Migration Mode. This special mode is required for the Import API to function and must be enabled programmatically.

Important: Space Visibility

As long as the Space is in Migration Mode, it is invisible to users. Users cannot see or access the space until migration is completed.

Spaces Created by Cloudiway

Automatically use Migration Mode during preprocessing. No additional configuration required.

Existing Spaces

If migrating to an existing space not in Migration Mode, Cloudiway automatically reverts to standard APIs.

Step 2: Create Channel in Migration Mode

Channels must be created programmatically within a space that is already in Migration Mode. Cloudiway handles this process automatically when the prerequisites are met.

Automatic Channel Creation

Cloudiway's preprocessing phase automatically creates channels in Migration Mode when the parent space is properly configured.

Step 3: Import Messages

When both the space and channel are in Migration Mode, running the migration automatically uses the Import API. This provides significant advantages over standard APIs:

Import API Advantages

Performance Enhancement

Migrate thousands of messages per hour, compared to standard API rate limitations

Metadata Preservation

Original creator information and timestamps are maintained in the migrated messages

Automatic Message Ordering

Messages are automatically sequenced correctly by Google based on their original dates

Step 4: Complete Space and Channel Migration

Delta passes allow new messages and replies to migrate while the space remains in import mode. To finalize the migration and make the space visible to users, you must execute the Post Migration Job.

Trade-off After Closing

Once the space is closed (no longer in Migration Mode), any subsequent migrations will use standard APIs. This means metadata will be injected into message bodies rather than preserved in native fields.

Step 5: Add Team Members

Membership migration occurs only after the space has been closed. Members cannot be added while the space is still in Migration Mode.

Membership Migration Timing

Plan your migration timeline accordingly - users won't have access until membership migration completes after the Post Migration Job.

Post Migration Job

The Post Migration Job is a critical step that finalizes the migration process. It performs three essential actions:

  1. 1
    Runs a Final Delta Pass

    Captures any messages sent during the migration period to ensure no data is lost.

  2. 2
    Closes the Google Space

    Exits Migration Mode and makes the space visible to users. Import API can no longer be used after this step.

  3. 3
    Migrates Membership

    Adds all team members to the space, granting them access to the migrated content.

Irreversible Action

The Post Migration Job cannot be undone. Once the space is closed, you cannot return it to Migration Mode. Ensure all content has been migrated before running this job.

Import API vs Standard API Comparison

Feature Import API Standard API
Throughput Thousands/hour Rate limited
Original Timestamps Preserved In message body
Original Sender Preserved In message body
Space Visibility Hidden until closed Visible immediately
Requirement Migration Mode None

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