{"product_id":"claude-code-website-migration-replatforming-system","title":"Claude Code Website Migration \u0026 Replatforming System","description":"\u003ch2 id=\"headline\"\u003eMove Your Website Without Losing What Matters.\u003c\/h2\u003e\n\n\u003cp class=\"sbs-lede\"\u003ePlan, 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.\u003c\/p\u003e\n\n\u003ch2 id=\"problem\"\u003eThe problem\u003c\/h2\u003e\n\n\u003cp\u003eA 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.\u003c\/p\u003e\n\n\u003cp\u003eAsk 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 \u003ccode\u003enoindex\u003c\/code\u003e still set, the DNS panel opened before anyone wrote down what was in it.\u003c\/p\u003e\n\n\u003ch2 id=\"solution\"\u003eThe solution\u003c\/h2\u003e\n\n\u003cp\u003eA structured migration system that runs inside Claude Code and treats a migration as what it is — a mapping and validation exercise:\u003c\/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eDISCOVER → INVENTORY → BASELINE → MAP → BUILD → MIGRATE → VALIDATE → CUT OVER → MONITOR → ROLL BACK IF NECESSARY\u003c\/code\u003e\u003c\/pre\u003e\n\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eWorking scripts\u003c\/strong\u003e 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.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eClaude Code commands\u003c\/strong\u003e that run the scripts, read the results and explain them — each marked \u003cstrong\u003eREAD ONLY\u003c\/strong\u003e, \u003cstrong\u003eMODIFIES FILES\u003c\/strong\u003e or \u003cstrong\u003ePRODUCTION IMPACT POSSIBLE\u003c\/strong\u003e, each with its purpose, inputs, preconditions, safety rules, steps, expected output, validation and rollback written down.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eA clear line\u003c\/strong\u003e 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.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSeven platform guides\u003c\/strong\u003e with the facts that change the plan: what each platform exports and imports, where its redirects live, its URL conventions, and what always breaks.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch2 id=\"included\"\u003eWhat is included\u003c\/h2\u003e\n\n\u003cp\u003e190 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.\u003c\/p\u003e\n\n\u003cdiv class=\"sbs-table\"\u003e\n\u003ctable\u003e\n\u003cthead\u003e\u003ctr\u003e\n\u003cth\u003eModule\u003c\/th\u003e\n\u003cth\u003eCovers\u003c\/th\u003e\n\u003c\/tr\u003e\u003c\/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e01-migration-discovery\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eThe facts before the plan: platforms, hosting, DNS, counts, forms, integrations, analytics, rollback; the questionnaire and the report\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e02-url-inventory\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eCrawl + sitemap + Search Console + analytics + logs, merged and reconciled — the baseline every comparison is measured against\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e03-content-inventory\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eContent types, thin\/empty\/duplicate\/orphan flags, a migration method per row\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e04-seo-baseline\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eTitles, descriptions, canonicals, robots, H1s, schema types frozen; the exports only a person can take\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e05-analytics-baseline\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eLoaders and IDs on every page; events, consent, the numbers from before\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e06-migration-mapping\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eThe URL map as the contract: KEEP \/ MOVE \/ MERGE \/ REMOVE, by rule and by hand, never to the homepage\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e07-content-migration\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eConvert, import or rebuild; HTML to Markdown with a review list; frontmatter and slugs from the map\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e08-media-migration\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eEvery image and file inventoried, moved, validated; the old host kept until references are zero\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e09-metadata-migration\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eMetadata carried, then compared; the three failures that take sites out of the index\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e10-structured-data\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eJSON-LD per type re-implemented and compared, subtypes recognised\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e11-internal-links\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eLinks rewritten from the map, audited for broken, old-domain, staging, redirect\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e12-redirects\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eMap, validate, generate for six platforms, deploy where they belong, test on the real origin\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e13-staging-validation\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eEverything provable before DNS, in one run; what staging cannot prove, listed\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e14-performance\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eTiming facts before and after, like for like\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e15-dns-cutover\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eRecord, lower TTL, change only the web records, verify, never touch mail\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e16-launch\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eGo \/ no-go rules, roles, the first hour, search engines told\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e17-post-migration-validation\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eThe full audit on the live domain; the scorecard and how it is computed\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e18-rollback\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eReadiness verified as facts; the decision matrix; the procedure\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e19-monitoring\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003e24 hours, 7 days, 30 days; 404 triage; when to decommission\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003e20-platform-guides\u003c\/code\u003e\u003c\/td\u003e\n\u003ctd\u003eWordPress → Astro, WordPress → Shopify, WordPress → WordPress, Shopify replatforming, Static → Astro, domain migration, URL-structure migration\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/tbody\u003e\n\u003c\/table\u003e\n\u003c\/div\u003e\n\n\u003cp\u003ePlus \u003ccode\u003e.claude\/commands\/\u003c\/code\u003e with 37 slash commands, \u003ccode\u003escripts\/\u003c\/code\u003e with 28 scripts, \u003ccode\u003etemplates\/\u003c\/code\u003e with \u003ccode\u003emigration-config.yaml\u003c\/code\u003e, the inventory, map, redirect, critical-page, DNS and risk-register CSVs, the cutover plan, the launch-readiness sheet, a \u003ccode\u003eCLAUDE.md\u003c\/code\u003e 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 \u003ccode\u003eexamples\/wordpress-to-astro\/\u003c\/code\u003e — a complete fictional migration with every inventory, map, comparison and report, produced by running the scripts.\u003c\/p\u003e\n\n\u003ch2 id=\"commands\"\u003eThe commands\u003c\/h2\u003e\n\n\u003cdiv class=\"sbs-table\"\u003e\n\u003ctable\u003e\n\u003cthead\u003e\u003ctr\u003e\n\u003cth\u003eCommand\u003c\/th\u003e\n\u003cth\u003eMode\u003c\/th\u003e\n\u003cth\u003ePurpose\u003c\/th\u003e\n\u003c\/tr\u003e\u003c\/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/migration-discovery\u003c\/code\u003e · \u003ccode\u003e\/migration-plan\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eRead \/ Files\u003c\/td\u003e\n\u003ctd\u003eThe facts, then the plan with gates, the automatable\/manual split and a seeded risk register\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/url-inventory\u003c\/code\u003e · \u003ccode\u003e\/target-url-inventory\u003c\/code\u003e · \u003ccode\u003e\/url-map\u003c\/code\u003e · \u003ccode\u003e\/url-coverage\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eRead \/ Files\u003c\/td\u003e\n\u003ctd\u003eSource and target inventories in one shape; the map; UNCHANGED \/ REDIRECTED \/ REMOVED \/ MISSING \/ BROKEN\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/content-inventory\u003c\/code\u003e · \u003ccode\u003e\/media-inventory\u003c\/code\u003e · \u003ccode\u003e\/media-validation\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eRead\u003c\/td\u003e\n\u003ctd\u003eWhat each URL is and what happens to it; every file, where used, whether it resolves\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/seo-baseline\u003c\/code\u003e · \u003ccode\u003e\/analytics-baseline\u003c\/code\u003e · \u003ccode\u003e\/performance-baseline\u003c\/code\u003e · \u003ccode\u003e\/dns-inventory\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eRead\u003c\/td\u003e\n\u003ctd\u003eThe “before”: metadata, tracking, timings, and every DNS record including the ones that must not change\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/content-migration\u003c\/code\u003e · \u003ccode\u003e\/metadata-migration\u003c\/code\u003e · \u003ccode\u003e\/content-normalize\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eFiles\u003c\/td\u003e\n\u003ctd\u003eHTML to Markdown with a review list; metadata into the target’s format; shortcodes, headings, paths tidied\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/redirect-map\u003c\/code\u003e · \u003ccode\u003e\/redirect-config\u003c\/code\u003e · \u003ccode\u003e\/redirect-validation\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eFiles \/ Read\u003c\/td\u003e\n\u003ctd\u003eThe validated map; the platform’s configuration; PASS \/ CHAIN \/ WRONG-CODE \/ WRONG \/ MISSING \/ LOOP \/ DEAD\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/metadata-compare\u003c\/code\u003e · \u003ccode\u003e\/schema-compare\u003c\/code\u003e · \u003ccode\u003e\/internal-link-audit\u003c\/code\u003e · \u003ccode\u003e\/old-domain-scan\u003c\/code\u003e · \u003ccode\u003e\/tracking-validation\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eRead\u003c\/td\u003e\n\u003ctd\u003ePage-by-page comparisons; links; references to the old and staging hosts; expected IDs on every page\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/critical-page-validation\u003c\/code\u003e · \u003ccode\u003e\/form-validation\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eRead\u003c\/td\u003e\n\u003ctd\u003eThe pages the business cannot lose, strictly; forms proven by a submission, not by presence\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/staging-validation\u003c\/code\u003e · \u003ccode\u003e\/performance-compare\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eRead\u003c\/td\u003e\n\u003ctd\u003eEverything checkable before DNS moves; timings after against before\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/rollback-readiness\u003c\/code\u003e · \u003ccode\u003e\/cutover-plan\u003c\/code\u003e · \u003ccode\u003e\/pre-launch-check\u003c\/code\u003e · \u003ccode\u003e\/migration-go-no-go\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eRead \/ Files\u003c\/td\u003e\n\u003ctd\u003eFacts a rollback needs; the exact DNS changes; the last gate; the recorded decision\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/migration-cutover\u003c\/code\u003e · \u003ccode\u003e\/migration-rollback\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eProduction\u003c\/td\u003e\n\u003ctd\u003eStep by step, each change quoted and confirmed, the rollback path stated first\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\n\u003ccode\u003e\/post-migration-audit\u003c\/code\u003e · \u003ccode\u003e\/website-migration-audit\u003c\/code\u003e · \u003ccode\u003e\/migration-report\u003c\/code\u003e\n\u003c\/td\u003e\n\u003ctd\u003eRead \/ Files\u003c\/td\u003e\n\u003ctd\u003e\n\u003cstrong\u003eThe master audit\u003c\/strong\u003e on the live domain: scorecard, findings by severity, GO \/ GO WITH WARNINGS \/ NO-GO; the client report\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/tbody\u003e\n\u003c\/table\u003e\n\u003c\/div\u003e\n\n\u003ch2 id=\"scorecard\"\u003eThe scorecard\u003c\/h2\u003e\n\n\u003cpre\u003e\u003ccode\u003eURL Coverage:            100%\nRedirect Integrity:       94%\nMetadata Preservation:    73%\nCanonical Integrity:     100%\nInternal Links:          100%\nMedia Integrity:         100%\nAnalytics:               PASS\nForms:                   PASS\nCritical Pages:          PASS\n\nOverall Migration Health: 94\/100\nLAUNCH RECOMMENDATION: GO WITH WARNINGS\u003c\/code\u003e\u003c\/pre\u003e\n\n\u003cp\u003eThat 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.\u003c\/p\u003e\n\n\u003ch2 id=\"usecases\"\u003eUse cases\u003c\/h2\u003e\n\n\u003cul\u003e\n  \u003cli\u003eMove a WordPress site to Astro on Netlify or Vercel with every post converted, every archive mapped, every redirect tested.\u003c\/li\u003e\n  \u003cli\u003eReplatform 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.\u003c\/li\u003e\n  \u003cli\u003eChange a WordPress host or theme and prove the metadata and structured data survived the theme swap.\u003c\/li\u003e\n  \u003cli\u003eChange domains: every URL redirected in one hop, both zones recorded, mail untouched, Search Console told in the right order.\u003c\/li\u003e\n  \u003cli\u003eFlatten a URL structure and rewrite internal links from the map instead of relying on redirects.\u003c\/li\u003e\n  \u003cli\u003eTake a static HTML folder into Astro with the shared markup componentised and the \u003ccode\u003e.html\u003c\/code\u003e URLs decided, not defaulted.\u003c\/li\u003e\n  \u003cli\u003eValidate a migration someone else did: crawl, compare, score, list what was lost.\u003c\/li\u003e\n  \u003cli\u003eRoll back deliberately, from the recorded DNS, when a blocker cannot be fixed forward.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch2 id=\"who\"\u003eWho it is for\u003c\/h2\u003e\n\n\u003cp\u003eDevelopers 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.\u003c\/p\u003e\n\n\u003ch2 id=\"safety\"\u003eSafety\u003c\/h2\u003e\n\n\u003cp\u003eEvery 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.\u003c\/p\u003e\n\n\u003ch2 id=\"compare\"\u003eHow it fits with the other five\u003c\/h2\u003e\n\n\u003cdiv class=\"sbs-table\"\u003e\n\u003ctable\u003e\n\u003cthead\u003e\u003ctr\u003e\n\u003cth\u003e\u003c\/th\u003e\n\u003cth\u003eMigration \u0026amp; Replatforming\u003c\/th\u003e\n\u003cth\u003eWebsite Launch System\u003c\/th\u003e\n\u003cth\u003eSEO \u0026amp; Website Audit\u003c\/th\u003e\n\u003cth\u003eConversion \u0026amp; Revenue\u003c\/th\u003e\n\u003cth\u003eOperations \u0026amp; Maintenance\u003c\/th\u003e\n\u003cth\u003eShopify Automation\u003c\/th\u003e\n\u003c\/tr\u003e\u003c\/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ePrice\u003c\/td\u003e\n\u003ctd\u003e$29.99\u003c\/td\u003e\n\u003ctd\u003e$19.99\u003c\/td\u003e\n\u003ctd\u003e$19.99\u003c\/td\u003e\n\u003ctd\u003e$19.99\u003c\/td\u003e\n\u003ctd\u003e$39.99\u003c\/td\u003e\n\u003ctd\u003e$39.99\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eStage\u003c\/td\u003e\n\u003ctd\u003eMigrate\u003c\/td\u003e\n\u003ctd\u003eBuild\u003c\/td\u003e\n\u003ctd\u003eRank\u003c\/td\u003e\n\u003ctd\u003eConvert\u003c\/td\u003e\n\u003ctd\u003eOperate\u003c\/td\u003e\n\u003ctd\u003eAutomate Shopify\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eBest for\u003c\/td\u003e\n\u003ctd\u003eA site that is moving\u003c\/td\u003e\n\u003ctd\u003eA site you are building\u003c\/td\u003e\n\u003ctd\u003eA site that is not ranking\u003c\/td\u003e\n\u003ctd\u003eTraffic that under-converts\u003c\/td\u003e\n\u003ctd\u003eA live site to keep healthy\u003c\/td\u003e\n\u003ctd\u003eA Shopify catalogue at scale\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eURL mapping, redirects, cutover, rollback\u003c\/td\u003e\n\u003ctd\u003eComplete\u003c\/td\u003e\n\u003ctd\u003eLaunch-day checks only\u003c\/td\u003e\n\u003ctd\u003eRedirect audit only\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003ctd\u003eRedirect audit only\u003c\/td\u003e\n\u003ctd\u003eShopify redirect list\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eBefore\/after comparison of metadata, schema, links, media\u003c\/td\u003e\n\u003ctd\u003eComplete\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003ctd\u003eSite-wide audit, one point in time\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003ctd\u003eBaseline comparison\u003c\/td\u003e\n\u003ctd\u003eCatalogue only\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eWorking scripts\u003c\/td\u003e\n\u003ctd\u003e28, standard library\u003c\/td\u003e\n\u003ctd\u003eNot included\u003c\/td\u003e\n\u003ctd\u003eNot included\u003c\/td\u003e\n\u003ctd\u003eNot included\u003c\/td\u003e\n\u003ctd\u003e11, standard library\u003c\/td\u003e\n\u003ctd\u003e32, standard library\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ePlatform guides\u003c\/td\u003e\n\u003ctd\u003e7 migration guides\u003c\/td\u003e\n\u003ctd\u003eBuild systems per platform\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003ctd\u003eNot covered\u003c\/td\u003e\n\u003ctd\u003e4 platform guides\u003c\/td\u003e\n\u003ctd\u003eShopify only\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/tbody\u003e\n\u003c\/table\u003e\n\u003c\/div\u003e\n\n\u003cp\u003eThe first three are also sold together as the \u003ca href=\"\/products\/complete-site-builder-stack\"\u003eComplete Site Builder Stack\u003c\/a\u003e. This one is separate and specific: it is for the weeks a site is moving. Before the move, the \u003ca href=\"\/products\/claude-code-seo-website-audit-toolkit\"\u003eSEO \u0026amp; Website Audit Toolkit\u003c\/a\u003e gives the baseline audit; after it, the \u003ca href=\"\/products\/claude-code-website-operations-maintenance-system\"\u003eOperations \u0026amp; Maintenance System\u003c\/a\u003e keeps the new site healthy; a Shopify destination pairs with the \u003ca href=\"\/products\/claude-code-shopify-automation-admin-api-toolkit\"\u003eShopify Automation Toolkit\u003c\/a\u003e for the catalogue import. Buying this one does not include the others, and there is no automatic upgrade credit.\u003c\/p\u003e\n\n\u003ch2 id=\"delivery\"\u003eDelivery and licence\u003c\/h2\u003e\n\n\u003cp\u003eA 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.\u003c\/p\u003e\n\n\u003cp\u003eLicensed to one person for unlimited sites, including client work. You may not redistribute or resell it. Full terms are in \u003ccode\u003eLICENSE.md\u003c\/code\u003e 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.\u003c\/p\u003e\n\n\u003ch2 id=\"notpromised\"\u003eWhat is not promised\u003c\/h2\u003e\n\n\u003cp\u003eNo 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.\u003c\/p\u003e\n","brand":"Site Builder Stack","offers":[{"title":"Default Title","offer_id":56280166629668,"sku":"SBS-CCWMRS-V1","price":29.99,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0987\/3925\/7636\/files\/product-migration-system.png?v=1789344153","url":"https:\/\/sitebuilderstack.com\/products\/claude-code-website-migration-replatforming-system","provider":"Site Builder Stack","version":"1.0","type":"link"}