BinaryWorks

Category: Migration Date: October 6, 2026 Author: Karthik Kalimuthu

Umbraco Migration or Upgrade? A Complete Guide to Your Next Step

Umbraco Migration or Upgrade?

On December 14, 2026, Umbraco 13 reaches end of life. If your website runs on Umbraco 13, or on an older version that is already unsupported, you face a decision that affects your budget, your security, and your content team’s daily work. You can upgrade to a newer version of Umbraco, or you can use this moment for an Umbraco migration to WordPress, Drupal, or another CMS.

This guide is written for the people who make that call. It explains how Umbraco versions are supported, what each path involves, how the platforms compare, what Umbraco 13 owners should do in the weeks ahead, and how to choose the right agency. All details are current as of October 2026.

TL;DR
  • Deadline: Umbraco 13 support ends December 14, 2026. Umbraco 17 is the current long-term support (LTS) version, supported until November 27, 2028.
  • On Umbraco 13: Upgrading to Umbraco 17 is usually the shortest path. Cost depends mostly on how many custom admin extensions your site has.
  • On Umbraco 7 or 8: There is no in-place upgrade, so you will rebuild either way. Compare Umbraco 17 with WordPress and Drupal before you commit.
  • Need more time? Umbraco’s Extended Long-Term Support (XLTS) covers LTS versions 10 and later for 6, 12, or 24 months.
  • Before any quote: Get a code and content audit. It is the only reliable way to size the work.

How Do Umbraco Releases Work?

Umbraco releases alternate between two types of major versions:

  • Standard-term support (STS): Supported for 12 months.
  • Long-term support (LTS): Supported for three years. LTS versions follow Microsoft’s .NET LTS schedule, so a new LTS arrives roughly every two years, with STS versions in between.

Every major version moves through four stages:

  1. Active: The version receives new features until the next major release ships.
  2. Support phase: Feature work stops, but bug fixes, regression fixes, and security patches continue. This lasts 3 months for STS versions and 18 months for LTS versions.
  3. Security phase: Only security issues are fixed. This lasts 3 months for STS versions and 12 months for LTS versions.
  4. End of life: The version receives no further updates of any kind.

Umbraco publishes its release roadmap well in advance:

  • Umbraco 19 (STS): December 10, 2026
  • Umbraco 20 (STS): June 24, 2027
  • Umbraco 21 (next LTS): December 9, 2027

For planning purposes, build your roadmap around LTS versions. Adopt STS releases only if your development team is ready to upgrade twice a year.

With that cycle in mind, here is where each version stands today.

Umbraco Versions and End-of-Life Dates

The table below groups Umbraco versions by support status as of October 2026.

Status Umbraco versions End of life What it means for you
Unsupported (legacy .NET Framework) 7 and 8 September 30, 2023 (v7); February 24, 2025 (v8) Rebuild on Umbraco 17 or move to another CMS
Unsupported 9 to 12, and 14 to 16 Between December 2022 and June 2026 Upgrade or migrate as soon as possible
Security fixes only 13 (LTS) December 14, 2026 Upgrade to Umbraco 17 or buy XLTS
Supported 17 (LTS) November 27, 2028 Recommended target for most organizations
Supported 18 (STS) June 25, 2027 For teams that want the newest features

The Umbraco 7 end of life date passed in September 2023, and Umbraco 8 followed in February 2025. Sites on either version face the biggest jump, because both run on the legacy .NET Framework and cannot be upgraded in place.

If your version sits in one of the unsupported rows, the next question is what that status means in practice.

What Happens When Your Umbraco Version Reaches End of Life?

Your website keeps running, but it stops receiving updates of any kind, including security patches. Umbraco no longer recommends using a version after that date.

Definition: Umbraco end of life (EOL)

Umbraco end of life is the date after which Umbraco HQ stops releasing bug fixes, security patches, and support for a specific version. The site still works, but any vulnerability discovered after that date stays open.

