How to Transfer a Domain to a New Registrar Without Downtime
domain transfersregistrar migrationDNS continuityauthorization codedomain management

How to Transfer a Domain to a New Registrar Without Downtime

RRegistrars.shop Editorial Team
2026-11-13
7 min read

Learn how to transfer a domain without downtime, preserve DNS, estimate costs, handle approval steps, and recover from common failures.

Moving a domain does not have to interrupt your website or email. This domain transfer guide explains how to check eligibility, preserve DNS, estimate the real cost, complete the move, and recover safely if the transfer stalls.

Overview

A domain transfer moves the registration record from one registrar to another. It does not automatically move your website files, email inboxes, databases, or hosting account. In many cases, your site and email can continue working throughout the transfer because the domain’s existing nameservers remain unchanged.

The safest approach is to separate the project into two parts: transfer the registration, and preserve or intentionally change the DNS configuration. Before beginning, identify where your DNS is hosted. It may be managed by the current registrar, your web host, a dedicated DNS provider, or a service such as a website builder. If you change registrars while leaving the nameservers and DNS records intact, visitors should continue reaching the same services. If you change nameservers at the same time, the risk of configuration errors is higher.

A transfer is commonly started from the receiving registrar, but the exact labels vary. Look for controls such as “Transfer domain,” “Move domain,” “Transfer in,” “Unlock,” and “Authorization code.” Keep access to the registrant or administrative email address available, and do not cancel the old registrar account until the transfer and post-transfer tests are complete.

For related ownership and setup checks, see How to Register a Domain Name for a Business. If you manage several domains, the portfolio guidance in Bulk Domain Registration for Businesses can help you plan the migration in batches.

How to estimate

Estimate the transfer before you submit it, rather than judging the cost from the advertised transfer price alone. Use this simple calculation:

Total transfer budget = transfer charge + required renewal or added term + optional services + tax or currency costs − applicable credits

The receiving registrar may charge a transfer fee, include an extension of the registration term, or present both together. Do not assume that every extension, country-code domain, or newer top-level domain follows the same process. Check the checkout summary and the registrar’s terms for the specific domain extension.

Also estimate the operational cost. A single domain may require only a few minutes of DNS review. A business portfolio may require a spreadsheet, owner approvals, renewal-date checks, DNS exports, and a staged migration. If the domain is close to expiration, include time for troubleshooting and avoid scheduling the transfer immediately before a critical launch or campaign.

For a better long-term comparison, record the receiving registrar’s renewal price as a separate input. A low transfer price does not necessarily mean a low ongoing cost. The guide to registrar pricing and real total cost provides a useful framework for comparing promotional and renewal pricing.

Inputs and assumptions

Before opening the transfer screen, collect the following information:

  • Domain and extension: Confirm the exact spelling and whether it is a generic, country-code, or specialized extension.
  • Expiration date: Note the current registration term and allow enough time for troubleshooting.
  • Transfer eligibility: Check whether the domain is subject to a recent registration, transfer, or registrant-change restriction. The current registrar or registry documentation is the right place to confirm this.
  • Transfer lock: Make sure the domain is unlocked before requesting the transfer. Some registrars display this as a status switch; others require support assistance.
  • Authorization code: Request the current transfer, authorization, or EPP code. Treat it as sensitive account information and use the newest code supplied by the registrar.
  • Contact access: Confirm that the relevant account and domain contact email addresses work. Check spam and filtering rules during the transfer window.
  • DNS location: Record the current nameservers and export or copy important A, AAAA, CNAME, MX, TXT, and other records.
  • Services in use: List the website, email, verification records, redirects, APIs, and subdomains connected to the domain.
  • New registrar terms: Review the transfer fee, renewal pricing, privacy options, DNS tools, support process, and expiration handling.

Use this pre-transfer checklist:

  1. Back up or document the DNS zone.
  2. Verify the website and email work before the move.
  3. Confirm the domain is eligible and unlocked.
  4. Obtain the authorization code.
  5. Check the receiving registrar’s price and transfer requirements.
  6. Start the transfer with the exact domain name and current code.
  7. Approve any confirmation message sent to the authorized contact.
  8. Keep the existing nameservers unless you have deliberately prepared a new DNS setup.

DNS records have different jobs, so do not replace them casually. For reference, use the DNS records cheat sheet before editing an A record, CNAME, MX record, or TXT record.

Worked examples

Example 1: One business domain

Assume a business is moving one domain. For planning purposes only, enter the receiving registrar’s displayed transfer charge as $12, any included or required registration extension as $0 additional, optional privacy or security services as $0, and estimated tax as $1. The planning total is $13. The actual amount must come from the checkout page for that domain and location; these figures are illustrative, not a current price claim.

Before submitting, the owner documents the nameservers and confirms that the website and email use those same nameservers. After the transfer, the owner checks the registrar dashboard, confirms the domain’s expiration date, and tests the website, email delivery, and key subdomains.

Example 2: A five-domain portfolio

Suppose five domains are moving and the registrar shows an illustrative transfer amount of $10 per domain. The base estimate is 5 × $10 = $50. Add any required taxes, premium-domain charges, optional services, or differences between extensions. Then compare the combined renewal price at the new registrar with the old portfolio cost.

For this migration, a spreadsheet should include domain name, extension, expiration date, current registrar, DNS provider, transfer status, authorization-code status, new expiration date, and post-transfer test result. Move one low-risk domain first if the registrar process is unfamiliar. This is especially useful for teams comparing API access, bulk controls, and DNS features; see best registrars for developers and teams.

If the transfer fails or appears stuck

Check the transfer status in both registrar accounts, confirm that the authorization code was entered correctly, and look for a pending approval email. If the code has expired or was regenerated, obtain a new one. If the domain remains locked or ineligible, ask the current registrar for the specific reason rather than repeatedly submitting requests.

A transfer normally does not provide a simple “undo” button. The practical rollback is to leave the current DNS unchanged, keep the old registrar account active, and resolve the failed request there. If the transfer has completed but the site is unavailable, first compare the new account’s nameservers with the documented values. Restore the correct nameservers or DNS records, then test again. Avoid deleting the domain, canceling hosting, or changing multiple DNS components while diagnosing the issue.

When to recalculate

Recalculate the transfer budget and migration plan whenever a price or eligibility input changes. Review it before submitting if the domain’s expiration date moves closer, the registrar changes its transfer fee, the extension’s rules differ from your previous domain, or the receiving registrar adds a paid privacy, DNS, email, or security option to checkout.

Revisit the plan after a failed transfer, a change of domain owner or contact details, a nameserver migration, or the addition of important services such as business email. For portfolios, recalculate whenever you add domains or change the desired renewal dates. Transfer and renewal policies can also change, so confirm current registrar and registry instructions rather than relying on an old screenshot or remembered interface label.

After completion, schedule a final review: verify the registration term, auto-renew setting, nameservers, DNS records, website, email, redirects, and account security. Enable strong account protection where available and keep the authorization code out of shared documents that do not need it. The domain registrar account security checklist covers the access controls worth reviewing.

The safest transfer is a documented one: preserve DNS first, calculate the complete cost, move the registration in a controlled window, and test every service afterward. That process makes a future registrar change faster without treating continuity as a matter of luck.

Related Topics

#domain transfers#registrar migration#DNS continuity#authorization code#domain management
R

Registrars.shop Editorial Team

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