Moving a Business Website: Do You Need to Transfer the Domain Registrar?

Moving a website to a different hosting provider does not necessarily require moving its domain registration to another registrar. Before commissioning a supplier change, separate the website launch, the domain's registration management and any change of registered holder. Treating all three as one “domain transfer” can create an unnecessary dependency for launch.

This is a migration-planning guide, not permission to change an account, transfer a domain or bypass a lock. Confirm the applicable rules with the providers responsible for the actual domain. ICANN's registrar-transfer guidance should not be assumed to govern every country-code domain in exactly the same way.

Name the change you actually need

Imagine a fictional consultancy replacing an old website. Its current registrar can remain responsible for the registration while the new site runs elsewhere. Alternatively, the business may also want a different registrar, or need to correct who holds the registration. These are separate requirements even when one supplier offers all the services.

Write down the requested outcome for each part: where the website should run, who should manage the registration, which service should answer DNS queries and whether the registered holder changes. A supplier saying “we handle everything” should still explain which of those changes is included.

The official ICANN transfer FAQ expressly describes changing web-hosting providers instead of registrars as a possible way to avoid the inter-registrar transfer process. It also mentions changing nameservers or the hosting IP address and recommends checking the available options with the registrar or host.

Check transfer readiness before setting the launch dependency

The same FAQ describes circumstances that can prevent or restrict an inter-registrar transfer, including recent registration, recent transfer and certain changes to registrant information. It distinguishes situations in which a registrar may deny a transfer from situations in which denial is required.

Do not turn those examples into a promise that every domain is transferable immediately, or that every lock has a removable switch. Ask the responsible registrar for the actual reason, applicable policy and next permitted action for your domain. Have it confirm how a proposed contact or holder change affects the intended sequence before making that change.

That does not mean leaving inaccurate registration information unresolved. It means getting a supported plan rather than casually editing details and discovering that the planned transfer date no longer works. If the website move can proceed independently, document that option instead of silently delaying the whole project.

Separate registration confirmation from service continuity

For the migration brief, ask who will preserve or recreate the necessary DNS configuration and verify the website and email services. A transfer request being submitted does not prove those services work at the intended destination. Conversely, a new website loading successfully does not establish that registration management has moved.

These are proposed acceptance controls, not guarantees made by the ICANN FAQ. Confirm whether any DNS or email service depends on the supplier being left, and agree its continuation or replacement before ending that service. Avoid cancelling the old bundle merely because one part of the move appears complete.

Keep authorisation material out of ordinary project documents. The FAQ describes an Auth-Code used for registrar transfers. The authorised domain holder should handle that material through the providers' secure processes, not paste a real code into a public ticket, article draft or chat. The planning record needs responsibility and status, not the code itself.

Accept each outcome separately

Agree evidence for each change actually in scope. Registration management, holder details, DNS service, website functionality and email continuity need their own checks. Record an unfinished registrar transfer honestly even if the new website is already live; do not describe a pending request as completed.

Use an invented service map at a website migration discussion. Include one scenario where hosting changes but registration stays put, and another where the registrar confirms a transfer restriction. Ask the supplier to explain the permitted sequence and the checks that protect continuing services.

The useful deliverable is a migration with explicit dependencies, not a vague promise to “move the domain”. No domain, provider account, nameserver or live website was changed to prepare this article.