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 your temporary destination domain;
  2. Migrate all historic email and Google Drive data (whatever is applicable)
  3. Rename all the migrated source users to another (sub-domain or temporary domain) 
  4. Change the primary domain at the source*
  5. Delete the original primary domain from the source per this guide
  6. Add the new domain to the destination instance as a secondary domain
  7. Add that domain to all new migrating destination users as aliases
  8. Update your CloudM Migrate config to migrate from the new primary domain to the temporary destination domain
  9. Run the delta migration for email and Google Drive
  10. Rename the users in the destination from the temporary domain to the new domain
  11. Create a new CloudM MIgrate project/configuration to then migrate contacts, calendars/resources and tasks (if applicable)
  12. Change the primary domain on the destination
  13. Finally, you may need to perform a cleanup by removing the temporary destination domain/associated aliases. 

*Changing the primary domain is not available for: 

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 sales@cloudm.io 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?
2 out of 2 found this helpful