Webflow to Sanity: Can Your Marketers Still Edit the Site?

The short answer

For content, yes. For layout, no.

Once Sanity's visual editing is set up, your marketers edit on a live preview of the real site. They click a headline, land in the field that controls it, and watch the page change as they type. They can drag existing sections into a new order and build a landing page from blocks that already exist.

What goes away is the Webflow Designer. In Sanity, a new kind of section, a new layout, or a change to fonts and spacing is a code change. Someone has to add it before your marketers can use it.

So the question to ask your team isn't "is Sanity easy?" It's "how often do we design something new, rather than fill in something that exists?"

What changes day to day

Assuming the site is built with Sanity's visual editing (more on that below):

The first four rows are most of what a marketing team does in a normal week. The last two are what people actually miss.

The part the migration stories skip

Visual editing isn't something you switch on in Sanity. It's built into your site. Sanity's own docs describe it as three pieces wired into the frontend: live preview of drafts, click-to-edit overlays, and drag-and-drop page building, hosted in a Studio plugin called the Presentation tool.

A Sanity site built without it gives your marketers a column of form fields and a publish button, with no idea what the page will look like until it's live. That's the version people complain about, and it's a build decision, not a limitation of Sanity.

If someone is quoting you a Webflow-to-Sanity migration, ask them four things:

1. Will our editors have live preview and click-to-edit, through the Presentation tool?
2. Which section blocks will we get, and can we reorder them ourselves?
3. Are the SEO title, meta description and social image fields editors can see?
4. When we need a new block, who adds it, how long does it take, and what does it cost?

The fourth one matters most. It's the recurring cost the one-week migration stories leave out.

What Sanity costs a marketing team

From sanity.io/pricing on 1 October 2026:

• Free, $0. Up to 20 seats, but only two roles: Administrator and Viewer. Every marketer who edits is an admin. 10,000 documents, 3 days of draft history, no scheduled drafts.
• Growth, $15 per seat a month. Adds Editor and Contributor roles, scheduled drafts, comments, 25,000 documents and 90 days of history.

For most marketing teams, Growth is the realistic plan:

Sanity per year = editors × $15 × 12

Compared against Webflow's Premium plan (billed yearly, before any Webflow workspace seats), with hosting for the new site at $0 (Cloudflare Pages' free tier) to $240 a year (Vercel Pro, one seat):

Two things fall out of this. At normal traffic, Sanity isn't where the saving comes from; a migration there pays back slowly, if at all (our Webflow price increase breakdown does that arithmetic with rebuild costs included). The saving shows up at high bandwidth, the case covered in Webflow bandwidth pricing.

The second catch is one that's easy to miss: Sanity has its own bandwidth meter. Growth includes 100 GB a month, then $0.30 per GB. If the new site serves images straight from Sanity's CDN, a heavy site moves its bandwidth bill rather than removing it. At 500 GB a month of image traffic, that's 400 GB over, or $120 a month. Have the site optimise images at build time and serve them from your host, and the saving in the table holds.

How the content actually moves

For a typical marketing site with a blog, case studies and a few landing pages:

1. Export. Each Webflow collection comes out as CSV, or through Webflow's Data API for anything with references between collections.
2. Model. Each collection becomes a Sanity schema. This is where SEO fields and section blocks get decided, so it's worth an hour with the people who'll edit.
3. Convert. Rich text becomes Sanity's Portable Text. Embeds and custom code inside rich text need checking one by one.
4. Re-host images. Webflow's CSV export keeps image URLs pointing at Webflow's CDN. They work until the Webflow project is deleted, then every image breaks. Re-upload them during the migration, not after.
5. Keep every slug. Same URLs where possible, a 301 redirect where not.

Steps 1 and 3 are where coding agents save real time. Step 2 is where a migration succeeds or fails for your marketers, and no tool decides it for you.

Test it with your team before you commit

Before anyone signs a migration, give your marketers 30 minutes in a Sanity starter with visual editing (Sanity publishes starters for Next.js and Astro). Ask them to do three real tasks from last month:

• publish a post with an image and a meta description,
• change a headline on a live page,
• build a landing page from existing sections.

If they finish all three without help, Sanity will work for your team. If they get stuck on the third, find out whether it's the tool or the starter's blocks. If they get stuck on the first, don't migrate yet.

When we'd tell you to stay on Webflow

• Your marketers design new layouts most weeks. That's the Designer's job, and headless takes it away. You'd be trading a platform bill for a developer bill.
• Nobody will own the code afterwards. Every new block type needs someone. Without an owner, the site freezes at launch.
• Your Webflow bill is small. Under about 200 GB a month, the table above shows a few hundred dollars a year of difference, which won't pay back a rebuild.

If none of those apply, Sanity is a sound place to land, as long as visual editing is part of the build rather than an afterthought. Our Webflow migration service starts with a free stay-or-go review with your numbers, and we'll tell you if staying is the better call. The risks beyond the CMS (forms, redirects, the last 20%) are in what the one-week Webflow-to-Claude-Code stories leave out.

Common Questions