Moving a fast-growing site from Webflow to Sanity CMS has always meant writing a custom migration script, juggling CLI tools, and hoping rate limits don’t ruin the final run.
That is, until now. Today, we’re officially launching MigrateKit,
MigrateKit encapsulates the same workflows my team and I used at Ramp when migrating from Webflow to Sanity CMS in 2024.
Why Webflow to Sanity migrations hurt
Sanity’s official recommendation leaves teams with a costly detour:
- You need a developer who understands Node, the Sanity CLI, HTML-to-Portable Text conversion rules, and API rate limiting.
- Every collection requires custom mapping code plus retry logic, caching, and asset helpers.
- One malformed rich text field or image URL can force you to rerun the entire job.
- Stakeholders see nothing until engineering has stitched together another log dump.
- Sanity even maintains an entire migration courses — Replatforming from a legacy CMS to a Content Operation System — covering everything from deterministic IDs, API limits, and error handling, which is proof of how much engineering effort they expect.
That’s why migrations stall for weeks, even when everyone agrees Sanity is the right long-term home; Without MigrateKit, migrations
What MigrateKit delivers
MigrateKit replaces all that custom plumbing with a browser-based workspace built specifically for Webflow to Sanity migrations:
- Schema-aware field mapping – Connect your Sanity project once, pull the real document types and fields, then visually map each Webflow column.
- Automatic HTML to Portable Text conversion – Rich text, embeds, and inline formatting come across cleanly without touching
htmlToBlocks scripts. - Reliable asset handling – We detect every image/file reference, upload to Sanity, and let Sanity’s asset pipeline deduplicate identical files so you don’t burn storage on repeats.
- Deterministic IDs and safe drafts – Imports land as drafts composed with stable IDs based on Webflow Item IDs, so reruns never create duplicates.
- Zero-setup reliability – Built-in throttling, retries, and logs mean you can run migrations from any modern browser. No CLI, no
npm install, no bespoke infra.
How teams use MigrateKit
- Connect your Sanity project – Sign in, pick the right dataset (staging or production), and authorize MigrateKit.
- Upload the Webflow CSV export – Drop in the file exactly as Webflow gives it to you; we auto-detect slugs, titles, booleans, and dates.
- Map, preview, and test – Map columns to Sanity fields, preview sample docs, then run a draft import into staging.
- Promote to production – Once everything looks right, re-run into production with the same stable IDs and clean Portable Text.
Most teams finish their first migration in an afternoon instead of burning two sprint weeks on glue code.
See it in action
Prefer a quick demo before jumping in? Check out this 2-minute video.
Want the full rundown step-by-step?
Head to docs.contentwrap.io for detailed guides and troubleshooting notes.
Honest scope today
Right now, the self-service MigrateKit app focuses on getting
Cross-collection reference wiring, schema generation, image optimization, and migrations from additional CMSs are part of the custom migrations our team can run for you—just contact us from the site and we’ll scope the engagement alongside product access.
Start your migration
Ready to start your migration to Sanity without a script? Then head over to app.contentwrap.io to begin for free.
