What an Umbraco 7 to 13 Migration Actually Costs

Umbraco 7 reached end of life in September 2023. Organizations still running it are accumulating security exposure, and the hosting and support options have narrowed considerably. If you're planning a migration to Umbraco 13, the first thing to understand is that this is not an upgrade — it's a rebuild.

Why it's not an upgrade

Umbraco 8 introduced a fully rewritten core. The document types, templates, and content structure from Umbraco 7 don't migrate directly. The third-party packages commonly used with Umbraco 7 — Archetype, Vorto, various grid and form tools — don't have direct equivalents in Umbraco 13. The underlying framework moved from .NET Framework to .NET Core.

What this means in practice: the content can be migrated with tooling, but the website itself needs to be rebuilt on the new platform. The templates are rewritten. The package integrations are replaced or rebuilt from scratch. If the existing site had custom development against Umbraco 7 APIs, that code needs to be rewritten — the APIs are different.

A developer who tells you this is a straightforward upgrade either hasn't done one or is being optimistic about scope. Get a detailed assessment before you commit to a timeline or budget.

What drives the cost

Content complexity. A simple brochure site with a handful of document types and straightforward page templates costs significantly less to migrate than a site with custom grid editors, nested content, member portals, or commerce integration. The document type count is a reasonable proxy for complexity.

Custom development against Umbraco 7 APIs. Any code built against the Umbraco 7 API layer needs to be rewritten for Umbraco 13. This includes custom data types, custom sections, event handlers, and surface controllers that go beyond standard usage.

Third-party package replacements. Some Umbraco 7 packages have modern equivalents. Others don't and require building the functionality from scratch or finding a different approach. The package inventory needs to be assessed early because replacements for complex packages can dominate the project scope.

Content volume. Migrating hundreds or thousands of content nodes requires tooling and validation. It's automatable, but getting it right — especially for complex or nested content — takes time.

Design scope. If the visual design is being updated alongside the migration, that adds scope. If it's a straight migration of the existing design to the new platform, less so, though template rewrites still require front-end time.

Realistic cost ranges

A small site — under 20 document types, simple templates, minimal custom development, no member functionality: $15,000–$30,000.

A medium site — 20 to 50 document types, custom features, package dependencies, basic member functionality: $35,000–$75,000.

A large or complex site — extensive custom development, member portals, commerce, many package dependencies, high content volume: $80,000 and up, sometimes significantly more depending on integration complexity.

These ranges assume a developer or agency with direct experience in both Umbraco 7 and Umbraco 13. A team learning the platform while doing the migration will take longer.

What to watch for in quotes

Be skeptical of proposals significantly below these ranges. Umbraco 7 to 13 migrations are consistently underscoped by teams that haven't done one before, because the platform incompatibilities aren't fully visible until you're mid-project.

When evaluating vendors, ask specifically: how do you handle document type migration, how do you approach custom development rewrites, and what does your content validation process look like after migration? The specificity of the answers tells you whether the vendor has done this before or is estimating based on how Umbraco migrations used to work.

If you're still on Umbraco 7 and not ready to migrate

The minimum action is to reduce your exposure while you plan. Move the site behind a WAF if it isn't already. Monitor for vulnerabilities in the Umbraco 7 codebase and its dependencies. Don't invest in new features on a platform you'll be rebuilding.

Start the migration planning process before you're forced into it by a security incident. Emergency migrations cost more, take longer, and produce worse outcomes than planned ones.