Moving a company domain does not have to interrupt your website, email, or SSL. This business domain transfer checklist gives you a repeatable workflow for estimating timing and effort, preparing DNS and email, comparing registrar policies, testing the destination, and completing the change with a controlled cutover.
Overview
A domain transfer moves the registration record from one registrar to another. It does not automatically move your website files, hosting account, mailboxes, DNS zone, certificates, or application data. Those services may remain where they are, or you may move them separately.
That distinction is the foundation of a zero-downtime plan. If the current DNS provider continues answering queries during the registrar transfer, your website and email can keep working while the registration changes. Problems usually arise when a team changes the nameservers, recreates DNS records incompletely, cancels the old hosting account too early, or forgets that email and SSL depend on different systems.
Use this guide when you are changing registrars, moving website hosting, adopting a new DNS provider, consolidating a domain portfolio, or preparing a domain transfer service for several company domains. For a broader operational view, pair this checklist with the domain portfolio management guide.
What a successful transfer protects
- Website availability, including redirects, APIs, checkout pages, and subdomains.
- Email delivery and access through the correct MX, SPF, DKIM, and DMARC records.
- HTTPS certificates and automatic renewal processes.
- Ownership, privacy, renewal, billing, and account-security settings.
- A usable rollback plan if the new DNS configuration fails validation.
How to estimate
Estimate the transfer as three separate workstreams: registration, infrastructure, and validation. This prevents a simple registrar move from being confused with a complete website migration.
- Registration work: confirm the domain is eligible, unlock it if required, obtain the authorization code, submit the transfer, and approve any confirmation messages.
- Infrastructure work: inventory and reproduce DNS records, prepare the new website or host, verify email settings, and check certificate coverage.
- Validation work: test the live site, DNS answers, sending and receiving mail, redirects, forms, APIs, monitoring, and renewal settings.
For planning, use this simple effort model:
Total migration effort = preparation time + transfer administration + testing time + contingency.
Preparation and testing are controlled by your environment. The registrar portion depends on the provider, domain extension, approval steps, transfer locks, and whether the transfer is manually reviewed. Do not promise a fixed completion time until you have checked the current registrar instructions and the rules for the specific top-level domain.
For a hosting change, estimate downtime risk separately from domain-transfer time. A website can be moved to a new server before the domain changes. This is usually safer than transferring the registration and changing the website destination at the same moment. A staging environment can help you test the new site first; see Website Staging Environments for Small Businesses.
Inputs and assumptions
Record these inputs before you schedule the change. They form the working file for the transfer and make the process repeatable for the next domain.
Domain and registrar inputs
- Domain name, extension, current registrar, destination registrar, registrant account, and renewal date.
- Current transfer-lock status and the process for unlocking the domain.
- Authorization-code or EPP-code location, expiration rules, and approval contacts.
- Any registrar, registry, or administrative restrictions that could delay a transfer.
- Privacy or proxy status, ownership details, two-factor authentication, and billing authority.
DNS, hosting, and email inputs
- Authoritative nameservers and a complete export or written copy of the DNS zone.
- A, AAAA, CNAME, MX, TXT, SRV, CAA, and redirect records, including records for subdomains.
- Website origin addresses, CDN settings, firewall allowlists, webhooks, APIs, and third-party verification records.
- Email provider, MX priority, SMTP and IMAP hostnames, ports, encryption requirements, and authentication settings.
- SPF, DKIM selector records, DMARC policy, mail forwarding, catchalls, and transactional email services.
- Certificate names, renewal method, certificate authority account, and any certificates installed outside the main web host.
Reduce DNS TTL values before a planned nameserver or record cutover, provided the current provider permits it. A shorter TTL can help recursive resolvers refresh records sooner, but it does not guarantee instant worldwide change. Make the change early enough for existing TTL values to age out, and restore a normal operational TTL after the cutover is stable.
Registrar policy comparison
Policies change, and domain extensions can have different rules. Treat this table as a comparison framework, not as a substitute for the current provider’s instructions.
| Policy item | Common pattern | What to verify before transfer |
|---|---|---|
| Transfer lock | Many domains must be unlocked by the current registrar. | Whether the lock is automatic, where it is changed, and whether an account security setting also blocks transfer. |
| Authorization code | The code is usually requested from the current registrar and entered at the destination. | How the code is delivered, how long it remains valid, and whether a new code invalidates the old one. |
| Approval process | Some transfers require an email approval or account confirmation; others may complete after a waiting period. | Which contacts receive messages and whether manual approval can accelerate completion. |
| Transfer time | Completion may range from a short administrative process to several days, depending on approvals and registry rules. | The provider’s current estimate for the exact domain extension and whether weekends or review queues matter. |
| Fees and renewal | A transfer may have a fee or include a registration-period extension, depending on the extension and provider. | Total charge, renewal date after transfer, taxes, privacy pricing, and any promotional renewal terms. |
Check current registrar documentation and applicable registry or ICANN requirements immediately before submission. If ownership information, privacy status, or account contacts change, confirm whether that action creates a separate transfer restriction or approval step.
Worked examples
Example 1: Registrar-only transfer
A company keeps its existing web host, DNS provider, mail provider, and certificates. The team exports the DNS zone for reference, verifies that the current nameservers will remain in place, unlocks the domain, obtains the authorization code, and submits the transfer. After approval, it checks the domain status, nameservers, website, and email. In this case, the main risk is administrative: an expired code, missed approval message, incorrect account contact, or an unexpected lock.
Example 2: Registrar and hosting move
A company is also moving to new business web hosting. Before transferring the domain, it copies the site, databases, scheduled tasks, environment variables, redirects, and certificate configuration to the destination. It tests the new host through a staging address or controlled hosts-file test. DNS records are imported and compared line by line. The team then lowers relevant TTLs, changes only the records needed for the new host, and leaves email records unchanged. The old host remains available until monitoring confirms that the new site and mail flows work.
Printable pre-transfer checklist
- ☐ Confirm the legal owner, registrar account, renewal date, and responsible operator.
- ☐ Export or document every DNS record, including subdomains and verification TXT records.
- ☐ Confirm website hosting, email, SSL, CDN, API, and third-party dependencies.
- ☐ Validate MX, SMTP, IMAP, SPF, DKIM, and DMARC settings.
- ☐ Back up website files, databases, mail data, and DNS configuration.
- ☐ Reduce TTLs for records that will change, allowing time for prior TTLs to expire.
- ☐ Confirm the destination host and DNS provider are ready before changing production records.
- ☐ Check transfer-lock status, request the authorization code, and verify approval contacts.
- ☐ Confirm certificate names and renewal ownership; renew or reissue certificates when required.
- ☐ Submit the transfer and retain confirmation numbers, dates, and support contacts.
- ☐ Test HTTPS, redirects, forms, APIs, sending, receiving, and mailbox access after the change.
- ☐ Update WHOIS or registration details, privacy settings, renewal billing, monitoring, and documentation.
When to recalculate
Revisit this checklist before every domain transfer, hosting migration, nameserver change, or DNS-provider change. Recalculate the effort when the domain extension changes, the company uses new email or security services, the website adds critical subdomains, or the transfer includes a change in ownership or account contacts.
Review the registrar’s current lock, authorization-code, approval, fee, and timing rules before each submission. Also review applicable registry and ICANN guidance when policy notices or registration-data requirements change. Transfer estimates, privacy behavior, and renewal treatment should be treated as changeable inputs rather than permanent facts.
After the transfer, keep the old DNS and hosting services available for a planned verification period when practical. Monitor DNS answers from more than one network, inspect certificate validity, send and receive test messages, and check critical application paths. Once results are stable, restore normal TTL values, remove obsolete access, and record the new registrar, renewal date, nameservers, and recovery contacts in your domain inventory. For ongoing controls, consult the guides to DNS management, SSL certificates, and website backup and recovery.