How to Transfer a Business Domain Without Downtime: A Step-by-Step Checklist

Overview

A domain transfer moves the registration record from one registrar to another. It is separate from moving website files, changing web hosting, or switching email providers. Keeping those activities separate is the foundation of a low-risk migration.

In many cases, the website and email can remain online throughout the registrar transfer because the domain continues to use its existing nameservers. However, the exact process depends on the domain extension, current registrar, destination registrar, account permissions, and any transfer restrictions that apply. Treat the registrar’s instructions as the final authority, especially for country-code domains or domains with unusual registration requirements.

The safest sequence is:

1. Document the current domain, DNS, hosting, and email setup.
2. Confirm that the business controls the registrar account and registrant contact details.
3. Resolve renewal, lock, verification, or ownership issues before starting.
4. Unlock the domain and request its transfer authorization code, if required.
5. Initiate the transfer at the new registrar.
6. Keep existing nameservers and DNS records unchanged unless a separate DNS migration is planned.
7. Verify the website, email, security settings, and renewal controls after completion.

A domain transfer service may help coordinate the process, but it cannot replace access to the current registrar, accurate ownership records, or a verified DNS backup. Before beginning, review the business DNS management guide and record every service that depends on the domain.

Checklist by scenario

Scenario 1: Changing registrars while keeping hosting and email unchanged

This is usually the simplest transfer. The goal is to change the registrar without changing where the domain’s DNS is hosted.

• Write down the domain name, registrar, expiration date, account owner, and administrative contacts.
• Export or copy the current DNS zone, including A, AAAA, CNAME, MX, TXT, and any verification records.
• Confirm which nameservers are currently assigned to the domain.
• Check that the website loads on both the root domain and the www version, if both are used.
• Confirm that business email can send and receive messages.
• Check whether the domain is locked against transfers and note how the current registrar displays that status.
• Request the authorization code, sometimes called an EPP or transfer code.
• Start the transfer with the new registrar using the exact domain name and requested contact information.
• Do not change nameservers unless the new registrar or a separate hosting migration requires it.
• After completion, confirm that the DNS records, website, email, SSL certificate, redirects, and domain renewal settings still work.

Keeping the original nameservers in place avoids combining a registrar change with a DNS change. If you also plan to move hosting, use a separate staging and cutover plan. The guide on how to point a domain to a new host covers that related task.

Scenario 2: Transferring the domain and moving website hosting

A hosting migration adds another potential failure point. Build and test the site at the new host before changing DNS. Confirm that the database, media files, application settings, forms, redirects, analytics, scheduled tasks, and integrations have been moved.

• Create a complete backup of the current website and database.
• Set up the new hosting environment before the domain transfer begins.
• Test the site through a temporary URL, hosts-file entry, staging domain, or another controlled method.
• Confirm the new server has the required runtime, database version, storage, backups, and access controls.
• Lower DNS time-to-live values ahead of a planned nameserver or record change when appropriate for your DNS setup.
• Choose a cutover window when the business can monitor forms, orders, logins, and email.
• Change DNS only after the new site is ready and a rollback plan exists.
• Keep the old hosting active until the new site and DNS behavior have been verified.

For broader planning, use the business website launch checklist. It helps separate domain registration, hosting, DNS, security, and go-live tasks.

Scenario 3: Transferring a domain when email is business-critical

Email deserves its own verification plan. A registrar transfer usually does not require changing MX records, but an accidental nameserver change or incomplete DNS copy can interrupt mail delivery.

• List every email-related DNS record, including MX, SPF, DKIM, and DMARC records.
• Identify whether email is hosted by the same company as the website or by a separate provider.
• Confirm that the current mail provider remains active during the transfer.
• Record aliases, forwarding addresses, shared mailboxes, and third-party sending services.
• Test internal and external delivery before and after the transfer.
• Review the domain’s security and authentication records after any nameserver change.

Do not assume that copying only the website’s A record is enough. DNS record types serve different purposes; the guide to DNS records for business owners can help identify what must be preserved.

What to double-check

Registrar and ownership details

• The current account has an accessible, monitored login and current recovery methods.
• The legal business owner or an authorized operator controls the domain account.
• Registrant, administrative, and technical contact details are accurate where applicable.
• Privacy protection does not hide information that the registrar requires for verification.
• The domain is not subject to an unresolved ownership dispute, payment issue, or account restriction.
• The domain is not within a registrar or registry transfer restriction period. Requirements vary, so verify them directly.

Transfer authorization and approval

Use the authorization code exactly as provided and treat it as sensitive account information. Some transfers require an approval email or an action in the current registrar account; others proceed through a different workflow. Monitor the relevant inboxes and registrar dashboards, and do not approve an unexpected request that does not match the transfer you initiated.

DNS, hosting, and SSL

• Compare the saved DNS records with the records active after the transfer.
• Confirm that the nameservers are the intended nameservers.
• Check the root domain, www hostname, important subdomains, and redirects.
• Verify that the SSL certificate covers the hostnames customers use.
• Test contact forms, checkout pages, logins, APIs, webhooks, and other critical functions.
• Confirm that DNS-based verification records for advertising, analytics, email, and SaaS tools remain present.

Renewal and security controls

After the transfer, review the expiration date, renewal setting, billing method, and renewal notifications. Turn on multifactor authentication if available, limit account access to people who need it, and store recovery information in the company’s approved password manager. Domain privacy protection can reduce unwanted exposure, but it should not replace accurate internal ownership records or a documented renewal process. For related renewal planning, see what happens when a domain is not renewed.

Common mistakes

• Changing everything at once: A registrar transfer, host migration, DNS provider change, and email move should not be treated as one untested action. Separate them when possible.
• Failing to document DNS: A forgotten TXT record can break email authentication or a connected service even when the website still loads.
• Starting during a launch or campaign: Avoid transferring a critical domain immediately before a major promotion, product release, or seasonal sales period.
• Using an outdated authorization code: Request a fresh code when the current one has expired, been regenerated, or no longer matches the registrar’s instructions.
• Ignoring account ownership: A domain registered through a former employee’s email or an unmonitored account is an operational risk, regardless of the registrar.
• Closing the old account too early: Keep access to the former registrar until the transfer, DNS, billing, and contact details have been checked.
• Assuming propagation means failure: DNS changes can appear differently across networks for a period of time. Check authoritative records and multiple access points before making another change.
• Skipping monitoring: Watch uptime, website transactions, email delivery, and important subdomains after the change. A practical monitoring plan is outlined in the website uptime monitoring guide.

When to revisit

Revisit this checklist before any registrar transfer, hosting migration, DNS provider change, ownership change, or major website launch. It is also useful before seasonal planning cycles, when staff responsibilities change, or when a business consolidates multiple domains.

Update the checklist whenever your registrar, hosting platform, email provider, DNS workflow, security policy, or approval process changes. Review the domain inventory at least as often as the business reviews other critical software accounts. For companies managing several domains, keep a simple register with the domain, purpose, owner, registrar, nameservers, renewal date, critical DNS dependencies, and recovery contact.

Before you act, assign one person to own the transfer and another to verify the result. Save the DNS snapshot, transfer details, test results, and final account settings in the company’s operational records. Then complete the transfer in a controlled window, confirm the website and email, enable appropriate security controls, and schedule a follow-up check after the new registrar account has been in normal use.