Site migrations go wrong constantly. The cost is usually a 30-60% traffic drop that takes months to recover from. We’ve watched Bergen County businesses lose entire quarters of pipeline because somebody clicked “publish” on a new site before the redirect map was finished. The good news: every migration disaster follows the same predictable pattern, which means it’s preventable with a checklist.
Migration types that need this
Not every site change is a migration, but more changes qualify than people realize. Four scenarios trigger the full playbook:
- Domain change. Rebrand, acquisition, or moving from a .net to a .com. Every backlink on the internet now points to the wrong place.
- Platform change. WordPress to Shopify, Wix to WordPress, custom build to Webflow. URL structures rarely survive intact.
- Redesign with URL changes. A “refresh” that reorganizes the sitemap. Looks cosmetic, behaves like a full migration.
- Host migration. Lower-risk on paper, but DNS misconfigurations, SSL gaps, and IP-based reputation issues bite often.
What goes wrong
The failures repeat: broken or missing redirects, lost meta titles and descriptions, image URLs that 404 because the media library wasn’t moved cleanly, a Google Business Profile that still points to the old phone number or homepage, and a Search Console property that was never re-verified on the new domain. Each one is a small mistake. Together they compound into ranking collapse.
The pre-migration checklist (10 items)
Before anything goes live, every item below needs to be done and verified:
- Full crawl of the old site. Screaming Frog or equivalent. You can’t redirect URLs you don’t have on a list.
- Redirect map for every URL. Every old URL gets a 301 to its closest new equivalent. No bulk redirects to the homepage.
- Schema preserved. Local business, FAQ, breadcrumb, and review markup all carry over.
- Sitemap regenerated. New XML sitemap with the new URLs only, ready to submit.
- Robots.txt verified. Confirm staging-site blocks are removed and production is crawlable.
- GA and GSC backup. Export historical data before access changes.
- Internal link audit. Update every internal link in content to the new URL structure, not relying on redirects.
- NAP citations queued. Name, address, phone updates ready to push to directories the day of cutover.
- Staging tested with crawlers. Run a full crawl on staging as if it were live. Fix everything that flags.
- Communication queued. GBP update, social bio links, email signatures, paid ad destination URLs all ready to flip.
The post-migration checklist
The work isn’t done at launch. The first 14 days decide whether rankings hold:
- Monitor 404s daily for two full weeks. Anything that surfaces gets a redirect added within 24 hours.
- Watch Search Console for indexation drops, coverage errors, and manual actions.
- Resubmit the new sitemap to Google and Bing. Request indexing on priority pages.
- Fix anything broken within 48 hours. Broken images, missing pages, layout breaks on mobile, slow LCP.
- Verify GBP, Apple Maps, Yelp, and the top 10 citation sources reflect the new URL.
A real example: a Bergen County contractor migrated from WordPress to Webflow without a redirect map. They lost 47% of organic traffic and held that loss for four months before recovering. The fix wasn’t complicated — it was a properly built redirect file and a Search Console resubmission. The damage was waiting four months to do it.
How AJD handles this
We run migrations as a project, not a launch event. Pre-migration crawl, redirect map review, schema audit, and a staging-site dress rehearsal all happen before any production change. Post-launch we monitor Search Console and 404 logs daily for two weeks and fix issues the same day they surface. The goal is a flat traffic line through the transition — not a recovery story.
Planning a redesign, replatform, or domain change? Talk to AJD Digital Solutions before the migration, not after. We’ll map the redirect plan, audit the schema, and run the cutover so rankings hold. Book a migration consultation.
