Failed Website Migration: Rollback Plan Before You Touch DNS

Most failed migrations fail at cutover, not at design. If you cannot reverse DNS, hosting, and redirects in a documented window, you do not have a launch plan — you have a hope. Write the rollback before anyone lowers TTLs.

Inventory must-win URLs: home, money pages, login, checkout, top landing pages from Search Console and ads. Map each to a 301 on the new stack and test on staging hosts. Screenshot key templates so “looks fine” has a baseline.

Backups are useless if restore is untested. Practice restore on a throwaway environment. Record credentials for DNS, CDN, SSL, and the old host. Assign one person who can execute rollback without a meeting.

First-hour checks after cutover: robots.txt, sitemap, HTTPS, forms, payments, analytics, and a sample of redirects. Watch Search Console and server 404 rates. If checkout or lead forms fail, roll back — do not “hotfix in production” for six hours while ads keep spending.

SEO parity includes titles, canonicals, hreflang (if any), and structured data that still validates. Content parity is not optional for pages that rank. Launching a thin redesign and promising “SEO later” is how traffic cliffs happen.

If a migration already went wrong, or cutover is this week and the rollback is vague, send both old and new URLs for a free audit. I will rank risks and a fixed-price stabilize-or-rollback path.