In practice, end of life affects five areas:

  • Security exposure: Newly discovered vulnerabilities go unpatched.
  • Package support: Maintainers of form, search, and SEO add-ons shift their effort to supported versions.
  • Framework support: Umbraco 13 runs on .NET 8, which Microsoft also stops supporting in November 2026. Both layers of your stack lose support within weeks of each other.
  • Audit findings: Unsupported software is routinely flagged in security reviews, vendor risk questionnaires, and cyber insurance renewals.
  • Umbraco Cloud hosting: Sites stay hosted for the length of the XLTS period, but only projects with an active XLTS contract receive patches. After XLTS coverage ends, projects move from shared to dedicated hosting for a final 12 months.

Can You Extend Support With Umbraco XLTS?

Yes, if you run an LTS version from Umbraco 10 onward. Umbraco’s Extended Long-Term Support (XLTS) works like this:

  • Coverage: 6, 12, or 24 months of extra security patches.
  • Start date: Coverage begins the day after end of life.
  • No gaps: Extensions must be continuous.
  • Delivery: Updates arrive through a private NuGet feed.

Umbraco designed XLTS for organizations with frozen budgets, sites in maintenance mode, complex installations, and teams short on developers. Treat it as a bridge. It keeps your site patched while you plan, but you still have to make the move eventually.

That move takes one of two forms, and the difference between them shapes your budget.

Umbraco Upgrade vs. Umbraco Migration: What’s the Difference?

An Umbraco upgrade keeps you on Umbraco and moves your site to a newer version. An Umbraco migration moves your content, structure, and features to a different CMS.

Definitions

Umbraco upgrade: Moving a website to a newer Umbraco version while keeping Umbraco as the platform. Content and much of the code carry forward, depending on the starting version.

Umbraco migration: Rebuilding a website on another platform, such as WordPress or Drupal, and transferring its content, URLs, and integrations to that platform.

For older versions, the line between the two blurs. Umbraco’s own documentation states there is no direct upgrade path from Umbraco 8 to the latest version. You can keep your content by reusing the database, but all templates and custom code must be reimplemented for ASP.NET Core.

A jump from Umbraco 7 or 8 therefore carries most of the cost of a migration. That makes it the right moment to compare platforms rather than default to the next version.

How Do You Upgrade Umbraco to the Latest Version?

To upgrade Umbraco, choose your target version, follow the upgrade path that matches your current version, and audit custom code and packages before work begins. Think of this section as an Umbraco upgrade guide written for budget holders rather than developers.

Which Umbraco Version Should You Upgrade To?

For most organizations, the answer is Umbraco 17.

  • Umbraco 17 is the current LTS version, supported until November 27, 2028.
  • Umbraco 18 is the newest release, but as an STS version it reaches end of life on June 25, 2027.

Umbraco’s own guidance:

  • Stay on Umbraco 17 if you are settled there and don’t need the new Library and Elements features.
  • Choose Umbraco 18 if you want those features now.
  • Upgrade to Umbraco 17 or later if you are still on Umbraco 13.

What Does Umbraco 17 Change for Your Team?

Umbraco 17 brings a new framework, a redesigned admin interface, and a new rich text editor. Each change affects developers, editors, or both.

  • Framework: Umbraco 17 runs on .NET 10, Microsoft’s current LTS framework.
  • Admin interface: The backoffice was rebuilt in TypeScript and Lit starting with Umbraco 14, replacing the old AngularJS interface. Editors coming from Umbraco 13 will notice the change.
  • Rich text editor: Tiptap became the rich text editor in Umbraco 15, and TinyMCE is gone by version 17. Formatting tools behave differently.
  • Scalability: The backoffice can be load balanced across servers.
  • AI connectivity: Umbraco’s official MCP server works only on version 17. It lets AI tools report on, add, or edit content in your backoffice.

What Is the Upgrade Path From Your Current Version?

Umbraco 13 can upgrade directly, Umbraco 10 to 12 must pass through 13 first, and Umbraco 7 and 8 require a rebuild.

