Domain Transfer Checklist: How to Move a Website Without Losing Email or Traffic
domainsregistrarsdomain transferDNSemailwebsite migration

Domain Transfer Checklist: How to Move a Website Without Losing Email or Traffic

HHelps.website Editorial Team
2026-11-07
6 min read

Use this domain transfer checklist to move registrars safely while protecting DNS, email, SSL, website access, and renewal settings.

A domain transfer can be routine, but changing registrars without preparation may interrupt email, expose DNS mistakes, or create avoidable downtime. This reusable domain transfer checklist explains how to move a domain safely while keeping your website, mailboxes, security records, and traffic working as expected.

Overview

A registrar transfer moves the registration management of a domain from one registrar to another. It does not automatically move your website files, hosting account, WordPress installation, email mailboxes, or DNS services. Those parts may remain where they are, so the safest approach is to separate the migration into two activities: transferring the domain registration and preserving the services connected to the domain.

Before starting, identify which provider currently handles each function:

  • Registrar: manages the domain registration, renewal, transfer lock, and authorization code.
  • DNS provider: publishes records such as A, CNAME, MX, TXT, and NS records.
  • Web host: serves the website and may provide the server IP address or target hostname.
  • Email provider: handles mailboxes and typically depends on MX, SPF, DKIM, and sometimes DMARC records.
  • SSL provider or hosting platform: supports HTTPS certificates and domain verification.

If you are unsure which service controls DNS, look at the domain's nameserver entries in the current registrar account or use a trusted DNS lookup tool. For a record-by-record explanation, see DNS Records Explained: How to Set Up A, CNAME, MX, TXT, and NS Records.

Checklist by scenario

Scenario 1: You are changing registrars but keeping the same website and DNS provider

  1. Confirm ownership access. Sign in to the current registrar, verify the registrant contact details, and make sure you can receive messages sent to the administrative or registrant email address.
  2. Record the current configuration. Export or copy the full DNS zone, including A, AAAA, CNAME, MX, TXT, SRV, and verification records. Save the current nameservers, renewal date, auto-renewal setting, and domain contact information.
  3. Check transfer eligibility. Review the current registrar's transfer status and any applicable restrictions. A recently registered, transferred, or contact-updated domain may have a transfer hold depending on the domain extension and registrar rules.
  4. Disable the transfer lock. Registrars may call this a registrar lock, transfer lock, or domain lock. Do this only when you are ready to submit the transfer.
  5. Request the authorization code. The code may be called an EPP code, AuthInfo code, or transfer code. Treat it as sensitive account information and do not publish it in a ticket or public document.
  6. Start the transfer at the new registrar. Enter the exact domain name and authorization code, then review the destination account and contact details before confirming.
  7. Keep the existing nameservers unchanged. If the DNS provider is staying the same, do not replace the nameserver entries merely because the registrar is changing. This is one of the most important steps for avoiding an accidental website or email outage.
  8. Approve and monitor the transfer. Complete any confirmation steps shown by either registrar. Check the transfer status from both accounts rather than assuming submission means completion.

Scenario 2: You are moving the registrar and DNS provider

Moving both services requires more planning because the new DNS provider must contain the correct records before nameservers change. Recreate the zone first, including website records, email records, verification tokens, subdomains, redirects, and third-party integrations. Compare the new zone against the saved copy line by line.

Lowering DNS time-to-live values before a planned nameserver change may help some resolvers refresh sooner, but it does not instantly update every cached response. Make the change with enough lead time, and leave the old DNS service active until the new nameservers are serving the complete zone. For practical nameserver guidance, consult the DNS Settings Guide.

Scenario 3: You are moving the domain and website to a new host

Complete the website migration separately from the registrar transfer whenever possible. Back up the site and database, copy the files, test the new hosting environment, and confirm the target IP address or hostname. If the site uses WordPress, review the WordPress Site Maintenance Checklist before changing DNS.

Keep the old host available until the new site has passed functional checks. Test the homepage, key pages, forms, logins, checkout or other critical workflows, redirects, robots.txt, and XML sitemap. This separation makes it easier to identify whether a problem comes from hosting, DNS, or the registrar transfer.

What to double-check

  • Email continuity: Confirm that MX records still point to the email provider. Preserve SPF, DKIM, and DMARC records, and send test messages in both directions after any DNS change.
  • Website records: Verify the root-domain A or AAAA record and the www CNAME or equivalent record. Check important subdomains such as app, shop, staging, or portal.
  • HTTPS: Confirm that the new host or platform can issue or renew the SSL certificate for every required hostname. Test both HTTP-to-HTTPS redirection and certificate coverage.
  • Nameservers: Check that the domain uses the intended nameservers after the transfer. A registrar change should not silently replace DNS delegation.
  • Renewal settings: Confirm the expiration date, auto-renewal preference, payment method, and renewal contact at the new registrar. Do not assume the old registrar's settings carry over.
  • Privacy and contact details: Review registration data, privacy settings, and the account's recovery email and multi-factor authentication. Use a monitored address that is independent of the domain being transferred when practical.
  • Access and documentation: Remove unnecessary users or API tokens from the old account, store the new registrar's support details, and record the final nameservers and renewal date.

Common mistakes

Changing nameservers unnecessarily. A registrar transfer does not require a DNS migration. Keeping the existing nameservers is usually the least disruptive option when hosting and DNS are unchanged.

Transferring before checking email records. The website may appear healthy while mail delivery fails. Save and verify MX and authentication records before making changes.

Letting the domain expire during the process. Start with enough time to resolve account verification, payment, or eligibility issues. A transfer is not a substitute for renewing a domain that is approaching expiration.

Testing only from one device. Check the site, email, and HTTPS from more than one network or use external DNS and uptime checks. Cached DNS responses can hide a delegation problem.

Deleting the old account too early. Keep access to the previous registrar, DNS provider, and host until the transfer is complete and all services have been verified.

Changing several systems at once without a rollback plan. If the registrar, nameservers, host, email provider, and WordPress installation all change together, troubleshooting becomes difficult. Stage the work and document the previous settings.

When to revisit

Use this checklist before every domain registrar migration, acquisition, ownership change, hosting move, or renewal audit. Revisit it before seasonal planning cycles if the domain supports a time-sensitive campaign or business process. It is also worth reviewing after changes to your email provider, DNS platform, hosting architecture, SSL process, or account security settings.

As a final action, schedule a short post-transfer review. Confirm the domain status, nameservers, website response, HTTPS certificate, email delivery, renewal date, and DNS records. Save the final configuration with the date and responsible account owner. If something fails, compare the current settings with that record and use a structured website troubleshooting checklist rather than making unrelated changes.

Related Topics

#domains#registrars#domain transfer#DNS#email#website migration
H

Helps.website Editorial Team

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