Domain Transfer Checklist: How to Move a Domain Without Downtime

Overview

If your goal is to move domain without downtime, the most important thing to understand is this: a registrar transfer is not the same as moving web hosting. In many cases, your website stays on the same server and your DNS records keep doing the same job. What changes is the company that manages the domain registration.

That distinction matters because many transfer problems come from changing too much at once. A domain transfer, DNS update, hosting migration, email move, and SSL certificate setup can all be done together, but combining them increases the chance of errors. If uptime matters, the safest approach is usually to transfer the registration first, keep DNS unchanged during the process, and only then make separate hosting or email changes.

Use this domain transfer checklist before you start:

• Confirm you have access to the current registrar account and the administrative contact email.
• Check whether the domain is eligible for transfer and not close to expiration.
• Review all DNS settings, especially A, CNAME, MX, TXT, and nameserver records.
• Identify where your website, email, and any third-party services currently depend on the domain.
• Disable the transfer lock when you are ready.
• Request or copy the domain auth code if your extension requires one.
• Start the transfer at the new registrar with the exact domain name.
• Approve transfer emails promptly.
• After completion, re-enable domain lock, confirm WHOIS privacy settings, and verify renewal preferences.

For readers who are still sorting out the larger picture of domain and hosting, it may help to review a broader launch workflow in How to Start a Website: Domain, Hosting, DNS, SSL, and Email Setup Checklist. If your move is tied to a larger platform decision, Website Builder vs WordPress vs Hand-Coded Site: Which Is Best for Your Goals? is also a useful companion.

Checklist by scenario

This section gives you reusable domain transfer steps based on the type of move you are making. Start with the general checklist, then follow the scenario that matches your setup.

Scenario 1: Registrar transfer only, with no hosting or email changes

This is the cleanest case and usually the best option if uptime is your priority.

1. Inventory your current setup. Note your current registrar, expiration date, nameservers, DNS host, web host, and email provider. Take screenshots or export zone records if possible.
2. Verify the admin email works. Transfer approvals often go to a contact address tied to the domain registration. If that inbox is unavailable, fix that before doing anything else.
3. Check expiration timing. Avoid starting a transfer at the last minute. A domain close to expiration adds pressure and reduces room for delays.
4. Leave nameservers unchanged. If your DNS is already working, do not switch nameservers just because you are changing registrars. This is one of the simplest ways to avoid downtime.
5. Unlock the domain. Most registrars place a transfer lock on domains by default. Remove it only when you are ready to proceed.
6. Get the domain auth code. This may also be called an EPP code or authorization code, depending on the registry and interface.
7. Start the transfer at the new registrar. Enter the domain, submit the auth code if required, and complete the checkout.
8. Approve confirmation messages. Watch both your inbox and spam folder. Delays here are common.
9. Wait for completion. During this stage, your website should continue working if DNS stays unchanged.
10. After transfer, review settings. Re-enable the lock, confirm contact details, check WHOIS privacy, and verify auto-renew choices.

If you want a clearer view of transfer pricing versus renewal pricing before choosing a registrar, see Domain Name Pricing Guide: Registration vs Renewal vs Transfer Costs by TLD.

Scenario 2: Transfer domain and move DNS management to the new registrar

This adds complexity because DNS changes can affect website hosting, email, subdomains, verification records, and third-party tools.

1. Export or copy every existing DNS record. Do not rely on memory. Record A, AAAA, CNAME, MX, TXT, SRV, and any custom records you use.
2. Create the same zone at the new DNS host first. Before switching nameservers, recreate the records exactly.
3. Pay special attention to email records. MX, SPF, DKIM, and verification TXT records are easy to miss and can interrupt delivery.
4. Check TTL values if you plan ahead. Lowering TTL in advance can make later DNS changes propagate more predictably, though this only helps if done before the switch.
5. Transfer the domain registration. The transfer itself can happen while the domain still uses the old nameservers.
6. Only change nameservers after the new zone is ready. Switching too early is a common cause of downtime.
7. Monitor site and email after the nameserver change. Test homepage access, www/non-www behavior, contact forms, and mailbox delivery.

If you need a refresher on common records, How to Connect a Domain to Microsoft 365, Google Workspace, and Web Hosting Using DNS Records can help you map what each record does.

Scenario 3: Transfer domain while also moving web hosting

This is where people often confuse domain transfer with website migration. Treat them as separate tasks even if they happen in the same week.

1. Build and test the new hosting environment first. Do not start by moving the domain. Get the new hosting account ready and verify the site there using a temporary URL, preview domain, hosts file method, or staging environment.
2. Keep the domain pointed at the old host until the new site is ready. This preserves uptime while you test.
3. Transfer the domain registration without changing DNS. Let the registrar transfer complete while the live site remains on the current DNS path.
4. Once the new host is confirmed, update DNS records. Change A records or nameservers only after you know the new site works.
5. Check SSL after the DNS change. SSL can fail temporarily if the certificate is not installed on the new host before traffic arrives.
6. Monitor closely for mixed-content issues, redirect loops, and caching artifacts.

