Case Study
View Case StudyTray.ai
Migrating hundreds of thousands of pages, re-platforming and extending for the leading composable AI integration platform
We are the Contentful to Storyblok migration experts
Challenges with Contentful
With all good things, there’s a “depends on how you use it and who is using it” clause. Contentful usage-based pricing can quietly snowball, especially for smaller teams or projects running on lean budgets. Its API-first approach might make developers grin, but the non-technical users might find themselves staring at setup screens, wondering, “Wait… where’s the editor?”
More often than not, the main reason Contentful sucks is because a developer has built it incorrectly, as it has a whole host of opinionation, that isn't widely known. E.g.
You need to be extremely careful with the number of documents you build, as you could very easily push yourself into enterprise from an early stage.
We'd always recommend speaking to us first, before completely writing it off.
Key pain points
Potentially high costs
Contentful isn’t a cheap CMS. As your traffic, models, or team grows, pricing can climb faster than expected.
Complex for non-technical users
Marketers and editors may need a small learning curve before they feel at home. It’s powerful but not always plug-and-play.
Integration dependency
A lot of magic happens through third-party tools. Great for flexibility, but it does mean extra setup instead of getting everything out-of-the-box.
Limited native features
Contentful keeps the core CMS clean and minimal, but that also means more building and configuring to get advanced functionality.
Learning curve for new teams
,If your team is moving from a traditional CMS, expect some onboarding time. Structured content is amazing but new for many.
Requires careful management
Because it’s so flexible, projects need good governance. Without it, content models can get messy and harder to maintain over time.
Benefits of Storyblok
If you’ve ever tried explaining “headless” to a content team and watched their eyes glaze over, Storyblok is your peace offering. On the surface, it appears to be great. For instance, its visual editor makes you feel like you are finally living in 2025. But start digging, and you’ll find some gremlins in the codebase and the pricing page. Their APIs are still missing some basic functionalities like fetching child or sibling pages.
Still, if Storyblok is your choice, we can make it work. Our team knows how to set it up cleanly, dodge the common blockers, and keep your build from turning into another “looked nice, aged badly” project.
Key advantages
Visual editing capabilities
Yes, you read that right, you can do real-time, on-page editing. Make a change, see it instantly, no staging limbo, which means you can stop “guess and publish.”
Component-based approach
You can build a component once and use it everywhere. You can also update a button or banner in one place, and the entire site fixes itself.
Efficient content structuring
Your content stays clean, organised, reusable, and not scattered across 40 pages. Developers work with structured data, editors drag-and-drop pieces like Lego. Everyone gets to stay sane.
Robust multi-language support
One CMS, many languages, zero chaos. Localise content without duplicate pages, messy exports, or spreadsheet archaeology.
Collaborative environment
Writers, designers, and editors can all jump in at the same time without breaking each other’s work. Add comments and approvals. View version histories for teamwork without the headache.
Highly customisable
If your design system can imagine it, you can use Storyblok to model it. There are custom fields, workflows, and logics that can bend to your stack rather than the other way around.
Get in touch
Book a meeting with us to discuss how we can help or fill out a form to get in touch
