Transferring a domain to a new registrar does not have to interrupt your website or email. This step-by-step domain transfer checklist helps you prepare the domain, preserve DNS settings, request the authorization code, verify the move, and know when to pause before changing anything.
Overview
A domain transfer moves the registration record from one registrar to another. It is separate from moving your website files, database, email service, or hosting account. In many cases, a domain can transfer while the website continues running on the existing web host.
The main risk is not the transfer itself but an avoidable change to DNS management. DNS records tell browsers and mail services where to find your website and email. If the new registrar replaces, omits, or changes those records, visitors may see an error or email may stop working. The safest approach is to document the current setup before starting and confirm that the same DNS service will remain authoritative after the transfer.
Use this general sequence:
- Confirm that the domain is eligible to transfer.
- Record the current DNS, hosting, email, and renewal details.
- Unlock the domain if a registrar lock is active.
- Request the domain authorization code, also called an EPP or AuthInfo code in some interfaces.
- Start the transfer at the new registrar using the exact domain and code.
- Approve any verification message and monitor the transfer.
- Check DNS, website, email, SSL, and renewal settings after completion.
Labels and approval steps vary by registrar, domain extension, and account security settings. Treat the registrar's current instructions as the final authority, especially if the domain is country-code or uses a specialized registry.
Checklist by scenario
Before you transfer any domain
- Confirm that you can sign in to the current registrar and access the domain's administrative contact details.
- Check the domain's expiration date and make sure there is enough time to complete the move without relying on a last-minute renewal.
- Review whether the domain has a transfer lock, a recent registration or transfer, a pending ownership change, or another status that may prevent transfer.
- Verify that the domain is not suspended or involved in an unresolved account issue.
- Record the current nameservers, A records, CNAME records, MX records, TXT records, and any other records used by your site or email.
- Save a copy of the current DNS zone if the registrar or DNS provider offers an export.
- Note where the website is hosted, where email is hosted, and which provider issues or manages the SSL certificate.
- Confirm that you have access to the email address used for transfer notices and account verification.
If you are unsure how the domain connects to your hosting account, review how to connect a domain to web hosting before making changes. Understanding whether your DNS is managed by the old registrar, your host, or a separate DNS provider is especially important.
If the website and email must remain online
- Do not cancel the old registrar account or hosting account before the transfer is confirmed.
- Keep the current nameservers unchanged unless you have deliberately planned a DNS migration.
- Capture screenshots or exports of custom records, including verification records for email marketing, analytics, payment tools, and domain-based services.
- Choose a transfer window when someone can test the site and email afterward.
- Check whether DNSSEC is enabled. If it is, follow the registrar's instructions for preserving or temporarily updating the relevant signing information.
A domain transfer and a website migration are different projects. If you are also moving hosting, plan the file, database, DNS, and testing work separately. The website launch checklist can help organize checks around a larger site change.
When you have the authorization code
- Copy the code directly from the current registrar rather than retyping it where possible.
- Check for spaces, hidden characters, capitalization, and punctuation.
- Start the transfer at the new registrar using the domain's exact spelling.
- Review the transfer price, included renewal terms, account contact details, and any optional services before submitting.
- Save the order or transfer reference number.
- Respond to legitimate approval or verification messages promptly, while checking the sender and destination carefully.
An authorization code proves that the transfer request is authorized; it does not move the website or recreate DNS records. Keep the code private and do not publish it in a support forum or shared document.
After the transfer completes
- Confirm that the domain appears in the new registrar account and that the registration status is active.
- Compare the nameservers with your pre-transfer record.
- Test the main domain, common subdomains, redirects, and secure HTTPS versions.
- Send and receive test messages for each important email address.
- Confirm that MX, SPF, DKIM, DMARC, TXT, and verification records are still present where applicable.
- Review the new expiration date and set a reminder for the next renewal review.
- Confirm that automatic renewal, account recovery details, multi-factor authentication, and billing information are configured as intended.
- Keep the old account accessible until you have completed all checks and no longer need its records or history.
What to double-check
Domain status codes can explain why a transfer is unavailable or still pending. The wording differs between providers, but this comparison is a useful starting point:
| Status or condition | What it usually means | What to check next |
|---|---|---|
| Transfer lock enabled | The registrar is preventing an outbound transfer. | Unlock the domain in the registrar account, then confirm that the status has updated before retrying. |
| Authorization code rejected | The code may be wrong, expired, mistyped, or linked to a different domain. | Request a fresh code and enter it exactly as provided. |
| Pending transfer | The request has been submitted and is awaiting processing or approval. | Check the transfer reference, approval messages, and the new registrar's status page. |
| Transfer denied or cancelled | A requirement was not met or a party rejected the request. | Read the stated reason, correct the issue, and contact the relevant registrar if the explanation is unclear. |
| Recent registration or transfer restriction | The domain may be temporarily ineligible under the applicable registry or registrar rules. | Check the extension's current policy and plan around the eligibility date. |
| DNS unchanged but site unavailable | The transfer may be complete, but another service or record has a problem. | Test DNS resolution, hosting, SSL, redirects, and origin-server availability separately. |
Also double-check ownership and contact information. A transfer is not a substitute for maintaining accurate account recovery details. Use a unique password and multi-factor authentication at both registrars when available. For a broader backup approach, see the website backup checklist for files, databases, email, and DNS settings.
Common mistakes
- Changing nameservers during the transfer: This adds a separate DNS change that can make troubleshooting difficult. Leave nameservers alone unless the plan specifically includes a DNS move.
- Letting the domain expire during the process: Start early enough to handle a rejected code, delayed approval, or manual support review.
- Assuming the new registrar copies DNS automatically: Some services may offer import tools, but never assume every record has been preserved. Compare the old and new DNS views.
- Closing the old account too soon: The old account may contain DNS records, invoices, transfer history, or recovery information you still need.
- Ignoring email: A website test alone does not prove that mail is working. Check inbound and outbound delivery, aliases, forwarding, and authentication records.
- Using an outdated authorization code: If a code is rejected, obtain a new one rather than repeatedly submitting an uncertain value.
- Confusing a registrar transfer with a hosting migration: Moving the domain does not move website files, databases, mailboxes, or server settings.
- Missing security notices: Review account alerts and verify messages carefully. Do not click suspicious links; sign in through the registrar's known website instead.
When to revisit
Use this checklist before every domain transfer, even if you have moved another domain successfully. Registrar interfaces, verification workflows, transfer fees, eligibility rules, and status labels can change. Review the current instructions whenever you transfer a new domain extension, move a high-value business domain, or work with a registrar you have not used before.
It is also worth revisiting your records before renewal planning cycles, after a staff or ownership change, and before a major website migration. Set a recurring domain audit to verify the registrar account, expiration date, automatic renewal setting, nameservers, DNS records, recovery email, and multi-factor authentication.
Your next practical step is to create a small transfer folder containing the current DNS export, hosting and email details, expiration date, registrar support information, and a transfer checklist. Once the transfer is complete, test the site and email, record the final settings, and keep the documentation with your other website backups. That preparation makes the next domain transfer faster without treating it as a risk-free, one-click change.
