FREEFirst project with us? Your landing page design is on the house.See the offer
Booking for Q4'26

Sanity to Webflow, when the code gets in the way.

Sanity is a fine CMS, and we build with it ourselves. But if the developer who set up your Studio has moved on, and marketing cannot add a section without a ticket, Webflow may suit you better. We tell you honestly, then move the content and rebuild the pages.

  • Documents and references mapped to Webflow collections
  • Portable Text converted, custom blocks handled one by one
  • GROQ-built routes read from your code, then every URL mapped
★★★★★5.0Trusted by ClanX, Petavue, Tata and more

Plan my Sanity move

Tell us a little. We reply within one working day with a price and timeline.

🔒 No spam. No sales calls unless you ask for one.

Got it. Thanks!

We will reply within one working day.

Trusted by founders and teams at

A Sanity to Webflow migration exports your dataset, maps documents and references to Webflow collections, converts Portable Text to HTML and rebuilds the front end in the Designer. Any changed URL gets a 301. It suits teams who want visual page building without developers. If your developers are happy with Sanity, a move may not help.

Why teams move off Sanity

Your Studio is code.
Who looks after it?

A Sanity Studio is a code project: schemas, custom inputs, a front end and queries. That is the strength of it, for teams with developers on hand. Without them, a new field or section type becomes a project of its own.

Webflow gives you less modelling power and more hands-on control of pages. We build on both, including Astro with Sanity, so if the real problem is a tangled Studio, we might suggest cleaning that up instead.

Review before launch

Your editors
try it first.

Before launch your team gets a staging link and an Editor login. Open pages on a phone and a laptop, then change a headline and publish a test post, so the new way of working is not a surprise.

Note anything that feels off right on the page. We fix it, and the domain waits for your yes.

staging.fieldandclay.comStaging
Field & ClayShop
STONEWAREMade slowly. Used daily.
1Field & Clay teamCan the photo be bigger?Resolved
DesktopSigned off
Field & ClayShop
STONEWAREMade slowly. Used daily.
2Field & Clay teamMenu feels crampedResolved
TabletSigned off
Field & ClayShop
STONEWAREMade slowly. Used daily.
3Field & Clay teamButton text too smallResolved
MobileSigned off
Waiting for sign-off on 3 screensAll screens signed off. Checklist green.Switch domain

Is the starting point

The dataset export is one document per line, plus asset files, in a compressed archive.

Platforms we build on

We work with Sanity and Webflow, so our advice does not lean on one.

Of search checks

Search Console gets a daily look for a fortnight after launch, and 30 days of safe changes run alongside.

From dataset to Designer

Documents in.
Studio out.

Nothing in your Studio runs in Webflow, but all the content can be brought across.

Documents

Each document type that needs its own pages becomes a collection. Singletons like settings become plain pages or components.

Portable Text

Stored as JSON and not tied to HTML. We serialise it to HTML, with a rule for each custom block type.

Page builder arrays

Arrays of section objects become Designer components on each page, rather than items in the CMS.

Images

Exported with the dataset. Hotspot and crop data does not transfer, so we export each image at the crops you need.

GROQ and live preview

Queries, Presentation tool and custom Studio inputs stay behind. Webflow handles lists and preview its own way.

References

Stored as IDs. We resolve them in a set order, so linked items exist before anything points to them.

Order matters

References, in
the right order.

In Sanity, a post points to an author by ID, and the author can point to other documents. Webflow needs the author item to exist first, so its new ID can go on the post.

We work out that order from your schema, import from the bottom up with the Webflow API or CSV, and check the links afterwards. Where a reference has no match in Webflow, such as a list of mixed document types, we agree a simpler pattern with you.

Launch checklist

Read from the code,
tested on staging.

Routes and metadata in a Sanity site are usually written in the front end, so that is where we start.

  • Route files and slugs are read from the front end repo.
  • Each custom block type in Portable Text renders properly.
  • Drafts are decided on, since exports can leave them out.
  • Metadata from queries matches what the live pages output.
  • Author and category links resolve to the correct new item IDs.
  • Images load at sizes that fit the new layout.
  • Webhook-driven rebuilds are confirmed unused, then switched off.
  • Forms handled in code send to the same place on the new site.

What moves

Your site,
moved layer by layer.

Moving from Sanity to Webflow is more than copying pages. These are the seven layers we move, in the order we move them.

  1. 01
    Audit

    Every URL, page, form and script on your Sanity site, listed in one sheet before anything moves.

  2. 02
    Content

    Pages, posts and collections moved into Webflow, field by field, so nothing is retyped by hand.

  3. 03
    Design and build

    Pages rebuilt in Webflow as reusable components, matching the look you have or a new design.

  4. 04
    Redirects

    Every old URL gets a 301 to its new address, so old links and search results still land on the right page.

  5. 05
    SEO carried over

    Titles, descriptions, schema and image alt text move with each page.

  6. 06
    Forms and tracking

    Forms, analytics and connected tools set up again and tested before launch.

  7. 07
    Launch and watch

    DNS switched and the sitemap submitted, then we watch Search Console for errors.

