A careful migration separates preparation, testing and the final change that sends visitors to the new hosting. Begin by identifying everything the website depends on: files, database, runtime settings, scheduled jobs, domain records, outgoing email and external integrations. A move can appear successful at first while a forgotten background job or mail setting causes problems later.
IN THIS ARTICLE
01 Prepare and test the destination
First, make a usable copy of the current site and arrange access to the old and new hosting. Keep the original service active. Copy the site into the destination environment and check it using an appropriate preview method agreed with our team. Verify the homepage, important internal pages, administrator login, images, forms and any features that write data. A preview address can affect application behaviour, so ask us how to test domain-sensitive functions.
02 Preserve new data and update the authoritative DNS
Next, plan the final data transfer. A static brochure site may change very little during the move. A store or booking system can receive new transactions continuously. Decide how those final changes will be preserved and whether a brief maintenance period is needed. Copying an older database over a newer live one can lose recent orders or submissions.
Update DNS at the provider that actually controls the domain's authoritative records. Preserve the records for email and other services you intend to keep elsewhere. Different visitors can temporarily reach different destinations while cached DNS answers expire, so continue monitoring both environments during the transition.
03 Verify the business functions after the move
After the move, check HTTPS, redirects, contact forms, outgoing notifications, scheduled jobs and payment integrations. Record any failures with the affected address and time. Ask us to investigate before shutting down the source account. A migration is complete when the destination's real business functions have been verified, not merely when a file transfer reports success.
How should DNS be changed during a live website migration?
- Record the current authoritative nameservers and all records used by the website, mail and external services.
- Prepare the destination and check its certificate and application configuration before directing visitors to it.
- If changing nameservers, build the required zone at the new provider and coordinate DNSSEC rather than leaving an old delegation-signing record behind.
During the transition, different resolvers may still use cached answers. Keep both environments available long enough to verify the actual handover. A lower TTL can help only after the previous cached TTL has expired; it does not instantly clear every resolver cache.