Webflow or Astro with a headless CMS

The conversation usually starts with a developer saying the marketing site should be in the codebase. They are often right about the reasons and wrong about the cost, because the cost is not the build. It is what happens to the marketing team afterwards.

What actually forces the move

Four things, and only four. If none of these is true, the move is preference rather than necessity.

The content has outgrown the CMS. Collection and item caps are real, not raisable, and a catalog that keeps growing will meet them. What Webflow will not do has the specifics.

Something must render per request. Pricing by account, gated content that is actually gated, region-specific legal copy. Anything decided before the page is sent cannot live in a static Webflow page.

The marketing site and the product need to share code. One design system, one component library, one deployment. If the same button has to exist in both and stay identical, keeping them in two tools is a running cost.

Content has to come from somewhere else. A PIM, an ERP, an internal service. Webflow can be fed by these with work; a headless build reads them natively.

What you actually trade

The hybrid nobody proposes

The framing is usually all-or-nothing and it does not have to be.

Keep the marketing site in Webflow, where marketing can ship, and build the part that genuinely needs code as its own application on a subdomain or a path. The docs, the app, the customer portal, the calculator that reads live pricing. Each lives where it belongs, and the team that owns it owns the tool.

This is what most companies should do and very few discuss, because the conversation arrives framed as a migration. The question is rarely "which platform" and usually "which parts".

How to tell which side you are on

One test, and it is not about features.

Count the changes the marketing team made to the site last quarter, and ask how many of them would have needed a developer in the other setup.

If the answer is most of them, moving to a headless build converts marketing work into engineering work, permanently. That is a real cost, paid every month, and it is almost never in the estimate.

If the answer is few, because the site barely changes or because a developer is already in the loop for everything, then the cost is small and the technical gains are real.

I do these migrations. Webflow to Astro and Webflow to Next.js cover what they involve, and what the Astro move looks like in code is the same job with the schema, the export and the component in front of you. I would just rather you move for the first reason than the fourth.