✓ ShippedByAgents
Practitioner (own blog/paper) Migration

Claude plans and reviews, Codex builds: a production music site migrated from a React SPA to Next.js in 36 hours

Nik McFly migrated a production music site from a React single-page app, whose page titles, canonical links and structured data were silently not reaching the document head, to a self-hosted Next.js site in 36 hours. Claude audited the site, wrote the plan, split it into releases and checked Codex's claims against staging and production; Codex built the app, moved routes, wrote tests and Docker/Caddy changes; the author made six product decisions and approved three production releases without writing application code. Each release started with a contract defining scope, done, required tests and rollback. Codex produced 27 commits and 7,803 lines; the site went from 0 to 45 routes with unique metadata in the initial HTML and 1,505 automated assertions per release.

The numbers (as reported)

Migration time36 hours
Codex output27 commits, 7,803 lines of source code
Routes with unique metadata in initial HTML0 → 45
Sitemap URLs resolving9 of 15 → 45 of 45
Automated assertions per release0 → 1,505
Production releases / rollbacks3 / 0
Largest initial JS download~1.3 MB → 658 KB

Facts

Company / subject
Nik McFly
Tools
Claude, OpenAI Codex
Codebase
brownfield
Work type
Migration
Stack
React, Next.js, Docker, Caddy, PostgreSQL
Published
2026-07-12
Last checked
2026-11-11

What the source claims Practitioner (own blog/paper)

Claimed by the builder, writing about their own work. Not checked independently.

  • A production site migrated from a React SPA to Next.js in 36 hours 36 hours
  • Routes with unique metadata in the initial HTML went from 0 to 45 0 → 45
  • Three production releases with no rollbacks 0 rollbacks
  • The owner wrote no application code
    “I did not write application code.”

Caveats

Self-reported by the site owner on his own blog. A single, fairly small site. The post does not say which Claude product (Claude Code or chat) was used. A staging Docker build filled the server disk and briefly caused production API errors during the migration. The author notes the performance numbers are for this migration only.

More stories by tool: OpenAI CodexClaude

Related topics: MigrationsBrownfield codebases

Source

nikmcfly.com (Nik McFly)

One email a week: what actually shipped

New sourced stories, the numbers behind them, and what didn't work. No hype.

We'll only use this to send the newsletter. See the privacy page.