Data Import from CloudM Migrate
While standard archiving occurs via CloudM Automate offboarding workflows, you may need to carry out a bulk migration of legacy user data or move data from other storage providers to Google Cloud Storage. CloudM Migrate facilitates this bulk movement, while the Archive interface allows you to import that data for indexed restoration later.
💡 Strategic Workflow Positioning & ROI:
The standard CloudM Automate offboarding workflow is a "one-by-one" engine optimized for Business As Usual (BAU) lifecycle events. However, the Data Import path is the required solution for large-scale projects requiring hundreds or thousands of users to be archived immediately or ASAP.
This is particularly critical for organizations approaching a Google Workspace Renewal. By utilizing the bulk migration path to offboard and archive users at scale before the renewal date, organizations can significantly reduce their license seat count and achieve immediate cost savings.
Licensing & Preparation
Licensing: Bulk migrations require CloudM Migrate licenses. To acquire these for your project, please contact your CloudM Account Manager or the Sales team.
Recommendation: Before attempting an import in CloudM Automate, you must first complete the migration to the storage bucket(s). Follow the technical requirements found in the CloudM Migrate Guide: Migrating to Google Cloud Storage.
Step 1: Migrate data to the Storage Bucket
Using CloudM Migrate, perform your bulk migration from the source environment into your target Google Cloud Storage bucket. Ensure the data is successfully landed and the bucket permissions are correctly configured to allow CloudM Automate access.
Step 2: Configure the Storage Bucket in CloudM Archive
- In CloudM Automate, navigate to Archive > Storage Configuration.
- Select the + Add configuration button.
- Enter the settings for the existing bucket that contains your bulk-migrated data.
- Set Retention Policies (or select Indefinite to prevent automated purging).
- Select Test Connection. ⚠️ If credentials do not match the bucket name, you must rectify the error before proceeding.
- Select Save.
Step 3: Populate the User Table
- Navigate to Archive > Data Import from CloudM Migrate.
- Select the required bucket from the tabbed list at the top of the screen.
- Select Re-Populate User Table to fetch the list of migrated users from the bucket metadata.
⚠️ Technical Note: You cannot initiate other tasks while the user table is being populated. Multiple buckets will appear as tabs; the active bucket is displayed in bold and underlined.
Step 4: Execution (Import All vs. Selected)
| Method | Instructions |
|---|---|
| Import All | Select Import All > Yes. This process is resource-intensive and prevents re-populating the user table while running. |
| Import Selected | Check the box next to specific email addresses and select Import Selected. Note: Users already in the queue or successfully imported cannot be re-selected. |
Monitoring Progress
Use the View Imports or Import History buttons to track the following statuses:
- Not Imported: In the queue.
- Preparing: Identifying data for import.
- Importing: Actively moving into Archive.
- Completed/Failed: Final states. Failed users will display a Retry button.
⚠️ Technical Restriction: You cannot import users from an external domain into Archive. Once an import is finished, users will be visible in Archive > Restoration.