Skip to content




KeystoneJS logo
Kontent.ai logo

From KeystoneJS to Kontent.ai

We are the KeystoneJS to Kontent.ai migration experts

Last verified:


The process

How we migrate from KeystoneJS to Kontent.ai

  1. 01

    Access and gating audit

    First we check the existing KeystoneJS and see whether the data is clean enough to move straight over to Kontent.ai, and plan around any auth walls or bot protection in the way.

  2. 02

    Rendering assessment and extraction

    Then we work out how KeystoneJS renders its pages and pull the content out, even without CMS access.

  3. 03

    AI-assisted sanitization

    Everything extracted runs through our sanitization pipeline, which flags slop, normalizes structure, and leaves us clean content to work with.

  4. 04

    Content-model design with the client

    Before anything moves, we agree the Kontent.ai content model with you, shaped around how your editors actually work.

  5. 05

    Transform and soft-migrate

    We transform the content to the agreed schema and run a full dry run, so mappings and edge cases prove out before production.

  6. 06

    Execute the real migration

    Once the dry run is clean, everything moves into Kontent.ai in one controlled cutover.

  7. 07

    Redirect mapping and throttled sitemap submission

    Every old URL gets mapped to its new home with the right redirect, so rankings and link equity survive the move.

  8. 08

    Agentic-browser QA

    Finally, automated browsers sweep the new site for data issues, design regressions, and missing SEO signals.

  9. Ready when you are. We'll bring the moving boxes.Start my migration


Challenges with KeystoneJS

Key pain points

The biggest challenge with KeystoneJS is that it hands you all the responsibility that a managed CMS would normally handle. Deployment is entirely on you, and the documentation around production hosting, Docker configuration, and scaling is thin. We've seen teams struggle to go from a smooth local development experience to a reliable production setup, especially if they don't have dedicated DevOps support. The admin UI Docker image alone can balloon to over a gigabyte, which is a headache for containerised deployments.

The community around Keystone is significantly smaller than competitors like Strapi or Payload. That means fewer tutorials, fewer plugins, and slower answers when you hit an edge case. The ecosystem of ready-made integrations is almost non-existent, so you'll be building most things from scratch. For an agency working on client projects with deadlines, that time cost adds up quickly.

Content editors also tend to have a harder time with Keystone compared to more polished alternatives. The admin UI is functional but feels utilitarian, and non-technical users often need more onboarding than you'd expect. There's no visual editing, no preview infrastructure, and no real content workflow features like drafts, publishing schedules, or approval chains without building them yourself. If your client's content team needs a CMS they can pick up and run with, Keystone usually isn't the answer.

Help me migrate


Deployment complexity in KeystoneJS

Deployment complexity

Self-hosting is the only option, and the docs don't hold your hand. Getting Keystone into production requires real infrastructure knowledge, and the large Docker image sizes make it worse.

Small community in KeystoneJS

Small community and ecosystem

Compared to Strapi or even Payload, the community is much smaller. Fewer plugins, fewer tutorials, and slower support when things go wrong.

No built-in content workflows in KeystoneJS

No built-in content workflows

There are no turnkey drafts, scheduled publishing, or approval chains. Keystone provides field primitives that can be assembled into publishing workflows, but you need to wire them up yourself.

Dated admin UI in KeystoneJS

Admin UI feels dated

The admin panel is functional but lacks the polish and UX of modern CMS interfaces. Non-technical editors often find it confusing and need more training.

No visual editing in KeystoneJS

No visual editing or live preview

There's no way for editors to see content in context before publishing. You'd need to build your own preview infrastructure, which is a significant engineering effort.

Scaling challenges in KeystoneJS

Scaling requires significant effort

Running Keystone under high traffic means managing session stores, reverse proxies, and server resources yourself. It doesn't scale as smoothly as cloud-native CMS alternatives.



Benefits of Kontent.ai

Key advantages

Calling your CMS "Kontent dot ai" is a brilliant way to convince people you’ve built an AI-powered future. And to be fair, the platform does have a clean editor, strong workflow tools, and a respectable multi-channel setup.

It's perfect for the kind of company that has more infosec members than it does have devs. But calling yourself an AI platform doesn’t mean you’re built like one.

Real AI-driven CMS platforms start at the foundation with structured content, flexible modeling, real-time indexing, and an architecture that doesn’t panic the moment you try something complex. Sanity doesn’t even market itself as "AI-first," but it’s been ahead of the curve for years. They shipped an embedding index before "AI CMS" was a pitch deck buzzword. We even built one of the first AI search tools on top of it.

So yes, Kontent.ai is great. If you want a polished interface and enterprise workflows, go for it. And if you’re dead-set on building your website there, talk to us first. We’ll walk you through it and maybe even find a better way before you spend six months discovering the limits yourself.

Start my migration


Intuitive content management

Intuitive content management

You shouldn’t need a week of onboarding to publish a paragraph. Kontent.ai nails this with a clean interface that doesn’t punish you for being a marketer instead of a developer.

Flexible content modeling

Flexible content modeling

Build content the way your brain works. Modular, structured, reusable. No dev intervention every time marketing decides "we need one more field."

Strong API-first architecture

Strong API-first architecture

The APIs are predictable, well-documented, and don’t require wild workarounds. Everything connects the way it should and developers stay happy too.

Tech stack integration

Tech stack integration

React, Vue, Angular, or whatever framework you’re obsessed with this week, Kontent.ai plays nice with all of them and keeps deployments smooth.

Advanced image transformations

Advanced image transformations

You can resize, crop, and optimize visuals without leaving the CMS. Think of it as an in-house designer that doesn’t complain about aspect ratios.

Real-time collaboration

Real-time collaboration

Writers, editors, and developers can work together without stepping on each other’s commits. Instant updates, fewer Slack messages, and zero "who overwrote my draft?" moments.





Common questions

KeystoneJS to Kontent.ai migration FAQs

Answers to the most common questions about KeystoneJS to Kontent.ai migration

KeystoneJS stores data through Prisma, so the database layer is well-structured and easy to export. The harder part is replacing everything Keystone doesn't give you. Most Keystone projects have custom-built preview systems, publishing workflows, and access control logic that are tightly coupled to the Node.js backend. Rebuilding those features in a new CMS takes planning. We typically budget 4 to 8 weeks for a Keystone migration depending on how much custom infrastructure the team has built around it.


Get in touch

Tell us what you're building. We reply within one working day. Jono or someone on the team picks up every message personally.

By sending this you agree to our privacy policy. We only use your details to reply.