Now booking enterprise content platform builds for 2026. Contact us

CMS migrations

The CMS migration library.

Field-mapped technical references, a page for every major source platform, dated comparisons, and vendor end-of-life dates — in one place. The CMS replatforming service covers running the move itself.

Reference

CMS end-of-life dates

Every vendor deadline in one table, each date linked to the vendor's own lifecycle page so you can check it at the source before planning around it.

See the dates
Technical references

How a content model moves to Payload. Working references with the field-by-field mapping tables and the export pipeline for each source.

Contentful → Payload

Migrate from Contentful to Payload

Field mapping, asset pipeline, rich-text transformation.

Read the reference
Contentstack → Payload

Migrate from Contentstack to Payload

Field mapping, modular blocks, global fields, references.

Read the reference
Oracle Content Management → Payload

Migrate from Oracle Content Management to Payload

Field mapping, digital assets, the repository and channel model.

Read the reference
Strapi → Payload

Migrate from Strapi to Payload

Field mapping, components, dynamic zones, the populate problem.

Read the reference
Wagtail → Payload

Migrate from Wagtail to Payload

Field mapping, StreamField, the page tree, rich-text embeds.

Read the reference
WordPress → Payload

Migrate from WordPress to Payload

Field mapping, ACF, Gutenberg to Lexical, permalinks.

Read the reference
Migrations

We have the experience to migrate off any major CMS.

  • We agree a fixed price and a delivery date before work starts.
  • We map every field and redirect before a record moves.
  • Your pages keep their URLs, and their rankings with them.
  • We train your editors before you go live.
  • You own the platform outright.
Track record

We have moved teams off legacy, enterprise and headless platforms alike. Every migration is scoped at a fixed price, with the business case agreed before work starts.

Comparisons

When to pick each platform. Kept current, with pricing and vendor claims checked at the source.

Migration writing

Recent writing on migrations. Guides, decision frameworks, and vendor news.

The Drupal to Payload guide and Webflow to Payload guide cover content mapping, the migration process and when to stay on your current platform.

View all posts
Migrations

Migrating from Liferay to Payload: a 2026 guide for portal teams

Liferay requires custom code using javax packages to move to Jakarta from DXP 2025.Q3 and Portal 2026.Q1, and its 2026 Free Tier keeps SAML and MFA behind an Enterprise key. None of that forces a replatform. This guide sets out what a CMS can take over from a portal, what it cannot, and how to decide.

Migrations

Migrating from FirstSpirit to Payload: a guide for institutional and enterprise teams

FirstSpirit runs large editorial estates in the German-speaking market, and its export routes decide how a move to Payload starts: External Synchronization is built for templates, the REST API is alpha and CaaS carries no history. The guide covers the route, the guarantees to keep and what has no equivalent.

Migrations

Migrating from CoreMedia to Payload: a guide for institutional and enterprise teams

CoreMedia runs some of the largest editorial estates in the German-speaking market. This guide covers what a move to Payload involves: how content comes out, which editorial guarantees have to survive the move, and which parts of the platform have no Payload equivalent at all.

Migrations

Migrating from Hygraph to Payload CMS: export, schema, and the federation layer

Hygraph has no dataset export command. The migration reads content back through the GraphQL Content API a page at a time, maps models and components onto Payload collections, and works out which content the federation layer never stored in the first place.

Migrations

Webflow, Framer and Medusa put agents inside the platform

Webflow shipped agent Skills for ChatGPT and Codex on 24 August, then announced Source, a code-native agent platform, on 2 September. Framer gave its canvas agent 3D transforms on 1 September. Medusa's MCP server can import a Shopify store from a single prompt. What each one solves, and what it does not.

Migrations

Migrating from Magento to Medusa: a commerce-first guide

A Magento exit is a commerce migration first. This guide maps Adobe Commerce or Magento Open Source catalog data, customers, orders, extensions, and URL rewrites into a Medusa build, with Payload used only where the storefront needs structured content.

We're booking content platform
engagements for 2026.

Twenty-five minutes to walk through the work and decide if we're the right team for it. Scoping and a fixed price come after.