Claude Code Website Migration & Replatforming System

Move Your Website Without Losing What Matters.

Plan, execute and validate website migrations with Claude Code — WordPress to Astro, WordPress to Shopify, host and theme moves, Shopify replatforming, static sites, domain changes, URL-structure changes. Every URL inventoried, every page mapped, every redirect tested, metadata and structured data compared page by page, media and forms and analytics verified, DNS recorded before it is touched, and a scorecard that says GO, GO WITH WARNINGS or NO-GO from evidence. Not a prompt pack: 28 working scripts, 37 Claude Code commands, 20 modules including seven platform guides, 13 checklists, and a complete fictional migration to read before you run your own.

The problem

A migration is not a copy. The new site builds, deploys, looks right — and three weeks later the search traffic is half what it was, a partner’s link lands on a 404, the contact form has been posting to nothing, the images break when the old hosting is cancelled, and nobody can say which of the 1,400 old URLs were supposed to go where. The deployment succeeded. The migration failed. Most of what was lost was not on anyone’s list, because nobody made the list.

Ask a capable model to “migrate the site” and you get the other failure: content converted without its metadata, every missing page redirected to the homepage, production launched with staging’s noindex still set, the DNS panel opened before anyone wrote down what was in it.

The solution

A structured migration system that runs inside Claude Code and treats a migration as what it is — a mapping and validation exercise:

DISCOVER → INVENTORY → BASELINE → MAP → BUILD → MIGRATE → VALIDATE → CUT OVER → MONITOR → ROLL BACK IF NECESSARY

• Working scripts for the parts a machine should do: a crawler that builds the URL inventory with status, metadata, canonicals, indexability, links, images, forms and structured data; a URL map drafter; an HTML → Markdown converter that flags what it could not convert; a redirect generator for nginx, Apache, Netlify, Vercel, Shopify and Cloudflare that refuses loops, chains and homepage dumps; a redirect tester that reports valid, missing, loop, chain, wrong destination and dead target; URL, metadata and schema comparison; canonical, robots and sitemap checks; an internal-link audit; an old-domain scan; a DNS inventory with before/after comparison; a critical-page validator; a rollback-readiness check; and the audit that scores it all. Python standard library only; nothing to install.
• Claude Code commands that run the scripts, read the results and explain them — each marked READ ONLY, MODIFIES FILES or PRODUCTION IMPACT POSSIBLE, each with its purpose, inputs, preconditions, safety rules, steps, expected output, validation and rollback written down.
• A clear line between what is automatable (inventory, compare, generate, test), semi-automatable (the map, the conversion — the scripts draft, a person decides) and manual (what a page becomes, DNS, forms, checkout, the go/no-go call). Per migration type, in a matrix.
• Seven platform guides with the facts that change the plan: what each platform exports and imports, where its redirects live, its URL conventions, and what always breaks.

What is included

190 files, 20 modules, 37 commands, 28 scripts, 7 platform guides, 13 checklists, 6 report templates — about 78,000 words plus working code. Every number here was counted from the bundle at build time.

Plus .claude/commands/ with 37 slash commands, scripts/ with 28 scripts, templates/ with migration-config.yaml, the inventory, map, redirect, critical-page, DNS and risk-register CSVs, the cutover plan, the launch-readiness sheet, a CLAUDE.md and six redirect configuration samples, 13 checklists, 6 report templates, a reference set (the automation matrix, go/no-go and rollback matrices, monitoring windows, troubleshooting) and examples/wordpress-to-astro/ — a complete fictional migration with every inventory, map, comparison and report, produced by running the scripts.

The commands

The scorecard

URL Coverage:            100%
Redirect Integrity:       94%
Metadata Preservation:    73%
Canonical Integrity:     100%
Internal Links:          100%
Media Integrity:         100%
Analytics:               PASS
Forms:                   PASS
Critical Pages:          PASS

Overall Migration Health: 94/100
LAUNCH RECOMMENDATION: GO WITH WARNINGS

That is the example migration’s real output. The score is the mean of the six percentages, minus ten per failure among analytics, forms and critical pages; any blocker — a critical page down, checkout broken, redirect gaps, DNS unrecorded, a certificate failure, the target unreachable, no verified backup, analytics absent when the business depends on it, production noindexed, canonicals pointing at staging, forms broken — makes it NO-GO regardless of the number. Every line names the file it was computed from; anything not measured is reported as NOT CHECKED, not scored. The score orders the work. It does not predict rankings or traffic and it is not a guarantee.

Use cases

• Move a WordPress site to Astro on Netlify or Vercel with every post converted, every archive mapped, every redirect tested.
• Replatform a content site to Shopify: products, blog and pages into Shopify’s fixed URL structure, redirects as a CSV the admin accepts, checkout on the critical-page list.
• Change a WordPress host or theme and prove the metadata and structured data survived the theme swap.
• Change domains: every URL redirected in one hop, both zones recorded, mail untouched, Search Console told in the right order.
• Flatten a URL structure and rewrite internal links from the map instead of relying on redirects.
• Take a static HTML folder into Astro with the shared markup componentised and the .html URLs decided, not defaulted.
• Validate a migration someone else did: crawl, compare, score, list what was lost.
• Roll back deliberately, from the recorded DNS, when a blocker cannot be fixed forward.

Who it is for

Developers and agencies doing migrations for clients; site owners moving their own site; SEO practitioners who need the before, the after and the difference in a file; operators inheriting a migration that was never validated. It assumes you can run a command and read a CSV. It does not assume you have migrated a site before — the discovery module and the platform guides are written for a first one, and the example is a whole migration you can read end to end.

Safety

Every command declares its mode. Read-only commands write only reports and inventories. File-modifying commands announce every path first. Production-impact commands — the cutover and the rollback — quote each DNS record, old value and new, and wait for a yes; the current zone is recorded before the panel is opened, and only the web records in the plan change. The system will not destroy the source before the target is validated, change DNS without the record, delete redirects without review, redirect missing pages to the homepage, launch without rollback preparation, or leave production noindexed or canonicalised to staging — those are its ten rules, in every command. Credentials for hosting, DNS and the CMS stay with you; the scripts never read, print or store them.

How it fits with the other five

The first three are also sold together as the Complete Site Builder Stack. This one is separate and specific: it is for the weeks a site is moving. Before the move, the SEO & Website Audit Toolkit gives the baseline audit; after it, the Operations & Maintenance System keeps the new site healthy; a Shopify destination pairs with the Shopify Automation Toolkit for the catalogue import. Buying this one does not include the others, and there is no automatic upgrade credit.

Delivery and licence

A single ZIP, delivered by download immediately after purchase. 190 files, about 300 KB — Markdown, Python, CSV, YAML and configuration samples; nothing to install beyond Python 3, which your machine almost certainly has. A published SHA-256 checksum accompanies the download so you can verify what you received.

Licensed to one person for unlimited sites, including client work. You may not redistribute or resell it. Full terms are in LICENSE.md inside the archive. WordPress, Shopify, Astro, Netlify, Vercel and Cloudflare are trademarks of their owners; this product is independent and not affiliated with or endorsed by any of them.

What is not promised

No ranking, no traffic figure, no guarantee that a migration loses nothing. The system inventories what there was, compares it with what there is, and lists the difference with a severity and a fix; the decisions — what a page becomes, when to cut over, whether to roll back — are yours, and it is built so that they stay yours and are recorded.