Transferring a domain does not have to interrupt your website or email. This reusable checklist explains how to prepare DNS, confirm transfer eligibility, obtain the authorization code, coordinate registrar approval, and verify every service after the transfer is complete.
Overview
A domain transfer moves the registration record from one registrar to another. It is separate from moving the website files or changing the hosting server. In many cases, the site can remain online throughout the process because its DNS records continue directing visitors and mail to the existing services.
The safest approach is to separate the work into three stages:
- Prepare: confirm ownership, account access, contact details, DNS records, renewal timing, and transfer eligibility.
- Transfer: unlock the domain, request its authorization code, submit the transfer at the new registrar, and approve any confirmation messages.
- Verify: check the domain, website, email, SSL certificate, DNSSEC status, and renewal information after the transfer.
A domain transfer checklist is especially useful when the domain supports several systems. A business website may depend on DNS records for email, payment services, analytics, customer portals, verification tokens, and subdomains. Record those dependencies before making changes. If the transfer is also part of a hosting move, keep the registration transfer and hosting migration as separate workstreams where possible. For the hosting portion, see How to Migrate a Website to a New Host With Minimal Downtime.
Checklist by scenario
Scenario 1: Moving the domain while keeping the current hosting
This is usually the simplest transfer scenario. The goal is to change the registrar without changing where the domain points.
- Sign in to the current registrar and confirm that you can manage the domain.
- Save a copy of the current DNS zone, including A, AAAA, CNAME, MX, TXT, and any relevant verification records.
- Check that the registrant or administrative contact email is current and accessible.
- Confirm the domain is eligible for transfer under the applicable registrar and registry rules. Requirements can vary by extension and situation.
- Remove the registrar lock or transfer lock if the current provider requires it to be disabled.
- Request the domain authorization code, sometimes called an EPP code, transfer code, or auth code.
- Start the transfer at the new registrar and enter the domain name and authorization code carefully.
- Approve the transfer using any confirmation email or registrar dashboard workflow.
- After completion, confirm that the existing nameservers and DNS records are still present.
Do not change nameservers merely because the registrar changed. If the nameservers remain the same, the domain should continue using the existing DNS provider. For a separate explanation of DNS changes, read How to Point a Domain to Cloud Hosting: DNS Records, Nameservers, and Verification.
Scenario 2: Transferring the domain and moving to new hosting
Here, two changes may affect availability: the registrar transfer and the change in DNS destination. Prepare the new hosting environment before changing DNS.
- Build or migrate the website to the new host before the planned DNS cutover.
- Test the site using a staging address, temporary hostname, or hosts-file method where appropriate.
- List the DNS records required by the new host, including the web records and any custom subdomains.
- Confirm that the new server can issue or install the required SSL certificate.
- Plan the DNS change separately from the registrar transfer, unless there is a specific reason to combine them.
- After changing DNS, test both the root domain and the www hostname, along with redirects and canonical URLs.
Keeping the current DNS provider during the registrar transfer can reduce the number of variables. Once the transfer is complete and the site is stable, you can consider a DNS provider change as a separate, documented task.
Scenario 3: The domain is used for business email
Email deserves its own verification pass. A registrar transfer should not normally require changing MX records, but an incomplete DNS copy or accidental nameserver change can affect delivery.
- Document MX records and email-related TXT records before starting.
- Include SPF, DKIM, and DMARC records in the DNS inventory if they are configured.
- Confirm that mailboxes, forwarding rules, and third-party email services are still active.
- Send test messages to and from more than one mailbox after the transfer.
For planning considerations around mailboxes and domain-based email, see Business Email on Your Domain: Hosting Options, Costs, and Setup Requirements.
What to double-check
Eligibility, timing, and renewal
Review the current registrar's transfer status before requesting a code. A domain may be unavailable for transfer because of its extension, registration history, recent account changes, an active dispute, or another restriction. The exact rules depend on the domain extension and providers involved, so use the registrar's current instructions rather than relying on an old checklist.
Check the expiration date and allow enough time for troubleshooting. Do not begin immediately before a launch, campaign, holiday closure, or critical renewal deadline. Also compare the new registrar's renewal terms and account settings before starting. A low initial transfer price, if offered, does not by itself describe the future renewal cost or included services.
Account security and authorization
Use a secure, individual account at both registrars. Enable two-factor authentication where available, verify recovery methods, and avoid sharing an authorization code through an untrusted channel. Treat the code as a credential: enter it only in the intended registrar account and regenerate it if you believe it has been exposed.
Before and after the transfer, review registrar lock, recovery email, delegated users, and DNS access. The Domain Security Checklist provides a broader review of these controls.
DNSSEC and certificates
If DNSSEC is enabled, document the current DS records and understand how the new registrar or DNS provider will handle them. An incorrect DNSSEC configuration can make a domain appear unreachable even when ordinary DNS records are correct. Do not remove or recreate DNSSEC records casually; follow the documented process for the specific registrar and DNS provider.
Check HTTPS after the transfer. Visit the main domain, important subdomains, and redirect variations. If the hosting environment also changed, confirm that the certificate covers every required hostname. See SSL Certificate Options for Small Business Sites for certificate terminology.
Common mistakes
- Changing nameservers unnecessarily: A registrar transfer and a DNS provider change are different operations. Preserve the existing nameservers unless the migration plan calls for a change.
- Starting without a DNS inventory: Missing a TXT record can break email authentication or a service verification process even if the website still loads.
- Using an outdated authorization code: Codes can be regenerated or invalidated. Copy the current code carefully and avoid adding spaces.
- Ignoring the transfer lock: Check both the visible lock status and any registrar messages explaining why the domain cannot be moved.
- Transferring too close to expiration: A transfer may require actions from one or more parties. Build in time for approval and support requests.
- Assuming completion means everything is verified: A completed transfer does not prove that website routing, email, SSL, DNSSEC, or subdomains are working.
- Combining too many changes: Moving the registrar, DNS provider, hosting platform, email provider, and SSL setup at once makes diagnosis harder. Sequence changes when practical.
When to revisit
Use this checklist before every domain transfer, but revisit the details whenever the underlying systems change. Review it before seasonal planning cycles, a major product launch, a rebrand, a hosting move, or a planned change to business email. It is also worth reviewing after a registrar updates its dashboard, authorization-code workflow, security controls, or transfer instructions.
Keep a dated domain record containing the registrar, expiration date, nameservers, DNS provider, key DNS records, hosting account, email provider, DNSSEC status, and responsible account owners. Update it after each infrastructure change. A DNS troubleshooting checklist can help when a post-transfer symptom appears, while the domain portfolio guidance at Best Practices for Domain Portfolio Management can help with recurring reviews.
Final action list: choose a low-risk maintenance window, export or record DNS, confirm access and eligibility, unlock the domain, obtain a fresh auth code, submit and approve the transfer, then test the website, email, SSL, subdomains, and renewal settings. Do not close the old registrar account until the transfer is confirmed and the new account is fully usable.
