This article provides instructions on configuring a migration batch for migrating users from Google Cloud Storage (GCS) to Google Workspace. The setup process outlined here focuses on migrating Mail, Contacts, Calendars, Tasks, Documents and Conversations.
Before proceeding, ensure you have completed the steps in the Migration Guide to set up your migration project and added users to your migration batch.
Watchpoints
You can only migrate data which was previously uploaded to GCS buckets using CloudM Migrate or CloudM Archive.
You cannot migrate data which was manually uploaded to a GCS bucket.
1. Adding Items to Migrate
When preparing to migrate users to corresponding accounts at the destination, follow the format below:
- *Export Type: User
- *Export Name: Source primary email address
- *Import Type: User
- *Import Name: Destination primary email address
- Given Name: User's first name at the destination (leave blank if the user already exists at the destination)
- Family Name: User's surname at the destination (leave blank if the user already exists at the destination)
- Documents Path: Not required
- Documents Destination Path: Path of the folder to migrate to at the destination (optional; leave blank if migrating to the root of the destination user's MyDrive)
*Mandatory Field
Further instructions on adding entities to your batch can be found here: Adding Items to a migration batch
For each entity added, you can select the specific data types you wish to migrate. Ensure the 'Migrate' checkbox is enabled for all entities you intend to include in the migration run.
2. Configuration Settings
General Settings
In the General Settings section, ensure all domain mappings are configured correctly to facilitate replacing the source domain with the destination domain during the migration.
You can also apply date range filters for various data types to migrate information within a specific timeframe. Specify the date ranges you wish to include.
Source Settings
For a standard user migration, It is generally recommended to leave the destination settings at their default values.
Depending on your specific migration scenario, you may need to adjust additional settings. The article below provides a detailed overview of all available source settings for Google Cloud Storage:
Google Cloud Storage - Source Settings
Decryption key file path (.gkey): If you encrypt your data using a Customer Supplied Key, this is a required setting.
Destination Settings
For a standard user migration, It is generally recommended to leave the destination settings at their default values.
Depending on your specific migration scenario, you may need to adjust additional settings. The article below provides a detailed overview of all available destination settings for Google Workspace:
Google Workspace - Destination Settings
Advanced Settings
For a straightforward user-to-user migration, most advanced settings can remain at their default values. However, consider the following:
- Address Replacement: It is highly recommended to upload an address replacement CSV that maps source users to their corresponding destination users. This ensures permissions are correctly migrated. For more information, please refer to the Address Replacements article.
Additional settings are outlined here: Advanced Settings
3. The Migration Process
For a complete, in-depth guide that covers project planning, user communication, and detailed pre- and post-migration checklists, please review our comprehensive recommended strategy article: