A domain transfer does not have to interrupt a website or business email. This checklist shows how to prepare the domain, preserve DNS and renewal information, monitor the transfer, and create a rollback plan before moving from one registrar to another.
Overview
A domain transfer moves the registration record from one registrar to another. It does not automatically move your website files, hosting account, mailboxes, databases, SSL configuration, or DNS records. Keeping those systems available is the central requirement when you want to transfer a domain without downtime.
The safest approach is to separate the transfer into two workstreams:
- Registration work: confirm ownership, unlock the domain where required, obtain the domain authorization code, submit the transfer, and verify the renewal date and contact details.
- Infrastructure work: document DNS records, confirm that the current nameservers remain available, test the website and email, and prepare recovery steps.
In many cases, leaving DNS hosted with the existing DNS provider during the registrar transfer reduces risk. A registrar change and a nameserver change are separate operations. Changing both at the same time can make troubleshooting harder, especially when the website, email, verification services, and third-party applications depend on DNS records.
Transfer rules vary by domain extension, registrar, account status, and recent account or registrant changes. Before starting, check the current instructions from both registrars and the relevant registry. Treat the checklist below as an operational framework rather than a replacement for those requirements.
What to track
1. Domain eligibility and ownership
Record the domain name, extension, current registrar, account owner, registrant contact, expiration date, and auto-renewal setting. Confirm that you can access the administrative email address associated with the domain and that the account is protected with a strong password and multi-factor authentication where available.
Check whether the domain is subject to a transfer lock. A lock may be shown in the registrar dashboard as a transfer lock, registrar lock, or similar status. Some domains may also be temporarily ineligible for transfer after certain registration, transfer, or ownership changes. Because these conditions can change, verify the current status in the registrar account rather than relying on an old transfer guide.
2. Authorization and transfer details
Locate the domain authorization code, sometimes called an EPP code or transfer code. Store it securely and use the exact value supplied by the current registrar. Note when it was requested, whether it expires, and whether the new registrar requires the code during checkout or after the transfer order is created.
Also record the expected transfer fee, any included registration extension, the transfer approval method, and the renewal date shown after completion. Do not assume that the displayed date will remain unchanged until you confirm it in the receiving registrar account.
3. DNS and service dependencies
Create a DNS record inventory before making changes. Include the record type, host or name, value, time to live (TTL), purpose, and owner. A practical template looks like this:
| Type | Host | Value or destination | TTL | Purpose |
|---|---|---|---|---|
| A or AAAA | @ | Web server address | Current value | Root website |
| CNAME | www | Canonical hostname | Current value | Website alias |
| MX | @ | Mail provider hostname | Current value | Inbound email |
| TXT | @ or service host | Verification or policy value | Current value | SPF, DKIM, DMARC, or verification |
| CNAME or TXT | Service-specific host | Provider value | Current value | CDN, analytics, or SaaS integration |
Capture the authoritative nameservers as well. If DNS will remain with the existing provider, confirm that the receiving registrar will use those same nameservers after the transfer. If DNS will move, build and test the replacement zone before changing delegation.
4. Baseline tests
Before submitting the transfer, test the main website, important subdomains, outbound and inbound email, contact forms, payment or login flows, API endpoints, and certificate coverage. Record the results and the time of testing. This gives you a comparison point if a problem appears later.
Cadence and checkpoints
Use this side-by-side timeline to keep registration tasks separate from DNS and service checks:
| Transfer stage | Registration checklist | DNS and service checklist |
|---|---|---|
| Before requesting transfer | Confirm account access, ownership details, eligibility, transfer lock status, expiration date, and current transfer fee. | Export DNS records, record nameservers, verify hosting and email, and document baseline tests. |
| Before submitting order | Unlock the domain if required and obtain the authorization code through the current registrar's approved process. | Keep existing nameservers in place unless a separate DNS migration is planned and tested. |
| Transfer in progress | Monitor the new registrar's status, approval messages, and any confirmation requests. Do not delete the old registrar account. | Check website availability and email delivery at planned intervals. Avoid unrelated DNS edits. |
| After completion | Confirm the domain appears in the new account, verify the expiration and auto-renewal settings, and enable account security controls. | Verify nameservers and important records from more than one network or DNS lookup service. Test website, email, SSL, and critical subdomains. |
Schedule the work during a period when someone can monitor the domain and respond to approval messages. Avoid combining a registrar transfer with a website launch, major DNS redesign, hosting migration, or email provider change unless there is a clear reason to do so. Fewer simultaneous changes make the cause of an incident easier to identify.
Keep a dated transfer log containing the request time, authorization-code request, approval messages, status changes, DNS observations, and final verification. This is useful for portfolios with many domains and for future audits.
How to interpret changes
A transfer that is still processing is not necessarily failing. Status labels and approval procedures differ, so compare the message with the receiving registrar's instructions. If progress stops, check for a pending approval email, an incorrect authorization code, an active transfer lock, an ineligible domain status, or an account detail that requires correction.
If the website stops resolving, first compare the current nameservers with the recorded baseline. If the nameservers are unchanged, investigate the DNS provider, hosting endpoint, and individual records. If the nameservers changed, compare the active zone with your inventory. Pay particular attention to MX, TXT, DKIM, verification, and subdomain records; a root website may work while email or a third-party service is broken.
DNS observations can differ temporarily between networks because resolvers cache responses according to TTL values. Use a DNS propagation checker as one diagnostic input, not as proof that every user sees the same result. Check authoritative nameservers directly when possible, then test from representative networks.
If the transfer fails, do not immediately repeat every step. Preserve the error message, confirm the domain's current registrar and lock status, and contact the relevant registrar if the reason is unclear. A failed transfer normally does not require changing DNS, so the existing website and email can remain online while the registration issue is resolved.
Rollback workflow for a failed or risky transfer
- Pause additional changes and record the exact failure or symptom.
- Confirm which registrar currently controls the registration and which nameservers are active.
- Restore any accidentally changed nameservers or DNS records from the documented inventory.
- Verify website, email, SSL, authentication, and critical integrations.
- Keep the old registrar account, DNS account, and backups available until the new setup passes verification.
- Only restart the transfer after resolving the specific eligibility, authorization, or account issue.
When to revisit
Review this checklist before every domain transfer, registrar consolidation, ownership change, or portfolio audit. For active domain portfolios, perform a monthly or quarterly review of expiration dates, auto-renewal, registrar access, transfer-lock status, authorization-code procedures, nameservers, DNS ownership, and recovery contacts. A shorter review interval is appropriate for business-critical domains or domains supporting email and customer transactions.
Update the checklist whenever a registrar changes its dashboard or approval process, a registry changes transfer requirements, an extension introduces different eligibility rules, or your hosting and email architecture changes. Recheck transfer fees, renewal treatment, grace-period handling, and recovery options at the time of the transfer rather than copying assumptions from a previous move.
As a final action, create a transfer record for the next domain you plan to move. Fill in the ownership and expiration fields, export the DNS zone, run the baseline tests, and name the person responsible for monitoring the transfer. After completion, compare every item with the record and retain the completed checklist with your domain operations documentation. That small amount of preparation is the most reliable way to move a domain without turning a registrar change into a website or email outage.
