Transferring Domains Without Downtime

Know what transfers do and do not change

Transferring a domain moves registrar management and billing relationship. Hosting, website files, and mailbox providers stay where they are unless you also change nameservers or MX records. Keeping DNS stable is the simplest way to avoid downtime.

Prepare before you unlock

Confirm eligibility (often 60 days since registration or prior transfer), verify the registrant email works, and export a screenshot of current DNS. Lower TTLs a day ahead only if you also plan hosting changes during the same window.

• Check for registry locks or court holds that can block moves
• Remove stale contacts that cannot approve email confirmations
• Budget time for both losing and gaining registrar approvals

Auth code, unlock, and approval

Request the EPP/auth code, disable privacy if it blocks code delivery, and unlock the domain. Start the transfer at the new registrar and approve confirmation messages quickly so the order does not stall.

Keep DNS steady during the move

If nameservers already point to your host or DNS provider, leave them unchanged through the transfer. That usually preserves website and email continuity while ownership management switches.

Validate after completion

When the gaining registrar shows success, confirm nameservers, WHOIS privacy, and renewal dates. Update payment methods and notification emails so renewals do not silently fail at the new provider.

Close the loop

Re-enable domain lock, store any needed credentials securely, and notify teammates that the management portal changed. Save a short post-mortem of timing and issues so the next transfer is faster.

• Turn lock back on immediately
• Confirm auto-renew at the new registrar
• Update internal documentation with the new login location