Skip to content




KeystoneJS logo
Basehub logo

From KeystoneJS to BaseHub

We are the KeystoneJS to BaseHub migration experts

Last verified:


The process

How we migrate from KeystoneJS to BaseHub

  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 BaseHub, 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 BaseHub 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 BaseHub 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 BaseHub

Key advantages

BaseHub CMS is generating buzz among developers for its fast, collaborative, and AI-powered environment. We really like the Notion style editor. Feels great to drop a / and you type in what you want. E.g heading, or bullet points etc.

It's pretty good for creating and organizing content. Even for teams that are new to CMS platforms. Features like easy nested repeater fields, real-time branching for team workflows, and a built-in GraphQL API impress both solo makers and growing agencies. The platform’s Typesafe approach and AI-assisted writing tools help speed up the publishing process, while modern UI design keeps the learning curve gentle for newcomers.

If you can handle the initial information overload when you first spin up an environment it's an incredible tool for collaboration and rapid site scaffolding.

They also have a pretty good freemium pricing model (nodody has as good as Sanity) and strong documentation help projects get off the ground quickly, especially for Next.js and React use cases. Frequent updates and community engagement is high, and the core team that built it, are from a really nice design focused agency. So can't knock it that much.

Start my migration


Intuitive Notion-style editor

Intuitive Notion-style editor

Drop a / to insert blocks. The Notion-style editor is intuitive: fast, light, and easy to navigate

Effortless nested repeater fields

Effortless nested repeater fields

You can nest and stack content structures. It’s one of the few tools where complex schemas don’t instantly become a crime scene.

Real-time content branching

Real-time content branching

Branching lets teams experiment, test ideas, and push updates without breaking production. Preview changes instantly, merge when ready, panic never.

Ready-to-use GraphQL integration

Ready-to-use GraphQL integration

BaseHub ships with clean, auto-generated GraphQL APIs, so developers don’t waste hours wiring resolvers or schema stitching. Query, fetch, and ship.

Typesafe SDK support

Typesafe SDK support

You get fully typed responses out of the box, which means fewer runtime surprises and a smoother dev experience. Your IDE becomes your safety net.

Collaborative team workflows

Collaborative team workflows

Teams can work together without stepping on each other’s toes, with clean approval flows and role-based editing. It’s built for fast-moving content teams.





Common questions

KeystoneJS to BaseHub migration FAQs

Answers to the most common questions about KeystoneJS to BaseHub 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.