Should You Upgrade Your Umbraco Website?

Key Takeaways

• Umbraco 8 reached end of life on 24 February 2025, meaning no further security patches — sites still running v8 are increasingly vulnerable (Umbraco EOL announcement)
• Upgrading from Umbraco 8 to v17 is not a simple update — it's effectively a migration to a new platform due to the .NET Framework to .NET 10 transition
• The cost of not upgrading increases over time — security risks, performance degradation, and inability to find developers willing to work on legacy .NET Framework code
• You don't necessarily have to stay on Umbraco — for some businesses, a migration to a different platform is the more cost-effective long-term choice

If you're running a website on Umbraco, the upgrade question is probably on your mind. Maybe your hosting provider has mentioned it, or you've noticed things running slower than they used to. Perhaps you've tried to hire a developer and they've told you they only work with modern Umbraco.

We work with Umbraco regularly — from maintaining legacy v7 sites to building on v17 and planning v8 migrations. Here's an honest assessment of whether upgrading makes sense for your business.

Understanding Where You Are

The first step is knowing which version you're running. This matters because the upgrade path is very different depending on your starting point:

Umbraco 7 or Earlier

If you're on Umbraco 7, you're running on seriously outdated technology. Umbraco 7 reached end of life in September 2023. That means:

• No security patches since September 2023
• Running on .NET Framework 4.x (legacy technology)
• Increasingly difficult to find developers
• Many modern hosting environments are phasing out .NET Framework support

The honest assessment: You need to move. Whether that's to modern Umbraco or a different platform entirely, staying on v7 is a security liability.

Umbraco 8

Umbraco 8 reached end of life on 24 February 2025. It was a significant improvement over v7 with a modern backoffice and better content modelling. However, it still runs on .NET Framework, which is the core problem.

The honest assessment: Umbraco 8 is now past end of life with no further security patches. If you are still running v8, migration should be treated as urgent — every month of delay increases your security exposure. Plan your move as soon as possible.

Umbraco 10–12 (LTS)

These versions run on modern .NET (6/7/8) and are supported with security patches. Umbraco 10 LTS reached end of life on 16 June 2025. Umbraco 13 LTS reaches end of life on 14 December 2026. Umbraco 17 is the current LTS, supported until November 2028.

The honest assessment: If you're on Umbraco 10 or 12, check your current support status. Umbraco 10 has already reached EOL — upgrading to v13 is now the recommended path. Focus on staying on the latest LTS version.

Umbraco 13 (Previous LTS — Approaching EOL)

Umbraco 13 reaches end of life on 14 December 2026. If you are on v13, start planning your upgrade to Umbraco 17 (current LTS, supported until November 2028). You have time, but it should be on your roadmap for 2026.

Umbraco 17 (Current LTS)

You are on the latest long-term support version. No immediate action needed.

When Upgrading Makes Sense

Not every Umbraco site needs to upgrade immediately. Here are the scenarios where it's clearly the right call:

Your site handles sensitive data. If your Umbraco site processes payments, stores personal data, or handles any form of customer information, running on an unsupported version is a GDPR risk. The ICO can and does investigate breaches caused by unpatched software.

You're struggling to find developers. The .NET Framework talent pool is shrinking rapidly. Developers are moving to modern .NET, and those still working with legacy .NET Framework charge premium rates because the demand exceeds supply. If your current developer retires or moves on, you could be stuck.

Performance is degrading. Older Umbraco versions on .NET Framework are measurably slower than modern versions. If your site's Core Web Vitals are suffering — especially Largest Contentful Paint and Interaction to Next Paint — an upgrade will deliver significant improvements.

You need new features. Modern Umbraco has vastly better content modelling, media management, and API capabilities. If you're finding workarounds for things the CMS should handle natively, an upgrade removes those pain points.

Your hosting costs are increasing. Windows hosting for .NET Framework is becoming more expensive as providers consolidate. Modern Umbraco on .NET 8/10 runs on Linux, which is typically 30–50% cheaper for equivalent specifications.

When You Might Not Need to Upgrade

Sometimes the pragmatic answer is to hold off:

Your site is simple and low-risk. A 5-page brochure site with no forms, no user data, and no e-commerce functionality has a lower risk profile. The security argument is weaker if there's nothing valuable to compromise.

