A domain transfer is usually simple - until a business email stops delivering or a website points somewhere unexpected. The transfer itself moves your domain registration from one registrar to another. Your hosting, website files, and email do not automatically move with it. Keeping those pieces clear is how you change providers without disrupting the parts of your business customers rely on.
This practical guide explains how to transfer a domain name safely, what to prepare first, and where delays most often happen. For most common domains, the process takes five to seven days, although some transfers finish sooner once approvals are complete.
Know what a domain transfer does
Your domain registrar is the company that manages your ownership record, renewal date, contact details, and domain-level settings. Transferring a domain changes that registrar. It does not, by itself, change the server where your site lives.
That distinction matters. If your website and email are already working at your current host, they can keep working while the registration moves, provided the DNS records remain intact. If you are also changing hosting providers, treat the website migration and domain transfer as related but separate jobs. Move and test the site first, then update DNS when you are ready, or leave the existing nameservers in place until the new environment is verified.
A transfer also typically adds one year to the domain's registration term. That year is added after the current expiration date, subject to the domain extension's rules. It is not a reason to let a domain get close to expiration before starting.
Check whether your domain can be transferred
Before requesting an authorization code, confirm that the domain is eligible. The most common obstacle is the 60-day transfer lock. Many generic domains cannot be moved within 60 days of initial registration or a recent transfer. A change to the registrant's name, organization, or email may also trigger a lock if you did not opt out where that option was available.
Log in to your current registrar and check these basics:
- The domain is active and is not expired, suspended, or in redemption.
- It was registered or transferred more than 60 days ago.
- The registrant or administrative email address is current and accessible.
- The domain is unlocked for transfer.
- You can request the authorization code, sometimes called an EPP code or transfer key.
Rules vary by extension. A .com, .net, or .org transfer generally follows the process described here, while country-code domains can have different forms, timelines, and ownership requirements. If you use a newer extension or a country-code domain, review its specific transfer rules before scheduling a launch or renewal around the move.
Protect your website and email before you transfer
The safest approach is to document your current DNS before making any changes. Take screenshots or export every record in the DNS zone, including A, AAAA, CNAME, MX, TXT, and SRV records. Pay special attention to MX and TXT records because they often support business email, spam protection, and email authentication.
Your DNS setup may be managed at your registrar, hosting provider, or a separate DNS service. Find out which nameservers the domain currently uses. If you plan to keep those nameservers after the transfer, the transfer should not affect where traffic goes. If you plan to switch nameservers, create the complete DNS zone at the new provider first.
For a hosting move, test the new website before changing DNS. You can often preview it using a temporary URL, a hosts-file change, or a staging environment. Confirm that pages load, forms send correctly, logins work, SSL is active, and any store checkout or booking function behaves as expected. Make a current backup even if your hosting plan includes daily backups. A backup is most useful when it exists before you need it.
Email deserves the same care. If you use Google Workspace, Microsoft 365, or another third-party mail service, preserve the existing MX, SPF, DKIM, and DMARC records. If email is hosted with your current web host and you are moving it too, migrate mailboxes and test sending and receiving before changing the MX record.
How to transfer a domain name step by step
Start at your current registrar. Disable the domain transfer lock, then request the authorization code. The code is case-sensitive in some systems, so copy it exactly and keep it private. Do not post it in a support forum or send it through an unsecured channel.
Next, begin the transfer with your new registrar. Enter the domain name and authorization code, verify the registrant contact information, and pay the transfer fee if one applies. For many standard extensions, that fee includes the additional registration year.
You will usually receive an approval email at the domain's registrant or administrative email address. Approve the request promptly. The current registrar may also send a confirmation or offer an option to release the domain early. If you do nothing, the transfer can still complete after the standard waiting period, but approval can shorten the process.
While the transfer is pending, avoid changing the registrant email, locking the domain again, or making unnecessary account changes. Those actions can restart review steps or cause the transfer to fail. Continue monitoring both the old and new registrar accounts until the status shows complete.
Once the transfer finishes, log in to the new account and confirm the domain is present, unlocked only if you still need to make changes, and set to auto-renew if that fits your renewal process. Turn transfer lock back on. Also verify that renewal notices go to an address your team monitors, not a former employee or a generic inbox no one checks.
Avoid the DNS mistakes that cause downtime
A domain transfer does not normally require a DNS change. Problems arise when people assume it does and replace nameservers before the new records are ready. If the site is working and you only want a new registrar, leave the nameservers alone.
If you are moving hosting at the same time, lower the TTL on relevant DNS records 24 to 48 hours before the planned switch. A lower TTL can help changes spread more quickly, but it is not a guarantee that every visitor sees the new destination immediately. Keep the old hosting account active until traffic, forms, and email are stable on the new service.
Do not forget records that are less visible than the website's A record. A missing TXT record can break email authentication. A missing CNAME can interrupt a verification service. A missing subdomain record can take down a client portal, online store, or support tool even when the main homepage looks fine.
For business-critical domains, make a simple change plan: identify the current DNS host, record every entry, decide who has account access, choose a low-traffic window for DNS changes, and name the person responsible for testing afterward. That small amount of preparation prevents most avoidable surprises.
When to ask for help
A straightforward transfer is manageable for many site owners. It becomes more complicated when the domain supports multiple websites, agency client accounts, custom nameservers, a large email setup, or a site migration with tight timing. In those cases, having a human support team review the DNS plan can be worth more than rushing through a checklist.
If you are moving both hosting and registration, HillHost can help coordinate the hosting side, verify a migrated website, and provide practical guidance on the DNS changes needed to point traffic safely. The goal is not simply to get the domain moved. It is to keep your site, email, and customer experience intact while it moves.
A domain is a small line item in a business budget, but it is also the address customers use to find you. Transfer it before renewal pressure sets in, keep a clean record of your DNS, and give yourself enough time to test each change. That is how a routine administrative task stays routine.