Who owns the domain today?
Moving a website to new hosting does not always require transferring the domain registration, and changing DNS does not always require moving hosting. Start by mapping who owns the domain, which system controls its records, and what else those records support.
Find the registrar account, billing owner, renewal method, and administrators. The business should retain a clear path to its own domain without depending on an individual contractor’s personal login. Record recovery contacts in the approved secure system, not in a public project document. Confirm whether a planned change is a registrar transfer, DNS-provider change, website-host change, or a combination.
Ask for the current DNS record list before touching it. Email delivery, verification, subdomains, and other applications may rely on records that do not look connected to the main website. Cloudflare’s DNS explanation describes how domain names resolve to services. The practical lesson is that a domain change has more reach than a visual website change.
What must remain working during the move?
List the website, email, booking links, client portal, file services, and any campaign landing pages that use the domain. Identify the records and account owners for each. If the new web host supplies a target address, make sure the team knows exactly which record should change and which must stay. Never replace the whole zone from memory.
Plan timing with the people who receive inquiries and support requests. A temporary web issue and an email interruption have different consequences. Keep the old environment available until the new path is verified and the business has a rollback route. The team should know which system is authoritative at each step.
How will you check the domain and DNS transfer?
Verify the site from several networks and devices after the change. Check the secure connection, canonical domain, forms, email receipt, and important subdomains. DNS caching can mean not every user sees the same destination immediately. Do not call the move complete based only on what one administrator sees in one browser.
If the change includes new URLs, plan redirects and search signals separately. A DNS update points visitors to a host. It does not, by itself, map an old page URL to a new page. Google’s site move guidance covers that URL-level work when paths or domains change.
What makes recovery possible?
Save the approved record inventory, old and new targets, change owner, and reversal steps. Keep a snapshot or export of the zone before editing, with appropriate access controls. Decide who can authorize a reversal and when the team will use it. If the old host is shut down immediately, a DNS rollback may point visitors to nowhere.
Test key business actions after the move, not merely the homepage. A site can load while the contact form posts to an old endpoint or a payment callback still expects a former domain.
Gather ownership and records before the date.
Bring registrar and DNS ownership details, current records, hosting targets, email provider, important subdomains, and the proposed date. See domain registration for the related service path. Talk to a Specialist to plan a domain or host transition around the services that must stay available.
