Domain Transfer Checklist: What to Prepare Before Moving to a New Registrar

Overview

If you plan to transfer domain to new registrar accounts, the safest approach is to separate the transfer itself from any other major change. A domain transfer changes where the registration is managed. It does not need to change your web hosting, DNS records, nameservers, or email provider at the same time.

That distinction matters. Many domain problems happen because owners try to do three jobs at once: move the registration, change nameservers, and switch hosting. Each task can be done successfully, but stacking them together makes troubleshooting harder. If something breaks, it becomes unclear whether the issue is related to the registrar move, DNS propagation, hosting, or mail routing.

A better method is to prepare a simple transfer plan:

• Document the current setup before changing anything.
• Confirm the domain is eligible to transfer.
• Retrieve the domain auth code and verify approval contacts.
• Preserve DNS settings so the website and email continue working.
• Start the transfer during a low-risk window, not during a launch, sale, or campaign.
• Verify the domain after the move and confirm renewal settings.

In most cases, your pre-transfer checklist should cover five areas: registrar status, DNS management, website hosting, email delivery, and billing. If even one of those areas is undocumented, pause and fill the gap first.

Before you begin, make a record of the following:

• Current registrar name and account access details
• Domain expiration date and renewal settings
• Whether privacy protection is enabled
• Current nameservers
• All active DNS records, including A, CNAME, MX, TXT, NS, and any subdomains
• Where email is hosted and which MX records it depends on
• Any SSL, verification, or third-party service records tied to the domain

If you need a refresher on DNS record types, see DNS Records Explained: When to Use A, CNAME, MX, TXT, NS, and SRV. That article is useful to revisit before exporting or recreating records at a new provider.

Checklist by scenario

This section gives you a reusable domain transfer checklist by common situation. Start with the scenario that matches your setup, then apply the universal steps underneath it.

Scenario 1: You are only moving the registrar

This is the cleanest case. Your hosting stays where it is, your DNS remains unchanged, and you simply want better pricing, support, or account management.

• Confirm the domain is not near an important campaign, launch, or renewal deadline.
• Check whether the domain is unlocked. If not, unlock domain transfer in the current registrar dashboard.
• Request or retrieve the domain auth code.
• Verify the administrative contact email can receive approval messages.
• Note the current nameservers and confirm they will remain the same after transfer.
• Take a full screenshot or export of all current domain settings.
• Start the transfer at the new registrar and complete any email approvals promptly.
• After completion, verify nameservers are unchanged and auto-renew is configured the way you want.

This scenario is usually the lowest risk because the DNS management layer does not change.

Scenario 2: You are moving registrar and DNS management

This is still manageable, but it requires more preparation. If the domain currently uses registrar DNS and you plan to use DNS at the new registrar or another provider, recreate the zone file before changing nameservers.

• Copy every DNS record from the current zone, including root records, www, mail, verification TXT records, and subdomains.
• Reduce TTL values in advance if your current provider allows it and if you expect to update records soon.
• Create the full DNS zone at the destination before the transfer or nameserver change.
• Double-check priority values on MX records and exact TXT strings for SPF, DKIM, or verification records.
• Do not remove the old DNS zone until the new nameservers are confirmed live and working.
• Test website, email, and key subdomains after the nameserver update.

If you are changing nameservers, it helps to review expected timing in How Long Does DNS Propagation Take? A Practical Timeline by Record Type. That context makes it easier to plan around temporary cache differences.

Scenario 3: You are moving registrar while keeping email at a third-party provider

This is a common source of disruption because website owners often focus on the homepage and forget the mailbox. Domain transfer itself should not break mail, but DNS changes often do.

• Identify where email is hosted now.
• Record all MX records exactly as they appear.
• Document SPF, DKIM, and DMARC TXT records if used.
• Check for autodiscover or mail subdomain records.
• Confirm the admin contact email used for transfer approvals is not dependent on a mailbox that may be affected by DNS changes.
• If possible, use a secondary email address outside the transferring domain for critical transfer notices.

If email is business-critical, avoid combining the registrar transfer with a mail migration. Keep one variable stable while changing the other.

Scenario 4: You are preparing to move domain without downtime during a hosting migration

Here the domain transfer is only one part of a broader website migration. The safest order is usually: prepare the new hosting, test the site, update DNS when ready, and transfer the registrar only when the live environment is stable.

• Set up the new hosting account fully before touching the domain registration.
• Test the new site using a temporary URL, hosts file method, or provider preview tool.
• Make sure SSL is ready for the domain on the destination hosting.
• Review all DNS records needed to point the domain and subdomains correctly.
• Plan the DNS cutover separately from the registrar transfer when possible.
• Once the site is stable, complete the registrar move as an administrative cleanup step.

This sequence reduces confusion and is often the best way to move domain without downtime.

Universal pre-transfer checklist

Regardless of scenario, run through these steps before you click transfer:

