--- title: "How I Used AI Agents to Migrate my Entire Site to Astro" url: https://daily.dev/posts/how-i-used-ai-agents-to-migrate-my-entire-site-to-astro-ba6sfp5qn source_url: https://codewithandrea.com/articles/ai-agents-migrate-site-astro type: article source: "Code with Andrea" published: 2026-08-13T10:48:39.746Z updated: 2026-08-13T10:49:06.554Z tags: ["testing", "ai-agents", "vibe-coding", "astro"] reading_time: 13 upvotes: 1 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # How I Used AI Agents to Migrate my Entire Site to Astro **[Code with Andrea](https://daily.dev/sources/codewithandrea)** · 13 min read · 1 upvotes · 0 comments ## Summary A developer shares a detailed case study of migrating a 400+ page production site (six years old, built with the Swift static site generator Publish) to Astro using AI coding agents. The workflow: turn 'feature parity' into a testable migration contract, prototype the riskiest technical assumptions first, build a deterministic (non-LLM) migration tool for content transformation, split visual verification into fast and exhaustive tiers, and keep final product and production decisions human-owned. The author ran agents (GPT 5.6 Sol on a $100 Pro plan) inside tmux sessions on a VPS using Git worktrees, completing roughly 100 issues and 80 PRs over two weeks. References the Bun-to-Rust rewrite project as inspiration and cautionary tale, since that migration reportedly still isn't complete. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How can I verify that an AI-driven site migration hasn't broken anything across hundreds of pages? Combine curated visual screenshot comparisons with direct automated checks for every part of the migration contract, since screenshots alone can't catch issues like corrupted inline code or broken redirects. One migration split verification into fast focused checks for normal PRs and a full exhaustive suite (route/redirect checks, metadata and feed checks, content-transformation checks, and integration-boundary checks) run only at release-candidate gates. _daily.dev surfaces practical verification strategies for developers shipping large-scale AI-assisted migrations._ ### Why did the Bun rewrite in Rust using AI agents run into problems? The Bun rewrite in Rust used 64 parallel AI agents at an estimated API cost of $165,000, but a follow-up analysis found the rewrite still isn't complete despite initial success claims, raising doubts about letting large numbers of agents run unchecked on big migrations without human oversight at each step. _developers weighing large AI-driven rewrites can follow real-world outcomes like this one on daily.dev._ ### What is a good workflow for migrating a legacy codebase to a new framework using AI coding agents? Define the outcome and constraints as a testable migration contract, prove the riskiest technical assumptions with a small disposable prototype, build a deterministic (non-LLM) tool for repeated transformations with its own test harness, verify actual behavior rather than plausible-looking output, and keep high-stakes product and production decisions human-owned rather than delegated to agents. _daily.dev helps developers compare hands-on approaches to structuring AI-assisted migration projects._ ## Similar posts on daily.dev - [Agents change the math on big bang migrations](https://daily.dev/posts/agents-change-the-math-on-big-bang-migrations-pac5lf3qj) · swizec.com · 34 upvotes · 8 comments --- Tags: [#testing](https://daily.dev/tags/testing), [#ai-agents](https://daily.dev/tags/ai-agents), [#vibe-coding](https://daily.dev/tags/vibe-coding), [#astro](https://daily.dev/tags/astro) [View this post on daily.dev](https://daily.dev/posts/how-i-used-ai-agents-to-migrate-my-entire-site-to-astro-ba6sfp5qn)