Transfer a Domain Without Downtime: Step-by-Step Checklist + Registrar Policy Comparison
domain transferDNS setupmigration checklistregistrar comparisonsite launch

Transfer a Domain Without Downtime: Step-by-Step Checklist + Registrar Policy Comparison

CClaimed.site Editorial Team
2026-11-11
7 min read

Move a domain without taking your site offline using a DNS-first checklist, registrar policy worksheet, testing plan, and rollback steps.

Moving a domain does not have to take a website offline. This guide gives you a reusable domain transfer checklist for preparing DNS, confirming registrar requirements, choosing between a nameserver change and a registrar transfer, testing the result, and rolling back safely if something goes wrong.

Overview

A domain transfer moves the registration from one registrar to another. It does not automatically move your website files, database, email service, SSL configuration, or hosting account. Those are separate parts of a website migration.

You can usually keep a site available during a registrar transfer by leaving the domain’s existing DNS configuration unchanged. The main risk comes from changing nameservers, deleting DNS records, or allowing a transfer to begin before the new provider is ready. Treat the transfer as two related but separate projects: first preserve or reproduce the DNS setup, then move the registration if you still need to.

Before starting, record:

  • The current registrar and the account owner’s login details.
  • The domain’s expiration date and transfer status.
  • Current nameservers and every important DNS record.
  • Website, email, payment, analytics, CDN, and verification services connected to the domain.
  • Who can approve a transfer and who receives registrar notifications.
  • A tested backup of the website and database. See the website backup and restore checklist for a repeatable process.

Do not assume that transferring a domain also transfers DNS hosting. Some registrars provide DNS management, while others let you use an external DNS provider. Confirm where the authoritative DNS zone is hosted before changing anything. For a record-by-record review, use DNS Records Explained.

Checklist by scenario

Scenario 1: Transfer the registration but keep the current website and DNS

This is the lowest-change approach. It is appropriate when the website and email already work and your main goal is to move the domain to a different registrar.

  1. Capture the current configuration. Export or document the DNS zone, nameservers, forwarding rules, subdomains, MX records, TXT records, and custom verification records.
  2. Confirm eligibility. Check whether the domain is locked, subject to a recent registration or transfer restriction, under an ownership-change review, or missing a required authorization code. The exact rules depend on the registrar and domain extension.
  3. Verify account access. Make sure you can access both the current registrar and the administrative contact email. Check that contact details are accurate before requesting the transfer.
  4. Ask for the authorization code. The current registrar may call this an EPP code, transfer code, or authorization key. Copy it carefully and use it only through the new registrar’s official transfer workflow.
  5. Keep the existing nameservers in place. Do not change them merely because the registration is moving. This allows the current website and email DNS to continue answering while the transfer is processed.
  6. Start the transfer at the new registrar. Review the total term added, renewal settings, privacy options, and any transfer-specific conditions before payment or confirmation.
  7. Approve legitimate confirmation messages. Check the sender and use the registrar’s account dashboard where possible. Never provide a password or authorization code in response to an unexpected request.
  8. Test after completion. Confirm the domain status, nameservers, DNS records, website, forms, email sending, email receiving, redirects, and SSL certificate.

Scenario 2: Move the website to new hosting but keep the registrar

A registrar transfer is not required to change hosts. Build and test the site on the new hosting account first, then update only the records needed to point traffic to the new server. Depending on the host, that may mean changing an A record, a CNAME record, or the nameservers.

Lower the DNS TTL before the change if your DNS provider allows it. A shorter TTL can make future record changes take effect sooner for resolvers that honor the value, but it cannot remove every form of caching. Make the change during a monitored maintenance window, keep the old hosting account available, and do not cancel it until the new site and email have been tested.

For the detailed connection sequence, see How to Connect a Domain to Web Hosting.

Scenario 3: Move the registrar and hosting at the same time

Separate the changes whenever possible. First copy the DNS zone to the destination DNS provider or hosting account. Then verify the new website on a temporary URL, staging address, or hosts-file test. Transfer the registration while the old nameservers remain active. After the registrar transfer is complete, change nameservers or individual records only when you are ready to direct traffic to the new host.

If business email is involved, preserve MX, SPF, DKIM, and DMARC records. A website may appear healthy while email is silently interrupted. Record the existing values before editing them.

Registrar policy comparison worksheet

Policies, fees, transfer timing, privacy behavior, and forwarding features can change. Rather than relying on an old comparison, complete this table from each registrar’s current help pages and account screens immediately before moving a domain.

