Google Workspace Domain-Switch Migrations

Google Workspace domain-switch migrations can be performed in the same way as other Google Workspace migrations, however, if the source domain name is being migrated to the destination this adds an additional layer of complexity relating to the domain name registration and CloudM Migrate licensing. This guide explains how to perform such migrations without running into issues. It is very important to plan ahead to minimise downtime during this process, so we recommend this guide is reviewed thoroughly and all steps planned well in advance of a switch-over.

If the domain name is changing from source to destination?

If the source domain name(s) are not being migrated, then the migration can be configured and performed without any extra steps, as per this guide.

If the domain name itself is migrating?

Google Workspace domain-switch migrations that are keeping the same domain name differ because Google does not allow a domain to be associated with two instances at the same time. This means an initial migration must be performed to users with a temporary domain, then the domain must be deleted at the source and added to the destination before a delta migration is performed.

  1. Configure CloudM Migrate to migrate from your source domain to a temporary destination domain
  2. Migrate all historic email and Google Drive data
    • Consider also migrating historic calendar data before the following, see below*
  3. Change the primary domain at the source*
  4. Rename all the migrating source users to a temporary or secondary domain
  5. Remove all aliases associated with the domain. This is best done using GAM*
  6. Remove the migrating domain from the source
  7. Add the domain to the destination instance as a secondary or alias domain (depending on your needs)
  8. Rename your migrating destination users or add email aliases
  9. Update your CloudM Migrate config to migrate from the new primary domain to the temporary destination domain
    • Source domain and admin might need to be changed
    • Destination domain name and admin can remain the same
    • Your items list will need to reflect the changes above
    • Your domain replacement values will need to be updated
    • Your address replacements (if applicable), also
  10. Run the delta migration (mail, contacts, calendars, tasks, Drive and chats/Spaces)
  11. Upon completion, the source Google Workspace can be deleted, however, we recommend that you allow approximately a 1 month grace period before doing so. For example: in case additional migrations are required.
  12. You may wish to also delete the destination temporary domain (used solely for the migration) 

*Please see the following Google article which outlines the prerequisites for changing your primary domain. If the migrating domain is the primary domain, it cannot be removed and must be changed to a secondary domain to do so.

*GAM is a third party software which can be utilized to perform numerous tasks in Google in bulk. It is not supported by CloudM.

Google Secondary/Shared Calendars

It's important to note what is outlined in this this article. In Google to Google domain-switch migrations calendars should be migrated before the source domain is deleted because this action will result in users' secondary/shared calendars being deleted, also.


CloudM Migrate licenses are assigned to each destination domain. This means that when performing the delta migration, after renaming the accounts, it will require another CloudM Migrate license. If you are running such a migration, you should contact us through your account manager or via and we will be able to provide additional licenses to mitigate this at no extra cost. See the How is CloudM Migrate licensed? article for more information.

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