Why migrations stall
Moving files and a database is the easy part. The failure mode is usually a missing dependency: TLS renewal, a forgotten redirect, or mail that still points at the old host.
Order of work
- Map dependencies — hosting, DNS, TLS, redirects, and any mail or subdomain paths that must survive the switch.
- Prepare the destination — build and verify the new environment before touching live DNS.
- Define the cutover checklist — what “done” means for the site, HTTPS, and mail routes.
- Execute, then validate — do not stop at “DNS flipped.” Re-check the same checklist after the change is live.
When to ask for help
If the move crosses providers and nobody owns the full path, start with a hosting audit or describe the issue before the cutover window.
