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.
Migrate from Contentful to Payload
Field mapping, asset pipeline, rich-text transformation.
Read the referenceMigrate from Contentstack to Payload
Field mapping, modular blocks, global fields, references.
Read the referenceMigrate from Oracle Content Management to Payload
Field mapping, digital assets, the repository and channel model.
Read the referenceMigrate from Strapi to Payload
Field mapping, components, dynamic zones, the populate problem.
Read the referenceMigrate from Wagtail to Payload
Field mapping, StreamField, the page tree, rich-text embeds.
Read the referenceMigrate 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.
Find what you are on today.
Browse every platform- WordPress talk about a WordPress migration
- Adobe Experience Manager talk about a Adobe Experience Manager migration
- TYPO3 talk about a TYPO3 migration
- Drupal talk about a Drupal migration
- Sitecore talk about a Sitecore migration
- Kentico talk about a Kentico migration
- Umbraco talk about a Umbraco migration
- Contentful talk about a Contentful migration
- Contentstack talk about a Contentstack migration
- Strapi talk about a Strapi migration
- Sanity talk about a Sanity migration
- Magento talk about a Magento migration
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. Use the CMS comparison tool to check more platforms and features side by side.
AEM (Adobe Experience Manager) vs Payload CMS
Adobe's Java-based suite, licensed as Sites, Assets and Forms, vs a TypeScript content backend inside your Next.js app.
Read the comparisonCraft CMS vs Payload
A PHP CMS with Twig templates, multi-site and per-project licences vs a TypeScript backend inside your Next.js app.
Read the comparisonDatoCMS vs Payload
A hosted headless CMS with metered plans and visual editing vs a TypeScript backend you run and extend.
Read the comparisonDirectus vs Payload CMS
Choose how your data model becomes an editorial tool.
Read the comparisonDrupal vs Payload
A mature PHP platform with editorial workflow in core vs a TypeScript backend you shape.
Read the comparisonHygraph vs Payload
A hosted GraphQL platform that federates other APIs vs a TypeScript backend in your own codebase.
Read the comparisonOptimizely vs Payload
Optimizely's CMS, on .NET or as SaaS inside a wider experimentation and commerce suite, vs a TypeScript content backend inside your Next.js app.
Read the comparisonPrismic vs Payload
A hosted page builder around developer-built slices vs a TypeScript backend where blocks and rules live in code.
Read the comparisonSitecore vs Payload
A digital experience suite on .NET, self-managed or as SitecoreAI SaaS, vs a TypeScript content backend inside your Next.js app.
Read the comparisonStoryblok vs Payload
Visual editing in a managed platform vs a code-first application CMS.
Read the comparisonWebflow vs Payload
A visual website platform with hosting built in vs a content backend you pair with your own frontend.
Read the comparisonWordPress vs Payload
A publishing system with a vast ecosystem vs a TypeScript backend you shape.
Read the comparison Migration writing
Recent writing on migrations. Guides, decision frameworks, and vendor news.
The WordPress to Payload guide, Drupal to Payload guide and Webflow to Payload guide cover content mapping, the migration process and when to stay on your current platform.
CMS migration tools: crawl, export, transform and check before cutover
A crawler, an export, a transform script and a check each do one job in a CMS migration. This guide matches tools to those jobs, with their limits and costs, and includes a small example that catches missing records, images, locales and redirects before cutover.
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.
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.
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.
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.
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.
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.