Transferring a domain to a new registrar does not usually require moving your website, but a poorly timed or incomplete transfer can interrupt DNS, email, renewals, or account access. This guide provides a reusable domain transfer checklist, explains the authorization-code workflow, and shows how to protect your website while changing registrars.
Overview
A domain registrar manages your domain registration, renewal settings, contact details, transfer controls, and often your DNS management tools. Moving the domain to another registrar changes where those management functions are handled. It does not automatically move your web hosting, website files, databases, SSL configuration, or email service.
That distinction is important. A registrar transfer can often be completed without website downtime when your existing DNS records remain active and unchanged. However, changing the registrar and changing nameservers at the same time introduces additional risk. Treat them as separate tasks unless you have a specific reason to move both.
Before starting, compare the destination registrar’s renewal terms, DNS controls, domain privacy options, account security features, support process, and any transfer-related charges. A low initial price is less useful if the account is difficult to manage or the renewal date is unclear. For broader selection criteria, see how to choose a domain registrar and web hosting plan.
What a domain transfer changes
- Where you sign in to manage the domain.
- Which registrar handles renewal and registration administration.
- Where you configure registrar-level settings such as transfer locks and authorization codes.
- Potentially, which DNS management interface you use, depending on your nameserver setup.
What a domain transfer does not automatically change
- Your web hosting account or website files.
- Your hosting server’s IP address.
- Your email provider or mailbox contents.
- Your SSL certificate or website application settings.
Checklist by scenario
Scenario 1: You are moving the domain but keeping hosting and DNS where they are
- Record the current setup. Note the domain’s renewal date, nameservers, DNS provider, email provider, and important contacts. Export or document DNS records if your current provider supports that option.
- Confirm account access. Make sure you can sign in to the current registrar and access the administrative email address associated with the domain.
- Check transfer eligibility. Review the current registrar’s transfer status, domain lock setting, contact verification requirements, and any applicable transfer restrictions. Requirements can vary by domain extension and registrar.
- Unlock the domain. Disable the registrar lock only through the official account dashboard. Do not use an authorization code received from an unverified source.
- Request the domain authorization code. This may be called an EPP code, transfer code, or auth code. Copy it carefully and treat it like a password.
- Start the transfer at the new registrar. Enter the exact domain name and authorization code, then review the displayed renewal and transfer information before paying or submitting.
- Approve required messages. Watch the administrative email account and both registrar dashboards for transfer notices or approval requests.
- Keep the existing DNS active. Do not cancel the old registrar, DNS service, hosting account, or email service until you have confirmed that the transfer is complete and the website and email still work.
Scenario 2: You are transferring the domain and changing DNS providers
Prepare the new DNS zone before changing nameservers. Recreate the A, AAAA, CNAME, MX, TXT, and other records required by your website, email, verification services, and security tools. Compare the new zone with the old one rather than assuming that a basic website record is enough. The guide to DNS records and nameserver settings can help you identify the records involved.
Where possible, complete the registrar transfer first while the existing nameservers remain in place. Afterward, change nameservers as a separate, documented step and test the site, email, redirects, subdomains, and third-party integrations. If your hosting provider requires specific nameservers, confirm those values before making the change.
Scenario 3: The domain is close to renewal
Do not rely on the transfer process to solve a last-minute renewal problem. Check the expiry date, the destination registrar’s transfer guidance, and whether the transfer will extend the registration under the terms shown at checkout. If timing is tight, contact both registrars through their official support channels and consider renewing before transferring if that is the safer way to protect the domain. Keep receipts and confirmation emails.
Scenario 4: You manage several domains
Use a transfer sheet with the domain name, current registrar, destination registrar, renewal date, DNS provider, email provider, lock status, authorization-code status, transfer start date, and completion date. Transfer one low-risk domain first if you are testing a new registrar’s workflow. Keep business-critical domains on a separate schedule so one administrative error does not affect every service at once.
What to double-check
Renewal dates and costs
Capture the renewal date before you begin and verify it again after completion. Review whether the transfer includes a registration extension, whether renewal is enabled, and which payment method will be charged. These details depend on the domain extension and registrar, so use the transaction summary and account records rather than assumptions.
Privacy and contact information
Check the destination registrar’s domain privacy controls and confirm that the registrant, administrative, and technical details are accurate. Privacy protection may affect which contact details are displayed publicly, but it does not remove your responsibility to keep the registrar account information current. Use a monitored email address that is protected with a strong password and multi-factor authentication.
DNS, email, and SSL
After the transfer, test the root domain, www version, important subdomains, contact forms, and transactional email. Confirm that MX records still point to the correct email service and that TXT records used for email authentication or third-party verification remain present. Visit the website over HTTPS and check that the certificate is valid. If you also changed hosting or DNS, follow a separate domain, DNS, SSL, and email setup checklist.
Security and recovery
Enable multi-factor authentication at the destination registrar, review account users and delegated access, and save transfer confirmations in a secure location. Once the transfer is complete, re-enable the domain lock if the registrar provides that control. Confirm that recovery email addresses and payment details belong to the correct owner.
Common mistakes
- Changing nameservers unnecessarily: A registrar transfer alone may not require a DNS change. Changing both at once makes troubleshooting harder.
- Using an outdated authorization code: Codes can expire or be regenerated. Request a current code and enter it exactly as provided.
- Starting too close to expiry: A transfer can require review or approval. Begin early enough to handle an unexpected delay.
- Forgetting email records: Websites may load while email fails if MX, TXT, or related records were not preserved.
- Canceling the old service immediately: Keep the old registrar, DNS provider, and hosting account active until the new arrangement is verified.
- Ignoring transfer notifications: Approval requests may be sent to the domain’s administrative contact or displayed in a registrar dashboard.
- Assuming every domain extension follows the same process: Transfer rules, locks, fees, and approval steps can differ. Confirm the current instructions for the specific extension.
If the transfer does not complete
First, check the transfer status and any messages from the current or destination registrar. Confirm that the domain is unlocked, the authorization code is correct, and the administrative email account is accessible. Do not repeatedly submit new requests without understanding the failure message. If the transfer is rejected or canceled, leave your existing DNS and hosting in place, document the reason, and contact the registrar through its official support process. A failed transfer should not cause downtime if the active DNS and hosting services remain unchanged.
When to revisit
Use this checklist whenever you transfer another domain, prepare for a renewal, consolidate registrar accounts, or change hosting and DNS providers. Revisit it before seasonal planning cycles if your organization has busy launch periods, sales events, or maintenance freezes. Starting administrative work before those periods gives you time to verify account access and recover from errors without rushing.
Review the process whenever a registrar changes its dashboard, security controls, transfer instructions, pricing display, or domain privacy options. Domain-extension rules and approval workflows can also change, so confirm current requirements at the time of transfer rather than relying on an older checklist.
Practical next step: create a transfer record for each domain, write down its current registrar, renewal date, nameservers, DNS provider, and email provider, then verify account access before unlocking anything. Keep DNS unchanged during the registrar move unless a planned DNS migration is part of the project. After completion, confirm the renewal date, re-enable domain protection, test the website and email, and keep the confirmation record for future management.
