Domain Transfer vs Hosting: What Changes and What Does Not

Domain transfer vs hosting describes two different changes. A registrar transfer moves the domain registration and billing relationship. A hosting move copies your website or application to another server. You can complete either change without completing the other.

Quick comparison

What changes during a domain transfer?

The registrar transfer changes who manages the registration, renewal and transfer controls. It usually does not move website files, databases, mailboxes or DNS records. Keep the old services active until the transfer completes and the new registrar shows the correct nameservers, privacy setting and renewal date.

What changes during a hosting move?

A hosting move changes where your site or application runs. Create and test the new environment, copy data, verify SSL and email, then update the relevant A, AAAA or CNAME records. The registrar can remain unchanged throughout the migration.

Which move do you need?

1. Choose a registrar transfer when you want a different company to manage the domain or offer a better renewal price.
2. Choose a hosting migration when the website is slow, the server lacks features, or you need a new deployment environment.
3. Choose a DNS change when the domain should point to a new host, CDN, email provider or verification service.

Safe order of operations

1. Record current DNS, email and registrar settings.
2. Build and test the new hosting environment if a hosting move is needed.
3. Unlock the domain and request the Auth/EPP code only when it is eligible.
4. Submit and approve the registrar transfer.
5. Change DNS after the destination is ready, then verify the website and email.

How much does a transfer cost?

A registrar transfer often includes one additional registration year, but pricing and term rules vary by TLD. Compare the transfer price with later renewal, privacy and add-on fees. A hosting move has separate server and migration costs, while a DNS change may be free at the DNS provider.

Common mistakes

• Changing nameservers when only the registrar needed to change.
• Canceling old hosting before DNS and email have been verified.
• Forgetting MX, SPF, DKIM or DMARC records during a DNS migration.
• Assuming a transfer changes the website host automatically.

Registrar transfer checklist

Before starting, confirm that the domain is unlocked, eligible for transfer, and not within a registry or policy waiting period. Check the expiration date, the last transfer date, the registrant email address and the current public status codes. Save a copy of the DNS zone, including A, AAAA, CNAME, MX, TXT and verification records. A registrar transfer should be planned as a registration change, so these records are your rollback reference if a support ticket is needed.

At the receiving registrar, compare the transfer in price, the renewal price and any privacy or premium fees. Enter the exact domain name and fresh Auth or EPP code. Keep the old registrar account and hosting subscription active while the transfer is pending. When the request completes, check the new expiration date, nameservers, DNSSEC setting, privacy setting, auto-renew preference and payment method.

Hosting migration checklist

A hosting migration has a different risk profile. Build the destination first, copy the application and database, configure environment variables, install certificates and test the production hostname before changing DNS. If the site sends mail, verify outbound SMTP, inbound MX records and the authentication records used by recipients. Check scheduled jobs, uploads, redirects, analytics and third-party webhooks as well.

Lowering DNS TTL shortly before a planned cutover can reduce the time that resolvers keep old answers, but it does not make DNS instantaneous. Keep the old host available for the full overlap window. Monitor requests, error rates, forms and email after the change. Restore the previous records if the destination is unhealthy, then fix the destination before attempting the cutover again.

DNS changes that are easy to confuse with transfers

Adding a CNAME for a landing page, changing an A record for a server, or delegating nameservers to a managed DNS provider does not transfer the domain registration. The registrar still controls renewal, lock status and Auth codes. Conversely, a registrar transfer can complete while the existing DNS continues to point at the same host. Treat the registrar account, DNS provider and hosting provider as three separate roles even when one company sells all three services.

Email is the most common hidden dependency. A website can appear healthy after a DNS change while mail delivery fails because MX, SPF, DKIM or DMARC records were omitted. Record the full zone before editing it, preserve records for verification and monitoring services, and test both sending and receiving from more than one mailbox.

Decision examples

If your website is stable but another registrar has a better renewal price, transfer the registration and leave hosting and nameservers unchanged. If your site needs more CPU or a different runtime, migrate hosting and update only the records that route web traffic. If a new email provider gives you an MX record, make a DNS change while leaving both registrar and website hosting in place. If you need all three changes, stage them separately so one failure does not hide the source of the problem.

Final verification after the change

Use an external DNS lookup and a fresh browser session to verify the expected records. Load the home page, a deep page, a form and any authenticated callback. Send a test message to and from the domain, inspect the certificate and confirm redirects. Review the registrar dashboard for the domain status and expiration date, then keep a short change log with the old values, new values, timestamps and rollback contact. This record makes a later renewal, transfer or incident much easier to diagnose.

For transfer eligibility and denial reasons, review the ICANN Transfer Policy. For current prices, compare the domain transfer cost table.