Current version Path to Umbraco 17 What to expect
Umbraco 13 Direct upgrade Hours for simple sites; one developer documented a two-hour upgrade. Custom AngularJS admin extensions must be rewritten as Web Components. Sites with heavy block editor content may need a long-running content migration, because Umbraco 15 changed the storage format.
Umbraco 10, 11, 12 Upgrade to the latest Umbraco 13 first, then to 17 Two upgrade cycles, with package compatibility checked at each step
Umbraco 8 Content moves through Umbraco 10’s database migrations; templates and code are rebuilt Rebuild-level effort. Tools such as uSync Migrations convert legacy formats like Nested Content into Block List.
Umbraco 7 Multi-step content migration plus a full rebuild An Umbraco 7 to 17 migration is effectively a new build with your content carried over

How Much Does an Umbraco Upgrade Cost?

Cost depends less on your version number than on how customized your site is. A clean Umbraco 13 site can be upgraded quickly, while an Umbraco 7 or 8 site with custom features costs about as much as a new build.

Use these five questions to gauge your likely effort:

  1. Custom admin features: How many custom backoffice dashboards, property editors, or tools does your site have?
  2. Packages: Which third-party packages do you rely on, and does each have an Umbraco 17 version?
  3. Integrations: Which systems connect to your site, such as your CRM, single sign-on, search, or marketing tools?
  4. Block editor content: How much of your content is built with block editors?
  5. Hosting: Where is the site hosted, and is that environment ready for .NET 10?

The more of these that apply heavily to your site, the larger the project. An audit turns these answers into a fixed scope.

If those answers point to a rebuild, it’s worth looking beyond Umbraco before you commit.

How Do You Migrate From Umbraco to Another CMS?

You migrate from Umbraco by rebuilding your site on the new platform, moving content into it with repeatable scripted imports, and redirecting every old URL to its new address.

A migration is worth considering when:

  • An upgrade means rebuilding anyway, as it does from Umbraco 7 or 8.
  • .NET developers are hard to hire or keep at your organization.
  • Your other websites already run on WordPress or Drupal, so consolidating simplifies maintenance.
  • Your content team wants a different editing experience.

How to Migrate From Umbraco to WordPress

An Umbraco to WordPress migration follows these steps:

  1. Map content: Convert Umbraco document types into WordPress custom post types and custom fields.
  2. Rebuild templates: Recreate them as a WordPress theme or block-based design system.
  3. Export content: Use the Content Delivery API in Umbraco 12 and later, or database or uSync exports for older versions.
  4. Import content: Load it through the WordPress REST API or WP-CLI.
  5. Redirect URLs: Map every old URL to its new location with a 301 redirect.

WordPress suits marketing-led websites, teams that publish frequently, and organizations that want a large pool of developers and plugins. Plan for plugin governance from day one, because every plugin adds maintenance and security work. Complex approval workflows and multi-site setups also take more custom effort in WordPress.

When Does an Umbraco to Drupal Migration Make Sense?

An Umbraco to Drupal migration makes sense when your website has complex structured content, strict user roles and approvals, multilingual publishing, or multiple sites under one governance model. That profile is common in higher education, government, healthcare, and nonprofits.

  • Licensing: Drupal is open source, with no license fees.
  • Built-in governance: Granular permissions and content moderation come in the core platform.
  • Content import: Drupal’s Migrate API imports content from databases, JSON, and CSV files.
  • Version to target: Go straight to Drupal 11, since Drupal 10 reaches end of life on December 9, 2026.

What Other CMS Options Should You Consider?

  • Headless platforms such as Contentful, Sanity, and Storyblok suit organizations publishing to websites, apps, and other channels from one content source.
  • .NET-based digital experience platforms such as Optimizely and Xperience by Kentico let you keep your .NET skills, but they carry license fees.

What Does the Umbraco Migration Process Look Like?

  1. Audit: Inventory pages, document types, media, forms, members, and integrations.
  2. Clean up: Retire outdated and duplicate content so you migrate only what earns its place.
  3. Map: Match every content type and field to its new equivalent.
  4. Build: Create templates, components, and features on the target platform.
  5. Rehearse: Run scripted content imports several times before launch.
  6. Protect search visibility: Set redirects, and carry over metadata and structured data.
  7. Test and train: Check accessibility, performance, and functionality, then train editors.
  8. Launch: Freeze edits, run a final content sync, go live, and monitor rankings and errors.

