Move your Umbraco site
to a headless stack.

We migrate Umbraco sites to a modern headless setup. Your URLs and translations carry over, your editors get out from under the backoffice, and your developers stop maintaining a .NET runtime. No more major-version rebuilds, no more SQL Server bill, no more Document Types nobody can read.

Let's talk See if we're a fit

Trusted by

Umbraco was the friendly choice. Until upgrade time.

Umbraco earned its reputation as the .NET CMS that did not get in your way. Friendly, flexible, well-supported. It still is most of those things. But the cost of staying on the platform has crept up to the point where the next major version looks a lot like a rebuild, and the rebuild looks a lot like the right time to leave the .NET stack behind.

Umbraco 7 or 8 is end-of-life and the upgrade path quoted to you turned out to be a rebuild.

Document Types proliferated and now nobody is sure which one to pick when creating a new page.

Custom property editors were written by people who left the agency two contracts ago.

The Windows hosting bill and the SQL Server licensing keep climbing for a CMS that does not need either.

Editors guess at the layout because the Grid Layout preview never quite matches what ships.

Vorto or the variants API has turned every translation into a workaround your team has to remember.

The Reality

The platform is not the problem. The accumulated cost of staying on it is. Replatforming separates the content from the runtime.

What Survives the Move

Your content and translations come along.

Umbraco's strength is structured multilingual content with a clean export path. Content tree, language variants, Document Types, URL aliases all carry over. The migration is in the runtime underneath, not in the editorial structure your team already knows.

  • All your URLs

    every node, every culture-specific slug, every URL alias. We pull the URL tree from the Content Service and map it node by node.

  • Your content

    exported through the Management API or directly from the database. Document Type properties translate field by field into the new content model.

  • Your multilingual content

    language variants and Vorto fields move into native multi-locale content with hreflang configured from day one.

  • Your media library

    moved from the Media section to a CDN with proper image processing. ImageProcessor URL parameters are replaced with their CDN equivalents.

  • Your SEO signals

    page-level meta, canonical tags, sitemap, robots.txt and structured data are configured server-side, the same way they were in Umbraco.

What Changes

The .NET layer goes away.

Most of what makes an Umbraco site hard to maintain is platform plumbing. Document Types, the backoffice, the Grid, the IIS host. They go away. What replaces them is built around how editors and developers actually want to work, not around how Umbraco happens to organize the world.

  • Document Types

    become a small set of well-defined block schemas. We normalize the sprawl rather than copying it. Your editors stop guessing which type to pick.

  • Grid Layout and Block List

    are replaced by real components. What renders in the editor is what ships, with no separate preview to second-guess.

  • Custom property editors

    either get rebuilt as fields in the new CMS, replaced by built-in equivalents, or dropped if nobody uses them anymore.

  • The backoffice

    is gone. No more Settings section, no more Content Apps, no more remembering which tab a property lives under. Editors get a CMS designed for editors.

  • Windows, IIS, and SQL Server

    go away. The new site is static or server-rendered, hosted on a CDN. No more application pools, no more deployment slots, no more .NET runtime upgrades.

How It Works

The migration process

1

Audit and content model

We pull the content tree, walk through every Document Type, every language variant, every custom property editor, and every active package. Then we design the content model around how your editors actually publish, not around how the install grew over the years. You approve the model before development starts.

2

Migrate, translate, rebuild

Content is exported through the Management API or a direct database read and imported into Storyblok or DatoCMS. The frontend is built in Astro, with components replacing Razor views and Grid editors. Multilingual content is mapped to native multi-locale fields with hreflang from the first deploy. URL alias logic is reproduced per language so old links resolve.

3

Cutover and 30 days of watching

We launch on a low-traffic window, swap DNS, and monitor Search Console, Analytics, and Core Web Vitals for 30 days. Umbraco stays running as a fallback during the watch window. After 30 days you decide whether to keep us on with a subscription or take it from here.

A note on packages

Most Umbraco packages are platform-shaped solutions to platform-shaped problems.

uSync, Contentment, SEO Toolkit, the various form packages, half of them have built-in equivalents in a modern stack. The other half were workarounds for backoffice limitations. We list every installed package at the audit stage and decide which ones translate, which ones get dropped, and which ones need a small custom service.

Start with an audit

Pricing

Fixed price, no scope creep

Umbraco migrations vary in scope. A 60-page corporate site with two languages and a clean Document Type structure is one thing. A large-scale corporate site with a decade of property editor sprawl, custom packages, and grid content is another. The ranges below are where typical projects land. Once we scope yours, you get a fixed quote.

Migration project
€ 30.000 — € 75.000 fixed price

  • Full audit of your Umbraco install, packages, and content

  • Content model rebuilt around your editorial workflow

  • URL map covering culture-specific slugs and aliases

  • Content migration from Management API or database export

  • Frontend in Astro, CMS in Storyblok or DatoCMS

  • Multilingual with hreflang from day one

  • 30 days of post-launch monitoring

Ongoing subscription
€ 1.500 — € 3.500 per month (optional)

  • Same team stays accountable for the system

  • Performance and uptime monitored continuously

  • Content and component changes handled monthly

All prices are net, excluding applicable VAT.

Who This Is For

Who this is for

This works well if you

  • Run an Umbraco 7, 8 or 10 site facing another major version upgrade and want off the treadmill

  • Have a multilingual corporate site on Vorto or the variants API and want translations to feel native

  • Care about organic traffic and need every URL preserved through the move

  • Want your editors out of the Umbraco backoffice without retraining them on something just as fiddly

  • Run on Windows hosting and SQL Server and want both off the bill

  • Need a fixed price with a clear scope, not a time-and-materials project

This is not a fit if you

  • Use Umbraco Commerce as the core of the business and need a commerce-first replatform. Scope is different. Talk to us first

  • Have a Umbraco Heartcore setup already running headless and only need a frontend rebuild. We can help, just a different scope

  • Run a small brochure site where the cost of migration outweighs the gain

  • Are not sure yet what the right move is. Start with a Headless Audit

  • Need a new build from scratch with no legacy content. See Headless Website

If your website has become a bottleneck, let’s talk!

Let's talk Or email me directly