Introduction
Migrating a Webflow site to Sanity used to mean weeks of manual work: exporting CSVs, reformatting data by hand, and rebuilding content model decisions from scratch. AI now does most of that work.
You make the calls that need human judgment: scope, content model shape, which URLs change. AI handles the rest, reading your Webflow API data, writing migration scripts, transforming content to your Sanity schema, and generating the code that ties the new site together. What used to take a team of developers a month can be done in days, working with Claude Code or Cursor.
By the end of this course, you'll have:
- A Sanity project with schemas mapped from your Webflow collections and page sections
- Working migration scripts that fetch every CMS item from the Webflow API and import it into Sanity
- All assets uploaded and referenced correctly in the new content model
- Static page content extracted from the page DOM API and seeded into Sanity documents
- Redirects, forms, sitemap, and draft preview wired up and ready for launch
The pattern repeats at every stage: you generate structured data from the Webflow API and save it to disk, then hand those files to an AI agent along with a Sanity schema and ask it to produce the migration script. The AI reads your actual data, not a generic example, and writes code matched exactly to your collections.
You'll also use Sanity Content Agent after import to backfill anything the migration data is missing: meta descriptions, image alt text, and other fields where Webflow's exports are thin. Rather than filling in gaps manually across thousands of documents, you run Content Agent against the staging dataset before launch.
The scripts and patterns in this course work whether you have 200 CMS items or 100,000. Smaller projects write items to disk as NDJSON and import them sequentially, which is simple and easy to debug. Larger projects stream the same NDJSON files into @sanity/import, which batches transactions and avoids the memory and throughput limits that would otherwise stall a large migration. Each lesson calls out which threshold applies.
This course is written as a series of AI prompts. You can work through it manually, copy-pasting each prompt into Cursor or Claude Code as you go, or you can drop the guide into your project and let your AI editor use it as a persistent reference.
Read MIGRATION.md. This is a step-by-step migration guide. We're starting at Lesson 2: Audit Your Webflow Content. Follow the guide from that point — read the files it references, run the prompts it specifies, and tell me when you need my input or when a review step requires a decision.The AI uses the guide as its playbook for the session. You drive the pace; it handles execution. Each chapter works well as a single session. Tell it where you left off when you resume.
One thing this doesn't replace: the review checkpoints throughout the guide. When a lesson says to inspect AI output before continuing, do that. Autonomous execution without those checks is how you end up with a schema that doesn't match your site.
Next, you’ll audit your Webflow content before opening a code editor.