Headless CMS migration
to DatoCMS or Storyblok.
We move sites off WordPress, Drupal, TYPO3 or Sitecore onto DatoCMS or Storyblok, with Astro or Next.js on the front end. Every URL is mapped before cutover and we watch Search Console for 30 days afterwards. You get a fixed price for the whole thing, agreed before the work starts.
Trusted by
Trusted by
The state most sites reach us in
By the time a team calls us, the site is usually still running and the publishing process around it has become the expensive part.
Every publish waits on a developer and the campaign calendar is planned around that delay.
A new language or market adds months to the plan before a single word is written.
How the content is structured is knowledge that left with whoever built the site.
You have already decided to move and the open question is who runs it and what it costs.
The estimates you have collected come back as day rates with no fixed end.
The Reality
We take on sites where the content already exists and the URLs are already indexed. Both have to survive the move, and that is most of the work.
Where You Land
DatoCMS or Storyblok, with Astro or Next.js.
What you land on is a stack. Your content lives in DatoCMS or Storyblok. The site itself is built in Astro or Next.js. We work in all four, so the pair you get follows from your situation.
The CMS is chosen during the audit, against how your team edits: who publishes, how often, and how much they need to see on screen before they hit publish. The front end is chosen against what the site has to do. One published example is the Eversports move from WordPress to Storyblok on Next.js: six languages, shipped page by page as a proxy migration.
On Storyblok, your pages are blocks assembled into stories.
A block is either the story itself, a page or an article, or something nestable that sits inside another block. Your editors compose a page layout out of those pieces, and they do it on a preview of the real page: click an element in the preview and the block behind it opens for editing.
On DatoCMS, every page is a record sitting on a model.
Blocks are reusable across models, and they live only inside the fields set aside for them, which is why a link field cannot point at a block. The open-ended area is a Modular Content field, where the writer picks between a text section, a carousel or a call to action. Each page type keeps a tighter, more predictable shape that way, with the free-form part explicitly bounded. Editors click an element on the site itself to open it for editing.
Both of them hold rich text as structured data rather than as HTML, and that is the part to plan for if you are coming off WordPress. Every post body gets converted instead of copied across. Anything living as raw HTML inside a post, such as a shortcode, an embed or a hand-written table, needs a decision while the migration runs.
How It Works
How we run your migration to Storyblok or DatoCMS
You approve the plan and the price
We audit the current site, map every URL that has to survive, and design the content model with the people who will publish on it. You see the redirect plan and the fixed quote before any building starts, and nothing moves until you sign both off.
You review the build on real content
We design and build against your own pages. Every section becomes a block your editors can arrange themselves without touching CSS. You see it running on your real content well before cutover, and you tell us what has to change.
You go live with us still on it
We cut over, hold the redirect map, and watch Search Console for 30 days afterwards. Keeping responsibility for the system past that point is what the monthly tier below is for.
Our Framework
Every migration follows our Essential Launch Framework.
Six phases, three decision points, 12 to 18 weeks. You stay in control at every milestone.
Read about the frameworkBuilt for AI
Ready for the agents on both sides
The systems we ship come with the groundwork for AI workflows. Your marketing team can draft landing pages with AI assistance, and because the CMS is component-based, everything stays on-brand by default. The agents visiting your site can read it properly too. This is baseline, not an upsell.
Your team's AI tools
MCP server for your CMS, so AI tools can query and draft pages directly.
A DESIGN.md that explains your tokens, layout rules, and voice.
A SKILL.md for every component so a model uses it correctly.
Agents visiting your site
A markdown copy of every page, served to agents that prefer it.
Explicit bot rules and Content Signals in your robots.txt.
An Agent Skills index so AI agents know what your visitors can do.
Pricing
What moves the number
What we quote follows from what has to survive the move, which is why the range below is as wide as it is. The URL map is the first thing we size: how many live URLs need a redirect, and how many of those still earn traffic worth protecting. The content model is the second, priced on how many genuinely distinct page types your editors need rather than on page count. Multiple languages or markets sit on top of both.
What moves a project from the bottom of that range to the top is rarely technical. It is how many people have to sign off, how long they take, and how much of the old site the organisation is willing to leave behind. Two sites of the same size can land at either end for that reason alone. Once we have scoped yours the price is fixed. If you would rather buy the scoping on its own first, that is the Headless Audit.
Full audit of your current site
Migration strategy and redirect mapping
Content architecture before design
Design built around real content
Headless CMS with all components
AI workflow groundwork (MCP, DESIGN.md, agent-readable pages)
Go-live with SEO protection
30 days post-launch monitoring
Momentum, € 2.490: new pages, sections and components in your CMS, and small changes live the same working day
Ownership, € 4.990: everything in Momentum, plus new integrations built between your CMS, CRM and analytics
All prices are net, excluding applicable VAT.
Who This Is For
Who this is for
This works well if you
Have already decided to move and are choosing who does it
Are going from WordPress to Storyblok or DatoCMS and want the content model rebuilt for the destination
Run multiple markets or languages on one content model
Want your marketing team publishing without a developer in the loop
Want a fixed price and a named cutover date instead of a day rate
This is not a fit if you
Want a ready-made solution without custom development. See essentialweb.eu
Are early stage with no internal marketing team
Want a handover with no ongoing responsibility
Do not have a legacy site and need a new build from scratch
Are not sure yet what you need. Start with a Headless Audit
Came here about one source platform. Read WordPress to headless or Drupal to headless