Case Study
View Case StudyTray.ai
Migrating hundreds of thousands of pages, re-platforming and extending for the leading composable AI integration platform
From Magnolia to KeystoneJS
We are the Magnolia to KeystoneJS migration experts
Last verified:
Challenges with Magnolia
Key pain points
Magnolia is the definition of “enterprise for the sake of enterprise.” The setup is heavy, the learning curve is brutal, and unless you have a Java team lying around, good luck getting anything done without burning through budget. The proprietary modules lock you in fast, integrations feel like a maze, and the admin interface slows to a crawl once you start dealing with real content volume. The pricing is expensive, opaque, and somehow still manages to feel bad value. If you're not a Fortune 500 with a tolerance for pain, it’s a project risk.
And honestly, who even uses Java anymore?
Steep Java learning curve
Magnolia expects your team to be fluent in Java and its ecosystem, which slows onboarding and makes even simple tasks feel heavier than they should.
Resource-intensive setup
It demands serious infrastructure and long setup cycles, which immediately rules it out for teams that expect fast iteration or modern DevOps workflows.
Vendor lock-in concerns
Once you're in, you're in. Magnolia’s proprietary modules make moving away painful, expensive, and often not worth the engineering time.
Complex third-party integration
Connecting Magnolia with modern tools and APIs isn’t straightforward, usually requiring custom Java work instead of simple plug-and-play integrations.
Native subscription support
Licensing is firmly enterprise-tier, with opaque pricing and steep annual fees that can balloon quickly, a bad fit unless you're Fortune 500.
Proprietary module reliance
Key features live behind Magnolia’s own tightly controlled modules, limiting flexibility and forcing teams to work the “Magnolia way” instead of choosing best-in-class tools.
Benefits of KeystoneJS
Key advantages
KeystoneJS is one of those tools that really clicks if your team thinks in code. It's a schema-driven, open-source headless CMS built on Node.js, and the developer experience is genuinely good. You define your content models in TypeScript, Keystone generates a GraphQL API and an admin UI for you, and you're off. There's very little magic or abstraction hiding what's happening under the hood, which we appreciate when building complex projects for clients.
The Prisma ORM integration is a real highlight. Automatic migration generation, type-safe database access, and support for PostgreSQL, MySQL, and SQLite mean you're not fighting your data layer. If you've ever had to wrangle a CMS into supporting a non-trivial relational content model, you'll understand why this matters. Keystone lets you express those relationships cleanly and query them with a proper GraphQL API.
The document field editor is also worth mentioning. It's one of the more thoughtful rich text implementations we've seen in a headless CMS. You can embed custom React components directly into the editor, which means content teams can work with your actual design system components rather than generic blocks. For teams that care about structured content, Keystone gives you real tools to enforce it.
Where Keystone really shines is in projects where the development team wants full ownership of the stack. There's no vendor lock-in, no proprietary query language, and no surprise pricing tiers. If you want a CMS that feels like a well-designed library rather than a platform, Keystone delivers on that promise.
Schema-as-code with full TypeScript support
Define your entire content model in TypeScript with strong type inference throughout. The schema drives everything from the database to the admin UI to the GraphQL API.
Automatic GraphQL API generation
Every content type you define automatically gets a full CRUD GraphQL API with filtering, pagination, and relationship resolution. No manual endpoint wiring needed.
Prisma-powered database layer
Built on Prisma ORM with automatic migration generation and type-safe queries. Supports PostgreSQL, MySQL, and SQLite out of the box.
Flexible document field editor
The rich text editor supports custom embedded components that map to your design system, giving content editors structured authoring without sacrificing flexibility.
Granular access control
Fine-grained, field-level access control defined in code. You can write custom logic for create, read, update, and delete operations per field or per list.
Fully open source with no vendor lock-in
MIT licensed with no paid tiers or proprietary features gated behind a subscription. You own the entire stack and can host it wherever you want.
Common questions
Magnolia to KeystoneJS migration FAQs
Answers to the most common questions about Magnolia to KeystoneJS migration
How long does it take to migrate away from Magnolia CMS?
Magnolia migrations are among the most involved we handle. The Java-based architecture, proprietary modules, and tightly coupled workflows mean there's no quick extract-and-import path. Content needs to be exported from Magnolia's JCR (Java Content Repository), transformed, and loaded into your target platform. For a mid-sized enterprise site with 1,000 to 5,000 pages, expect 8 to 16 weeks. The timeline depends heavily on how many proprietary modules your team has adopted and how complex your multi-site setup is.
Why do companies leave Magnolia?
Cost and agility are the two main drivers. Magnolia's enterprise licensing is opaque and expensive, with annual fees that balloon as you add modules and environments. Teams also get frustrated by the Java dependency. Finding and retaining Java CMS developers is harder and more expensive every year, especially when modern headless platforms let teams build with JavaScript and TypeScript instead. The vendor lock-in from proprietary modules makes the decision feel overdue by the time teams finally commit to migrating.
Can we migrate from Magnolia to a headless CMS without losing our multi-site setup?
Yes, but the approach changes. Magnolia handles multi-site through its own orchestration layer, while headless platforms like Sanity use workspace configurations or project-level separation. We rebuild multi-site architectures using the target CMS's native multi-tenancy features. The content migration itself is the simpler part. The harder work is re-implementing your personalisation rules, approval workflows, and permission structures outside of Magnolia's proprietary ecosystem.
What makes migrating from KeystoneJS difficult?
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.
Why do teams move away from KeystoneJS?
Deployment complexity is the number one reason. Teams love Keystone during local development, then hit a wall getting it reliably into production. The Docker images can balloon past a gigabyte, the docs don't cover production hosting well, and there's no managed hosting option. The small community compounds this problem. When you hit an edge case, there are fewer people who've solved it before. Content editors also struggle with the admin UI, which lacks visual editing, live preview, and built-in publishing workflows that competing platforms ship by default.
How do we extract our content from KeystoneJS?
Since Keystone uses Prisma ORM, your content lives in standard PostgreSQL, MySQL, or SQLite tables with clean schemas. You can export directly from the database using SQL dumps or Prisma's query API. The content model is defined in your TypeScript codebase, so mapping fields to a new CMS is straightforward. We write automated scripts that handle the data transformation, including resolving relationships between lists and migrating file references. For a project with 20 to 50 Keystone lists, extraction and transformation usually takes 1 to 2 weeks.
Get in touch
Fill out the form below and we'll get back to you
