Website Migration & Platform Switching.
Most migrations break one of three things: the rankings, the content, or the URLs that customers have bookmarked. We plan the move end-to-end — a full 301 map, a content parity checklist, a staged cutover, and a rollback plan you can actually use. The site goes live on the new platform with its SEO equity intact and a working link from every old URL to the right new one.
A short list of
real things.
Not deliverables in the consultant sense. Actual files, pages, docs, access. Listed here so there's no surprise.
- 01Content audit of the existing site: pages, posts, media, forms, custom fields, metadata
- 02301 redirect map covering every old URL — ranked by traffic, with edge cases documented
- 03Parity checklist: every page, every asset, every integration accounted for before cutover
- 04New site built on the target platform, against the existing design or a refresh, on a staging URL
- 05Full content migration with metadata, SEO titles, descriptions, schema, and canonical tags preserved
- 06Form, analytics, and pixel re-wiring verified end-to-end on staging before DNS flip
- 07Cutover runbook: DNS plan, TTL drop, rollback procedure, monitoring checklist
- 08Post-launch monitoring report: Search Console errors, ranking movement, redirect hits, 404 recovery
Four principles.
No slogans.
Zero data loss, in writing
Every page, every image, every form submission, every redirect rule from the old site lives on a parity checklist. Nothing moves to production until that list reads 100%. If something can't migrate cleanly, we flag it on the list before cutover — not after.
SEO preservation is not optional
Every old URL maps to a new URL. Every canonical tag is preserved or consciously changed. Every piece of structured data ships on day one, not 'after launch'. A migration that loses 20% of organic traffic is not a migration that worked — it's one that got rushed.
Staged cutover, not a big-bang weekend
We stage the new site on a subdomain, run it in parallel against the live site, and verify parity before DNS flips. Cutover is a scheduled event with a written checklist, not a Friday night with fingers crossed.
Rollback that actually works
Before DNS changes, the old site is backed up hot, the TTL is dropped, and we rehearse the rollback. If the new site has a launch-day blocker, we can be back on the old site within an hour — not rebuilding from a three-week-old backup.
How we work, start to finish.
- 01Audit and plan
We crawl the existing site, export the URL inventory, and sit with your team to understand which content is canonical, which is stale, and which breaks on the old platform. Output: a migration plan with scope, risks, timeline, and a parity checklist you sign off on before any build starts.
- 02Build on staging
New site built on the target platform, on a staging URL you can review throughout. Content is migrated in batches — we diff the old and new side-by-side, page by page, until the parity checklist is green. Forms, analytics, and integrations are re-wired and tested against real submissions.
- 03Cutover
DNS TTL dropped 24 hours before. Redirects and canonicals verified on staging. Old site backed up hot. We flip DNS during a pre-agreed low-traffic window, monitor Search Console and analytics for the first six hours, and confirm every top-traffic page returns 200 on the new URL.
- 04Post-launch monitoring
Two weeks of active monitoring: crawl the site daily, track rankings on the top 100 queries, watch for 404s in Search Console, fix any redirect edge cases that surface. You get a written report at the end of the window — what moved, what held, what we changed.
The targets we migrate against.
Not headline numbers. These are the baselines we work to on every migration — the ones we hit consistently, and the ones we measure on real data after cutover.
Before you
ask us.
Migrate without losing what matters.
Tell us where you're moving from and to. You'll get a migration plan, a risk read, and a realistic timeline — plus an honest answer on whether the new platform is actually worth the switch.
or email hello@genvoid.com