Featured case studies
Trusted by Stripe, PayPal and 460+ more
Why teams leave Sanity
Four reasons marketing teams move their site off Sanity
Schema changes need code
New fields and page types live in your code. In Webflow, your team manages CMS fields without a developer.
Front end stays with engineers
Sanity stores content, but every layout is custom code. In Webflow, marketing builds and edits pages.
Two systems to maintain
You run Sanity and a custom front end, plus hosting and builds. Webflow puts them in one platform.
Local teams depend on others
Regional marketers often can't publish on their own. In Webflow, each market can manage its own pages.
What moves
What happens to your Sanity site when it moves to Webflow
Schemas and documents
We review your schemas and references, then plan Webflow CMS collections around how your marketing team publishes today.
Portable Text
We export your documents, convert Portable Text and custom blocks into Webflow rich text, and check the result before launch.
Images and files
Images and files move from Sanity's asset pipeline into Webflow, with alt text kept and links updated across your pages and posts.
Multiple languages
Each language moves to Webflow Localization. Markets can launch in stages, with redirects sending the rest to your old site until ready.
Other apps using the API
If a product or app also reads from Sanity, it can stay there. We move the marketing site and agree on the split with your engineers.
Front end and redirects
We rebuild your front end as Webflow templates and components, and map every old URL with 301 redirects ready for launch day.
How it works
Five steps to move your site
and protect your rankings
Start with the facts
We review every page and ranking
We crawl your site and pull rankings, traffic, backlinks, CMS content and integrations, so we know what brings in your leads and what could break in the move.
Then we decide with you which pages to keep, merge or drop, so you get a clear plan and scope before any work starts on the new site or its content.
Migration experience
We've moved large Sanity sites
GoodHabitz ran a six-language site on Sanity and a custom front end. We moved it to Webflow in stages, starting with English and German, and regional marketers now publish their own content.
Worth the investment
We were really impressed by how Flowout presented their approach, listened to us, and genuinely cared about the product they were going to provide. They helped us build our website from the ground up, from just five pages to nearly 100, including our resource center, blog, and CMS-powered legal pages.
John McClellan
Vice President of Marketing @shiphero
Adam Frank
Head of Growth & Marketing @Foxglove
Jeff Hanna
CEO @ShopwithFriends
Arkadiy Kondrashov
Head of Marketing @ Meridia
The team was really great, moved quickly and replicated what we had very fast. One of the things I appreciate most is that they took an extra day or two to make sure everything was right.
Felipe Brito
Head of Product @LUIH
What I liked the most was the direct access to the developer. It felt like Miha was part of our team, and we could just ask him like we would any other colleague to help us fix something, do something, or even teach us something.
Katie Zigelman
SVP Marketing @Alice
Development
/
Webflow integration
/
Design
/
Development
/
Localization
/
Development
/
SEO Optimization
/
Lottie animations
/
Ongoing maintenance
/
.svg)
FAQ
What marketing teams ask before they migrate
Will we lose SEO rankings when we move from Sanity to Webflow?
Some movement is normal while Google re-indexes your site. We plan every URL before the move, carry over titles, meta descriptions and schema, set up 301 redirects, and track rankings after launch, so we can fix any drop early. See our full Webflow migration process.
How do you handle URLs and redirects from a Sanity site?
We crawl your live site and map each old URL to its new page, including routes set in your front-end code. Webflow has its own rules for CMS URLs, so we plan the structure early and keep your current paths where we can. Everything else gets a 301 redirect for launch, and we check them again once the site is live.
What happens to our Sanity schemas and Portable Text?
We review your schemas and references, then plan Webflow CMS collections around them. Portable Text and custom blocks get converted to Webflow rich text. Webflow's CMS is simpler than Sanity's, so we agree with you on how to handle complex structures before we move anything.
Can you move a multi-language Sanity site in stages?
Yes. With GoodHabitz, we launched English and German first, and redirects sent the other languages to the existing site until each one was ready. Today, its whole six-language site runs on Webflow, and regional marketers publish their own content.
Do we have to leave Sanity completely?
No. If a product or app reads content from Sanity, it can stay there while the marketing site moves to Webflow. We agree on the split with your engineers, so nobody has to maintain the same content twice.
How long does a Sanity to Webflow migration take?
It depends on your page count, templates, integrations and languages, and on how many reviews your team needs. We share a timeline once we've looked at your current site, so the plan reflects your scope and not a general estimate.
How much does a Sanity to Webflow migration cost?
Migrations start from $10,000. Your final price depends on scope, including your pages, templates, CMS content, languages and integrations, and we confirm it after the first call. You can see our starting prices on the pricing page.
Will our team need to learn Webflow?
Your editors can update pages and CMS content without touching the Designer, and we train them before handover. We also leave docs on how the site is built. If you want ongoing help, our Evolve and Grow packages start from $5,000 per month.
Join Stripe, Kajabi and 460+ more
