How to Transfer a Domain to a New Registrar Without Downtime

Overview

A domain transfer moves the registration record from one registrar to another. It is separate from moving your website, cloud hosting, or email provider. In a well-planned transfer, the domain continues pointing to the same DNS service and infrastructure while the registrar changes in the background.

The safest approach is to separate the work into two decisions:

1. Where will the domain be registered? This is the registrar responsible for renewal, transfer controls, contact details, and the domain authorization code.
2. Where will DNS be managed? This may be the current registrar, a dedicated managed DNS provider, or a hosting platform.

You can transfer the registration without changing DNS. That is usually the simplest route when the website and email are working correctly. A nameserver change is a separate operation and should only be included when you have a reason to move DNS management as well.

Before starting, record your current setup. Save the domain’s nameservers, DNS records, renewal date, registrar account details, and any services that depend on the domain. If you need a refresher on record types, see DNS Records Explained: A, AAAA, CNAME, MX, TXT, and SRV Records.

Checklist by scenario

Scenario 1: Transfer the registrar only

Use this path when your website, email, SSL configuration, and DNS records are already working.

• Confirm the domain is eligible for transfer under the current registrar and registry rules.
• Verify that the registrant or account owner can access the administrative email and registrar account.
• Export or copy the current DNS records.
• Confirm the existing nameservers and plan to keep them unchanged.
• Unlock the domain if the registrar requires an unlocked status for transfer.
• Request the domain authorization code, also called an EPP code or transfer code.
• Start the transfer at the new registrar and enter the exact domain name and authorization code.
• Approve any confirmation email or registrar notification required to begin the transfer.
• Monitor the transfer status and verify that nameservers remain correct afterward.

This is generally the lowest-risk option because the domain’s DNS delegation remains with the existing provider. Still, do not assume that a registrar transfer automatically preserves every setting. Confirm the nameservers and key records after completion.

Scenario 2: Transfer the registrar and move DNS management

Choose this path when you want managed DNS, centralized domain and hosting administration, or a different provider for operational reasons. Treat it as two migrations rather than one.

• Copy every relevant DNS record before changing nameservers.
• Recreate records at the new DNS provider, including A, AAAA, CNAME, MX, TXT, SRV, and verification records where applicable.
• Pay particular attention to email records, including MX records and authentication records such as SPF, DKIM, and DMARC.
• Confirm that the new DNS zone is complete before changing nameservers.
• Change nameservers according to the new provider’s instructions.
• Allow time for DNS caching and verify resolution from more than one network or DNS-checking tool.
• Only then complete or continue the registrar transfer if the two operations are being coordinated.

For websites hosted on a cloud VPS or another server, verify that the destination IP address is correct and that the web server is configured for the domain. If you are also deploying or relocating the application, use a separate deployment plan; the production deployment checklist for cloud servers can help keep those tasks distinct.

Scenario 3: Transfer a domain used for business email

Email continuity deserves extra care because a missed DNS record can affect delivery even when the website remains online.

• Document MX records and their priority values.
• Copy TXT records used for SPF, DKIM, domain verification, or other email services.
• Confirm that the mail provider’s DKIM selectors and hostnames are recorded exactly.
• Check whether any subdomain is used for email, tracking, applications, or customer portals.
• Do not cancel the old DNS or hosting service until mail flow and website access have been tested.

A registrar transfer by itself should not require changing MX records. If email is already working, preserve the current DNS delegation unless there is a deliberate reason to change it.

Registrar comparison checklist

Do not choose solely on the advertised registration price. A suitable registrar should make ownership, DNS, security, renewal, and transfer controls understandable.

What to double-check

Eligibility and timing

Some domains may be temporarily ineligible for transfer because of a recent registration, recent transfer, ownership change, dispute, or registrar-level lock. The exact rules can vary by domain extension and situation. Check the current registrar’s transfer guidance and the receiving registrar’s requirements before making changes.

Review the expiration date as well. Avoid beginning a transfer so close to expiration that a delay could create an account or renewal problem. If the domain is near expiration, confirm with both registrars how renewal and transfer timing will be handled.

Authorization code and account access

Request the authorization code through the current registrar’s official account interface or support process. Treat it as sensitive account information. Enter it exactly as provided, including capitalization or punctuation if applicable. If the code is rejected, do not repeatedly guess; request a fresh code or ask the registrar to confirm the domain’s transfer status.

Lock, privacy, and ownership details

Check whether the domain has a transfer lock and whether it can be removed from the current account. Privacy protection may affect how contact details appear, but it does not replace accurate ownership information or account security. Confirm that the registrant name, organization, contact email, and account owner are correct before initiating a transfer. An ownership change can have consequences separate from a routine registrar transfer, so do not edit contact data casually during the process.

DNS and nameserver decision tree

Use this simple decision tree:

• Is the website and email working, and do you want to keep the current DNS provider? Keep the existing nameservers and transfer only the registrar.
• Are you moving to a new managed DNS provider? Recreate and verify the DNS zone first, then change nameservers as a separate controlled step.
• Are you moving hosting as well? Complete the hosting configuration, SSL setup, and DNS testing before pointing production traffic to the new server.
• Are you unsure where DNS is managed? Identify the authoritative nameservers first. Do not edit records at a provider that is not authoritative for the domain.

For hosting-specific planning, review how to connect a domain to cloud hosting and keep domain registration, DNS, hosting, and SSL tasks on separate checklists.

Post-transfer verification

After the transfer completes, verify:

• The domain appears in the new registrar account.
• The nameservers are the intended ones.
• The website loads on the root domain and important subdomains.
• HTTPS and the certificate work as expected.
• Email can be sent and received.
• MX, SPF, DKIM, DMARC, and verification TXT records are still present if relevant.
• Automatic renewal and payment details are configured at the new registrar.
• Two-factor authentication and account recovery details are enabled and current.

Common mistakes

• Changing nameservers unnecessarily: A registrar transfer does not require a DNS migration. Changing both at once makes troubleshooting harder.
• Forgetting non-website records: Email, verification services, APIs, staging environments, and subdomains may rely on records that are easy to overlook.
• Starting without a DNS copy: Take an inventory before modifying the authoritative zone.
• Waiting until expiration: Give yourself enough time to resolve eligibility, authorization-code, or account issues.
• Canceling the old service too early: Keep the old registrar, DNS provider, hosting account, or email service active until testing is complete.
• Assuming transfer equals hosting migration: Moving the registration does not move website files, databases, mailboxes, SSL certificates, or server configuration.
• Ignoring account security: A domain controls access to important services. Use unique credentials, strong authentication, and limited administrative access.

When to revisit

Keep this checklist with your domain records and review it before every transfer, ownership change, hosting migration, or renewal planning cycle. Revisit it when your registrar changes its dashboard, transfer workflow, privacy controls, or authorization-code process. Also review it after adding a new email provider, cloud application, subdomain, or verification service.

For a practical final pass, schedule the work during a period when you can monitor the website and email. Export the DNS record list, confirm eligibility, obtain the authorization code, decide whether nameservers will change, and assign one person to verify the result. After the transfer, record the new registrar, renewal date, nameservers, and account owner in your documentation. That small update makes the next domain transfer faster and reduces the risk of avoidable downtime.