Migrating from Hygraph to Payload.
We move teams off Hygraph and onto Payload, pages, assets, URLs and search rankings intact. Tell us what you're running below and we'll scope the move.
A Hygraph exit has no dataset export to download. Content comes back through the GraphQL Content API, which generates a singular and a plural query for every model, and the page size sets the pace: projects created after 14 June 2022 return 10 results by default with a documented maximum of 100, while older projects default to 100 with a maximum of 1000. A dependable export is a resumable cursor loop per model, carrying `endCursor` into the next request until `hasNextPage` goes false.
Two things separate this migration from other structured sources. Models map onto Payload collections while components stay embedded, so basic and modular components land as groups, arrays and blocks rather than collections of their own. And the federation layer holds no content to move: Hygraph documents remote sources as query-time resolvers into external systems, so anything federated stays in its system of record and what a migration replaces is the composition endpoint. Assets, localised fields and cross-entry references follow the usual order, with one project-specific check first, because the asset system changed in February 2024 and the older URL domain was retired.
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.