Transferring a domain between registrars does not have to interrupt your website or email. This practical domain transfer checklist explains how to prepare DNS, request the authorization code, protect email continuity, verify the transfer, and complete post-migration checks without changing more than necessary.
Overview
A domain transfer moves the registration record from one registrar to another. It does not automatically move your website files, hosting account, database, SSL configuration, or email mailboxes. Keeping those services available is mainly a matter of preserving the correct DNS settings and avoiding unnecessary nameserver changes during the transfer.
The safest approach is to separate the work into three areas:
- Registrar preparation: confirm ownership access, remove the transfer lock, and obtain the domain’s authorization code.
- DNS and service continuity: record the existing DNS zone and verify where the website and email are hosted.
- Transfer and verification: submit the transfer, approve any confirmation requests, and test the domain after completion.
A domain transfer usually leaves the active nameservers unchanged, but this depends on the registrar and domain extension. Before starting, check the receiving registrar’s instructions and the rules that apply to your specific extension. Some domains may be subject to transfer restrictions, pending account changes, or additional verification.
Do not cancel the old registrar account immediately. Keep it accessible until the transfer is complete, the domain is visible in the new account, and your website and email have passed testing.
Checklist by scenario
Scenario 1: You are transferring the domain but keeping the same hosting
- Confirm where DNS is managed. Look up the domain’s current nameservers. DNS may be managed by the old registrar, your web host, a dedicated DNS provider, or a CDN. The registrar and DNS provider are not necessarily the same company.
- Export or copy the DNS records. Record A, AAAA, CNAME, MX, TXT, and any other active records. Pay particular attention to records used for email authentication, verification services, subdomains, and third-party applications.
- Check the current website and email. Visit the domain, test important pages, submit a contact form, and send test messages in both directions if possible. This creates a useful baseline before the transfer.
- Unlock the domain. Sign in to the current registrar and disable the registrar transfer lock if the control panel provides one. The label may differ by registrar.
- Request the authorization code. The code may be called an EPP code, transfer code, or auth code. Copy it carefully and treat it as sensitive account information.
- Start the transfer at the new registrar. Enter the domain exactly as registered, provide the authorization code, and review the contact and administrative details before paying or submitting the request.
- Approve required messages. Watch the domain’s registrant or administrative email address for transfer confirmations. If the old registrar offers an approval option, using it may help the process finish sooner, but follow the instructions shown by the registrars.
- Keep the old DNS active. Do not delete the old DNS zone or cancel related hosting until the new registrar shows the domain as active and your records have been verified.
If your hosting and DNS choices are also changing, use a separate website migration guide or create a migration plan. A registrar transfer alone is less complex than moving a website, database, or email service at the same time.
Scenario 2: You are changing registrars and DNS providers
Prepare the new DNS zone before changing nameservers. Re-create every necessary record at the new DNS provider, then compare the old and new zones line by line. Include records for the root domain, www, application subdomains, email delivery, email authentication, domain verification, and any services used by developers or marketing tools.
Lowering DNS time-to-live values in advance can reduce the time some resolvers retain old answers, but it does not guarantee an immediate change everywhere. Make the nameserver change only after the new zone has been tested and the hosting, email, and SSL arrangements are ready. For a broader performance plan, see the guidance on CDN services for small websites.
Scenario 3: The domain is used for business email
Email deserves extra attention because a missing DNS record can affect delivery even when the website is working. Before the transfer, document the MX records and all related TXT records, including SPF, DKIM, and DMARC entries where applicable. Confirm whether mailboxes are hosted by your web host, a separate email provider, or a business productivity platform. A registrar transfer should not require moving mailboxes, but changing DNS providers or nameservers can affect them if records are incomplete.
For a service-level comparison, review email hosting versus web hosting email before combining a registrar transfer with an email migration.
What to double-check
- Account access: Confirm that you can sign in to both registrars and that the email addresses used for verification are monitored.
- Domain status: Check for a transfer lock, pending ownership change, expiration issue, or another status that could delay the request. If the reason is unclear, ask the current registrar before submitting the transfer.
- Authorization code: Use the latest code supplied by the current registrar. If a newly generated code replaces an older one, enter the current version.
- Nameservers: Save the exact nameserver hostnames and confirm that they will remain in place unless you intentionally plan a DNS migration.
- DNS records: Compare the complete record set, not just the website’s A record. MX, TXT, CNAME, and verification records are common sources of service interruptions.
- SSL and redirects: Test both the secure and non-secure versions of the website, the www and non-www versions if both are used, and important redirects after completion. DNS changes can expose an unprepared SSL configuration.
- Renewal settings: Review the new registrar’s renewal date, auto-renewal setting, contact details, and pricing before the transfer is finalized. For broader cost planning, see our guide to renewal pricing.
- Transfer confirmation: Save confirmation emails, order details, and support tickets until the domain appears correctly in the new account.
After the transfer, check the domain registration details, nameservers, DNS response, website pages, forms, transactional messages, and business email. Test from more than one network or use a DNS lookup tool to compare the published records. A successful registrar transfer is not complete from an operational perspective until the services connected to the domain still work.
Common mistakes
Changing nameservers without a prepared DNS zone
This is one of the most preventable causes of downtime. If the new DNS provider does not contain the website, email, and verification records, resolvers may receive incomplete answers. Copy the zone first, then make the nameserver change only when you are ready.
Assuming a domain transfer moves hosting
Moving the registration does not copy website files, databases, mailboxes, or control-panel settings. If you are also changing hosting, schedule that work separately and keep the old environment available until the new one has been tested.
Deleting the old account too early
The old registrar or DNS provider may still be needed to retrieve a code, approve a request, inspect records, or correct a problem. Retain access until the new setup is verified and any transfer-related hold has cleared.
Ignoring email records
Website checks alone are not enough. Test incoming and outgoing email, review MX records, and confirm that authentication records remain published. If email is business-critical, plan the transfer during a period when you can monitor delivery.
Combining too many changes
Changing the registrar, hosting provider, DNS provider, website platform, and email service in one session makes troubleshooting difficult. When possible, transfer the domain first, verify it, and then complete other migrations in controlled stages.
When to revisit
Use this checklist before every domain transfer, even if you have completed one before. Revisit it before seasonal campaigns, product launches, website redesigns, hosting changes, or planned staff and account changes. Registrar interfaces, verification steps, domain-extension rules, and DNS tools can change, so confirm the current instructions at both registrars before submitting the request.
It is also worth reviewing your domain records periodically, not only during a transfer. Confirm that auto-renewal and contact details are correct, remove obsolete DNS records carefully, and keep an up-to-date inventory of domains, nameservers, hosting accounts, email providers, and renewal dates.
Final action checklist: document the DNS zone, verify email, unlock the domain, obtain the current authorization code, start the transfer, approve required confirmations, preserve nameservers unless intentionally changing them, and test every connected service after completion. If any step is unclear, pause before changing DNS and ask the relevant registrar or hosting provider for clarification.