1. Check eligibility. Make sure the domain is in a transferable state according to the current registrar's rules and status indicators.
2. Review renewal timing. Avoid starting a transfer when the domain is about to expire or when your team may miss approval emails.
3. Unlock the domain. Many registrars prevent transfer by default until you remove the transfer lock.
4. Get the auth code. Store it securely and use the current code, not an older one.
5. Verify contact access. Confirm the registrant or administrative contact can receive and act on approval requests.
6. Back up DNS. Export or manually copy all records before any change.
7. Document nameservers. These are often the quickest clue when troubleshooting after transfer.
8. Review privacy and WHOIS-related settings. Some owners want to preserve current contact preferences after the move.
9. Pause unrelated edits. Do not change site hosting, mail routing, DNS provider, and registrar account all at once unless there is a compelling reason.
10. Plan post-transfer checks. Decide who will verify website, email, SSL, and renewal settings after completion.

What to double-check

Once the transfer is started, most problems come from a small set of overlooked details. These are the items worth checking twice.

1. Expiration and renewal timing

A transfer should not be treated as a last-minute renewal strategy unless you understand the timing and the registrar workflow. If the domain is close to expiration, complete your checks early and monitor the process carefully. It is also wise to verify the renewal pricing and settings at the destination registrar once the move is complete. For broader budgeting context, see Domain Registration Cost Guide: First-Year vs Renewal Pricing by Domain Type.

2. Nameserver continuity

If your plan is only to transfer the registration, your nameservers should usually remain exactly the same. A changed nameserver setting can redirect the domain to an empty DNS zone, parked page, or wrong host. Write down the current nameservers before you begin and compare them after the transfer completes.

3. Full DNS record coverage

Many owners copy the main A record and www record but forget mail, verification, or service-specific entries. Check for:

• Root domain A or AAAA records
• www CNAME
• MX records
• SPF, DKIM, and DMARC TXT records
• Verification TXT records for analytics, search, mail, or SaaS tools
• Subdomains for apps, stores, help centers, or APIs

The goal is not just to keep the homepage online. It is to preserve the entire working domain environment.

4. Approval email path

Transfer approvals often arrive by email. If the domain's own email service is unstable, inaccessible, or also being migrated, use an alternate address for monitoring where possible. At minimum, confirm who receives notices and who is responsible for actioning them quickly.

5. SSL and redirects

A registrar transfer alone does not usually affect SSL on your hosting, but any DNS change can. If you are also moving hosting, verify that the certificate is in place and that redirects from non-www to www, or HTTP to HTTPS, still behave correctly after cutover.

6. Existing third-party dependencies

Modern domains often support more than one website. A single domain might connect to forms, email marketing, CDN services, transactional mail, payment verification, or support portals. Search your current DNS zone for clues before assuming a record is no longer needed.

Common mistakes

If you want a short list of what causes most transfer pain, it is this section. These mistakes are common, avoidable, and expensive in terms of time.

Trying to transfer during a launch or campaign

Do not schedule a domain transfer while launching a new site, running paid traffic, or approaching a seasonal sales period unless there is no alternative. Administrative changes are best made during quiet windows.

Forgetting email records

A website outage is visible immediately. Email failures can go unnoticed for hours or days. Always review MX and TXT records before any DNS-related move.

Starting without a DNS backup

Even if you believe the destination registrar will import settings, keep your own copy. Screenshots, exported zone files, and a plain-text record list are all useful when a field is entered incorrectly.

Changing too many systems at once

If you are changing registrar, hosting, DNS provider, and CMS configuration together, troubleshooting becomes guesswork. Stage the work into separate steps.

Ignoring subdomains and verification records

Tools such as analytics platforms, search tools, SaaS apps, and email services often depend on TXT or CNAME records that are easy to miss. If those records disappear, the main site may still load while important services quietly fail.

Not confirming the transfer completed cleanly

Once the transfer is done, log in to the new registrar and verify:

• The domain appears in the correct account
• Nameservers are correct
• Contact details are accurate
• Auto-renew settings match your preference
• Domain lock is re-enabled if desired

A completed transfer is not the end of the process. It is the start of a short verification window.

When to revisit

This checklist is worth revisiting any time the underlying setup changes. Domain transfers are infrequent for many businesses, which is exactly why small details are easy to forget between moves.

Review this checklist again in the following situations:

• Before transferring any domain to a new registrar
• Before changing nameservers or DNS providers
• When moving web hosting or planning a website migration
• When changing email providers or domain-based mail routing
• Before peak trading periods, product launches, or seasonal campaigns
• When your registrar workflow, account permissions, or tooling changes

For teams managing several domains, turn this article into a repeatable internal process. Create a transfer worksheet that includes registrar access, auth code handling, DNS backups, approval contacts, and final verification checks. That small habit can prevent last-minute guesswork.

To make your next move simpler, take these action steps now:

1. Create a current inventory of every domain you manage.
2. Record each domain's registrar, expiration date, nameservers, and DNS host.
3. Store a fresh DNS export or manual backup for important domains.
4. List where email is hosted for each domain and which records support it.
5. Decide on a preferred transfer window outside of launch periods.
6. Bookmark your DNS reference articles so they are easy to revisit before changes.

If your transfer plan includes DNS edits, keep these references handy: DNS Records Explained: When to Use A, CNAME, MX, TXT, NS, and SRV and How Long Does DNS Propagation Take? A Practical Timeline by Record Type. Both are useful companions when you need to connect domain and hosting cleanly and reduce the risk of interruption.

The main principle is simple: prepare first, transfer second. When you treat domain registration, DNS management, hosting, and email as connected systems instead of separate boxes, transfers become much more predictable.