Self-service custom domain migration between Netlify accounts

ISSUE

Currently when your domain is associated with a Netlify account and you want to migrate it to another Netlify account you must have access to the original Netlify account, otherwise you need to contact support to get it removed from the original account.

Using the ticket system for such a migration request, (like we’re experiencing now), takes 48 * n hours on a Pro or Business account. Thus far it has been 42 hours for the initial response (only confirming verification instructions), and 26 hours (and still counting) without any action taken yet.

Even when it is actioned, since it may occur at any time (even while we’re sleeping), it runs the risk of effectively “taking the sites down” until such time as we reclaim the domains in the new account.

This issue will become more prevalent the longer Netlify exists, especially as people forget accounts or sites move between developers/agencies/freelancers in situations which may be hostile.

A quick search already reveals many examples, (but I can only post 6 links), so here’s the first few I spotted:
https://answers.netlify.com/t/netlify-custom-domain-custom-domain-is-owned-by-another-account/14362
https://answers.netlify.com/t/cannot-add-custom-domain-to-netlify-custom-domain-is-owned-by-another-account/31157

https://answers.netlify.com/t/domain-custom-domain-is-owned-by-another-account/12598

In all situations that require support the first step is always verifying you own the domain:

SOLUTION

Since Netlify’s support is so slow at resolving this kind of task, it should be added as a self-service feature along the lines of:

  • Press a button to initiate a transfer, which displays a TXT record & value to add to your DNS
  • (You go and add those to your DNS, then come back to Netlify)
  • Press a “verify & transfer” button
  • Netlify automatically confirms you have added the appropriate TXT record and value
  • Netlify automatically removes the custom domain from the old account and adds it to the new one

E.g. Precisely the same steps the support staff are doing manually, but automated so it can be instant.

1 Like

Hi @nathanmartin,

While we appreciate the feedback, calling us slow doesn’t set a good tone. We are trying our best and on our best days, we even reply to people within a few minutes.

The support team has been overloaded the past few days so sorry to see this taking so long for you. I’ll take a look at it right away and get it sorted.

UPDATE: I’m checking, but I’m not seeing your request in the helpdesk. Could you share the ticket number?

1 Like

@hrishikesh I’m not calling you personally slow and I understand that the support staff may be working hard, but as a paying customer waiting 42 hours for an initial response, and then another 39 hours (so far) with no resolution, is objectively slow. It’s poor customer service whether it is intentional or not.

Netlify’s sales staff recently informed me that any plan less than a $2,000 per month enterprise plan is considered “self service”, which is why I’m suggesting that this particular issue (and others like it) be made self serviceable so they do not rely on human support intervention at all.

Our ticket number is 71463, however there’s no rush actioning it as we moved the sites to Vercel in the interim and while we lodged the ticket several days ago it is now 11.43pm at night here on a Friday night.

No problem, all those domains have been removed.

Thanks for your assistance @hrishikesh, I’ve now claimed those custom domains.

Ultimately the self-service model is fine as long as it’s actually possible to self-service, so I hope my feature suggestion is taken into consideration.

Hey there, @nathanmartin :wave:

Thanks again for sharing this feedback. I want to confirm that we have opened a feature request and shared this with the appropriate teams at Netlify.

2 Likes

Just adding a follow up note that any system implemented for this should also account for the release/claiming of subdomains, as we encountered a subsequent issue here:

1 Like

Hi hrishikesh, I seem to be having the same problem as this dude. I’ve been searching through these forums, but haven’t really found a good place to start, so i’m just going to try leaving you a comment here.

I am trying to add www.yakkertech.com to my netlify site, and the domain is registered with godaddy.

To my knowledge, i am to add a TXT record to verify that i am the owner, which i can do.

Do you think you can help with with this? It would be much appreciated!

Thanks!
Mitch

Hey @mjhoracek,

Could you mention what site or account you’re trying to add this domain to? I can see this domain was connected to Netlify just yesterday.

Thanks for the quick reply. My netlify profile name is mjhoracek, and the deployment currently lives at yakkertech.netlify.app

Awesome okay, that domain was not being used in that other account, so I’ve removed it now and you should be able to connect it.

I see the changes, thank you so much! I really really really appreciate the quick help - i’ve got a CEO with his hair on fire w/regard to this issue.

Hi,

I would like to upvote this issue as well. It is causing us a heartache at the moment too. Automatic TXT record validation would save a lot of time both for us and the support team I believe.

I have opened a support ticket via email (82109) and added the TXT record, but if there is any chance of speeding it up, it would greatly help us.

Thank you!

1 Like

hi @Jni we are currently a little underwater with several team mates out, so thats why things might be a little slower than usual.

can you tell me which domain this is regarding? i can try and take care of this. thanks.

(post deleted by author)

hi there jni, we have verified your ownership and freed up the domain, you can use it now. i’ll also go ahead and close your helpdesk ticket too. sorry to be slow to get to you!

@perry actually you have perfect timing, thanks a lot!

1 Like