How to Transfer a Domain Safely: Registrar Change Checklist and Timeline
Domain TransferRegistrarsDomain ManagementDNS ContinuityRenewals

How to Transfer a Domain Safely: Registrar Change Checklist and Timeline

CCrazy Domains Editorial Team
2026-11-17
7 min read

Use this domain transfer checklist to protect ownership, DNS, website access, email, and renewal dates when changing registrars.

Transferring a domain to a new registrar is usually a controlled administrative change, but it can affect renewal dates, DNS management, website access, and business email if it is poorly timed. This guide provides a practical domain transfer checklist, a monitoring plan, and a verification workflow so you can move the registration without losing control of the domain or interrupting connected services.

Overview

A domain transfer moves the registration record from one domain registrar to another. It does not automatically move your website files, hosting account, mailboxes, WordPress installation, or DNS records. Keeping those services separate is the key to a safe transfer.

Before you start, identify where each part of your setup is managed:

  • Domain registrar: the provider responsible for the registration, renewal, contact details, transfer lock, and authorization code.
  • DNS provider: the service publishing records such as A, CNAME, MX, TXT, SPF, DKIM, and DMARC.
  • Web host: the provider serving your website, application, database, or WordPress installation.
  • Email provider: the service receiving and sending mail for your domain.

These may all be with one company, or they may be distributed across several providers. A registrar change should not require changing nameservers, but confirm the current arrangement before proceeding. The DNS records guide can help you document the records that must remain available.

Transfer rules vary by domain extension, registry, registrar, account status, and recent domain changes. Treat the instructions shown in your current and new registrar accounts as the controlling guidance, particularly for transfer eligibility, lock periods, authorization codes, fees, and confirmation messages.

What to track

1. Eligibility and ownership

Confirm that you can access the registrar account and the administrative contact method associated with the domain. Review the registrant name, organisation, email address, and privacy settings. Correct inaccurate details before beginning where possible, while considering whether a contact change could trigger a restriction under the applicable registration rules.

Check the domain's expiration date and renewal status. Do not begin a transfer when the domain is close to expiration unless you have confirmed the timing with both registrars. A transfer may take time, and an expired or suspended domain can follow a different recovery process. If renewal is urgent, resolve that issue first and retain the confirmation.

2. Transfer lock and authorization code

Many domains must be unlocked at the current registrar before a transfer can be initiated. Look for a setting described as a transfer lock, registrar lock, or similar control. Record the time you change it and check that the account displays the new status.

You will generally need an authorization code, sometimes called an EPP code, transfer code, or auth code. Request it through the current registrar's control panel or support process. Treat the code as sensitive account information: share it only with the intended new registrar and avoid storing it in an exposed ticket, chat, or public document.

3. DNS and service continuity

Export or record the current DNS zone before you submit the transfer. Include the nameservers and all important records, not just the website's A record. Pay particular attention to MX records for email, TXT records used for verification and email authentication, CNAME records for hosted services, and any records supporting subdomains.

Confirm whether the new registrar will preserve the existing nameservers or offer a separate DNS service. If the nameservers remain unchanged, the transfer itself should not require a DNS cutover. If they will change, recreate and verify the zone before switching. For email-specific checks, use the business email DNS checklist.

4. Website, SSL, and backups

Take a current website backup and confirm that you can restore it or access the backup files. A registrar transfer is not a substitute for a website migration, but a documented backup reduces risk if a DNS or account error occurs. Review the website backup and recovery plan before making changes.

Verify that your hosting account, SSL certificate, redirects, and application integrations are tied to the correct domain. If DNS remains unchanged, HTTPS should normally continue as before, but keep an eye on certificate and hostname errors after the transfer.

Domain transfer checklist

  • Record the registrar, expiration date, renewal setting, nameservers, and DNS provider.
  • Confirm account access and accurate contact details.
  • Check for a transfer lock, recent registration activity, or other eligibility restriction.
  • Obtain and securely store the authorization code.
  • Back up the website and document the DNS zone.
  • Start the transfer at the new registrar using the exact domain name.
  • Approve any confirmation request sent to the authorised contact or registrar account.
  • Keep the old registrar account available until the transfer completes and services are verified.

Cadence and checkpoints

A domain transfer timeline depends on the extension, registrar workflow, approval method, and whether the transfer is manually reviewed. Use the following checkpoints rather than assuming a fixed completion time:

StageWhat to checkAction
PreparationEligibility, expiration, lock status, contact accessResolve restrictions and document the current setup.
SubmissionDomain spelling, authorization code, transfer fee, new account detailsSubmit the request at the new registrar and save the reference.
ApprovalEmail or account notifications from either registrarApprove only requests you recognise; retain confirmation messages.
Pending periodTransfer status and expiration informationDo not cancel the old account or change DNS unnecessarily.
CompletionNew registrar ownership, renewal date, lock, privacy, and nameserversUpdate your inventory and verify the website and email.

For active business domains, check the transfer status at least once during preparation and again after each registrar notification. For a larger portfolio, maintain a monthly or quarterly domain inventory containing the registrar, owner, renewal date, DNS provider, hosting provider, and account recovery contact. This makes future transfers and renewal decisions less dependent on one person.

How to interpret changes

A completed transfer is not the same as a completed infrastructure review. Compare the new registrar account with your pre-transfer record and investigate differences rather than assuming they are harmless.

  • Nameservers changed: compare the active DNS zone with your saved copy. Missing MX or TXT records can affect email delivery, verification, or authentication.
  • Website is unavailable: check nameservers, A and CNAME records, hosting status, DNS propagation, and whether the hostname is covered by the SSL certificate.
  • Email is affected: verify MX records first, then SPF, DKIM, and DMARC records. Avoid replacing records with guesses; use the values supplied by your email provider.
  • Expiration date looks different: compare the old and new account records and review the transfer receipt or renewal confirmation. Ask the registrar to explain any discrepancy before relying on the displayed date.
  • Privacy or contact settings changed: restore the intended settings and confirm which contact receives security and renewal notices.
  • Transfer remains pending: check for an unapproved email, an active lock, an incorrect authorization code, or a registrar-specific review. Contact the relevant registrar rather than repeatedly submitting requests.

After completion, test the root domain and important subdomains over HTTPS, submit a test email if appropriate, and confirm that administrative logins and third-party domain verifications still work. If the move is part of a wider hosting change, follow the WordPress website migration checklist separately; changing registrars alone does not migrate a site.

When to revisit

Revisit this checklist before every domain transfer, before a renewal deadline, and whenever responsibility for the domain changes. A quarterly review is useful for business-critical domains or portfolios managed by several teams. At minimum, review the domain inventory monthly when a transfer is in progress and after any change to the registrar, DNS provider, host, email platform, or account owner.

Refresh the procedure when a registrar changes its dashboard, authorization-code process, privacy controls, fees, or transfer instructions. Also check the applicable registry guidance when transferring an unfamiliar domain extension, because eligibility and approval requirements can differ.

To finish a transfer safely, schedule a short post-transfer audit: confirm the registrar and renewal date, verify the transfer lock and privacy settings, compare nameservers and DNS records, test website and email access, and update your password manager, asset register, and renewal reminders. Keep the old registrar account and transfer correspondence until those checks are complete. Once the new arrangement is stable, record the next review date so the domain remains an actively managed asset rather than an overlooked subscription.

Related Topics

#Domain Transfer#Registrars#Domain Management#DNS Continuity#Renewals
C

Crazy Domains Editorial Team

Senior SEO Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.