Moving a Domain to Another Registrar

1. When you actually need to move a domain

Start with the vocabulary. Your domain is registered through a company called a registrar, you pay it once a year, and it keeps your registration in the global domain system. A transfer moves that registration to a different registrar. The address itself does not change and visitors notice nothing.

The reasons come down to a few. The most common is taking over a site and finding the domain sits in a contractor's account or under a former employee's personal login. Next is a registrar that has become unusable: the control panel will not let you in, support does not answer, or renewal notices go to a dead address. After that comes ordinary housekeeping, with four domains spread across three companies, separate invoices and expiry dates nobody tracks.

The first of those is the urgent one. If the domain is not in your name, whoever holds it can point it elsewhere, or simply let it lapse and watch somebody else take it. What that situation really needs is a change of ownership, and the transfer is only the last step that makes it stick.

2. Transferring, changing DNS and changing host are three different jobs

This section is worth reading slowly, because it is where the confusion lives. People say they want to move a domain to a new hosting company when what they mean is that they want the domain to point at a new server. Those two touch entirely different settings and carry entirely different risk.

Put simply, a transfer decides which company holds the registration. DNS decides which machine the name points at. The two are independent and can be done in either order or not at all. Anybody who only wants to change hosting needs the second one and never has to touch a transfer.

3. Four things to confirm before you start

The transfer process itself is not difficult. What stalls it is almost always preparation that was skipped. Confirm these four before pressing anything and you avoid most of the back and forth.

With all four settled, ask your current registrar for the authorization code, also known as an Auth-Code or EPP code. It is a string generated by the current registrar that proves you hold the domain, and the ICANN guidance for registrants is blunt about it: without that code, no transfer. Most registrars let you generate it in the control panel, and if yours does not, write and ask, because they are obliged to provide it.

4. What blocks a transfer: three different 60-day rules

Some refusals are written into the rules rather than being obstruction by your registrar. The ICANN transfer policy lists the grounds on which a transfer may be denied, and the three most commonly hit are all 60-day windows.

The first is a domain registered less than 60 days ago. A brand new domain has to wait, with no exceptions. The second is a domain that has itself been transferred within the last 60 days, so it cannot bounce between registrars in quick succession. The third is the one people trip over: changing the registrant name, organisation or email counts as a change of registrant and triggers a 60-day transfer lock of its own.

A few other grounds have nothing to do with you: unpaid fees from a previous period, an active legal dispute, or a domain caught up in a dispute resolution proceeding. Those need the underlying issue resolved, and a transfer will not route around them.

One note on scope. These rules govern .com, .net and the other domains ICANN oversees. Country registries write their own, and Taiwan's .tw and .com.tw are run under TWNIC rules where the process and the restrictions differ. Ask your registrar rather than assuming the rules above apply.

5. How long it takes, and whether anything goes offline

Five to seven days is the normal answer. The ICANN rules are explicit: if the current registrar does not respond within five calendar days of being notified, that counts as approval and the transfer completes on its own. To move faster, most registrars offer a button that releases the domain immediately, which usually gets it done the same day.

As for downtime, usually there is none. A transfer moves the registration record, not the settings that say where the domain points. DNS records normally travel with it untouched. Visitors see nothing and mail keeps flowing.

When you copy, do not stop at the website record. Mail delivery records, the records that authorise your mail to be sent, and the verification records various services asked you to add all sit in the same zone. Miss one and something quietly stops working, and mail problems in particular often go unnoticed for a couple of days.

6. Cost, and what to do once it lands

Cost is where the expectations go wrong. Most registrars do not charge a fee for the transfer itself, but transferring a generic domain normally includes a year of renewal, so what you pay is a year's registration and the expiry date moves forward by a year. The money is not wasted. It is simply a renewal rather than a processing charge.

That means you should compare renewal prices, not first-year promotions. Some registrars are startlingly cheap for year one and several times the price from year two, and only a three-year total shows which is actually better. Check whether DNS management is included, whether privacy protection costs extra, and whether the account supports separate logins for different people.

Three things to do once it lands. Put the registrant details into the company name with a company address, which is safe to change now. Turn on the transfer lock at the new registrar and enable two-factor authentication on the account, because a stolen domain account is worse than a stolen website login. Then set auto-renewal, confirm the payment method works, and put the expiry date in a company calendar rather than relying on a vendor reminder.

The principle underneath all of it: the domain and hosting accounts should be in the company's name, billed to a company address, with developers and agencies working through sub-accounts. Then whoever you hire next, the foundation stays yours.