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

Contentful to Webflow, one place to edit.

Contentful holds your content, a separate front end shows it, and each layout change needs a developer. If it mostly powers one marketing site, we bring both into Webflow, so your team can write, design and publish in one tool.

  • Content types mapped to Webflow collections, field by field
  • Rich text JSON converted to clean HTML
  • Old front end retired, every live URL mapped
★★★★★5.0Trusted by ClanX, Petavue, Tata and more

Plan my Contentful 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 Contentful to Webflow migration is two moves in one. Your entries go into Webflow CMS collections, and the separate front end is replaced by pages built in Webflow. It fits marketing sites where the team wants visual editing. If the same content also feeds apps or other channels, keep Contentful.

Why teams leave headless

Great content model.
Long way to a page.

Contentful is strong at structured content. For a product with an app, a site and more, one source for everything makes sense. For a single marketing site, the cost is a custom front end, builds and a developer on every layout change.

Webflow puts content and design in one tool. You give up some of that modelling depth and the delivery API across channels. So we check who else reads from your space before we recommend anything.

Becomes HTML

Contentful rich text is structured data. It has to be converted before Webflow can use it.

Reader listed

We list each app and channel that reads your space before anything gets switched off.

Of daily checks

Launch is not the finish. For a fortnight we open the coverage and performance reports daily.

From space to site

Content moves.
The front end retires.

Contentful only ever held half of your site. Here is where each piece goes.

Content types

Each becomes a Webflow collection. Deep or looping links between entries get simplified first.

Front end

Your Next.js, Gatsby or other code is replaced with pages and components built in the Designer.

Rich text

Stored as a tree of nodes in JSON. We convert it to HTML and decide what happens to entries embedded inside it.

Assets

The export lists assets but only downloads the files if asked. We fetch them, then upload them to Webflow.

Locales

Contentful keeps a value per locale, per field. We map those to Webflow Localization, if your plan fits.

Webhooks and apps

Builds, previews and connected apps fired from Contentful stop. We list what relies on each one.

Modelling for Webflow

Flatter, on
purpose.

Contentful lets entries link to entries to any depth, and marketing teams often use that for page builders: a page holds sections, sections hold cards, cards hold links.

Webflow collections are simpler, with plan limits on reference fields and nested lists. So content that repeats, like posts and case studies, becomes collections, and one-off page sections become Designer components your team edits on the page.

Launch checklist

Checked against
the live site.

Contentful does not know your URLs. The old front end made them, so we test from the live site.

  • Every live URL from a crawl and Search Console has a target.
  • Slug rules from the old code are read, including any locale prefix.
  • Draft and archived entries are decided on, as exports leave them out by default.
  • Embedded entries in rich text show up correctly, not as blanks.
  • Generated metadata matches: titles, canonicals and social images.
  • Each locale has its content, with hreflang set.
  • Other apps using the space are confirmed safe, or Contentful stays.
  • Forms from the old front end send to the same inbox or CRM.

What moves

Your site,
moved layer by layer.

Moving from Contentful 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 Contentful 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.

Review before launch

Side by side
with the old site.

Your old front end keeps running while we build, which makes review easy. Open the staging link next to the live page, on any screen size, and compare.

Marketing leaves comments on the page, and your developers can check the technical side. Nothing moves until you have closed every note and said 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

Contentful vs Webflow

A trade, not
an upgrade.

Contentful is better at structure across channels. Webflow is better at running a website.

FeatureWebflowContentful
Editing a page layoutVisual, in one toolNeeds a developer
Hosting and front endIncludedYours to build and host
Content across many channelsWebsite firstBuilt for it, by API
Content model depthCollections with plan limitsVery flexible
Editorial workflowsRoles and simple publishingStronger, depending on plan
Publishing a changePublish buttonOften a build and deploy
Best forOne marketing site, one teamOne source of content, many products

Our process

How a Contentful to
Webflow move runs.

A common plan for one marketing site with a separate front end. Your quote has your own dates. Coloured bars are ours, striped bars are yours.

Contentful to Webflow · scope to launchYou

