A domain transfer should be an administrative change, not a website outage. Knowing how to transfer domain names correctly means separating what moves – the registration – from what must keep running – your DNS, website, email, and connected services. Most transfer problems happen when those pieces are changed at the same time without a plan.

A transfer moves your domain registration from one registrar to another. It does not automatically move your hosting account, website files, mailboxes, or DNS records. That distinction gives you control: you can change registrars while leaving your site and email exactly where they are until you are ready to make other changes.

Before You Transfer a Domain Name

Start by checking the domain’s eligibility. Under standard registry rules, a domain generally cannot be transferred within 60 days of its initial registration or a previous transfer. Some registrars also apply a 60-day lock after certain contact-information changes, depending on the extension and the opt-in settings used when the change was made.

Confirm that the domain is active and that you can access the current registrar account. If the domain has expired, renewal may be necessary before a transfer can proceed. A domain in redemption or deletion status usually cannot be transferred at all, and recovering it can be expensive.

The practical question is not only whether the domain can move, but whether its current setup is documented. Before changing anything, make a copy of your DNS zone. At minimum, record the nameservers and every active record: A and AAAA records for websites, CNAME records for services, MX records for email, plus TXT records used for SPF, DKIM, DMARC, verification, and third-party tools.

This step matters most when DNS is managed at the registrar you are leaving. If the old registrar removes its DNS zone after the transfer, missing records can break email delivery, subdomains, or service verification even though the main website still appears online.

Decide What Should Stay Put

For a low-risk transfer, keep the existing nameservers in place until the registration has completed. Your site remains pointed at the same hosting server, and email continues using the same mail provider. The registrar changes in the background.

If your nameservers point to an independent DNS provider, there is usually very little to change. If your nameservers point to the old registrar, you have two workable options. You can recreate the entire DNS zone with the new registrar before or immediately after the transfer, or you can move DNS management to your hosting provider or a dedicated DNS service first.

Do not change nameservers, migrate hosting, and transfer the registration in one rushed session unless there is a real reason to do so. Each task has its own failure points. Keeping them separate makes it much easier to identify and fix a problem if one occurs.

How to Transfer Domain Names Step by Step

1. Verify the registrant email address

Transfer approval messages are sent to the registrant or administrative contact email address listed for the domain. Make sure that mailbox is active and accessible before you begin. If it uses an email address tied to the domain itself, such as admin@yourdomain.com, confirm that email will continue working during the transfer.

For a domain with outdated contact details, update them carefully. Check whether the current registrar will trigger a transfer lock after the change. If it will, you may need to opt out of that lock where permitted or wait before starting the transfer.

2. Unlock the domain

Most domains have a transfer lock enabled by default. In the current registrar’s dashboard, look for a setting labeled Domain Lock, Registrar Lock, Transfer Lock, or something similar. Disable it for the domain you intend to move.

Unlocking a domain does not hand it over to anyone. It simply allows a valid transfer request to be processed. Keep your registrar account protected with a strong, unique password and multi-factor authentication while the transfer is underway.

3. Request the authorization code

For many generic domains, including .com, .net, and .org, you will need an authorization code, often called an EPP code or transfer key. Request it through the current registrar’s domain management area. Some providers display it immediately; others send it by email or require a support request.

Treat this code like an account credential. Share it only with the registrar receiving the domain. If you suspect it was exposed, generate a new code before proceeding.

4. Start the transfer with the new registrar

At the receiving registrar, enter the domain name and authorization code, then review the transfer details. A standard transfer often includes a one-year extension to the registration term, though this depends on the domain extension and its registration history. The extension is typically added to the existing expiration date, subject to registry maximums.

Review the price before payment. A fair transfer quote should clearly show the transfer cost, renewal term if included, and any optional services. Domain privacy, email, security tools, and other add-ons may be useful, but they should be a deliberate choice rather than a surprise at checkout.

5. Approve the confirmation emails promptly

You may receive one or more confirmation emails from the gaining registrar and, in some cases, the losing registrar. Approve them as soon as you have verified the request. A missed approval email is one of the most common reasons a transfer stalls.

Some registrars offer an option to approve the transfer and release the domain early. If available, it can shorten the process. Without early approval, transfers commonly take five to seven days, although the exact timing depends on the registrar and the domain extension.

6. Confirm the domain after completion

Once the transfer completes, sign in to the new registrar and verify the registration expiration date, contact details, nameservers, and domain lock status. Re-enable the transfer lock after you confirm the domain is in the correct account.

Then test the services people actually use. Load the website on the main domain and common subdomains. Send and receive a test email. Check contact forms, online stores, scheduled tasks, and any third-party services that use DNS verification. DNS settings may look correct in a dashboard while one overlooked record still causes an operational problem.

Avoid the DNS Mistakes That Cause Downtime

The most damaging mistake is assuming that nameservers will automatically remain unchanged. Some transfer processes preserve them; others may apply the new registrar’s default nameservers if a setting is selected incorrectly. Before submitting the transfer, take a screenshot or written record of the current nameservers and DNS records.

Email deserves extra attention. A website may work with only one A record, but business email often depends on several records working together. Missing MX records stop delivery. Missing SPF, DKIM, or DMARC records can cause messages to be rejected or placed in spam. If you use Microsoft 365, Google Workspace, OX App Suite, or another hosted email platform, preserve every provider-required record.

DNS propagation only becomes a factor when you change DNS records or nameservers. A registrar-only transfer with unchanged nameservers should not require propagation time. If you do change nameservers, expect some users to see old and new DNS answers temporarily, based on cached records and TTL values. Plan that change during a lower-traffic period and avoid making several unrelated DNS edits at once.

When a Transfer Is Not the Right First Move

Sometimes the immediate problem is hosting, not the registrar. If your site is slow, your plan is overpriced, or support is unhelpful, moving hosting may address the issue while leaving the domain where it is for now. Likewise, a domain transfer will not fix a broken WordPress site, an exhausted VPS, or an email configuration problem.

On the other hand, consolidating domains and hosting can reduce the number of accounts you manage. For small businesses and personal site owners, having practical domain management, hosting, backups, and support under one provider can make renewals and troubleshooting simpler. The trade-off is that you should still keep clear records of where DNS, hosting, and email are managed instead of assuming one login controls every service.

If you are transferring several domains, do not start them all without checking renewal dates and access first. Move a noncritical domain as a test if you are unfamiliar with the receiving registrar’s process. That small trial can expose account, email, or DNS gaps before they affect a primary business domain.

A domain is a long-term business asset, even when it supports a small personal project. Keep its registration account accessible, renewal settings clear, and DNS records documented. Those habits make a future move routine rather than stressful – and leave you free to choose infrastructure based on cost, control, and the service you actually need.