Migrating from Strapi to Payload.
We move teams off Strapi and onto Payload, pages, assets, URLs and search rankings intact. Tell us what you're running below and we'll scope the move.
Strapi and Payload are close enough that much of the migration is mechanical: each Strapi content type becomes a Payload collection and most scalar attributes map directly. The work concentrates in Strapi-specific structures: components, dynamic zones, media, relations, and the API populate behavior. Single components map to Payload groups, repeatable components to arrays, and dynamic zones to Payload blocks, with each Strapi component type becoming a block type in the new schema.
Before importing, the export must include every nested relation, media item, component, and dynamic-zone path that the migration needs; an unpopulated Strapi response can look complete while silently omitting images and relationships. Media moves first, then entries are created with relation fields blank, recording Strapi IDs for a second relationship pass. Markdown or Blocks rich text is transformed into Lexical, i18n entries are grouped into Payload locale variants, and draft state is mapped through Payload versions and drafts.
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.