What you get

What comes with
every Contentful move.

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

01

Space audit

Content types, entry counts, locales and who reads them.

02

Redirect map

Built from the live site, since Contentful holds no routes.

03

Webflow build

The old front end redone in the Designer.

04

Content conversion

Entries mapped, rich text converted, assets uploaded.

05

Metadata carried

Read from the live pages, then set per page and template.

06

Forms and tools

Analytics, embeds and forms reconnected and tested.

07

Domain switch

Records changed on a call with you. Email left alone.

08

Search Console watch

Each day for two weeks, then each week.

Our work

Webflow sites
we have shipped.

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

Does anything else read from your space? Ask us first.

We send a free review of your content model and URLs, and a note on what would need to change. If other products depend on Contentful, we will tell you to keep it.

Get my free reviewFree, no strings

The guide

The Contentful to Webflow migration guide

Moving content and retiring a front end, without losing the URLs your search traffic relies on.

What is a Contentful to Webflow migration?

Contentful is a headless CMS, so your pages live in a separate codebase. Moving to Webflow replaces both: entries go into Webflow collections, and the Designer takes over from the front end. That makes it bigger than a CMS swap.

There is no importer between the two. We convert the export ourselves, then import with CSV or the Webflow API.

When staying on Contentful is the better call

  • The same content feeds an app, product screens or other channels
  • Your editorial workflow is complex and works
  • Many locales depend on how the space is set up
  • Your developers are happy and the site does its job

There is also a middle path: keep Contentful and sync chosen entries into Webflow. See Contentful and Webflow and Webflow vs Contentful.

Exporting from Contentful

The Contentful CLI command contentful space export writes one JSON file with content types, entries, assets, locales, webhooks, roles and editor interfaces. Asset files are only downloaded if you pass the flag for it, and drafts and archived entries are left out unless you ask for them.

We run it, then count entries per type against what the web app shows, so nothing is missed.

Rich text and embedded entries

Rich text is stored as a document tree, not HTML. We convert it to HTML for Webflow, which keeps supported tags and removes the rest on import.

Entries embedded inside rich text need a rule of their own. A quote block might become formatted text, while a product card might need to be a separate section. We find every type in use before writing the converter.

Getting images across properly

Webflow accepts image links in a CSV, but images imported that way do not get responsive versions. So featured images get sized first, and important ones are uploaded through Webflow directly. Contentful links in rich text are replaced, so nothing points back at the old space.

Keep the space running until you are sure each file came across.

Redirects, search and launch

Your URLs came from your old front end, not Contentful, so we read them from a crawl and from Search Console. Each changed path gets a 301 in Webflow, and folder changes use one wildcard rule where we can.

  1. We carry over titles, canonicals, social images and schema from the live pages.
  2. On a call, we point the domain at Webflow.
  3. We test, and submit the new sitemap.
  4. We check Search Console daily for two weeks.

Mapping every old URL is how you protect rankings. Some movement is normal after a change this size, and we will not promise otherwise.

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

FAQs

Contentful to Webflow
questions.

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

No. We export the space as JSON, reshape it, convert the rich text and import it into collections by CSV or API. You can keep using Contentful during the build.

You can move the website and leave Contentful running for the app, or keep Contentful as the source and sync only some entries. If most of the value is in shared content, we would likely suggest staying.

It is replaced for the marketing site. Anything that is truly a product feature can stay as an app. We list those together during the audit.

Usually with some simplifying. Webflow has plan limits on fields, references and nested lists, and we check your model against your plan. If it will not fit without real loss, we say so.

Any change of front end can. So every old URL gets mapped, and we match titles and schema against the live pages. Some movement is normal, and no one can guarantee positions.

A fixed quote after a 20 minute call. It depends on content types, entries, locales and pages. First-time clients get $500 off projects of $2,000 or more.

Each Contentful locale can map to a Webflow locale, if your plan has Localization. Check current Webflow pricing for it. We test the language switcher, URLs and hreflang on every locale.

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.

Ready when you are

Let's bring your site
into one place.

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