If you are comparing hosting environments before the move, Best Cheap Web Hosting 2026: What You Actually Get at Entry-Level Prices and Best Domain and Hosting Bundles 2026: Compare Convenience, Control, and Total Cost can help frame convenience versus control.

Scenario 4: Transfer domain with active business email

Email is the part most likely to cause real disruption. A website outage is visible and usually fixed quickly. Email problems can be quieter and more expensive.

1. Identify your email provider. Make sure you know whether email is handled by your web host, Microsoft 365, Google Workspace, or another platform.
2. Document all email-related DNS records. This includes MX, SPF, DKIM, DMARC, autodiscover, and any service-specific CNAMEs.
3. Do not assume the new registrar will import them. Many do not, or they do so inconsistently.
4. Test sending and receiving before the move. This gives you a baseline.
5. During transfer, avoid changing DNS unless necessary. The fewer variables you touch, the lower the risk.
6. After any DNS move, test again from external accounts. Send to and from a few major providers if possible.
7. Check mailing lists, forwarding, and form notifications. These are often forgotten even when primary mailboxes work.

What to double-check

Before and after the transfer, a small review can prevent most avoidable issues. Use this as your final pass.

Account access and ownership

• You can log into both the old and new registrar accounts.
• Your contact email is current and monitored.
• The domain is registered in the correct legal or business name where relevant.
• You have saved invoices or proof of ownership if needed later.

DNS settings

• Nameservers are exactly what you expect.
• A and CNAME records point to the correct hosting environment.
• MX records still point to the active email provider.
• TXT records for SPF, DKIM, verification, and third-party services are present.
• Subdomains used for landing pages, shop systems, or support tools still resolve.

Website behavior

• The root domain and www version both load correctly.
• HTTPS works without certificate warnings.
• Primary redirects still behave as intended.
• Forms, checkout, login, and API-connected features still function.

Registrar settings

• Domain lock is turned back on after the transfer completes.
• WHOIS privacy is enabled if you want it and if your setup supports it.
• Auto-renew is set the way you intend, not just left at the default.
• Billing details are current so the domain does not lapse later.

For a broader primer on privacy settings, see WHOIS Privacy Explained: What It Hides, What It Doesn't, and When You Need It.

Common mistakes

Most transfer failures are not dramatic technical problems. They are usually process mistakes. These are the ones worth avoiding.

Changing registrar, hosting, email, and DNS all at once

It is tempting to do a full cleanup in one session. In practice, separating the registrar transfer from hosting and email moves gives you cleaner troubleshooting and fewer unknowns.

Starting too close to expiration

A domain transfer is not something to leave for the final days before expiry. Even when things go smoothly, approvals and processing take time. Give yourself margin.

Ignoring the admin contact inbox

If the transfer confirmation goes to an old email address or one tied to the domain you are actively changing, you can trap yourself in a loop. Make sure you can receive messages before beginning.

Forgetting that email depends on DNS

Many site owners focus on the homepage and forget MX and TXT records. The website can stay online while email silently breaks. Always review mail routing separately.

Assuming the new registrar will mirror your old DNS perfectly

Even if import tools exist, review every record manually. Small differences matter, especially for email authentication, third-party verifications, and subdomains.

Leaving security settings unfinished after the move

Once the domain arrives at the new registrar, lock it again, confirm privacy settings, and review who in your team has access. A completed transfer is the right time to tighten controls.

Using the transfer as a substitute for due diligence

If you are moving because you are unhappy with your provider, make sure the new registrar actually fits your needs. Compare interface quality, support, renewal practices, DNS tools, and account security. If you are still choosing where to register or transfer, How to Buy a Domain Name Safely: Availability Checks, Ownership, and Checkout Red Flags is a useful related read.

When to revisit

A domain transfer checklist is not something you use once and forget. Revisit it whenever your domain setup changes or your risk tolerance gets lower.

Practical times to review this process include:

• Before renewal season or annual planning. If you manage several domains, that is a good time to consolidate registrars, review renewal settings, and decide whether a transfer still makes sense.
• Before changing web hosting. A coming hosting migration is the right moment to separate domain registration tasks from DNS and server changes.
• Before launching business email or moving providers. Email raises the cost of DNS mistakes, so refresh your checklist before you touch anything.
• When account access changes. Team turnover, agency offboarding, or a business restructure are good reasons to verify registrar ownership and transfer readiness.
• When workflows or tools change. A new registrar interface, a new DNS provider, or a different website hosting stack can change the exact order of operations even if the core logic stays the same.

If you want a simple action plan, use this one:

1. List every domain you own and where each one is registered.
2. Record nameservers, DNS host, web host, and email provider for each domain.
3. Mark which domains are safe to transfer now and which should wait because of expiration timing or active projects.
4. Create a saved DNS backup before any move.
5. Transfer one low-risk domain first if you are using a new registrar for the first time.
6. After completion, standardize security settings and renewal reminders across your portfolio.

The safest domain transfer steps are usually the least exciting ones: document first, change one layer at a time, and verify every dependency after the move. That approach may feel slower, but it is the most reliable way to move a domain without downtime.