Migration guide

Can you migrate Contentful to WordPress?

Last updated: July 2026 · By the Replatform Radar team — specialists in pre-migration CMS content audits

Yes — Contentful to WordPress is a real and increasingly common reverse migration, where teams leave a headless CMS to cut cost and complexity and regain an all-in-one system that both authors and renders content. Because Contentful is API-only with no rendering layer, the project is not just data movement: you model Contentful content types as WordPress post types and Advanced Custom Fields, convert Rich Text JSON back into WordPress HTML or block markup, and build an actual theme that Contentful never had. The content export itself is straightforward through Contentful's Content Management API, but rebuilding the front end and re-establishing authoring convenience is the bulk of the work. It is a deliberate trade of headless flexibility for lower cost and a simpler, coupled editing experience.

Contentful is a headless CMS: it stores content as entries of defined content types, serves them over a REST/GraphQL API, and represents formatted body copy as structured Rich Text JSON. Crucially, it has no rendering layer — every Contentful site relies on a separate front-end application (Next.js, Gatsby, etc.) to fetch and display content. WordPress is the opposite: a coupled PHP CMS where the database, the admin, and the rendering theme live together, content is modeled as posts and custom post types (commonly extended with Advanced Custom Fields), and formatted content is stored as HTML or Gutenberg block markup.

Teams migrate this direction to reduce recurring cost, collapse a two-system (CMS plus separate front end) architecture into one, and give editors a familiar all-in-one authoring experience with live preview and a built-in theme. The migration has three distinct workstreams: remodeling Contentful content types and their reference fields as WordPress post types and ACF field groups; transforming Rich Text JSON (including embedded entries and assets) into WordPress HTML or block content; and building a theme from scratch, since Contentful contributed no templates, CSS, or markup. Because there is no shared rendering heritage, the front end is effectively a greenfield build rather than a port.

In your report — not a generic checklist

The Contentful → WordPress detail, catered to your site

A pre-migration scan produces a report tailored to this exact transfer, covering the parts that decide whether the project goes smoothly:

How Contentful and WordPress compare across the dimensions that matter for a migration
The field-mapping table — what each Contentful construct becomes in WordPress
The Contentful to WordPress-specific gotchas that silently cause data loss, broken links, and ranking drops
Realistic timeline & cost drivers for this migration
Your own site’s findings scored against all of it

Scan my site for this migration →

FAQ

Contentful to WordPress: frequently asked questions

Why would you migrate from Contentful to WordPress?

Mainly to cut cost and complexity. Contentful's per-seat SaaS pricing plus the need for a separate front-end application makes it expensive and operationally heavy for many teams; WordPress collapses authoring and rendering into one lower-cost stack and gives editors a familiar all-in-one experience with live preview.

How do I convert Contentful Rich Text to WordPress?

You write a transformer that parses Contentful's Rich Text JSON node tree and emits HTML or Gutenberg block markup. There is no built-in exporter, and the tricky part is resolving embedded-entry and embedded-asset nodes into inline content, since those are references rather than raw markup in the JSON.

Can I export content out of Contentful?

Yes. Contentful's Content Management API and the contentful-cli export tool produce a full JSON dump of content types, entries, and asset metadata. That export is the easy part; the effort is transforming that JSON into WordPress post types, ACF fields, and rendered content, and re-hosting the assets.

Do I need to rebuild the front end when moving to WordPress?

Yes, completely. Contentful is headless and ships no rendering layer, so there is no theme, template, or CSS to carry over. The WordPress theme is built from scratch, which is usually the single largest part of the migration and unlike CMS-to-CMS moves where a design already exists.