How to Transfer a Domain Without Downtime: A Step-by-Step Checklist

Overview

A domain transfer moves the registration record from one registrar to another. It is separate from moving your website files or changing your hosting account. In many cases, the existing DNS service can remain active during the transfer, which helps keep the website and email online.

The safest approach is to separate the work into three parts: prepare the domain, submit and monitor the transfer, then verify the domain and its services afterward. Do not cancel the old registrar account before the transfer is complete. The old registrar may still be responsible for the domain’s active registration, DNS records, renewal settings, or transfer status until the new registrar confirms completion.

Transfer requirements vary by domain extension and registrar. Treat the instructions in the current registrar and receiving registrar dashboards as authoritative, especially for contact verification, transfer restrictions, authorization codes, and fees. If the domain is close to expiration, has recently changed ownership, or is involved in a dispute, allow extra time and check the relevant registrar requirements before starting.

Checklist by scenario

Before transferring any domain

• Confirm ownership and access. Make sure you can sign in to the current registrar account and access the administrative contact email. If the domain is managed by a colleague, developer, or former provider, resolve account ownership before beginning.
• Record the current configuration. Export or copy the DNS zone, including A, AAAA, CNAME, MX, TXT, and verification records. Also note nameservers, DNSSEC settings, subdomains, redirects, and any custom email routing.
• Check the domain status. Look for a registrar lock or transfer lock and confirm whether the domain is eligible to move. Some domain extensions use different transfer procedures, so review the receiving registrar’s instructions.
• Verify contact information. Ensure the registrant or administrative contact details are accurate and monitored. An approval message sent to an old address can delay the process.
• Review renewal timing. Avoid starting immediately before expiration when possible. Keep the current account active until the transfer is confirmed and review how the transfer affects the registration term and renewal settings.
• Secure both accounts. Turn on two-factor authentication where available, use unique passwords, and check recovery methods. A domain transfer can affect a high-value business asset, so treat account access as part of the transfer plan.

If the website is moving to new hosting too

A domain transfer and a hosting migration can happen together, but combining them creates more variables. For lower risk, transfer the domain while keeping the existing nameservers and website online. Move the site separately, test the new hosting environment, and change DNS only after the new site is ready.

If you must change hosting and registrar at the same time, lower DNS time-to-live values in advance where your DNS provider permits it, copy all records carefully, and schedule the change when you can monitor the site and email. Use the website migration checklist for minimal downtime alongside this domain transfer workflow.

When you need to preserve email

Email is often more sensitive than a website because missing an MX or authentication record can affect delivery and trust. Before the transfer, document MX records and any SPF, DKIM, DMARC, or provider verification TXT records. Do not assume that a new DNS provider will copy them automatically.

If email is business-critical, test sending and receiving before the transfer and again afterward. The guide to business email on your domain provides additional planning points for mail hosting and DNS requirements.

After the transfer is submitted

1. Confirm that the transfer request appears in the receiving registrar account.
2. Save the transfer reference, authorization code request, and any confirmation messages.
3. Watch both registrar accounts and the administrative email for approval or verification requests.
4. Do not change nameservers, DNS records, or account ownership unnecessarily while the request is pending.
5. Check the transfer status periodically, but avoid repeatedly cancelling and resubmitting the request.

What to double-check

Registrar lock and authorization code

The current registrar may require you to disable a transfer lock before the domain can move. The receiving registrar will usually request a transfer authorization code, sometimes called an EPP code or transfer code. Copy it exactly, keep it private, and request a new code if you believe it has been exposed. Do not send the code through an unverified support channel.

DNS and nameservers

Find out whether DNS is hosted at the current registrar, your web host, a managed DNS provider, or another service. The registrar transfer itself may not change nameservers, but changing registrars can expose configuration gaps if the current DNS service is tied to an account you plan to close. If you are changing nameservers, use a nameserver and DNS setup guide to verify the records before making the change.

After any DNS change, use multiple networks or a DNS propagation checker to compare results. DNS responses can differ temporarily while caches update. The DNS propagation troubleshooting guide explains how to check A, CNAME, MX, and nameserver records.

SSL, redirects, and verification services

Confirm that the new environment still supports the certificate for the root domain and relevant subdomains. Check HTTPS redirects, canonical hostnames, CDN settings, analytics verification, payment provider records, and search-engine verification tokens. A transfer does not normally replace a certificate, but a DNS or hosting change can affect certificate validation and site availability.

Transfer failure or unexpected delay

If a transfer fails, read the exact status message rather than immediately repeating the process. Common causes include an active lock, an incorrect authorization code, an unapproved contact request, a domain-specific restriction, or an account mismatch. Re-enable the lock only after confirming that the transfer is no longer pending, then contact the relevant registrar with the transfer reference and domain status details.

Common mistakes

• Changing DNS and registrar at once without a record of the old zone. Create a complete DNS inventory first.
• Using an outdated email address. Update contact details before requesting authorization or approval.
• Closing the old registrar account too early. Keep access until the transfer, DNS, website, and email checks are complete.
• Assuming the website and email are the same service. They may use different DNS records and providers.
• Ignoring domain security. Review 2FA, recovery email addresses, registrar lock, DNSSEC, and account permissions after the move. See the domain security checklist for a broader review.
• Testing only the homepage. Check important subdomains, forms, logins, redirects, APIs, and email delivery as well.

When to revisit

Use this checklist whenever you transfer a domain, change the registrar of record, consolidate a domain portfolio, or move DNS management to another provider. Revisit it before seasonal planning cycles, major product launches, website migrations, or periods when support coverage may be limited.

Workflows and registrar interfaces can change, so verify the current instructions before acting. A practical final checklist is:

1. Confirm account access, ownership, contact email, renewal date, and domain eligibility.
2. Back up DNS records and identify every website, email, SSL, and verification dependency.
3. Secure both registrar accounts and record the current nameservers.
4. Unlock the domain and obtain the correct transfer authorization code.
5. Submit the request, monitor approval messages, and keep the old account active.
6. After completion, verify the domain status, nameservers, DNS records, website, email, HTTPS, and renewal settings.
7. Re-enable appropriate locks and confirm recovery details once the transfer is finished.

Keeping this record with your infrastructure documentation turns a domain transfer from a rushed account change into a controlled, repeatable operation.