This quick start guide provides you with the basic information to configure CloudM Migrate for a migration to and from Google Vault. It is highly recommended that you read the documentation in full for your platforms in order to understand all of the options available to you during a migration.
CloudM Migrate currently supports email only migrations to/from Google Vault.
The following software should be installed on the migration workstation:
- CloudM Migrate
What else do I need?
- Google Vault is connected to your G Suite account and so please perform the same steps as described for G Suite.
- To enable Google Vault for your domain, please see this article.
Migrating to Vault
If you are already migrating to G Suite, the migration to Google Vault requires an additional separate license
Migrating from Vault
- You will need at least 30GB free disk space on each migration server.
- Additional Google APIs must be enabled using API Manager and Scopes added using the G Suite Admin Console
- Google Vault API, Scopes (https://www.googleapis.com/auth/ediscovery,https://www.googleapis.com/auth/ediscovery.readonly)
- Google Storage API, Scope (https://www.googleapis.com/auth/devstorage.read_write)
- Billing must be enabled for the Google project being used for the migration. This is necessary to avoid very low Google Vault export quota limits. Enabling it allows for higher export quotas, however, with a possible resulting cost. This cost is something your Google account manager should be able to discuss with you.
- Exporting from Google Vault is subject to quota limitations. If you find user migrations are failing with quota errors you should contact Google to have the limits increased.
- Ensure you have setup the G Suite domain and APIs and enabled the extra APIs required by Google Vault.
- Select Google Vault in the source platform selector.
- Enter the Account details into the Google Vault configuration settings for the source, making sure to follow the instructions for each setting in the documentation available here for source and inside CloudM Migrate.
- Enter the Service Account details into the configuration settings. Please click here to see how to set this up.
- Once the Service account is set up to get the Service email go to Credentials > Manage Service Account then 'View Client ID'.
- Copy the Service account (be sure to only copy the email address and not title of project as shown below).
- Enter your license key. Please click Help > Licence Key to apply the licence. Paste in licence key and click Apply.
- Setup your destination platform. Instructions are available for G Suite, Google Vault, Microsoft Exchange or Office 365 and Exchange Online Archives.
- Test the configuration using the configuration test tool, available at ‘Tools->Check Connections’. See this article for more information about the connection test tool. You will also need to complete the settings for the destination platform before running this test. If any problems are encountered with the connection test, please examine the error and make the adjustments to your configuration settings.
- Generate your user list and select the users and items you would like to migrate in the ‘Users/Resources’ tab.
- Start your migration
The Google Vault export process extracts the labels Google stores against each item. In some circumstances these labels may not correspond to what is visible in the Google UI
- Custom labels. The export provides custom labels in lowercase, with spaces converted to hyphens
- Extra labels. The export will also contains Internal/System Google labels