From KeystoneJS to Magnolia

We are the KeystoneJS to Magnolia migration experts

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.

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

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.

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 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 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 Magnolia

Key advantages

Magnolia shines if you’re the kind of organisation that genuinely needs the full DXP kitchen sink. It packs personalisation, workflows, multi-site orchestration, multilingual publishing, DAM, marketing automation hooks, and every enterprise acronym you can think of. If your teams run complex global content operations with strict governance, Magnolia’s mature permission system, stability, and long-standing enterprise reputation make it a safe, compliant option.

To be transparent, we don’t actually prefer or build with Magnolia (or any of the DXP-flavoured headless CMSs). They try to do everything, and like most jack-of-all-trades platforms, they don’t excel at the things modern teams actually need that is speed, flexibility, clean workflows, and sane pricing. We’d happily point you toward modern alternatives like Sanity that give you 10× the agility without the enterprise bloat.

A grid with striped blocks forming a square path around a central warning sign, with dashed arrows indicating clockwise movement.

Java-based enterprise integration

Built on Java, Magnolia plugs neatly into large enterprise stacks that already rely on Java systems and legacy infrastructure. If your organisation lives and breathes JVM, Magnolia won’t fight your architecture.

Secure, scalable architecture

Magnolia’s core is engineered for high-security, high-traffic environments, with strong access control, clustering, and enterprise-grade stability. It’s built to survive heavy editorial activity and large content delivery demands.

Grayscale UI wireframe showing a left sidebar with icons and a right content panel with forms and a progress bar.

Real-time page templating

Editors can adjust components and layouts and immediately preview results, making large enterprise content operations faster and less error-prone.

Editable component previews

Magnolia’s component-level previewing gives editors clarity on how complex pages come together, reducing back-and-forth with developers and keeping multi-team workflows sane.

Multi-site management tools

Designed for global brands, Magnolia supports multiple sites, languages, and regional variations under one roof.

Advanced workflow automation

From multi-step approvals to compliance-driven publishing flows, Magnolia handles heavyweight governance. This is the stuff big enterprises actually need when 20 departments want access but only 2 should publish.