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.
- We carry over titles, canonicals, social images and schema from the live pages.
- On a call, we point the domain at Webflow.
- We test, and submit the new sitemap.
- 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.







