I'll soon be changing my primary domain on G Suite, say from old.com to new.com.

I log into MANY Google services (e.g., Google Analytics) under old.com. After I change the G Suite primary domain, will these other Google services automatically transfer the accounts to a login under new.com?

Or when I login under new.com will it be a brand new account with all the previous info lost?

I would hope the former, since otherwise changing your primary domain would be a huge inconvenience...

There is a similar unanswered question from 5 years ago here, but G Suite has made big changes to primary domain transfers since then.

  • I suggest you to ask on Google Cloud Connect
    – Rubén
    Aug 3, 2018 at 19:29
  • @Rubén, I'll check that out. I asked G Suite support, and they said they couldn't help. :(
    – new name
    Aug 3, 2018 at 20:04
  • I'd appreciate feedback if you think this is not a good question for this SE...
    – new name
    Aug 3, 2018 at 20:23
  • Some people could argue that the question is on topic on this site as most of the G Suite administrator tasks are done through admin.google.com (a web app) but as there are very few G Suite administrators participating on this site and the question is about an edge case I don't think that this question will have an answer soon other than the one that you could post if you decide to share here your findings. (Side note: I didn't vote on this question yet)
    – Rubén
    Aug 3, 2018 at 21:33

1 Answer 1


Since I'm doing this, I'll provide an answer to help others. I'll update as I go through the process.

Before you start

  • To be safe, I added my personal gmail as a full admin user to every service I use. This is easy to do for a lot of Google services like Analytics and Webmaster Tools.
  • Go to your Google Account page to see where you are using your account for login and other things (https://myaccount.google.com/u/1/permissions). To be safe, switch from OAuth to password login where you can. Changing your primary domain could break OAuth logins.
  • This is a good resource.


I tested out accounts with multiple domains before doing the switch. I created [email protected] (the current primary domain) and [email protected] (a secondary domain). When I login to Google Analytics (GA) with [email protected], it is a different GA account than the one at [email protected].

For another test, I created a [email protected] account, sent an email, and created a GA account with that email. I then used the G Suite rename feature to rename [email protected] to [email protected]. After renaming, (1) the [email protected] account had the emails from [email protected], and (2) when I logged into GA with [email protected] it had automatically converted the GA account I created before the rename. This is a good sign!

Changing the Primary Domain

I pulled the trigger yesterday, and it worked very well. Almost flawlessly. Here are the steps I took to change my primary domain from old.com to new.com.

  1. new.com was a domain alias of old.com To make it the primary domain, you need to remove it as an alias and add it back as a secondary domain. The only (very small) hitch is that you need to explicitly remove new.com as an alias of all your users and groups. I have just a few users so it wasn't a big deal for me. Mail sent to new.com likely stopped working for a bit, but the rest of the process was so quick that it doesn't really matter.
  2. Now, I held my breath and clicked the button to switch my primary domain to new.com. old.com became a secondary domain. This happened instantaneously.
  3. I logged in to Analytics under old.com and it still worked.
  4. I "renamed" (that's what Google calls it) users from old.com to new.com. This basically switches the accounts from one domain to the other.
  5. I then logged in to Analytics, Webmaster Tools, Google Cloud Console, and Blogger under new.com and they all worked and carried over all the info from the old.com account. This was my biggest concern so I was very pleased that this just worked!
  6. The last step is to change old.com from a secondary domain to a domain alias of new.com. This was the one flaw of the process. The groups for abuse@ and postmaster@ are stuck with old.com and I am not able to move them to new.com. Because of this, I cannot remove old.com as a secondary domain. I contacted G Suite support and they were quite helpful, and I hope to hear back from them soon.

Overall, a remarkably easy process for a fairly big change. Kudos to Google for making this so easy.

  • 7
    What about the Oauth with 3rd party services?
    – Marcel
    Dec 28, 2018 at 20:17
  • 1
    Thanks for the comprehensive walkthrough. The google help article is a good resource for this too: support.google.com/a/answer/7009324. Just a note that you can now 'rename' groups. Select the group to go to the group details page > click the down arrow on "Group information" > click the edit button on "Group details" > Change the domain and click save. The old domain is added as an alias when doing this, the same as when renaming a User.
    – ajbeaven
    Oct 2, 2019 at 0:40
  • Hi, Thanks for the very comprehensive walkthrough. Can we assume that the inbox also has all your existing emails when you rename?
    – vaisaghvt
    Jan 13, 2020 at 9:01
  • @vaisaghvt,correct, all emails stayed in the gmail inbox.
    – new name
    Jan 13, 2020 at 13:12
  • 1
    I just ran the same process and have two notes to add: 1. If you plan on converting the "old" domain into an alias then while renaming the users/groups make sure to check that the old domain is NOT added as an alias. If it does then remove it because you wont be able to delete the old domain and turn it into an alias (Google could have made this much simpler!!!) 2. WRT 3rd party oauth services where I used the old domain account as a login: So far everything seems to be working without needing to do anything. I.e. I signed in to GoDaddy, GitLab with the new account and there were no issues.
    – nsof
    Apr 24, 2020 at 12:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.