Webflow to a headless CMS
when the CMS is the bottleneck.
We move Webflow sites into a content system that can feed more than one website. Your Collections come out as a real content model, relationships and locales intact, and your URLs stay where they are. The design comes with you too. Honestly, that is the easy part.
Trusted by
Trusted by
Webflow was the right call. Until it wasn’t.
Webflow’s CMS was built to fill pages on a Webflow site, and it is genuinely good at that. The strain shows up when your content picks up a second job. Someone wants the same product copy inside an app, a partner asks for a feed, marketing adds a second language. Each of those meets a system where a Collection carries one template and one schema, where reference fields are a budget your site plan sets, and where anything programmatic waits behind a per-minute rate limit. All of it is Webflow working as designed. What changed is your side. This is one path through our wider headless migration practice. The same conversation happens when teams leave Squarespace and Wix, though the limits they hit are different ones.
One Collection, one template is the rule everything else is built on. A second layout for the same content type means a second Collection.
Reference fields ran out before your model did. Outside Enterprise a Collection tops out at 10 reference fields, and the site plan sets that budget.
Nested Collection lists stop at three levels. Course to lesson to assignment is as deep as a page can show, no matter how deep the model behind it goes.
A second language is a per-locale add-on with its own tiers, and the locales have to come off the site before you can cancel it.
Deciding who can publish is a Workspace plan feature. The publishing toggle lives on Growth and Agency.
Anything programmatic queues behind 60 or 120 API requests per minute, with one successful site publish per minute on top of it.
The Reality
Code export hands you the HTML, CSS and JavaScript. The CMS content stays behind. Webflow’s own documentation says Collection lists on an exported site show the empty state, and localized content does not come along either. Getting the content out is the actual project.
What Comes With You
Your content model comes out whole.
A Webflow migration done properly is a content migration first. Every Collection and every link between them, locales included, gets pulled out through the Data API and re-modeled somewhere it can grow. The design comes across as well, and it takes the least of our attention.
Every Collection item
pulled through the Webflow Data API and re-modeled in DatoCMS or Storyblok. Reference, multi-reference and option fields all have somewhere to land.
Your relationships
arrive as relationships. The multi-reference links holding your content together stay links, so nothing gets flattened into a text field on the way over.
Your locales
become first-class locales in the new CMS, each one a property of the content itself.
Your URLs
every page slug and Collection item URL is mapped, including the Collection URL folder Webflow puts in front of each item, so /post/your-article keeps working.
Your design
rebuilt in Astro and faithful to what you have now. It is the part clients worry about most and the part we worry about least.
What Changes
One Collection stops meaning one template.
A Collection is a page database, and that is exactly right while the pages are the product. Every Collection carries one page template and one schema, so the thing you file and the thing that renders it are the same object. Once your content has a second job, the content type and the page layout have to come apart.
Content types and layouts
come apart. The same article can render three ways in three places without a second Collection existing to hold the second layout.
Relationships
are part of the model. How many you have and how deep they go becomes a modelling decision you make with us.
Your content gets an API
of its own. The website becomes one consumer of the content instead of the place the content lives. A partner feed reads the same source the homepage does.
Editorial roles
come from the content system. Draft, review, schedule and publish become states on the content, scoped to the people who should have them.
Bulk work
stops being an event. Importing a few thousand items or backfilling a field across a Collection runs as a job against the CMS.
Hosting and ownership
move to you. Most clients land on Bunny, Cloudflare, or Vercel. If you want to change agency, hosting, or CMS later, nothing physical is preventing it.
How It Works
Moving a Webflow CMS into a real content model
Audit the content model and how your team uses it
We pull every Collection through the Webflow Data API, including reference fields, multi-reference links and any locales you run. Then we look at how your team actually uses them. Which fields sit empty, which ones people paste HTML into, which Collection exists only because something needed a second layout. The new content model comes out of that. You approve it before any code is written.
Migrate the content, rebuild the front end
Collections are imported into DatoCMS or Storyblok through their API with the relationships intact. The design gets rebuilt in Astro against the new model. We test every page against the live Webflow site before cutover, and we check the content inside the CMS as carefully as the pages on the screen.
Cutover and 30 days of watching
We launch on a low-traffic window, swap DNS, and monitor Search Console, Analytics, and Core Web Vitals for 30 days. Webflow stays live as a fallback during the watch window. After 30 days you decide whether to keep us on with a subscription or take it from here.
A note on your editors
The people who feel a migration are the ones in the CMS every day.
They file four posts a week around a model somebody drew a year ago, and nobody has asked them how it is going. We sit with them before we design a single content type. Of course some of what they ask for is a workaround they stopped noticing years ago, and finding those is half the value of the exercise.
Start with an auditPricing
Fixed price, no scope creep
Webflow migrations vary in complexity. A 30-page site with two Collections and one editor is one thing. A 200-page site with nested multi-reference relationships, three locales and a dozen people filing content is another. The ranges below are where typical projects land. Once we scope yours, you get a fixed quote.
Full audit of your Collections, reference fields, locales, and editor workflows
Content model rebuilt for a real headless CMS
Content migrated through the Webflow Data API with relationships intact
Redirect map for every page and Collection item
Frontend in Astro, CMS in DatoCMS or Storyblok
Design rebuilt faithfully against the new model
Editorial roles and review steps set up with your team
30 days of post-launch monitoring with Webflow as fallback
Same team stays accountable for the system
Performance and uptime monitored continuously
Content and component changes handled monthly
All prices are net, excluding applicable VAT.
Who This Is For
Who this is for
This works well if you
Find yourselves planning content around Collection and reference limits
Need the same content in more than one place, like an app, a newsletter, or a second brand
Run a second language and pay per locale for it
Have editors and reviewers who need real roles and a real review step
Do bulk and programmatic content work that keeps meeting the per-minute rate limit
Have a content model that outgrew what one template per Collection can express
This is not a fit if you
Run a marketing site with two Collections that changes a few times a year. Webflow is doing its job
Want a designer-first workflow with no developer involvement. That is what Webflow is good at
Have one person who is both the editor and the designer. The handoff problem you would be paying to solve does not exist yet
Are not sure yet what is wrong. Start with a Headless Audit
Need a new build from scratch with no legacy to preserve. See Headless Website