Migrating from Contentful to Payload.
We move teams off Contentful and onto Payload, pages, assets, URLs and search rankings intact. Tell us what you're running below and we'll scope the move.
A Contentful to Payload migration is mostly a field-model transfer until rich text, references, and media enter the picture. Every Contentful content type becomes a Payload collection, and most scalar fields map directly. The work starts with a space export that includes content types, entries, and assets, then reads the content model before any transform code is written. Assets move first, because upload and relationship fields need Payload media IDs before entries can point to them.
References require a two-pass import. The first pass creates entries with relationship fields empty and records a Contentful entry ID to Payload document ID map. The second pass updates entries once all target documents exist, resolving references and circular links through that map. Contentful Rich Text is a separate JSON tree, so it is transformed into Payload's Lexical shape, with embedded entries handled after IDs exist. Locales are also remapped explicitly before localized writes run.
Who runs the migration
We are a Payload partner agency and a top contributor to the project. When something in the platform needs attention, we have direct access to the maintainers.
We have run this kind of move at enterprise scale. We migrated Ingersoll Rand's China sites off Oracle Content Manager in five months, with zero downtime at cutover, and we built the Council of Europe Development Bank's events platform to the deadline of their 70-year anniversary.
The first conversation is a free consultation. Scope, cost, and timing are agreed before any work starts.