How to transfer a domain name to another registrar
Move a domain to a new registrar without downtime: unlock it, get the auth code, approve the transfer and keep DNS and email running throughout.
Moving a domain to a different registrar is routine work, and it is also one of the few web tasks where a missed detail can take a business's website and email offline for days. The usual reasons to move are simple: the domain sits in an old agency's account, the renewal prices crept up, or you want all your domains in one place with one login. Whatever the reason, the process is the same, and it goes smoothly when you prepare DNS before you touch the transfer itself.
Disclosure: some links in this guide are partner links. If you buy through them, MMIX may earn a commission; your price stays the same.
Marketing MIX has moved client domains between registrars since 2012. The sequence below is the checklist we run on every transfer.
What a transfer changes, and what it leaves alone
A domain transfer moves the registration from one registrar (the "losing" registrar) to another (the "gaining" registrar). The name, the ownership and the expiry date stay with you. What can change is DNS, and that is where the risk sits.
Where your DNS lives decides the risk
DNS can be hosted in three places: at the registrar, at your web host, or at a separate DNS service such as Cloudflare. If DNS lives at the host or at a DNS service, the transfer does not touch it, and your website and email keep working throughout. If DNS lives at the losing registrar, those records can disappear when the domain leaves, unless you recreate them at the new provider first. Our guide to DNS records explains what each record does.
Step-by-step: transferring a domain name
Step 1: Check that the domain is eligible
Look up the domain in ICANN Lookup. It shows the current registrar, the expiry date and the status codes. A status of clientTransferProhibited simply means the registrar lock is on, which you will switch off in Step 4. Statuses such as serverHold or pendingDelete point to a bigger problem that needs the current registrar's support team.
Registrars usually refuse a transfer during a set period after a new registration or a previous transfer, commonly 60 days for generic domains such as .com. Some also apply a lock after you change the registrant's name or organization. The exact rules depend on the extension and on current ICANN policy, so check with your registrar before you plan the date. Avoid starting a transfer in the last days before expiry: renew first if the date is close.
Step 2: Copy your current DNS records
Open the DNS panel wherever your nameservers point and record every entry: A and AAAA records for the website, CNAME records for subdomains, MX records for email, and TXT records for SPF, DKIM, DMARC and service verifications (Google Search Console, Microsoft 365 and similar). Screenshots work; an exported zone file is better.
If your DNS is hosted at the losing registrar, recreate these records at the new DNS provider and switch the nameservers there before the transfer begins. Wait until the change has spread, then continue. This single step is what prevents downtime.
Step 3: Update the contact email and turn off privacy if required
Transfer confirmations and the auth code often go to the registrant email on file. If that address belongs to a former employee or a closed mailbox, update it now and confirm you can receive mail there. Some registrars ask you to switch off WHOIS privacy so the gaining registrar can confirm the request; turn it back on at the end.
Step 4: Unlock the domain and get the auth code
In the losing registrar's control panel, find the domain settings and disable the registrar lock (it may be called the transfer lock or domain lock). Then request the authorization code, also known as the EPP code or transfer key. Some registrars show it on screen; others email it. Treat it like a password: anyone holding it and an unlocked domain can start a transfer.
Step 5: Start the transfer at the new registrar
At the gaining registrar, start a transfer and enter the domain and the auth code. With the Namecheap domain transfer page you can check several domains at once and see which are ready to move. During checkout, choose to keep the existing nameservers unless you have already prepared DNS at the new registrar. For most generic domains the transfer adds a year to the registration, and the time already paid usually carries over.
Step 6: Approve the transfer and wait
Watch the registrant mailbox for confirmation emails from both registrars and approve them. The losing registrar may send a notice with a link to accept or reject the transfer; accepting it usually completes the move sooner. Without action, generic domains usually complete within about five to seven days. Country-code domains follow their own registry's process and timing.
Step 7: Verify DNS, lock the domain and set renewal
When the domain appears in the new account:
Load the website over https and send a test email to and from the domain.
Check the nameservers in ICANN Lookup match what you expect.
Re-enable the registrar lock and WHOIS privacy.
Turn on auto-renewal and confirm the card on file.
Add the new expiry date to the company calendar.
What to check and common mistakes
DNS hosted at the old registrar and never copied. The website and email stop working once the domain leaves. Copy the records first.
Auth code sent to a dead mailbox. Update the registrant email before you request the code.
Transfer started days before expiry. Renew first, or the domain can expire mid-transfer.
Lock left off afterwards. Re-lock the domain as soon as it arrives.
Email authentication lost. If SPF, DKIM or DMARC records were not carried over, mail starts landing in spam. The SPF, DKIM and DMARC setup guide shows how to rebuild them.
Several domains moved in one batch with no list. Keep a simple table of domain, old registrar, status and date moved, so nothing falls through.
A transfer is quick for one domain with DNS hosted elsewhere. It gets slower when an old agency holds the account, when nobody knows where DNS lives, or when email for the whole team depends on records nobody has documented. In those cases we inventory the domains, rebuild DNS ahead of time and move each domain into an account the business owns.
Prefer to hand it off? MMIX sets up domain, hosting, email and DNS for you — since 2012. Tell us about your project and we will reply with a plan.
Send your site address. We look at the site, your ads and your search presence and send back what to fix first and a one-month plan. Ads management is quoted after the review.