Migrating from Wagtail to Payload.
We move teams off Wagtail and onto Payload, pages, assets, URLs and search rankings intact. Tell us what you're running below and we'll scope the move.
What the migration involves
Condensed from the full migration guide and the blog migration guide.
A Wagtail to Payload migration is usually not a judgement on Wagtail's quality. The guides frame it as a stack-alignment move for teams whose front end has moved to React and Next.js, whose hiring is centred on TypeScript, or whose content model has outgrown Wagtail's page-centric structure. Wagtail and Payload are both code-first, so fields map well, but StreamField, the page tree, rich-text embeds, and the Python-to-TypeScript handoff define the project.
StreamField content maps naturally to Payload blocks, but every block type needs an explicit rule. The Wagtail page tree is rebuilt through relationships, stored slugs, and URL path fields because Payload collections are flat. Exports usually run through a Django management command that preserves concrete page models, raw StreamField data, draft state, page order, and locale values. Images and documents move first, RichTextField HTML and Wagtail-specific embeds are transformed into Lexical, and original URL paths are kept for redirects.
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.