Transferring a domain does not have to interrupt a website or business email. This reusable domain transfer checklist explains how to prepare the domain, preserve DNS and email service, complete the registrar migration, verify the result, and plan for renewal and security afterward.
Overview
A domain transfer moves management of a domain from one registrar to another. It is separate from moving the website itself, changing the hosting company, or changing the domain’s nameservers. Keeping those activities separate is the simplest way to reduce risk.
In a typical registrar migration, the domain continues using its existing nameservers and DNS records while the transfer is processed. The website and email should therefore continue operating as long as the DNS zone remains available and unchanged. You may later point the domain to new hosting, but that is a separate DNS change with its own testing plan. For background, see how to point a domain to web hosting.
The exact screens, terminology, fees, approval steps, and transfer eligibility rules vary by registrar and domain extension. Treat the workflow below as a provider-agnostic plan, then confirm the current instructions with both registrars and the relevant registry when needed.
Basic sequence: inventory the domain, confirm eligibility, preserve DNS, secure the accounts, unlock the domain, request the authorization code, start the transfer, approve or monitor it, and verify every service afterward.
Checklist by scenario
Scenario 1: Moving the domain while keeping the same hosting
This is usually the lowest-risk scenario because the website and mail infrastructure do not need to move. Before starting:
- Record the current registrar, domain expiration or renewal date, nameservers, and account owner.
- Export or document the complete DNS zone, including A, AAAA, CNAME, MX, TXT, SRV, CAA, and any verification records in use.
- Confirm where DNS is managed. It may be the current registrar, a separate DNS provider, a hosting platform, or a service such as Cloudflare.
- Confirm that the website, email, payment tools, analytics, advertising platforms, and other services still use the expected domain.
- Check that the domain is eligible for transfer and is not subject to a transfer lock, recent registration or transfer restriction, legal hold, or unresolved account issue.
- Enable two-factor authentication on the current and new registrar accounts and verify the recovery email and phone details.
After the transfer completes, avoid changing nameservers unless there is a separate reason to do so. Log in to the new registrar, confirm the domain is present, and compare the displayed nameservers and DNS settings with your pre-transfer record.
Scenario 2: Moving the domain and changing hosting
Separate the registrar transfer from the hosting migration whenever possible. First prepare and test the new website on its temporary address, staging URL, or hosts-file override. Then decide when to change DNS. This approach gives you a clear rollback path instead of combining several changes that are difficult to diagnose.
- Build or copy the site to the new host.
- Test pages, forms, logins, media, redirects, transactional messages, backups, and administrator access.
- Confirm the new host has the correct SSL configuration for the domain.
- Reduce DNS record time-to-live in advance only if you understand the effect and have a reason to accelerate a planned DNS change.
- Transfer the domain while retaining the existing nameservers, or complete the hosting change separately according to your migration plan.
- Change only the required DNS records, then test from more than one network.
A registrar transfer alone should not be treated as a website migration. The shared hosting, VPS, and cloud hosting guide can help when the hosting change is part of a larger scaling decision.
Scenario 3: Moving business email or DNS management
Email is often more sensitive than the website because a missed MX, SPF, DKIM, or DMARC record can affect delivery or authentication. Capture the current records before making changes. Ask the email provider for the exact records it expects, and do not remove existing records until the replacement service has been tested.
If DNS will move to a new provider, recreate the zone before changing nameservers. Include verification records used by email, marketing, accounting, customer support, analytics, and other business tools. After the nameserver change, send test messages in both directions and check that important messages are not being rejected or misclassified.
Scenario 4: A domain is managed by a team or former administrator
Establish ownership before requesting a transfer. Confirm that the registrar account uses a company-controlled email address rather than an individual’s mailbox. Identify who can approve transfers, access DNS, recover the account, and pay renewal charges. If a former employee or supplier controls the account, document the handover and resolve access issues before beginning the migration.
What to double-check
Eligibility, lock status, and authorization
At the current registrar, confirm the domain is active, the registrant contact details are accessible, the domain lock can be changed, and the authorization code can be requested. The code may be called an EPP code, transfer code, or auth code. Copy it carefully and use the current code, since a newly generated code may replace an earlier one.
Do not assume every domain extension follows the same transfer process. Requirements can differ by extension, registrar, account status, and recent changes to registration information. If the domain appears unavailable for transfer, ask the current registrar for the specific reason rather than repeatedly submitting requests.
DNS and nameserver continuity
Write down the nameservers exactly as displayed, including spelling and order where relevant. Confirm whether the authoritative DNS zone is hosted at the registrar or elsewhere. A registrar transfer may leave nameservers unchanged, but you should verify the result instead of relying on that assumption.
Use a DNS lookup tool or propagation checker after any nameserver or record change. Check the authoritative answer and several public resolvers, while remembering that resolver caches can show different results for a period of time. A DNS result that looks correct from one location is not complete proof that every user sees the same answer.
Website, email, and certificate checks
- Open the homepage, key landing pages, forms, checkout or booking flows, and administrator login.
- Confirm HTTP redirects, canonical URLs, robots rules, and XML sitemaps still use the intended domain.
- Test the root domain and the www version if both are supported.
- Send and receive email using more than one mailbox where possible.
- Check MX, SPF, DKIM, and DMARC records against the email provider’s documented requirements.
- Confirm the certificate is valid and that HTTPS works on the hostnames visitors use.
- Verify domain-based services such as search consoles, payment callbacks, webhooks, and third-party verification records.
Renewal and billing
Record the renewal date before and after the transfer. A transfer may affect the expiration date or add registration time depending on the extension and the transaction, but do not rely on assumptions. Review the new registrar’s renewal settings, payment method, auto-renewal status, contact notifications, and domain renewal pricing. Schedule a reminder well before expiration so a failed payment or inaccessible mailbox does not become an emergency.
Post-transfer security
Once the domain appears at the new registrar, confirm the domain security lock is enabled, two-factor authentication is active, recovery details are current, and account notifications go to monitored addresses. Review who has access and remove former users. If DNSSEC is enabled, verify that its status and key-signing information remain consistent; incorrect DNSSEC changes can make a domain unreachable. Use the domain security checklist and DNSSEC setup guide for a separate security review.
Common mistakes
- Changing nameservers unnecessarily: A registrar transfer does not automatically require a DNS change. Keep the existing nameservers when they are working and there is no hosting migration.
- Starting immediately before renewal: Give yourself time to fix an authorization, lock, payment, or approval problem. Check the renewal timeline before initiating the transfer.
- Forgetting email records: Website availability does not prove that business email works. Preserve and test MX and authentication records.
- Editing DNS without a copy: Export or document the zone first. Include records that are not obvious from a simple website lookup.
- Using an old authorization code: Request a fresh code when appropriate and paste it without added spaces. If it fails, generate a new one and confirm the transfer status.
- Ignoring account ownership: A domain controlled by a personal address or former administrator is a recovery risk even when the transfer succeeds.
- Assuming propagation is an outage: Check authoritative nameservers, public resolvers, DNS TTLs, hosting responses, and certificate status before concluding that the website is down.
- Combining too many changes: Registrar, DNS, hosting, email, and website changes made at once create avoidable troubleshooting complexity.
A simple troubleshooting decision tree
The transfer cannot start: Check eligibility, lock status, account permissions, contact details, and the authorization code. Then ask the current registrar whether an extension-specific restriction applies.
The transfer is pending: Review the status at the gaining registrar, look for an approval email, and check whether the current registrar provides a confirmation or cancellation option. Do not submit multiple transfers unless the registrar tells you to.
The website is unavailable after the transfer: Compare nameservers before and after the move. If they changed, restore the intended nameservers or recreate the missing DNS zone. If they did not change, investigate the hosting service, origin server, certificate, and application separately.
Email stopped working: Check MX records first, then SPF, DKIM, DMARC, mailbox status, and the provider’s delivery logs. Avoid deleting records while diagnosing the issue.
The domain is at the new registrar but cannot be managed: Verify the account, domain status, security lock, contact email, and registrar support case. Keep written records of the transfer confirmation and ownership details.
When to revisit
Use this checklist before every registrar migration, even if you have completed one before. Revisit it before seasonal campaigns, product launches, planned hosting changes, business ownership changes, or periods when support availability may be limited. It is also useful after switching email providers, DNS providers, security tools, or internal administrators.
Review the workflow whenever a registrar changes its interface or transfer process, a domain extension introduces different requirements, your DNS architecture changes, or a new service is added to the domain. At least once a year, audit the renewal date, payment method, account recovery details, DNS records, domain lock, two-factor authentication, and ownership documentation even when no transfer is planned.
Printable action list: document the current registrar and expiration date; export the DNS zone; identify the DNS and hosting owners; test the website and email; secure both accounts; confirm eligibility; unlock the domain; request the authorization code; start the transfer; approve or monitor it; verify nameservers and DNS; test website, email, HTTPS, and third-party services; confirm renewal and billing; re-enable the domain lock; and store the final confirmation with your operational records.
For a broader registrar evaluation before the next move, compare total cost, privacy, security, and support in this best domain registrar for small business guide. A careful transfer is less about speed than about preserving a known working configuration and making each change easy to verify or reverse.