You're planning a complete rebuild anyway. If you're 6–12 months away from a full website redesign, investing in an Umbraco upgrade that you'll replace is poor value. Spend that budget on the new build instead.

Your budget is genuinely constrained. An Umbraco 8 to 13 migration typically costs £3,000–£8,000 depending on complexity. If that budget simply isn't available, focus on the security mitigations you can afford — WAF, stricter access controls, regular backups.

Upgrade vs. Migrate: The Key Decision

Here's the question most agencies won't ask you: should you stay on Umbraco at all?

Umbraco is excellent for content-heavy sites with complex editorial workflows. But if your site is relatively simple — a brochure site, a small blog, basic service pages — Umbraco may be more CMS than you need.

Consider the alternatives:

| Scenario | Umbraco Upgrade | Different Platform | |----------|----------------|--------------------| | Complex content structure | ✓ Best option | May lose editorial features | | Simple brochure site | Possibly over-engineered | Custom build or WordPress may be more cost-effective | | E-commerce needed | Umbraco can do it, but... | Shopify is purpose-built | | Tight budget | £3,000–£8,000+ | Custom build from £2,500 | | In-house .NET team | Natural fit | Retraining cost | | No technical team | Consider managed options | WordPress or custom with SiteCare |

We've recommended clients move away from Umbraco when their needs have changed. It's not a reflection on the platform — it's about matching the tool to the job. Our CMS comparison guide covers the full landscape.

What an Umbraco Upgrade Involves

If you decide to upgrade, here's what to expect:

From v8 to v13 (Major Migration)

This is not a click-a-button upgrade. The transition from .NET Framework to .NET 8 means:

1. Backend rebuild — controllers, services, and custom code rewritten for .NET 8
2. Template migration — Razor views updated to modern syntax
3. Package replacement — many v8 packages don't have v13 equivalents
4. Content migration — database schema changes require careful data migration
5. Testing — thorough testing of all functionality, integrations, and edge cases

Timeline: 4–8 weeks depending on site complexity Cost: £3,000–£8,000+

See our detailed Umbraco v8 to v13 upgrade guide for the full technical breakdown.

From v10/12 to v13 (Minor Upgrade)

Upgrading between modern Umbraco versions is much simpler:

1. NuGet package updates — update dependencies
2. Breaking change review — check Umbraco's migration notes
3. Testing — verify custom functionality

Timeline: 1–3 days Cost: £500–£1,500

Taking the Next Step

If you're unsure whether to upgrade, here's a practical approach:

1. Identify your current version — check the Umbraco backoffice (bottom-left corner shows the version number)
2. Assess your risk — does your site handle personal data? Process payments? Store anything sensitive?
3. Get a technical audit — have a developer review your site's codebase and identify the migration complexity
4. Compare costs — get quotes for both an Umbraco upgrade and a fresh build on a different platform
5. Make a decision based on 3-year TCO — not just the upfront cost

Our website audit service includes a CMS assessment that covers all of this. The mini audit is free — we'll tell you where you stand and what your options are.

Frequently Asked Questions

Is it safe to keep running Umbraco 8 after end of life?

It depends on your risk tolerance. There are no more security patches, so any new vulnerabilities discovered in .NET Framework or Umbraco 8 will remain unpatched. For sites handling personal data, this creates GDPR compliance risk. For simple brochure sites with no data collection, the immediate risk is lower but still present. NCSC guidance recommends against using end-of-life software in production.

Can I upgrade Umbraco myself?

A v10 to v13 upgrade is feasible for an experienced .NET developer. A v8 to v13 migration is not a DIY job — it requires deep knowledge of both the old and new frameworks. We'd strongly recommend engaging a specialist for any cross-framework migration.

How long does an Umbraco upgrade take?

A v10/12 to v13 upgrade typically takes 1–3 days of developer time. A v8 to v13 migration takes 4–8 weeks including testing. Timeline depends on site complexity, custom code volume, number of integrations, and content volume.

Related Reading

• Umbraco v8 to v13 Upgrade Guide
• Umbraco 8 End of Life: What It Means for Your Site
• Umbraco vs WordPress: Which Is Right for Your Business?
• Umbraco 13 Features Guide
• Umbraco Development Costs in the UK

Running an older Umbraco site and want to know your options? Book a free mini audit and we'll assess your site, outline the upgrade path, and give you an honest recommendation — even if that means moving to a different platform entirely.