Migrating from and to Google Cloud Storage

Permanently deleted user

Updated November 14, 2023 20:43

Currently, only owned items will be migrated.

Google Cloud Storage supports every source platform and every item type for storage.

Please note that, although we can migrate from an Archived Google user as a source platform (export object), we cannot migrate into an Archived Google as a destination platform (import object).

This is due to a Google Workspace limitation.

When migrating from Google Cloud Storage, currently, you can only use CloudM Migrate to data that was previously created using CloudM Migrate or CloudM Archive. You cannot migrate data manually uploaded to a GCS bucket at this time.

General and Source Platform prerequisites

Setting up a service account and Google APIs

Please refer to the Setting up the Service Account and enable the APIs within Google Workspace for CloudM Migrate article.

Destination Platform prerequisites

You will also need to:

Create a bucket - Open the Google Cloud Platform, navigate to Storage > Browser and create a bucket for the items to be migrated to. Make a note of the bucket name you'd like to migrate data into.
Back in the storage browser, click on the three dots on the right of the bucket you made and select Edit bucket permissions,
Click Add member and in the New members field, paste the service account email address that you made earlier,
Click Select a role and add Storage Object admin permissions.
Set encryption and decryption permissions to the KMS key (if required) - If a KMS key is required for encryption, permissions need to be given to the Cloud Storage Service account. To do this:
- Open the Google Cloud Platform,
- Navigate to Storage
- Select Settings
- Copy Service Account under Cloud Storage Service Account
- Navigate to Security > Cryptographic Keys
- Check the key ring you are going to use
- Click add member under permissions tab on the right side
- Paste the service account email in the new members text box.
- Select Cloud KMS -> Cloud KMS CryptoKey Encrypter/Decrypter role and save.

For more information on KMS keys, please refer to the Using customer-managed encryption keys article on the Google Cloud help site.

Configure Source Platform settings

Google Cloud Storage

Account Details

Domain Name – The name of the Google domain to migrate from. This may be either a primary or secondary domain. Note: you can only migrate users to one domain at a time. If you have both primary and secondary domain users, they must be processed in separate migrations.
Authentication Method - Set whether to use a P12 key or a JSON key as the authentication method.
Service Account Email Address - Before attempting to configure CloudM Migrate, you should have created a Google Cloud platform project and created a service account for it. If you have selected to use a P12 key, you will need to input the service account's email address in this field.
Private Key - The file path to the P12 or JSON key that was generated and downloaded when creating the OAuth service account.

Google Cloud Storage Details

Bucket Name - The name of the bucket that has been created in the Google Cloud Platform, under Storage > Browser.

Google Cloud Storage Options

List Objects Page Size - The maximum number of results to return for individual queries to the Storage API.

Decryption Options

Decryption Key File Path - The location of your decryption key file.

Configure Destination Platform settings

Google Cloud Storage

Account Details

Domain Name – The name of the Google domain to migrate to. This may be either a primary or secondary domain. Note: you can only migrate users to one domain at a time. If you have both primary and secondary domain users, they must be processed in separate migrations.
Authentication Method - Set whether to use a P12 key or a JSON key as the authentication method.
Service Account Email Address - Before attempting to configure CloudM Migrate, you should have created a Google Cloud platform project and created a service account for it. If you have selected to use a P12 key, you will need to input the service account's email address in this field.
Private Key - The file path to the P12 or JSON key that was generated and downloaded when creating the OAuth service account.

Google Cloud Storage Details

Bucket Name - The name of the bucket that has been created in the Google Cloud Platform, under Storage > Browser.

Google Cloud Storage Options

Max File Size - The maximum size of the files to be uploaded (in bytes).
Cache Existing Object Details - Cache details of existing objects in the destination. Setting to True (checked) will decrease the number of HTTP requests made per item at the expense of increased disk usage.
Compress Objects - Compress the objects before they are uploaded. Setting to True will use less cloud storage space at the expense of slowing down the import.

Encryption Options

Please note that only one encryption method is required - either KMS or Encryption Key File.

KMS Key Full Name - The full name of the Google Cloud key management service key. The service account must have the Encrypter / Decrypter role on the key. Please note that the service account referred to here is Cloud Storage service account and not the service account for migration.
Encryption Key File Path - The location of your encryption key file. The key file is a text file containing a 32 bytes base64 string.

For more information on KMS keys, please refer to the Using customer-managed encryption keys article on the Google Cloud help site.

Select which users to migrate

It's now time to add which users you'd like to migrate.

When migrating, you may be able to Get Users from the actions menu. If this option is unavailable, you can manually import users via a CSV file or simply add them individually via the plus icon.

Selecting a star next to any specific user or users will prioritize their migration. When a migration starts, threads will be assigned to any starred user so that their migration can start immediately.

At this point you can choose what to migrate for each user, you can migrate mail , contacts and calendars.

Enter your user's full email address within the Export Name field. If you have already created your Microsoft 365 users then you will just need to enter their username.

Select how much mail to migrate

CloudM Migrate lets you decide how much mail you'd like to migrate to your shiny new system.

If you are changing your email address as part of the migration you can verify that the domain names are correct here. You can also specify specific address replacements in the respective section of the advanced settings.

For more information on domain and address replacements, see this page.

Start your migration

We know that you may want to start your migration in the middle of the night, or over the weekend, but we don't expect you to stay up in order to do so. With CloudM Migrate, you can decide to schedule exactly when you'd like the migration to occur.

Start the migration.

Review your migration results

During the migration process, CloudM Migrate will report back in real time exactly who is being migrated and the items being processed. All you now need to do is sit back, relax and wait for your migration to complete.

Check the progress of your migration.

Once complete you can download a full report for your migration.