ItemCurrent registrarDestination registrarWhat to confirm
Transfer feeRecord current amount and renewal termRecord current amount and renewal termWhether the transfer includes an extension and which payment method is used
Typical completion timeRecord stated rangeRecord stated rangeWhether approval can speed completion and what can delay it
Transfer lockCheck account statusCheck destination requirementsWhether the domain must be unlocked and how the status is changed
Authorization codeFind request and delivery methodFind submission methodWhere the code is requested, how long it remains valid, and whether it is case-sensitive
WHOIS privacyRecord current settingRecord destination settingWhether privacy remains enabled, must be reselected, or varies by extension
DNS and forwardingRecord nameservers, records, and forwardsRecord available DNS, URL forwarding, and subdomain featuresWhether forwarding is preserved or must be rebuilt
Renewal settingsRecord auto-renew statusRecord auto-renew statusRenewal date, default setting, and notification contacts

Use the domain renewal costs guide to compare the transfer with the registrar’s longer-term renewal terms, not just the initial transfer charge.

What to double-check before and after the transfer

DNS and TTL

Save the complete DNS zone, including records that are easy to overlook: TXT records for email authentication, CNAME records for SaaS tools, SRV records for specialized services, and records for staging or regional subdomains. Confirm which provider is authoritative by checking the domain’s nameservers in the current registrar account or a trusted DNS lookup tool.

Do not delete the old DNS zone until the new zone has been tested and the transition is complete. If you are changing DNS providers, copy records first and compare them line by line.

Ownership, security, and privacy

Use a unique registrar password and multi-factor authentication. Confirm that the transfer lock is enabled again after a completed transfer if the new registrar does not enable it automatically. Review account recovery email addresses, delegate access, and notification settings.

WHOIS privacy is not identical across every domain extension or provider. Check the destination registrar’s current explanation for your specific extension, and confirm whether public contact information, verification messages, or ownership records are affected. More safeguards are listed in the domain security checklist.

Functional testing

  • Open the root domain and the www version over HTTPS.
  • Test important pages, redirects, forms, checkout steps, and login flows.
  • Send and receive test email from more than one mailbox.
  • Check SSL certificate coverage for the root domain, www, and critical subdomains.
  • Review analytics, search verification, advertising pixels, webhooks, and API callbacks.
  • Check both mobile and desktop versions.

Common mistakes and rollback checklist

The most common mistake is changing too many variables at once. A domain registrar transfer, hosting migration, nameserver change, CMS update, and email migration should not all happen without a separation plan. Another frequent error is cancelling the old hosting or DNS service immediately after the new account appears ready.

Watch for these failure points:

  • Starting a transfer with an outdated administrative email address.
  • Using an authorization code copied incorrectly or obtained from an unofficial message.
  • Changing nameservers without copying MX, TXT, or third-party verification records.
  • Assuming DNS propagation is complete because one device shows the new site.
  • Forgetting domain forwarding, subdomains, or non-website services.
  • Allowing auto-renewal or privacy settings to differ from the intended configuration.

If something breaks, use this rollback sequence:

  1. Identify whether the failure is registration, DNS, hosting, email, SSL, or application-related.
  2. Restore the last known-good DNS records or nameservers if they are still available.
  3. Keep the old host and DNS provider active while testing the correction.
  4. Check DNS from multiple networks and allow reasonable caching time before declaring the rollback complete.
  5. Review registrar notices and account status for a pending verification or transfer issue.
  6. Document the cause and the successful fix before attempting the next change.

A registrar transfer normally cannot be “rolled back” in the same way as a file deployment. If the registration has already moved, stabilize DNS first, then decide whether a new transfer is necessary.

When to revisit this checklist

Reuse this checklist before every registrar transfer, hosting migration, rebrand, domain consolidation, or major email-provider change. Revisit it before seasonal launches when a failed DNS change would affect campaigns or sales, and again whenever your registrar, host, DNS provider, or email platform changes its workflow.

Policy details should be checked at the time of action: transfer fees, authorization-code delivery, lock controls, privacy treatment, forwarding tools, and expected processing times are provider-specific and can change. Review the comparison worksheet quarterly if it is maintained as a site resource, and refresh it sooner after a registrar announcement or a change to applicable registration rules.

For your next migration, make a copy of this article’s checklist, fill in the provider-specific values, schedule a low-risk change window, and assign one person to monitor the website and email while another performs the transfer. That small amount of preparation is usually more valuable than trying to repair an incomplete DNS change after launch.

Related Topics

#domain transfer#DNS setup#migration checklist#registrar comparison#site launch
C

Claimed.site Editorial Team

Domains and Web Hosting Editors

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.