# KeystoneJS to Sanity migration > How to migrate from KeystoneJS to Sanity, with a side-by-side comparison and FAQs. --- ## Source: KeystoneJS - **Type:** headless - **Official site:** https://keystonejs.com - **Last reviewed:** 2026-07-28 ## 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. ## 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. ## Target: Sanity - **Type:** headless - **Official site:** https://www.sanity.io - **Pricing:** https://www.sanity.io/pricing - **Last reviewed:** 2026-07-28 ## Key advantages You know where our bias' lies. We think Sanity is literally the best headless content management out there. The schema is code-based, so it can be easily versioned, scaled, and extended without a heap of third-party hoops to jump. Providing you build it with a solid foundation, which we always recommend Turbo Start Sanity, it's going to be the most valuable hub for content you can imagine. It's got a very unique tooling called the Live Content API, which in simple terms means when you press publish, its live. No issues with caching, and a single API usage that scales perfectly with multichannel content delivery. It also offers one of the best editorial experiences in the industry with Presentation and customizable content structures. We're obviously huge fans of it, and we've pivoted our business with it when we realised how ahead it is. ### Real time collaboration You write, your teammate tags in, adds citations, and updates the same doc without stepping on each other. It’s the fastest way to ship content without the "who has edit access?" chaos. ### Live preview block building With Sanity, you don’t have to guess what your page might look like. Real-time previews update the moment you type. It’s a 1:1 mirror of your site before it ever goes live, so your campaigns look right the first time. ### Meta tags, structured content Sanity’s structured content gives Google clean data and rich schema, so your pages surface higher without manual hacking. Automated schema, smarter metadata, and better rankings. ### Better media management A blazing-fast media library with first-class support for Cloudinary, Mux, Wistia and more. Upload, drag-and-drop, preview without wrestling with assets, and waiting for spins of doom. ### Automated social sharing Ever wanted to share one update, and automatically populate every social platform? Welcome to the future we've built that. Why should social media be a chore. ### Automated image generation Sanity keeps your subject centred and sharp like a tiny author thumbnail or a full-page hero banner. There are no awkward crops, or chopped heads. Your visuals just look right everywhere. ## Key pain points We obviously prefer Sanity, so much so that our own website is on Sanity. But if you don't have the right implementation team, you might find yourself in a bad situation. Its highly customizable nature can lead to complexity and time-consuming setup processes for less experienced developers. We've inherited our fair share of stinkers, but we advise that before you jump ship, you let us look over it to see if it's salvageable. That said, if you are considering moving, we can help you migrate away with automated migration scripts, web scraping, and content mapping. It'll be a 1:1 with whatever platform you choose. ### Not always plug-and-play Sanity gives you a ton of flexibility, but it’s not a "drag-and-drop" CMS. If your team prefers instant themes and presets, you’ll need a little extra setup to get started. ### Potentially high resource demand As your content model grows, Sanity gives you incredible power and real-time performance. Just keep in mind that very large projects may require a bit more horsepower behind the scenes. ### Less ideal for beginners Editors love Sanity once everything is set up, but teams switching from traditional CMSs may need a short onboarding period to learn the workflow. ### Infrastructure management needed Unlike hosted CMS platforms, you own your content pipeline. That gives you full control and scalability, but also means setup and environments need to be managed properly. ### Technical skill required Since Sanity is schema-driven, developers can model content precisely the way your business needs it. Non-technical teams benefit from that structure, but setup usually requires engineering support. ### Complexity in setup Sanity doesn’t force rigid templates or assumptions. You have to define everything like content, structure, and workflows. The tradeoff: a bit more initial setup for much more flexibility long-term. ## Frequently asked questions ### 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. ### How much does Sanity cost? Sanity's Free plan includes 20 user seats, 10,000 documents, 1M CDN API requests, 250K regular API requests, 100GB of assets, and unlimited locales. The Growth plan is $15 per seat/month for up to 50 seats, with 25,000 documents and the same API allowances, plus pay-as-you-go overages, private datasets, and 5 roles including Editor, Developer, and Contributor. Enterprise pricing is custom for organisations that need custom roles, dedicated SLAs, or single-tenant infrastructure. Most mid-size teams we work with stay well inside Growth's limits. ### Why should we migrate to Sanity instead of another headless CMS? Sanity's Live Content API means content goes live the instant you press publish, with zero caching issues. We've migrated teams from WordPress, Contentful, Drupal, and legacy platforms, and the consistent feedback is that the editorial experience is faster and more flexible. The schema-as-code approach means your content model is version-controlled alongside your codebase. Pricing starts free for small teams and scales predictably, unlike platforms that hit you with surprise API overage bills. ### What does a migration to Sanity actually involve? A typical migration has three phases. First, we map your existing content model to a Sanity schema, which usually takes 1 to 2 weeks depending on complexity. Second, we build automated migration scripts that transfer your content, media assets, and relationships. Third, we set up the frontend integration and editorial workflows. For a mid-sized site with 500 to 2,000 pages, the full process usually runs 4 to 8 weeks. We use our Turbo Start Sanity foundation to accelerate the setup so you're not starting from zero. ### How long does it take before our content team is productive in Sanity? Most editors are comfortable within the first week. Sanity's Presentation tool gives them a side-by-side live preview that feels intuitive, especially for teams used to visual page builders. The real-time collaboration means multiple editors can work on the same document without conflicts. We typically run a 2-hour onboarding session and provide a custom guide tailored to your specific content model. After that, editors rarely need developer support for day-to-day publishing.