Gemin
Start a project

Contentful to Webflow

Migrate from Contentful to Webflow

Contentful plus a custom front end is often more machinery than a marketing site needs. Sometimes the right move is to consolidate into Webflow. Sometimes Contentful should stay and Webflow should simply render it.

Start a project

A migration like this usually takes 3–4 weeks

Why people move

What changes when you move from Contentful to Webflow.

What is being compared Contentful Webflow
What it is Contentful A headless CMS with no front end Webflow A CMS with a front end attached
Content modeling Contentful Deep, with real relationships and validation Webflow Collections with references, and caps Contentful wins on modeling. The question is whether you need what it offers.
Preview Contentful Needs a front end built for it Webflow Native
When to stay Contentful Many channels, one content source Webflow One website

Once you have decided

What actually migrates.

What you have What happens Why
Entries Move Comes across as it is. The content survives the move and the work is transporting it, not remaking it. Extracted through Contentful's APIs and transformed into collection items. How much transforming depends entirely on the content model, which is what the rest of this page is about.
Content types and references Rebuild Made again in Webflow. The old version is a reference rather than something that can be imported. Redesigned rather than imported. A type becomes a collection where the two models agree, and where entries reference entries that reference entries, the relationships get reorganized around what each page actually renders. This is the row that is actually the work.
Rich text Rebuild Made again in Webflow. The old version is a reference rather than something that can be imported. It arrives as a document tree rather than as markup, with references to embedded entries and assets inside it. Converting it means deciding what each embedded thing becomes on the other side, and there is no import that decides that for you.
Assets Move Comes across as it is. The content survives the move and the work is transporting it, not remaking it. Exported and rehosted. The transformations written into Contentful's asset URLs do not travel with the files, so equivalent sizing and formats get rebuilt on the new site.
URLs and redirects Reconfigure The same thing, set up again. Nothing is recreated, but it has to be pointed at the new site by hand. Depends entirely on what the old front end was doing.
Localization Depends Not answerable in general. Which one it is turns on your plan, your export or a decision nobody has made yet. Contentful's is stronger. Webflow Localization covers many cases and not all.

Before you budget it

Where this migration gets complicated.

  1. 01

    Every asset URL changes, and the transforms in them stop working

    Contentful serves images from its own CDN with resizing and format parameters written into the URL. Those transformations do not travel with the file, so equivalent sizing, formats and responsive behavior are rebuilt as part of the migration rather than inherited with the asset.

  2. 02

    Rich text is structured, not markup

    Contentful stores rich text as a document tree with embedded entries inside it. Converting it to Webflow's rich text means deciding what happens to every embedded entry, and there is no import that decides that for you.

How it runs

How the migration works.

  1. 01

    Plan

    What Contentful owns, who else consumes it, and whether it should remain the source of truth.

  2. 02

    Build

    Templates in the Designer, against the model the content map settled rather than against whatever the old frontend rendered.

  3. 03

    Migrate

    Content in, assets rehosted and checked against the source, and every address that changes given a rule pointing straight at its replacement.

  4. 04

    Launch

    Forms at the record, every template at three widths and every old address requested, all before anything is switched. Then typically 3–4 weeks from start to live, and a week of watching what the old addresses return.

What you are buying

What is included.

  • Design rebuild

    Rebuilt directly against the existing site.

  • Responsive development

    Desktop, tablet and mobile, built and checked.

  • CMS architecture

    Collections and fields mapped before build.

  • Content migration

    Migrated and checked against the source.

  • Asset migration

    Collected, compressed and rehosted.

  • Forms and integrations

    Tested through to the final record.

  • Redirects

    Changed URLs mapped directly to replacements.

  • Metadata and canonicals

    Preserved wherever possible.

  • Search footprint preservation

    URLs inventoried before and checked after.

  • Pre-launch QA

    Forms, templates and old URLs verified.

  • Post-launch support

    One week of indexing and traffic checks included.

Search visibility can move during a migration. The goal is to preserve what search engines already understand, and to catch what changed quickly after launch.

Other migrations

Coming from somewhere else?

Reach out and see if we are a good fit.

Start a project

Currently booking two to four weeks out.