Case study
View case studyJamb
We rebuilt Jamb on Sanity and Next.js, merging two legacy PHP sites into one calm catalogue without losing the SEO equity their antique and reproduction collections had built up.
From BaseHub to Sanity
We are the BaseHub to Sanity migration experts
Last verified:
Challenges with BaseHub
Key pain points
BaseHub is one of those platforms that feels like it was built by a developer, for a developer, and at no point did anyone ask, “Won't marketers need to be able to edit on the go?” Once you’re inside, it’s tables inside tables inside tables, like a Russian doll but somehow less fun. And as we’ve said before, we genuinely appreciate good engineering… but BaseHub often feels like someone shipped the database schema and called it a CMS.
BaseHub is painful to use, in our opinion. Because the platform is still young, features sometimes glitch, real-time collaboration hiccups, and localization or migration workflows can get messy fast. Documentation gaps and unpredictable branching only add to the frustration. If you're determined to build on BaseHub, we can walk you through the safest path… or at least help you avoid the inevitable “why is this breaking again?” moments.
Occasional feature glitches
New features sometimes ship a bit wobbly, so expect the occasional “why is this suddenly broken?” moment.
Not yet enterprise-ready
It’s great for small teams, but big orgs will hit walls fast. Workflow maturity and stability just aren’t there yet.
Limited third-party integrations
If you rely on a rich ecosystem, BaseHub won’t meet you halfway. You’ll be wiring a lot of things yourself.
Localization support gaps
Multi-region content teams will feel the pain quickly as language handling still needs serious tightening.
API rate limiting constraints
Push it too hard and you’ll hit rate limits faster than you expect, which can block larger deployments.
Sporadic stability issues
Real-time collaboration and branching can hiccup under pressure, making scaling workflows frustrating.
Benefits of Sanity
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.
Common questions
BaseHub to Sanity migration FAQs
Answers to the most common questions about BaseHub to Sanity migration
How do we migrate content out of BaseHub?
BaseHub exposes content through its GraphQL API, so extraction means writing queries to pull your content tree and transforming the responses into your target CMS format. The nested repeater structure can make this tricky since deeply nested content needs to be flattened or re-mapped depending on where you're going. Media assets need to be downloaded and re-uploaded separately. For a typical project with moderate content volume, we budget 2 to 4 weeks for the full migration.
Why do teams leave BaseHub?
BaseHub is still a young platform, and teams hit its limits as projects grow. The most common complaints we hear are feature glitches in production, limited third-party integrations, and an interface that feels more like a database browser than a CMS. Localization support is weak, API rate limits bite harder than expected on high-traffic sites, and real-time collaboration can hiccup under pressure. Teams that need enterprise-grade reliability often outgrow BaseHub within 6 to 12 months.
Is BaseHub stable enough for production sites?
For small marketing sites and developer portfolios, BaseHub works fine. For anything with real traffic, multiple editors, or complex content workflows, we'd urge caution. The platform ships features quickly but stability doesn't always keep pace. We've seen branching break under pressure and collaboration features hiccup at inconvenient moments. If your business depends on publishing uptime, you want a CMS with a longer track record of production reliability.
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.
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 with 25,000 documents and the same API allowances, plus pay-as-you-go overages and 5 roles including Editor, Developer, and Contributor. Enterprise pricing is custom for organisations that need custom roles, SLAs, or private datasets. Most mid-size teams we work with stay well inside Growth's limits.
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.
