Based on our first-hand experience with a bunch of Google Workspace migration projects, we have seen businesses like yours fall in one of the following categories.
- Rebranding. You already have a Google Workspace account in use with all your users, but now because of rebranding, you want to change the domain name. This process is comparatively easy as it does not need data migration.
- Merger / Acquisition. There are 2 entities, both with their own Google Workspace account (with their respective users), and now they need to be merged to become a single account. This one is a bit complex as it includes data migration, deletion of one entity and merging with another.
I will explain to you the process we follow here at Googally for both of the above scenarios. This process has helped us achieve great results for our customers like BioGaia (you may read their migration case study here).
I hope this helps you understand the path forward regardless of whether you work with us or some other Google partner for your project.
Rebranding use case
Let me start with an example case study to help you understand the process better in each case.
Example scenario
- You are a small business that has been using Google Workspace for all of your 50 employees.
- Your primary domain name in Google Workspace is old.com
- You are rebranding and decided to go with the new.com domain.
- Your website will now be new.com instead of old.com (you would have a redirect so visitors are redirected from old.com to new.com website).
- Important. The assumption here is that new.com is not registered or in use with Google Workspace yet.
Desired result with Google Workspace
- All your users should have and use [email protected] instead of [email protected].
- If anyone by mistake sends an email to [email protected], it should not be bounced, but rather should be delivered to the respective [email protected].
- No workspace data should be lost during the rebranding exercise. When users log in to their [email protected], they should find all their data intact including email, calendar, docs etc.
Googally’s migration process (Rebranding)

- Add new.com as a secondary domain under your old.com Google Workspace account.
- Swap the primary domain from old.com to new.com
Note. Changing the primary domain name does not change users’ email addresses in Google Workspace, hence the next step.
- Run the script to quickly change users’ email addresses from [email protected] to [email protected].
When a user’s primary email address is changed in Google Workspace, Google retains the user's old email address as an email alias (or nickname). This is helpful because if someone sends an email to [email protected], this alias email will ensure this email lands in [email protected]’s mailbox.
- Set up Send Mail As to allow [email protected] to be able to send emails as [email protected]. This step is optional based on the customer’s requirements.
Result after following our process
- Your rebranding of the Google Workspace domain is completed successfully without any data loss or downtime.
- Your users now have a new email address ([email protected]) to send and receive emails.
- Emails accidentally sent to [email protected] come to the respective [email protected].
- Optionally, [email protected] can also send as [email protected] if required.
Merger / acquisition scenario
Now, let me explain to you the process we follow for merger / acquisition scenarios. To simplify things a bit, let us keep the same example scenario with a change in situation to represent merger or acquisition.
Example scenario
- You have been using Google Workspace on your company domain new.com for all of your users.
- You acquired a company and their domain name is old.com.
- Your management decided to merge and present them as one entity, instead of running them with their own names (old.com and new.com).
- You would have a website redirect set up sometime so website visitors would be redirected automatically from old.com to new.com.
- The company you acquired (old.com) also uses Google Workspace for all of their employees, and has a bunch of data including emails, calendar, contacts, drive files etc.
- Important. This assumes both old.com and new.com have their own Google Workspace accounts in use.
Desired result in Google Workspace
- You want one single Google Workspace account, and each user should have one primary email address (e.g. [email protected]) to meet business objectives.
- Acquired company’s employees (e.g. [email protected]) should now have [email protected] email address as they are now part of new.com. This way you only pay for a workspace license once per employee.
- No data should be lost during this merger, and [email protected] users should see all of their data (including emails, calendar, contacts, docs) when they log in to their new mailbox ([email protected]).
- You want a setup where all users can send and receive emails in their [email protected] mailbox, however if someone sends them an email on their old email [email protected], you want that too to come to the new email [email protected].
- Optionally, when your users reply to emails, by default it should be sent from their new [email protected] email, but they should also have an option to send as [email protected] right from [email protected] mailbox.
Googally’s migration process (Merger)
Our migration process starts as soon as we receive required migration information from you. Here is the step-by-step process.
- We add a temporary secondary domain to your old Google Workspace account, under old.com in our example here, let's call this temporary.old.com.
- We migrate emails, calendar, and contacts (and optionally Drive files) for all / required users from [email protected] to [email protected] (Note, we’ll create the users in new.com if you haven’t created them yet).
The following steps are performed on weekends (usually on Friday evening as you won't have much email traffic). We also use scripts to speed up some of these process steps.
- Once the initial migration is completed, we’ll swap the primary domain from old.com to temporary.old.com, and rename all your users from [email protected] to [email protected].
- Now we delete the domain old.com from its instance. This instance will only have temporary.old.com left now, and all your users’ emails are now [email protected].
- We add old.com as a secondary domain under new.com, and verify the domain ownership via DNS record creation.
You will have a few minutes of downtime between steps 4 and 5, because when we delete a domain from Google Workspace, Google needs some time to purge it from their database, and then we can re-add this domain under the new domain (e.g. new.com in our example).
However, if due to the nature of your business you can’t afford these few minutes of downtime on a weekend evening, please let us know. We have another option to ensure zero downtime, but it’ll increase the migration scope and pricing.
- At this stage, we have both your domains (old.com and new.com) under one Google Workspace account, all your users here have [email protected] primary email address.
- We now add an email alias for each of your users, so all users get [email protected] email alias, we do this step to ensure emails sent to users’ old email address (e.g. [email protected]) do not bounce, and are instead delivered to users’ new email address (e.g. [email protected]).
- We make any DNS changes if required (e.g. DKIM for this secondary domain).
- We let you review everything and start using your new / branded Google Workspace.
- Once you are settled down, you can delete everything from your old domain (e.g. temporary.old.com) to avoid paying for Google licenses there.
Result after following our process
- Your two separate Google Workspace accounts are now merged into one. You have one centralized administration console to manage everything.
- Your acquired company users now also have a [email protected] mailbox to send and receive emails. In addition, any emails sent to [email protected] would also come to the respective [email protected], so no email bounce.
- Your acquired company’s users’ data including email, calendar, contacts (and optionally Drive files) are migrated successfully with no data loss.
- Optionally, all your acquired company’s users have an option to send emails as [email protected] if needed.
Don't have time or expertise to do it? Check out our white glove Google Workspace to Google Workspace migration offering with transparent pricing.



