How to Transfer a Domain to a New Registrar Without Losing It

“Transferring a domain” sounds like something that could go wrong quietly, in the background, while a business keeps running its site and email as if nothing were happening. In the large majority of cases nothing does go wrong — but the transfers that do stall or fail almost always trace back to the same handful of preventable mistakes: a domain still locked, an approval email nobody could see, an auth code that's already expired, or a transfer started days before the domain was due to renew. None of that takes any real technical skill to avoid; it just takes doing the steps in the right order.

What transferring a domain actually does (and doesn't do)

Transferring a domain moves who manages the registration — the account it renews through, and where add-ons like privacy protection are bought — from one registrar to another. It does not move the domain's DNS records, nameservers, website or email unless those are deliberately changed too. A domain pointing at the same hosting before a transfer still points at that same hosting after one, provided the nameservers aren't touched along the way. This is different from domain lock, a setting that only controls whether a transfer can start at all; that guide covers what the lock does and why it should normally stay switched on.

Before you start: the pre-transfer checklist

• Confirm the domain isn't inside a post-registration or post-transfer lock window. Registry transfer policy typically blocks a new transfer for around 60 days after a domain is first registered, after it was last transferred, or after its registrant contact details last changed. There's no way around this one — it just needs waiting out.
• Unlock the domain at the current (losing) registrar. Nearly every registrar shows this as a “Transfer Lock” or “Domain Lock” toggle in the domain's settings — the same protective setting covered in our guide to domain lock, explained. Switching it off to start a genuine transfer is the one legitimate reason to ever do it.
• Make sure the WHOIS/registrant email address is one that's actually checked. The transfer approval message (sometimes called a Form of Authorization, or FOA) is sent to that address. If WHOIS privacy is masking it behind a stale forwarding address, or the registrant email itself is outdated, the approval message never reaches anyone and the transfer stalls or is automatically cancelled.
• Check auto-renew if the domain is close to its renewal date. Some registrars pause auto-renewal automatically once a transfer starts; others don't. It's worth confirming rather than assuming, so the domain doesn't renew mid-transfer and complicate the timing.

Step-by-step: the transfer-in process

1. Request the transfer authorisation code (also called an EPP code, auth code or transfer key) from the current registrar. It's often shown directly in the domain's management panel, or delivered by email within a few days of the request.
2. Start the transfer at the new registrar, entering the domain name and the authorisation code.
3. Approve the transfer. Depending on the registrar, this means clicking a confirmation link in the approval email sent to the WHOIS/registrant address, or approving the request directly inside the losing registrar's account.
4. Wait out the transfer window. If nobody actively approves or rejects the request, most transfers complete automatically after about five days.
5. Confirm the move once it's done. Check the new registrar's dashboard shows the domain, and that DNS and email are still resolving correctly if anything was changed along the way.
6. Re-lock the domain at the new registrar. Transfer lock isn't always carried over automatically, so it's worth checking rather than assuming it switched back on.

The four things that most often break a transfer

• Domain lock left switched on. The single most common reason a transfer request is rejected outright before it even starts — see the checklist above.
• WHOIS privacy hiding the approval email. Privacy protection is genuinely useful day-to-day, but during a transfer it can mean the approval message goes to a masked address nobody checks. Confirming the registrant email is current and reachable before requesting the auth code avoids this entirely.
• An expired or mistyped auth code. Auth codes are usually only valid for a limited window and can only be used once. If the transfer wasn't started promptly after receiving the code, it's simpler to request a fresh one than to troubleshoot an old one.
• Starting the transfer too close to expiry. A transfer that's still pending when the domain expires can stall considerably, since most registries won't process a transfer on an already-lapsed domain until it's renewed. Leaving at least two to three weeks of runway before the renewal date avoids this entirely.

How long it actually takes

Most domain transfers complete within five to seven days of the new registrar submitting the request — faster if the losing registrar actively approves it, and defaulting to that same roughly five-day window if nobody responds either way. A transfer can be rejected within that window, usually because the domain is still locked, the auth code is wrong, or the account details don't match; a rejected transfer has to be corrected and restarted rather than automatically retried.

Where Gotka Technologies fits

Gotka's domain registration service includes free transfer-in on every domain, alongside domain lock and privacy protection, from RM10 a year — so moving a domain across doesn't carry an extra transfer fee on top of the usual registration cost. For the setting that protects a domain against being moved without permission in the first place, see domain lock, explained. Once the transfer is done, Gotka's Cloud Hosting on LiteSpeed servers is worth considering if the domain's website or email is moving providers too, not just the registration.