Start with an inventory, not a DNS change
Write down the current domain, hosting account, public addresses and the service responsible for DNS. Include the www version, subdomains, mail records and any external forms. A website move and a mail move are separate changes. Keeping them separate makes faults easier to identify. List the pages people can already reach, including old links from other sites.
Prepare the destination while the original still works
Place a copy on the destination and inspect it using a controlled preview. Check navigation, images, downloads and the response for a missing page. If the application needs a database, restore a matching copy rather than assuming the files are sufficient. For a static site, test that every page opens directly; navigating from the home page alone can conceal broken paths.
Make an address-by-address map
Keep useful page addresses wherever possible. When a path changes, redirect it to the closest equivalent page. Sending every old article to the home page loses context for visitors and search engines. Include both trailing-slash variants and any old query-string links in the map. Test a small representative sample first, then check the complete list.
Treat DNS as a transition
Changing a DNS record does not instantly move every visitor. Cached answers may continue to point to the old host. Keep both versions available during the transition and avoid making unrelated changes at the same time. Lowering a record's TTL only helps once existing cached answers have expired; it is not a retrospective cache flush.
Keep a usable rollback
Save the old DNS values and a dated copy of the site before the change. Define what would trigger a rollback: broken checkout, missing pages, certificate errors or a service that cannot be restored promptly. Confirm who can make that decision. A backup becomes useful only when the files, configuration and restoration steps are accessible to the person doing the recovery.
Check from the visitor's side
After the move, test HTTP and HTTPS, the preferred domain and its aliases, a deep page and a deliberately missing address. Check mail separately if its settings changed. Keep the old hosting copy until the migration has been observed across the expected cache period and the important journeys have passed. Record the actual checks, not just the time the DNS button was pressed.
Put it into practice
| Address | Expected result |
|---|---|
| example.org/guide/ | Same article at the destination |
| www.example.org/guide/ | Redirect to the preferred hostname |
| example.org/not-a-page/ | A useful 404 response |
Sources & further reading
Examples and worksheets on this page are illustrative. Documentation links were checked in November 2026; follow the relevant product’s current instructions.
