Case Study
View Case StudyTray.ai
Migrating hundreds of thousands of pages, re-platforming and extending for the leading composable AI integration platform
From Contentful to Craft CMS
We are the Contentful to Craft CMS migration experts
Last verified:
Challenges with Contentful
Key pain points
Contentful is one of those platforms where the bill can catch you off guard. The free tier caps you at 25 content types and 100K API calls, and a single marketing site can blow past both without warning. The next step up is $300 a month, and enterprise pricing often lands in the $50K to $100K+ a year range.
Users on Reddit regularly flag the same thing: tier jumps are forced by hitting one limit, not by needing the bigger feature set. Content model caps alone can push you into a higher plan you don't otherwise need.
The other issue is that Contentful has strong opinions about how content should be modelled, and those opinions aren't always documented. Projects built without that knowledge tend to accumulate performance problems and awkward workarounds. Before writing Contentful off, speak to us, a lot of the pain we see is implementation, not platform.
Pricing climbs fast
Contentful isn't a cheap CMS. Once you pass the free tier's content type or API call limit, you're on the $300/month Lite plan, and enterprise pricing often starts at $50K+ a year.
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 Craft CMS
Key advantages
Craft CMS is one of those platforms we genuinely respect from a developer standpoint. The content modelling is best-in-class for a traditional CMS. You define sections, entry types, and fields with real precision, and the authoring experience maps cleanly to the underlying data structure. If your content team needs a CMS that actually reflects how the site is built, Craft delivers that better than most. The Twig templating layer is clean and predictable, and the admin UI is fast and intuitive once editors get past the initial learning curve.
Where Craft really shines is in the middle ground between simple marketing sites and full-blown enterprise builds. It's flexible enough to handle complex content architectures without the bloat of something like WordPress, and the built-in GraphQL API means you can use it headless if you want to pair it with a modern frontend. The plugin ecosystem is smaller but noticeably higher quality than what you'd find in WordPress, and the Composer-based workflow means your whole project can live in version control properly.
We've seen agencies build genuinely impressive work on Craft, especially for content-heavy sites where editorial workflows matter. If your team includes developers and you want a CMS that rewards careful architecture, Craft is a solid choice. It's not trying to be everything to everyone, and that focus shows.
That said, we'd typically recommend a headless CMS like Sanity for most of the projects we take on. Craft is at its best when you're comfortable with PHP and want a tightly integrated traditional or hybrid setup. If you're building on Next.js or a modern JavaScript stack, you'll find more natural fits elsewhere.
Exceptional content modelling
Craft's field and section system gives you precise control over your content structure. You can model complex relationships between content types without fighting the CMS.
Clean authoring experience
The admin panel is fast, well-organized, and maps directly to how content is structured. Editors can work efficiently once they understand the layout.
Built-in GraphQL API
Craft ships with a native GraphQL API, so you can use it headless without plugins or workarounds. It's deeply integrated and well-documented.
Composer-based modern workflow
Everything is managed through Composer, so your project, plugins, and dependencies all live in version control. Deployments through CI/CD pipelines work smoothly.
Higher quality plugin ecosystem
The plugin store is smaller than WordPress but the quality bar is noticeably higher. Plugins are better maintained and less likely to break your site on update.
Granular user permissions
Built-in role and permission management is detailed and flexible. You can lock down exactly what each editor can see and do without needing third-party plugins.
Common questions
Contentful to Craft CMS migration FAQs
Answers to the most common questions about Contentful to Craft CMS migration
How much does Contentful cost?
Contentful has a Free tier with 10 users, 100K API calls per month, 25 content types, and 10,000 records. The Lite plan is $300/month for 20 users, 1M API calls, and 100GB CDN bandwidth. Premium is custom pricing with unlimited API calls and a 99.99% uptime SLA. We've seen teams hit the free tier's API ceiling or content type cap fast, and the jump to Lite is often forced by a single limit rather than a feature need.
What are some alternatives to Contentful?
Sanity is the alternative we recommend most. It gives you real-time collaboration, a customizable studio, and pay-as-you-go pricing that doesn't punish you for scaling. Storyblok is worth considering if your editors want a visual builder. We've migrated teams off Contentful to both, and Sanity consistently gets the best feedback from developers and content editors alike.
How does Contentful compare to Sanity on pricing?
Contentful charges $300/month for its Lite plan with hard caps on API calls, seats, and content types. Sanity's pricing is usage-based, starting free and scaling with actual consumption. For most mid-size projects, Sanity ends up significantly cheaper. The real difference is that Sanity doesn't gate core features behind premium tiers the way Contentful does with roles, SSO, and content modelling limits.
Can I migrate from Contentful to Sanity?
Yes. We've migrated dozens of Contentful projects to Sanity. The structured content model in Contentful maps well to Sanity's schema, so most migrations are straightforward. Content, assets, references, and localized fields all transfer. Our typical migration takes 2-4 weeks depending on the number of content types and the complexity of your references. We handle frontend rewiring too if you're on Next.js or a similar framework.
Is Contentful good for large enterprise websites?
It can be, but the costs get steep. Enterprise plans are custom-priced and often land in the $50,000-$100,000+ per year range. If you have deep pockets and your team already knows the platform, it works. If you're evaluating from scratch, we'd push you toward Sanity for enterprise use. You get equivalent API performance, better real-time editing, and a pricing model that doesn't penalize growth.
How much does Craft CMS cost for an agency managing multiple sites?
The costs add up quicker than most agencies expect. The Solo tier is free for single-user projects, Team is $279 per project, and Pro is $399 per project. Both paid tiers carry a $99 annual renewal fee. If you're running 10 client sites on Pro, that's $3,990 upfront plus $990 per year in renewals before you've paid for a single plugin. Popular plugins like SEOmatic, Blitz (caching), and Navigation run $99-$199 each. Factor in PHP hosting ($20-$100/month per site depending on traffic) and the total per-project cost lands between $500 and $1,500 in year one. It's reasonable for individual projects but the aggregate cost across a portfolio is where agencies feel the squeeze.
What are the hidden costs of running Craft CMS?
Beyond licensing, three costs catch teams off guard. First, PHP hosting. Craft needs PHP 8.2+, MySQL or Postgres, and proper server configuration. You can't deploy to Vercel or Netlify like you would with a headless CMS. Budget $20-$100/month per site for decent managed hosting. Second, major version upgrades. Craft doesn't let you skip versions, so going from Craft 3 to 5 means stepping through 3 to 4, then 4 to 5, each with breaking changes to Twig templates and plugin compatibility. We've seen agencies spend 20-40 hours per upgrade. Third, developer dependency. Craft assumes your team has PHP developers on hand. If your agency is moving toward JavaScript stacks, maintaining Craft expertise becomes an overhead.
Should I migrate from Craft CMS to a headless CMS?
It depends on your stack direction. If your team is comfortable with PHP and Twig, and your sites are traditional server-rendered builds, Craft still works well. But if you're building with Next.js, React, or any modern JavaScript framework, Craft becomes friction. Its GraphQL API exists but it's a bolt-on, not a native experience. The content modelling in Craft is genuinely good, and that translates well to headless platforms. We've migrated Craft sites to Sanity where the content structures mapped over almost one-to-one. The frontend rebuild in Next.js typically takes 6-10 weeks, and the result is faster, cheaper to host, and easier to iterate on.
What's the biggest challenge when migrating off Craft CMS?
Twig templates. Every piece of frontend logic in a Craft project lives in Twig, and none of it carries over to a modern JavaScript framework. You're essentially rebuilding every template from scratch. Content migration itself is manageable since Craft's data structures are well-organised, and you can export through the Element API or direct database queries. The other challenge is plugin replacement. If you rely on Craft plugins for forms, SEO, or search, you need to find equivalents in your new stack. We build a dependency audit before any Craft migration so there are no surprises mid-project.
Get in touch
Fill out the form below and we'll get back to you
