What is a Sanity to Webflow migration?
It moves your content out of a Sanity dataset into Webflow collections, and replaces the front end that used to query it with pages built visually. Your Studio is retired with it.
You get one tool for writing, design and hosting. You give up custom editing tools and the ability to use the same content anywhere by query.
When staying on Sanity is the better call
- Developers are on hand and shipping well
- Content goes to apps or other channels as well as the site
- Your model is deeper than Webflow plan limits allow
- Marketing mostly needs a better Studio, not a new platform
Compare Webflow CMS vs Sanity. If you like Sanity and just want a tidier build, see Sanity CMS.
Exporting a dataset
sanity datasets export writes a gzipped tarball with your documents and assets. Any asset that returns an error is excluded, so we check the count. A flag leaves out drafts, which is what we normally want, as long as you have published what you plan to keep.
We also read the schemas, since the export has your data but not an explanation of what each field is for.
Converting Portable Text
Portable Text is structured JSON that can be turned into HTML, Markdown or anything else. Standard paragraphs, headings, lists and links are simple. Custom blocks, such as a callout or a code sample, need a decision each.
Webflow rich text keeps supported HTML and strips the rest on import, so anything fancy becomes an embed, a separate field or plain text. We show you each case before running it across every post.
Your code held more than you think
Metadata, sitemaps, canonical rules and redirects are often written in the front end, not in Sanity. Same for form handlers, analytics tags and any server logic. So we read the repo, not only the dataset.
If some of it is really an app, it can stay as code on its own subdomain or path. See Webflow development for how we handle custom code in a build.
Redirects and launch
Your route files decide your URLs, so we list them, then check against a crawl and Search Console. Changed paths each get a 301, and we keep the slug wherever Webflow's collection paths allow it.
- The TTL goes down a day ahead.
- On a call, the domain moves to Webflow.
- We check redirects, forms and tags on the live site.
- We send the sitemap, then read Search Console daily for two weeks.
Each old URL is mapped because that is how you protect what you have earned in search. Some movement is normal. Nobody can guarantee where you land.







