Domain Transfer Checklist: How to Move a Domain Without Downtime or Lost Email
domain-transferDNSregistrarswebsite-migrationemail-continuity

Domain Transfer Checklist: How to Move a Domain Without Downtime or Lost Email

VViral Domains Editorial Team
2026-11-15
7 min read

A practical domain transfer checklist for protecting DNS, website access, and email when moving to a new registrar.

Moving a domain to a new registrar does not have to interrupt a website or email service. This domain transfer checklist gives you a repeatable workflow: inventory DNS records, confirm ownership and eligibility, unlock the domain, obtain the authorization code, monitor the transfer, and verify every service afterward. It also shows what to track monthly or quarterly so future registrar changes are easier to plan.

Overview

A domain transfer changes the registrar responsible for managing your domain registration. It does not automatically move your website files, hosting account, mailboxes, databases, SSL configuration, or content. Those services may continue working during the transfer, provided the domain’s DNS settings remain available and unchanged.

The main risk is not usually the transfer itself. Problems arise when the owner cannot access the registrant account, DNS records are undocumented, a transfer lock is still active, or email depends on records that nobody has recorded. Treat the move as a controlled change to domain management rather than as a complete website migration.

Before starting, identify two separate systems:

  • Registrar: the company where the domain is registered and renewed.
  • DNS provider: the service hosting the domain’s DNS records. This may be the current registrar, the new registrar, your web host, or a separate DNS platform.

If the DNS provider will remain the same, a registrar transfer can often proceed without changing nameservers. If you plan to move DNS at the same time, separate the projects where possible. Transferring the domain first and changing DNS later makes troubleshooting much clearer.

What to track

1. Ownership and account access

Confirm that you can sign in to the current registrar and that the registrant or domain owner contact is correct. Check access to the associated email address, enable multi-factor authentication where available, and record which person or organization is responsible for approving changes. Do not begin with an account that only a former employee, contractor, or inactive email address can access.

Record the domain’s expiration date, auto-renewal setting, current registrar, DNS provider, nameservers, and renewal contact. A transfer can take time, so avoid starting immediately before an expiration deadline unless you have confirmed the registrar’s process and have a backup renewal plan.

2. Transfer eligibility

Look for a registrar control labelled domain lock, transfer lock, or a similar status. The domain generally needs to be unlocked before the gaining registrar can process the move. Some domains may also be restricted because of a recent registration, a recent transfer, a pending ownership change, a dispute, or another registry-level condition. The exact requirements depend on the domain extension and registrar.

Ask the current registrar whether any restriction applies and how it is displayed. Do not assume that a domain is transferable simply because it is active in your account.

3. The authorization code

Request the domain authorization code, also called an EPP code, transfer code, or auth code. Store it privately and enter it only in the new registrar’s official transfer flow. Codes may expire or be regenerated, so use the current code and avoid copying extra spaces. If the code is not visible, request it through the registrar’s documented recovery process rather than guessing.

4. A DNS-record inventory

Export or copy the current DNS zone before making changes. Your inventory should include the record type, host or name, value, time to live if shown, and purpose. Use a table such as this:

TypeHost/nameValue or destinationPurpose
A or AAAA@ or subdomainIP addressWebsite or application
CNAMEwww or another hostTarget hostnameWebsite, CDN, or platform mapping
MX@Mail serverIncoming email
TXT@ or service hostVerification valueEmail authentication or service verification
CAA@Certificate authority ruleCertificate issuance control
NS@Nameserver hostnamesDNS delegation

Also record subdomains used for newsletters, stores, forms, analytics, staging sites, or creator platforms. An apparently unused record may support a service that is checked only occasionally.

5. Website and email dependencies

Test the home page, key landing pages, forms, checkout or subscription paths, and at least one real mailbox. Note the expected web host, mail provider, SSL status, and any third-party services that use the domain. Keep a recent website backup and confirm that your hosting account can be accessed independently of the domain.

Cadence and checkpoints

Before the transfer

  1. Confirm the domain, current registrar, DNS provider, expiration date, and renewal setting.
  2. Verify registrant account access and the email address used for transfer notices.
  3. Export or document all DNS records, including email authentication records.
  4. Back up website files, databases, and important configuration.
  5. Check the domain’s lock status and possible eligibility restrictions.
  6. Obtain the authorization code through the current registrar.
  7. Create the destination registrar account with strong authentication.
  8. Choose a low-risk window and avoid making unrelated DNS or hosting changes.

