A website hosting move should begin with an inventory and a tested destination, then a controlled DNS change. Website traffic and domain email can depend on different records. Changing a web address is not a reason to delete the rest of the zone.
Capture the current state
Record the existing nameservers, web records, MX records and email-related TXT records. Save a zone export if your DNS provider supports it. Identify which provider currently answers authoritative DNS and who controls the domain registration. If changing DNS providers as well as hosting, review DNSSEC and the registrar's DS configuration with the relevant provider before the switch.
Prepare the destination first
Upload the website, verify its configuration and test a temporary or controlled preview address. Check an inner page and any backend action. Prepare HTTPS for the intended hostnames using the destination provider's supported process. A preview working over a temporary name does not prove the final hostname's certificate is ready.
- Preserve the old web record values for rollback.
- Plan the content and database freeze if the site accepts writes.
- Confirm the DNS provider's rules for apex records and CNAMEs.
- Lower relevant TTLs in advance when supported; previously cached answers keep their earlier expiry.
Cut over and check separate services
Change only the records required by the agreed migration. Verify the root domain and www separately. Check HTTPS, an inner route, a real application action and email delivery. Keep the old environment available for the agreed transition period so cached requests and rollback can be handled.
There is no universal instant propagation guarantee. Resolver caches, prior TTLs and authoritative configuration affect what visitors see. If the destination fails, use the saved rollback values and account for cached answers rather than repeatedly flipping records.
For a site with a database, pair this checklist with a restore rehearsal. Vibe Hosting's hosting options provide the product entry point; discuss the actual domain and application requirements before moving an active business site.