Migrating from Kentico to Payload.
We move teams off Kentico and onto Payload, pages, assets, URLs and search rankings intact. Tell us what you're running below and we'll scope the move.
A Kentico to Payload migration begins with the difference between Portal Engine and MVC. Portal Engine sites keep more logic and layout inside Kentico through web parts and portal templates, so there is more to untangle and reproduce. MVC sites already separate the front end into a .NET application, which makes the content layer cleaner to lift out. The audit also covers custom modules, page types, fields, integrations, scheduled tasks, and the media library.
Kentico page types and custom module classes are mapped into Payload collections with typed fields, relationships, and access rules. The guide argues against copying a bloated page type verbatim: end of life is used to simplify the model, keep the fields that are actually used, and rebuild the front end in Next.js. What carries across is the content, media, relationships, and URL value worth preserving; what gets rebuilt is the content model, the data move, the front end, and the SEO-safe cutover.
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.