Sanity vs Webflow

Who does the
work matters.

Sanity needs developers to get the most from it. Webflow is built to not need them for everyday work.

FeatureWebflowSanity
Building new pagesDesigners and marketersDevelopers, then editors fill them
Content modellingGood within plan limitsVery deep, in code
Content across channelsWebsite firstQuery from anywhere
Custom editing toolsLimitedBuild what you need
HostingIncludedSeparate front end to host
Code ownershipCode export is limitedYour repo
Best forMarketing teams who own the siteTeams with developers on hand

Our process

How a Sanity to
Webflow move runs.

A common plan for a Sanity marketing site with a code front end. You get your own dates with the quote. Coloured bars are ours, striped bars are yours.

Sanity to Webflow · scope to launchYou

What you get

What comes with
every Sanity move.

No add-on surprises. These come with every project.

01

Schema and route audit

Studio schemas, queries and route files, read line by line.

02

URL map

Built from routes and a crawl, with a 301 for each change.

03

Designer rebuild

Components, classes and variables for your team to use.

04

Dataset move

Documents imported in reference order, with text converted.

05

Search parity

Metadata and schema matched against the live pages.

06

Forms and scripts

Whatever your code did for forms and tags, redone and tested.

07

Domain cutover

DNS changed on a call with you. Mail records untouched.

08

Post-launch watch

Search Console every day for two weeks, then weekly.

Our work

Webflow sites
we have shipped.

Try us first · Try us first · Try us first ·

Might a cleaner Sanity setup be enough? Ask us first.

We build on both, so we look at your Studio, your front end and your URLs for free, then tell you which way we would go. Sometimes that means staying.

Get my free reviewFree, no strings

The guide

The Sanity to Webflow migration guide

How to move from a code-first setup to a visual one, and what you give up along the way.

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.

  1. The TTL goes down a day ahead.
  2. On a call, the domain moves to Webflow.
  3. We check redirects, forms and tags on the live site.
  4. 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.

FAQs

Sanity to Webflow
questions.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

Only sometimes. We build on Sanity and like it. Moving helps when no developer owns the setup and marketing is stuck. If your developers are happy, it often does not.

Not directly. We export it, write a small script to reshape the documents and convert the text, then import with the Webflow API or CSV.

We list each type. Most become formatted text, an embed or a separate field. A few may need a new layout on the page. You see the plan before we run it.

Yes. Custom inputs, document actions and the Presentation tool stay with Sanity. Webflow has its own Editor and CMS, which many marketing teams find enough, but check before you decide.

We map every old URL, keep slugs where we can and match metadata to the live pages. Rankings can still move for a while after launch, which is normal. We cannot guarantee them, and neither can anyone else.

You get a fixed quote after a 20 minute call. Schema size, custom blocks and page count decide it. First-time clients get $500 off projects of $2,000 or more.

If marketing wants to build pages visually, Webflow. If you want to own the code and keep a headless CMS, stay in code. We do both and will say which fits.

For 30 days after launch we make safe changes for free: copy edits, image swaps, colour tweaks and link updates, and we fix anything we built that does not work. New sections, page redesigns and new features are not part of it. We quote those separately, or they are covered by a care plan.

Wall of love

Don't take
our word for it.

Hear it from the founders and teams we have built for.

Bailey McElligott, Design Director
Bailey on working with Kookies.
Bailey McElligott · Design Director0:17
Verified review
5.0
★★★★★
"They are very professional and the best at what they do."

Juned Khatri, Chief, BubbleWrap
Web development · Dec 2022 to Jan 2023 · Quality, schedule, cost and willing to refer: 5.0

Read it on Clutch
"Fast, efficient and beautifully designed! Kookies nailed our website with pixel-perfect execution and smooth interactions."
Juned KhatriFounder, ClanX
"They are very professional and the best at what they do. Kookies surpassed expectations with Webflow. Thrilled with the results!"
Juned KhatriChief, BubbleWrap
"Kookies' professionalism, dedication and exceptional design skills exceeded our expectations. Highly recommended for high-quality work and timely delivery."
AA
Ali Al MuttawaCo-founder, Artal Invest
"A thorough job, with high-quality work in a short timeframe. Abdul and his team were prompt, professional and patient with all our inputs. Happy to recommend them."
Sejal SinghiManaging Consultant, Baraka Impact Finance

Ready when you are

Let's see if your site
belongs in Webflow.

Send the form and get a price and timeline within one working day. Or book a quick call with our team.

WebflowPremium PartnerProud to build the Webflow way★★★★★5.0 on Clutch
Abdul Quadir
Talk to our teamA senior lead runs your call. Abdul, our founder, often joins.

Book a free 20 minute call

Pick a day that works for you.

See open timesOpen calendaror email hello@kookies.io
Book a callGet a quote