During the transfer

Start the transfer from the gaining registrar and enter the domain and authorization code carefully. Watch both registrar accounts and the domain’s administrative email for approval, rejection, or verification messages. Record the date and each status change in a simple log.

Do not cancel the old hosting account or delete the DNS zone while the transfer is pending. If the nameservers remain the same, the existing DNS service should continue answering requests. If the new registrar requires a DNS zone to be created, compare it against your inventory before changing delegation.

After completion

  1. Confirm that the domain appears in the new registrar account.
  2. Check the expiration date and enable the intended renewal setting.
  3. Verify nameservers match the planned DNS provider.
  4. Compare important DNS records with your inventory.
  5. Open the website over both the main domain and the www version if both are used.
  6. Send and receive test messages from an external mailbox.
  7. Test forms, logins, redirects, payment flows, and other important paths.
  8. Confirm SSL certificates and monitoring tools report normally.
  9. Keep the old registrar account and DNS records available until verification is complete.

Use a transfer log with columns for date, registrar, status, message received, action taken, and next checkpoint. This turns a confusing support issue into a traceable change record.

How to interpret changes

Observed status or symptomLikely area to checkPractical response
Transfer cannot be startedDomain lock, eligibility restriction, incorrect extension, or incomplete account informationReview the current registrar’s transfer panel and ask support for the specific restriction.
Authorization code rejectedOld code, typing error, extra space, or regenerated codeRequest a fresh code and paste it carefully into the official transfer form.
Transfer is pendingRequired approval, verification, or registrar processingCheck both accounts and email notices; do not repeatedly submit new transfers.
Website stops resolvingNameserver change or missing A, AAAA, or CNAME recordCompare the active DNS zone with the pre-transfer inventory.
Website works but email failsMissing MX, TXT, or provider-specific recordsRestore the documented mail records and test from outside the organization.
Some users see the old siteCached or still-changing DNS responsesCheck authoritative nameservers and allow normal DNS caching to update before making further changes.

Separate registration status from DNS status. A domain can be successfully transferred while DNS is misconfigured, and DNS can remain healthy while a transfer is still pending. Checking these layers independently prevents the wrong fix.

Rollback plan

A transfer itself may not be reversible in the same way as a software deployment, so define a service rollback instead. Keep the original DNS zone intact, retain access to the old registrar until the website and email are verified, and know which nameservers and records should be restored if a new DNS configuration fails. If you changed nameservers, switching back to the previously working DNS provider may restore service, but make that change only after confirming the old zone is still available. Document every change and avoid deleting accounts until the observation period is over.

If email is business-critical, prioritize restoring MX and authentication records. If the website is affected, compare the active A and CNAME records with the known-good inventory. For a complex failure, pause additional changes and contact the registrar or DNS provider with your domain, timestamps, screenshots, and the exact symptom.

When to revisit

Review this checklist before every domain transfer, registrar consolidation, ownership change, or DNS-provider migration. Even if no move is planned, revisit the inventory monthly or quarterly for domains that support active publishing, newsletters, memberships, or revenue. Confirm that account access, renewal settings, nameservers, DNS records, backups, and responsible contacts are still current.

Update the workflow whenever a registrar changes its dashboard, authorization-code process, security controls, transfer notices, or terminology. Recheck it when the domain extension’s registry rules change, when a new email or hosting provider is introduced, or after an incident involving an expired domain, lost mailbox, or unexpected DNS change.

For your next move, begin with the DNS inventory rather than the transfer button. Assign one person to monitor registrar messages, another checkpoint for website and email testing, and a final review date for removing obsolete accounts. That small routine makes it easier to move a domain safely, preserve continuity, and manage future renewals with confidence.

For related planning, see the domain renewal and expiration guide, the guide to pointing a domain to web hosting, and the website backup and recovery plan.

Related Topics

#domain-transfer#DNS#registrars#website-migration#email-continuity
V

Viral Domains Editorial Team

Domains and Web Hosting Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.