Domain Pains – Transfering from Google Apps to GoDaddy

February 12th, 2010 by Livingston | Print Domain Pains – Transfering from Google Apps to GoDaddy

Well, I must admit that I buy too many domain names.  Every time I get an idea for a product or service, I think of domain name that works well and claim it.  Not that the names alone are that incredible, but they’re related to the idea and it’s a $10 motivation fee that I charge myself.  Actually they’re usually 7.49, I always add a coupon code to my order (for everything purchased online).

The trouble started when I decided to purchase a number of domains through Google Apps (  They had a deal with godaddy/enom where they would be the broker, and you could get domain privacy included in the $10/year rate.  It also automatically set you up with Google Products/Webmaster tools/Google Pages, etc.

All was fine and dandy until I wanted to get my domains all together with one company, GoDaddy.  Here’s the problem: every time I bought a name through Google, they were buying from GoDaddy through a unique GD account.  So this means, buy 25 domains, and you have 25 separate log-ins and 25 unique passwords to deal with.  Not to mention that each of them are private, so before you can transfer them you must go to, and request each domain’s corresponding DBproxy account number, which will let you request forgotten password email, which will then allow you to update your password – Didn’t know this until step #7 below – again this is needed for every one of those 25 domains.

So here are the steps (the below order takes into account delays/lag time with account# requests, password resets and updates to take place.)

  1. Request to transfer your domains, this is done through the service where you want to ultimately purchase and manage your domains.  I was trying to transfer from Google Apps to GoDaddy, so initiated the transfers through GD.  What gets confusing is that your purchase through Google was really also through GoDaddy.  You’d think it would be an easy transfer from GD to GD, but the support reps can’t help you here since they don’t support transactions through Brokers (Google Apps) – sucks but makes sense.
  2. Find the original purchase email from Google Domains – this will give you a link to create your first admin account.   Once you’ve logged in to the admin panel, go to Advanced Settings –> Domain Names –> DNS Settings.  This will give you your unique GoDaddy user name and password for that domain, along with a customer service pin #.
  3. Once you’ve logged in, there are two steps here.  First unlock the domain.  Second, request the authorization number to be sent via email.
  4. While you’re waiting for the above steps to process, go to and track down your customer number by adding the domain name itself and completing their captcha.  This will send you an email with the customer number.
  5. Once you get the customer number, you can request to reset the password.  They’ll send you an email with a URL-Key to create a new one.
  6. When you have the customer number and your updated password – login to DBProxy and check the box that says ‘remove this domain from the private something or other”.
  7. If you don’t do step #6 prior to beginning the transfer of the domain, you’re transfer will be rejected and you’ll get this lovely and vague error message:  Dear Registration Private,  The transfer of from Google Apps to another registrar could not be completed for the following reason(s):   Express written objection to the transfer from the Transfer Contact. (e.g. – email, fax, paper document or other processes by which the Transfer Contact has expressly and voluntarily objected through opt-in means). If you believe that this domain name does not fit the situation described above, go to for assistance.  Regards,  Domain Services Google Apps”
  8. When you first requested the transfer, you should have received an email that includes the Transaction ID: 748953143 and Security Code: JF8dGH8176 for your domain.
  9. Eventually you will also receive an email with your Authorization Info:  2348750148PO4677.
  10. Now that your domain is unlocked, it is no longer private, you have your transaction ID, Security Code, Authorization code, go to your GoDaddy Account and view ‘Domain Transfers’.  This is where you’ll see the 4 steps (progress meters) of the transfer.
  11. Since you’ve already initiated the transfer, now you need to authorize the transfer.  Check the domain name box, and in the upper right screen, click and hold the Authorize button, it will provide a drop-down box to select ‘begin authorization’.  <– Poor User Interface and confusing, I was so exasperated at this point that I didn’t see the drop-down, or it took a second longer than I was willing to wait.
  12. Add all your transaction ID, security code and then ‘Accept transfer’, then add the Authorization code.
  13. If all goes well, you should receive a very friendly (not) email from Google stating that it takes 5 days to process.  And that if you want to change your mind FOR ANY REASON, simply log-in to their account to cancel.  Of course they make it really easy to cancel a transfer.
  14. Voila – and that’s just for a single domain.  Because they’re all purchased through Google, with unique GoDaddy accounts, there is no easy or automated (bulk) way to do this.

The above may be obvious to some, but I had a heck of a time making this happen, there were quite a few steps, the GD to GD piece confused me and I’m still in the process of transferring the rest.



  1. smudgers

    3. Once you’ve logged in, there are two steps here. First unlock the domain. Second, request the authorization number to be sent via email.

    You lose me here. It takes me to access@enom and gives me a bunch of random gibberish, but nothing about unlocking or sending authorization numbers via email. Any help?

  2. smudgers

    Scratch that last question. Enom requires you to email them at
    and request that you have your domain unlocked. I have also requested for them to remove the privacy at this stage. I’m assuming your instructions are based on the google/godaddy relationship, rather than the google/enom.

    This process has been much more of a pain than I ever imagined that it would be.


Leave a Reply

You must be logged in to post a comment.