Domain Transfer Checklist: Move a Domain Without Losing Your Website or Email

Overview

A domain transfer moves the registration record from one registrar to another. It does not automatically move your website files, email mailboxes, hosting account, or DNS service. In many cases, a transfer can be completed without changing the nameservers, which helps keep an existing website and email service online. However, that outcome depends on the current DNS setup and the actions taken during the move.

Before starting, identify three separate services:

• Registrar: The company that manages the domain registration.
• DNS provider: The service publishing records such as A, AAAA, CNAME, MX, TXT, and verification records. This may be the registrar, a hosting company, or a separate provider.
• Website and email hosts: The services that deliver the website and process email.

Keeping these roles distinct is the foundation of a transfer domain without downtime. A registrar change alone should not be treated as a complete migration. First document what exists, then confirm the receiving registrar's process, and only afterward request the transfer.

For a broader view of total ownership costs, compare registration, renewal, transfer, and privacy charges in the domain price comparison guide. A low transfer price may not be the lowest long-term cost if renewal terms, add-ons, or premium pricing differ.

Checklist by scenario

Before transferring any domain

1. Confirm ownership and account access. Sign in to the current registrar and verify that you control the account, registrant contact details, and security methods. Make sure the email address used for approvals is monitored.
2. Check transfer eligibility. Review the registrar's current rules for newly registered, recently transferred, expired, suspended, or otherwise restricted domains. Policies can vary by domain extension and account status, so use the registrar's instructions rather than relying on a general checklist.
3. Record the expiration date. Note the domain's current expiration or renewal date and allow time for troubleshooting. Do not begin a planned business-critical transfer immediately before a deadline.
4. Review the domain lock. Many registrars use a transfer lock that must be disabled before an outgoing transfer. Confirm both where the control appears and whether the change has taken effect.
5. Request the domain authorization code. Also called an auth code or transfer code, this credential is normally obtained from the current registrar. Treat it as sensitive information and share it only through the receiving registrar's secure transfer form.
6. Export or document DNS records. Save the current A, AAAA, CNAME, MX, TXT, and any other relevant records. Include records used for email authentication, website verification, subdomains, redirects, and third-party applications.
7. Check costs at both registrars. Confirm the receiving registrar's transfer charge, the expected registration extension if applicable, renewal pricing, privacy availability, and any optional services. For comparison methods, see the guide to registrar deals and transfer costs.

If the website and email must remain online

1. Write down the current nameservers before changing anything.
2. Confirm that the current nameservers will remain attached to the domain during the registrar transfer, unless you are intentionally moving DNS.
3. Verify that the website's primary domain, www version, subdomains, and redirects resolve correctly.
4. Review email records, especially MX records and the related SPF, DKIM, and DMARC records where used by your mail provider.
5. Ask the website, email, and DNS providers whether any account-specific verification is required after a registrar change.

Do not change nameservers simply because you are changing registrars. Nameserver changes are a separate DNS migration and can create a different propagation and testing plan.

If you are consolidating a portfolio

Prepare one inventory row for every domain. Include the domain name, extension, current registrar, expiration date, DNS provider, website status, email status, lock status, authorization-code status, transfer cost, and next action. Group transfers by operational risk rather than transferring every domain at once. Start with an unused domain or a low-risk project to confirm the workflow, then move domains that support active sites, customer accounts, or business email.

If you are moving a premium, expired, or auction domain

Confirm who currently controls the registration and whether the domain is still eligible for a standard registrar transfer. A marketplace purchase, expired-domain acquisition, or auction payment may involve a separate ownership-change or push process. Do not assume that a marketplace transaction and an inter-registrar transfer are the same action. Keep transaction records and verify the domain appears in the correct account before changing DNS or publishing a site.

What to double-check

DNS and email continuity

Compare the saved DNS record list with the live zone at the DNS provider. Look for overlooked records on subdomains, staging environments, payment pages, APIs, and verification services. Email deserves a separate review because a website can appear healthy while incoming or outgoing messages fail.

If you intend to move DNS providers as well as registrars, create the new zone before changing nameservers. Recreate the records, validate them with the relevant providers, and plan the nameserver change as its own migration. If you are not moving DNS, avoid editing the zone unless a specific application requires it.

Registrar account and security

• Use a unique, strong password for the receiving registrar.
• Enable multi-factor authentication when available.
• Confirm the recovery email and phone details.
• Review account users, delegates, API keys, and saved payment methods.
• Check whether transfer locks, renewal settings, and privacy settings match your intended configuration.

Approval and status tracking

Submit the transfer from the receiving registrar using the exact domain name and authorization code. Monitor both registrar accounts and the administrative email address for approval requests or status messages. The timing and approval steps vary, so follow the current instructions shown by the registrars involved. Save confirmation messages and note the date the transfer was submitted, approved, and completed.

After completion, confirm that the domain appears in the new account, the expiration information is understood, and the nameservers are still correct. Test the bare domain, www address, important subdomains, website forms, and email sending and receiving.

Common mistakes

• Transferring without a DNS inventory: A forgotten TXT or MX record can interrupt verification or email.
• Changing nameservers unnecessarily: This turns a registrar transfer into a DNS migration without a prepared replacement zone.
• Waiting until expiration week: A delayed approval, locked domain, or incorrect code leaves little room to recover.
• Using an old authorization code: Request a fresh code when the registrar indicates that codes expire or can be regenerated.
• Ignoring account security: A successful transfer does not protect an account with outdated recovery details or shared credentials.
• Comparing only the introductory offer: Check renewal, privacy, transfer, and add-on costs before choosing the destination registrar. The domain coupons and promo codes guide explains how to evaluate the real deal before checkout.
• Assuming a transfer moves hosting: Registration, DNS, website files, databases, and mailboxes may remain with separate providers.

When to revisit

Use this checklist before every domain transfer, not just the first one. Revisit it before seasonal planning cycles, portfolio consolidations, a registrar change, a hosting migration, a business rebrand, or an email-provider change. It should also be reviewed whenever registrar interfaces, transfer rules, domain-extension requirements, privacy options, or security tools change.

A practical final pass is simple: confirm eligibility, unlock only when needed, obtain the authorization code, document DNS, protect email, submit the transfer, monitor approval, and test every important service afterward. Keep the completed inventory with your domain records so the next migration starts with verified information rather than guesswork.