Dropbox to Google Workspace

Dropbox to Google Workspace


Before starting your migration project, set up the Dropbox and the Google Workspace configurations using the configuration guides. Ensure that both tenants have passed their connectivity tests with no errors.

The destination for the Dropbox user or Team Folder can be a personal Google Drive or Shared Drive.

Standard Pre-stage Migration

There are multiple approaches available to migrating data with CloudM Migrate. The following approach will prestage data older than 30 days as a batch. This will be followed by a Delta Sync to migrate recent data after your DNS cutover for a complete lossless migration.

This approach eliminates user confusion from recent items being moved as they are created and categorized during normal business. The result will be a more accurate account of recent changes on the destination and less user support.

CloudM Migrate doesn't duplicate emails or documents. Once a document is migrated, it is not moved again or updated on the destination even if it has changed on the source. Documents are not duplicated but may be overwritten in delta migrations.

Adding Users

Back to Top

On Step 3 on the left, select Add items to migrate for options on how to collect targeted items to migrate from Google. The following options will be available:

  • Get items from source - This is fetch where CloudM Migrate will attempt to list all supported items within scope.
  • Bulk add/import items - Provide CloudM Migrate a CSV of targeted items.
  • Add User - Add a specific user to the project.

Scanning the Source

It's recommended to perform a scan against your Dropbox source environment to proactively look for problems. While in CloudM Migrate select Step 5 on the left and then select Start. Depending on the size of the environment this can take some time to complete. When complete select Export Scan Results to download a zip of the scan results.

The important files to check are the FileScanReport.html and MailScanReport.html. Users that have items errors are highlighted in red. Important errors to look for are:

  • Dead User Objects. Files owned by non-existent accounts.
  • External File Shares. Items CloudM Migrate cannot migrate as they are external to the environment.

Domain and Address Replacements

Note: Domains should always be mapped, but address replacements are optional and usually only need to be provided when you have specialist requirements. CloudM Migrate maps usernames and email addresses automatically if they have been configured in the user list however if you need to map unlisted users you can add them to the Address Replacements File.

There are a number of options which control how replacements are performed. It is important to understand how these applied, in which order and under which conditions. It is possible to end up with incorrect email addresses if the options are not fully understood.

Replace Usernames – Replace any re-mapped usernames from the users tab, when migrating the items specified in Domain Replacement Types in Common settings. If this option is disabled and replacements are required, explicit mappings for email addresses and domain names should be provided via the other settings in this section. Only addresses that belong to source domains are automatically mapped.

Address Domain Replacements - If migrating from one domain name to another, specify the domain names that should be replaced and the value with which they should be replaced with. For example, when migrating from example.com to domain.com, you should provide example.com and domain.com in this setting. If migrating from one Google Workspace domain to another, domain replacements are performed automatically unless Replace CSV Addresses Only is selected and you have not provided the domain mappings within the file.

Address Replacements (File) – Use this option to provide an explicit list of email addresses to be mapped as part of a migration. If performing domain consolidation or if you have other specialized requirements then this option can be used to map any source email address to any other address. Addresses should be mapped using a simple CSV file containing two columns, the first for the address to be replaced and the second the replacement address.


CloudM Migrate allows you to create a batch from your master user list, in a separate configuration. This enables you to quickly segment your user list and streamlines your migration process by running batches of users.

  1. Select the users you want in your migration batch.
  2. From the menu, select Create Batch.
  3. Name your Child Configuration.
  4. Select your configuration type.
  • Disable Migration Items - Use this if you want to modify the migration items for a subset of your users. e,g. Do not migrate Drive.
  • Delete Migration Items - Use this if you want to create a subset of users to migrate. e.g. a VIP group of users.
  1. Select Create to create the batch, or Create and Edit or create the batch, and be taken to the edit screen for that batch. Batches can be modified from the Projects screen, and work in the same way as normal configuration.

Date Ranges

You can filter files based on the selection and date ranges set for Migrate Files From and Migrate Files To settings. The Filter Date Type setting allows you to specify whether the date used is based on the file's created date or the file's last modified date.

Delta Migrations

Delta migrations of files to Google Drive will migrate any new files that were not found as part of the previous migration(s), but will also detect if files have been modified or updated since the last migration.

Files or folders that have been edited, have had permissions changed, have been renamed or otherwise changed will have the destination copy deleted and then the file is re-migrated to the destination with the updated source file.

Execute Migration

When ready to execute, select the Paper Airplane on the left and select Start to begin the migration.

Statistics and Summary

After starting the migration, you'll have the option to view progress and export a summary by selecting Start and then selecting View Progress. Select More Statistics to see a complete summary by item type for your current batch.

To export a report of the migration for record keeping select Projects in the left navigation. Select Item Progress and then select the orange User progress link. By selecting the top and right most orange button a file of item success by user can be downloaded.

Was this article helpful?
0 out of 0 found this helpful