Skip to content




KeystoneJS logo
HubSpot Content Hub logo

From KeystoneJS to HubSpot Content Hub

We are the KeystoneJS to HubSpot Content Hub migration experts

Last verified:


The process

How we migrate from KeystoneJS to HubSpot Content Hub

  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 HubSpot Content Hub, 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 HubSpot Content Hub 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 HubSpot Content Hub 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 HubSpot Content Hub

Key advantages

HubSpot Content Hub (formerly CMS Hub) is designed so business users can update pages, run campaigns, and push content without ever Slacking a developer at 9 p.m.

It’s genuinely simple to implement, the drag-and-drop editor behaves, and the CRM integration does all the heavy lifting, from personalization to lead capture to automated follow-ups. The Content Hub rebrand bolted Breeze AI onto all of it: Content Remix repurposes one piece of content into emails, social posts, and landing pages, and there’s built-in podcast and video hosting now too. You barely need a dev unless you’re trying to make something unusually fancy, because HubSpot’s whole pitch is: "Let marketing ship it themselves."

But if you do want to build something more complex or need help figuring out where HubSpot fits into your stack, reach out. We can help you avoid unnecessary and very expensive upgrades, weird theme restrictions, and the classic "why is this locked behind Enterprise?" surprise.

Start my migration


Intuitive drag-and-drop interface

Intuitive drag-and-drop interface

Non-technical teams can update pages, layouts, and content without ever pinging a developer. The editor is straightforward, visual, and fast, making day-to-day site changes painless.

Deep CRM integration

Deep CRM integration

Forms, leads, emails, CTAs, and all of it connect back to HubSpot’s CRM automatically. This gives teams real personalisation power and a unified view of how users move from visitor to lead to customer.

Built-in SEO tools and analytics

Built-in SEO tools and analytics

HubSpot flags issues, suggests improvements, and provides performance insights without extra tools. It’s practical for teams who want clear SEO direction baked directly into the CMS.

Secure cloud hosting with SSL/CDN

Secure cloud hosting with SSL/CDN

Hosting, security patches, SSL, and updates are all handled by HubSpot. Sites stay fast and secure without anyone babysitting servers or worrying about downtime.

AI content tools with Content Remix

AI content tools with Content Remix

Breeze AI is baked into the editor. Content Remix repurposes existing pages and posts into new formats, and the AI writer handles first drafts. Useful for small teams that publish across several channels.

Live WYSIWYG previews

Live WYSIWYG previews

Changes can be reviewed in real time before publishing, which reduces mistakes and makes approvals easier. What you see in the editor actually matches what goes live





Common questions

KeystoneJS to HubSpot Content Hub migration FAQs

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