Domain Transfer Checklist: Move a Domain Safely Between Registrars
domain transferregistrarsEPP codedomain ownershipDNS continuity

Domain Transfer Checklist: Move a Domain Safely Between Registrars

VVarious Cloud Editorial Team
2026-11-15
6 min read

Use this domain transfer checklist to move registrars safely while preserving DNS, website, email, ownership, and renewal control.

A domain transfer moves your registration from one registrar to another, but it does not automatically move your website, email, DNS records, or hosting account. This domain transfer checklist helps you verify eligibility, preserve DNS continuity, obtain the authorization code, approve the transfer, and audit the result so you can move a domain without unnecessary downtime or loss of control.

Overview

Transferring a domain is usually an administrative change rather than a website migration. The domain remains the same, and its nameservers may continue pointing to the existing DNS provider throughout the process. That separation is what makes a carefully planned transfer possible without interrupting a website or business email.

Before starting, identify four separate systems:

  • Registrar: The company that manages the domain registration and renewal.
  • Registry: The domain extension’s central operator, where applicable.
  • DNS provider: The service hosting your A, AAAA, CNAME, MX, TXT, and other DNS records.
  • Hosting and email providers: The services running your website, applications, mailboxes, and related tools.

A transfer normally changes the registrar relationship. It does not by itself copy DNS zones, website files, databases, mailboxes, SSL certificates, redirects, or hosting subscriptions. Confirm the target registrar’s process and the applicable registry or industry rules before beginning, because eligibility, approval, contact verification, transfer locks, fees, and timing can vary by domain extension and registrar.

What to track

1. Record the current configuration

Create a small transfer record for each domain. Include the domain name, current registrar, target registrar, expiration date, registrar account owner, renewal setting, nameservers, DNS provider, and the people authorized to approve changes. Save a current export or written copy of the DNS zone if your provider supports it. Pay particular attention to MX, SPF, DKIM, and DMARC records if the domain supports business email.

Also document services that depend on the domain, such as website hosting, APIs, payment callbacks, verification records, staging environments, monitoring, and subdomains. This inventory gives you a baseline for post-transfer validation.

2. Check transfer eligibility

Review the domain’s status in the current registrar account. A registrar lock or client transfer prohibition generally needs to be removed before the transfer can proceed. Some domains may also be restricted because of a recent registration, a recent transfer, a registrant change, an unresolved dispute, an expired or suspended status, or extension-specific rules. Do not assume every domain follows the same requirements.

Verify that the administrative or registrant contact details are current and accessible. Transfer approval messages may be sent to an address associated with the registration. If contact information has recently changed, check whether the registrar or registry applies a temporary transfer restriction or requires an additional confirmation.

3. Obtain and protect the authorization code

Request the domain authorization code, also called an EPP code, transfer key, or auth code, through the current registrar’s account or support process. Treat it like a credential: share it only with the target registrar’s official transfer workflow, avoid placing it in public tickets or chat channels, and request a replacement if you believe it has been exposed. Codes can expire or be regenerated, so use the current code when submitting the transfer.

4. Confirm what moves and what does not

ItemUsually transferred with the domain?Action to take
Domain registrationYes, if eligible and approvedStart the transfer at the target registrar and confirm the extension’s process.
Domain name and registration datesGenerally remain associated with the domainCheck the renewal or expiration date after completion.
DNS records and nameserversNo automatic copy should be assumedKeep the existing DNS service active and compare records before changing providers.
Website files, databases, and hostingNoLeave the hosting account in place unless you are performing a separate migration.
Email mailboxes and messagesNoKeep the email provider active and verify MX and authentication records.
SSL certificatesNoConfirm certificate coverage and renewal settings with the hosting or certificate provider.
Privacy settingsNot consistentlyReview privacy behavior and contact display settings at the target registrar.
Auto-renewal and billingNoConfigure payment details, renewal preferences, and account alerts again.

5. Submit, approve, and validate

Unlock the domain only when you are ready to submit the transfer. Enter the domain and authorization code at the target registrar, then monitor both registrar accounts and the relevant contact inboxes for approval requests. Follow the official confirmation path rather than links from unexpected messages.

When the transfer completes, confirm that the domain appears in the correct account, the nameservers are unchanged unless you intentionally changed them, DNS answers are correct, and the website and email work from more than one network. Check HTTPS, redirects, important subdomains, sending and receiving mail, and domain renewal settings. If you use a DNS propagation checker, treat it as a diagnostic aid rather than a substitute for testing the services themselves.

Cadence and checkpoints

Use a transfer checklist at three points: before submission, while the transfer is pending, and after completion.

Before submission

  • Confirm the domain spelling and target registrar account.
  • Record nameservers, DNS records, renewal date, and current billing settings.
  • Verify contact access and check for registrar or registry restrictions.
  • Confirm the authorization code is current.
  • Keep the existing hosting, DNS, and email services active.

While pending

  • Monitor approval emails and the transfer status in both accounts.
  • Do not make unrelated DNS or ownership changes unless necessary.
  • Record any error message exactly; it can indicate a lock, code problem, contact issue, or extension-specific restriction.
  • Watch the website and email through the expected transfer window.

After completion

  • Verify registrar ownership, domain status, nameservers, expiration date, and auto-renewal.
  • Review privacy, account security, recovery contacts, and user permissions.
  • Test the apex domain, www host, key subdomains, HTTPS, forms, and email.
  • Remove outdated payment details or access from the former registrar when appropriate.

How to interpret changes

A successful transfer with no change in nameservers should normally leave the website and email architecture unchanged. If the site stops resolving, compare the active nameservers first. If the nameservers are correct but records are missing, the issue may be a DNS zone problem rather than the registration transfer itself.

If email fails, inspect MX records and the related SPF, DKIM, and DMARC records. If HTTPS fails, verify that the certificate still covers the domain and that the hosting platform recognizes the domain. If the domain is not visible in the new account, check the transfer status and account identity before attempting another transfer.

Do not interpret a low transfer price or an apparently completed order as proof that the domain is fully configured. A transfer can complete while auto-renewal is disabled, privacy settings differ, billing is incomplete, or a critical DNS record was overlooked. Treat the post-transfer audit as part of the transfer, not as optional cleanup.

When to revisit

Revisit this checklist before every domain transfer and whenever ownership, registrar, DNS provider, hosting provider, or email provider changes. For a domain portfolio, perform a monthly or quarterly review of registrar access, expiration dates, auto-renewal, nameservers, DNS ownership, privacy settings, and recovery contacts. This recurring review can reveal abandoned domains, duplicate accounts, expired payment methods, or records managed by a former provider.

Refresh the operational details of this process at least annually and whenever a registrar or registry changes its transfer workflow. Recheck requirements after a recent registration, ownership update, transfer attempt, lock change, or authorization-code expiration. Policies, approval methods, transfer fees, privacy behavior, and expected timelines can differ, so use the current registrar and registry instructions for the domain extension involved.

For your next transfer, start by exporting the DNS record list and writing down the current nameservers. Then confirm eligibility, unlock only when ready, obtain a fresh authorization code, submit the transfer, monitor approval messages, and complete the post-transfer audit. Keeping these steps together helps preserve control of the domain while separating registration work from any later hosting or website migration.

Related Topics

#domain transfer#registrars#EPP code#domain ownership#DNS continuity
V

Various Cloud Editorial Team

Technical SEO 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.