With both paths laid out, a side-by-side view of the three most common destinations makes the trade-offs clearer.

Umbraco 17 vs. WordPress vs. Drupal: How Do They Compare?

All three are open source with no license fees for the core software. They differ in technology stack, available talent, and how much structure and governance they handle out of the box.

Umbraco 17 WordPress Drupal 11
Technology .NET (C#), SQL Server PHP, MySQL PHP, MySQL or PostgreSQL
License MIT GPL GPL
Release model New LTS roughly every two years, three years of support Continuous releases; sites are expected to stay current New major every two years, about four years of support
Permissions and workflows User groups built in; approval workflows via add-ons Basic roles; plugins for workflows Granular roles and content moderation built in
Multilingual Built-in language variants Plugins Built into core
Developer availability Smaller, .NET-focused pool Largest pool of the three Specialized, mid-sized pool
Best fit Teams with .NET skills that value a clean editing experience Marketing-led sites that publish often Complex, governed, multilingual, or multi-site estates

Should You Upgrade or Migrate? A Decision Framework

Upgrade when you are on Umbraco 13 and the platform still serves your team well. Evaluate a migration when you are starting from Umbraco 7 or 8, when .NET skills are scarce, or when your requirements match WordPress or Drupal more closely.

Your situation Likely best path
On Umbraco 13, editors are happy, .NET team in place Upgrade to Umbraco 17
On Umbraco 13 with few custom extensions Upgrade to Umbraco 17; effort is usually modest
On Umbraco 7 or 8 and a rebuild is unavoidable Price Umbraco 17, WordPress, and Drupal side by side
Struggling to hire or keep .NET developers Evaluate a WordPress or Drupal migration
Complex permissions, multi-site, or multilingual needs Compare Drupal with Umbraco 17
Marketing team wants faster publishing and more plugins Evaluate a WordPress migration
Budget frozen or deadline unrealistic Buy XLTS (LTS versions 10 and later) and plan the move

Before committing, leadership should agree on five answers:

  1. Total cost: What is the three-year cost of each path, including hosting, support, and future upgrades?
  2. Skills: Who will maintain the site, and which platform matches those skills?
  3. Roadmap: Which capabilities will you need, such as AI tools, headless delivery, or personalization?
  4. Editor experience: How well does the current editing experience work for your content team?
  5. Compliance: Which security, hosting, and accessibility requirements must the platform meet?

Not Sure Whether to Upgrade or Migrate?

Get a side-by-side view of effort, timeline, risk, and three-year cost for your Umbraco site. Our CMS experts recommend the path that fits your team and goals, not a preferred platform.

Schedule a Call With Our Expert →

Once you have a direction, the calendar decides how much room you have to act.

What Should Umbraco 13 Sites Do Before December 14, 2026?

Audit your site now, decide on your path by mid-November, and either complete the upgrade or order XLTS before December 14. XLTS coverage must start the day after end of life with no gap. As of early October, that leaves about ten weeks.

When Action
October, weeks 1 to 2 Audit code, packages, and integrations. List every custom admin extension.
October, weeks 3 to 4 Price an upgrade to Umbraco 17 against a migration. Agree on a budget and an owner.
By mid-November If the upgrade cannot realistically finish by December 14, order XLTS for 6, 12, or 24 months.
December 14 Be live on Umbraco 17, or be covered by XLTS.
Early 2027 Finish the upgrade or migration within your XLTS window.

XLTS is a paid contract, so every extra month adds cost without adding capability. The sooner the audit happens, the more options stay open.

How Do You Choose the Best Umbraco Migration or Upgrade Agency?

Choose an agency that does four things:

  • Audits before quoting.
  • Holds credentials you can verify for Umbraco or for your target platform.
  • Shows comparable projects from a similar starting version.
  • Recommends upgrade or migration without bias.

When you compare Umbraco migration services, the agency will shape cost, timeline, and risk more than the platform itself.

Which Credentials Should You Verify?

Check the agency’s Umbraco partner tier and its developers’ certifications.

  • Partner tiers: Umbraco’s partner program has three tiers, each requiring active certified developers. Silver requires at least one Certified Professional, Gold at least one Certified Expert, and Platinum at least one Certified Master or two Certified Experts. You can confirm any agency’s tier in the Partner Finder on umbraco.com.
  • Target-platform expertise: For a migration, also confirm proven WordPress or Drupal expertise.
  • Case studies: Ask for examples that match your starting version, with results such as search traffic retained after launch.

What Should You Ask Before You Sign?

Ask questions that reveal how the agency manages risk, not just how it builds.

  • Will you audit our code and content before giving a fixed quote?
  • How will you handle custom admin extensions and packages that lack Umbraco 17 support?
  • What is your plan for redirects and search ranking monitoring?
  • How long will content editing be frozen during cutover?
  • Is the quote fixed price or time and materials, and what is excluded?
  • Which accessibility standard will you test against, such as WCAG 2.1 AA?
  • Who supports the site after launch, and what response times do you commit to?

What Are the Red Flags?

Be cautious of any agency that:

  • Recommends a platform before reviewing your site.
  • Quotes without access to your code, packages, and integrations.
  • Has no documented redirect or SEO plan.
  • Offers no post-launch support model.
  • Cannot show a comparable project.

Why Organizations Choose BinaryWorks for CMS Upgrades and Migrations

BinaryWorks is a CMS, digital marketing, and AI solutions agency. Our team of certified Drupal and WordPress engineers contributes to the open-source Drupal project and has delivered enterprise CMS work since 2009.

Organizations planning an Umbraco move work with us for five reasons:

  • Platform-neutral advice: We compare an Umbraco upgrade with a WordPress or Drupal migration and recommend the path that fits your team, budget, and roadmap.
  • Numbers before commitments: You get effort, timeline, risk, and three-year cost for each option before you sign anything.
  • Search protection built in: URL mapping, redirects, and post-launch monitoring are part of every migration plan.
  • Support after launch: Ongoing maintenance keeps your new platform patched and current.
  • Growth beyond the rebuild: Our digital marketing and AI teams help your new site earn visibility in search engines and AI answers.

Frequently Asked Questions

Is Umbraco 7 Still Supported?

No. Umbraco 7 reached end of life on September 30, 2023, and receives no security patches. Because it runs on the legacy .NET Framework, moving forward requires a rebuild on a supported version or on another CMS.

What Is the Latest Version of Umbraco?

The latest version is Umbraco 18, an STS release from June 25, 2026, with Umbraco 19 due on December 10, 2026. For stability, most organizations should target Umbraco 17, the current LTS version.

Should We Redesign Our Website During an Umbraco Upgrade?

It depends on your starting version. From Umbraco 7 or 8, templates are rebuilt anyway, so a redesign adds little extra effort. From Umbraco 13, keeping the upgrade separate from a redesign usually lowers risk and gets you onto a supported version faster.

How Long Does an Umbraco to WordPress Migration Take?

It usually takes a few weeks for a small brochure site and several months for a large site with integrations, member areas, or multiple languages. Content volume and custom features drive most of the timeline.

Can We Keep Our Content and URLs When We Migrate?

Yes. Content is moved with scripted imports. URLs can be kept identical where the new platform allows, or redirected with 301 redirects so visitors and search engines reach the right page.

Will an Umbraco Migration Hurt Our Search Rankings?

Not if it’s planned properly. Rankings are protected by mapping every URL, carrying over metadata and structured data, and monitoring search performance closely for several weeks after launch.

Plan Your Umbraco Move Before December 14

Review your version, custom code, and integrations with a BinaryWorks expert. Leave the call with a clear recommendation and the next steps to keep your site secure.

Schedule a Call With Our Expert →