Umbraco 8 End of Life: What UK Businesses Need to Know

Key Takeaways

• Umbraco 8 reached end of life in February 2025 — no more security patches, bug fixes, or official support from Umbraco HQ
• Running an unsupported CMS is not a future risk — it is a present security vulnerability with GDPR implications
• Three migration paths: upgrade to Umbraco 17 (current LTS, supported until November 2028), rebuild on a different platform, or take a phased approach via v13
• Typical UK migration costs range from £3,000 for simple sites to £8,000+ for complex installations, with a 4–8 week timeline

Umbraco 8 reached end of life in February 2025. If your website is still running on it, you are no longer receiving security patches, bug fixes, or official support from Umbraco HQ. This is not a future risk — it is a present one.

We work with a number of businesses that inherited Umbraco 8 sites or built on it when it was the right choice. The platform served them well. But the world has moved on, and leaving an unpatched CMS facing the open internet is a problem that compounds over time.

Here is what you need to know, and what your options are.

What Umbraco 8 End of Life Actually Means

End of life does not mean your site stops working tomorrow. Your Umbraco 8 site will carry on running. But "carrying on" is not the same as being safe.

From February 2025, Umbraco HQ stopped releasing:

• Security patches — any newly discovered vulnerabilities in Umbraco 8 will not be fixed
• Bug fixes — existing known issues will not be resolved
• Compatibility updates — as the .NET ecosystem evolves, Umbraco 8 falls further behind
• Official support — you cannot raise issues with Umbraco HQ and expect a resolution

The practical consequence is that your site is running on software with a growing list of known and unknown vulnerabilities, with no remediation coming.

The Technology Gap: .NET Framework 4.8 vs .NET 8+

Umbraco 8 was built on .NET Framework 4.8 — Microsoft's legacy Windows-only runtime. It works, but it is end of the line. Microsoft has been clear that .NET Framework will not receive new features, only critical security fixes, and even those have a horizon.

Umbraco 17 (current LTS) runs on .NET 10 — Microsoft's latest cross-platform runtime. Umbraco 13 (previous LTS, approaching EOL December 2026) runs on .NET 8. The differences matter:

• Performance: .NET 8 is significantly faster than .NET Framework 4.8
• Security: Modern runtime with active patching and a strong security track record
• Hosting flexibility: Runs on Linux, meaning cheaper and more flexible cloud hosting
• Long-term support: .NET 8 is supported until November 2026. .NET 10 (powering Umbraco 17) is an LTS release supported until November 2028
• Ecosystem compatibility: Modern packages, libraries, and tooling no longer support .NET Framework 4.8

Staying on Umbraco 8 is not just a CMS decision — it is a decision to stay on an entire legacy technology stack.

The Real Security Risks

Let us be direct about what this means in practice.

Known Vulnerabilities Remain Unpatched

The Umbraco security team has historically been responsive and responsible with disclosure. But that relationship ended when Umbraco 8 hit EOL. Any CVEs (common vulnerabilities and exposures) discovered from February 2025 onwards will be fixed in supported versions. Umbraco 8 gets nothing.

The CMS Admin Panel Is Exposed

Umbraco's backoffice is typically accessible at `/umbraco`. Attackers specifically target known CMS admin routes. An unpatched Umbraco 8 installation is a known target with a shrinking window of protection.

Third-Party Package Vulnerabilities

Most Umbraco 8 sites use packages from the Umbraco Marketplace and NuGet. Many of those packages have also dropped support for Umbraco 8. If a vulnerability is found in a package your site depends on, you face a choice: remove the functionality, or leave the vulnerability in place.

Hosting and Compliance Risk

If your site handles customer data — even something as basic as a contact form — you have GDPR obligations. Running software you know is unpatched and potentially vulnerable creates a compliance exposure that your legal and insurance teams would find uncomfortable.

Your Migration Options

There is no single migration path — it depends on your site's complexity, your content structure, and how much custom development was involved.

Option 1: Umbraco 8 to Umbraco 17 (Current LTS)

Umbraco 17 is the current long-term support release. It runs on .NET 10 and is supported until November 2028. This is now the recommended migration target for Umbraco 8 sites because:

• The content model (Document Types, Data Types) is conceptually similar
• Umbraco provides official guidance on the v8 to v13 migration
• Third-party package coverage is reasonable for v13
• It is a known quantity for developers who have worked with Umbraco

The catch: this is not an in-place upgrade. Umbraco 8 to v13 requires rebuilding the .NET project structure, migrating the database schema, and testing every template, macro, and custom component. For most sites, this means weeks of development work.

Typical cost: £3,000 – £8,000+ depending on complexity. Typical timeline: 4–8 weeks.

Option 2: Umbraco 8 via v13 (Phased Approach)

For complex sites with extensive custom functionality, a phased approach can reduce risk: migrate to Umbraco 13 first (stabilise on .NET 8), then upgrade to v17 within 6 months. This spreads cost and testing across two smaller jumps rather than one large leap.

The trade-off is that v13 reaches end of life on 14 December 2026, so this approach only works if you commit to completing the v17 upgrade promptly. Delaying leaves you on another expiring version.

Option 3: Change CMS Entirely

For some businesses, an Umbraco migration is the right time to ask whether Umbraco is still the right platform. If your site's requirements have changed — simpler content, smaller team, lower budget for ongoing maintenance — a move to a different CMS (or a more appropriate framework) might serve you better in the long run.

We will always give you an honest answer here. If Umbraco is overkill for what you need now, we will say so.

What Does Migration Actually Involve?

Every migration is different, but the core process follows a similar path.

1. Audit your existing site Before writing a line of code, we document everything: Document Types, Data Types, content tree structure, custom components, third-party packages, and any bespoke functionality. This audit drives the project plan.

2. Set up the new project We create a fresh Umbraco 17 project with .NET 10, establish the hosting environment, and configure CI/CD pipelines. We do not try to upgrade in-place — a clean foundation avoids carrying forward legacy debt.

3. Rebuild the content model Document Types and Data Types are recreated in the new version. Where Umbraco's property editors have changed between versions, we identify the closest equivalent and document any gaps.

4. Migrate content This is often the most labour-intensive part. Content can be migrated using Umbraco's Content Migration API, third-party tools, or direct database work — depending on volume and complexity. We test every content type thoroughly before sign-off.

5. Rebuild templates and components Umbraco 8 used Razor views in a specific structure. The new version has a slightly different pattern. Templates, partial views, and any surface controllers need rebuilding. This is also the point where we modernise the front-end if required.

6. Test, test, test We run through every page type, form, and integration. We check for broken links, missing content, and any edge cases in the content model. We also run security scanning against the new site before launch.

7. Go live DNS cutover, SSL verification, redirect mapping (critical if URL structure changes), and post-launch monitoring.

What About My Current Hosting?

Umbraco 8 sites typically run on Windows hosting with IIS. Umbraco 13+ on .NET 8 can run on Linux, which opens up a wider and often cheaper range of hosting options — including cloud providers that offer better performance and resilience.

As part of any migration we handle, we include a hosting recommendation based on your traffic, uptime requirements, and budget. Our SiteCare plans cover ongoing hosting, security monitoring, updates, and support for the migrated site.

Timelines and Urgency

Umbraco 8 EOL has already happened. Every month you remain on it is another month of compounding risk.

If you have not yet started the conversation about migration, the time to start is now — not when something goes wrong. Emergency migrations are expensive, stressful, and sometimes not possible if a security incident has already compromised your data.

A planned migration, handled properly, takes 4–8 weeks for most sites. An unplanned response to a security incident could take longer and cost significantly more.

How We Can Help

We have worked with Umbraco sites across a range of sectors — professional services, education, non-profit, and commercial. We understand the platform, we know the migration gotchas (and there are several), and we do not disappear after go-live.

Our custom website development service covers Umbraco migrations from scoping through to launch. We handle the technical rebuild and can advise on content strategy, hosting, and ongoing maintenance.

If you are not sure where your site sits, start with a conversation. We can review your existing Umbraco installation and give you a straightforward assessment of the work involved.

Ready to get off Umbraco 8?

If your site is still running on Umbraco 8, the time to act is now. We will audit your existing setup, scope the migration properly, and deliver a site that is secure, performant, and supported for years to come.

Start the conversation — no obligation, no sales pitch. Just an honest assessment of what your migration involves and what it will cost.

Frequently Asked Questions

Is Umbraco 8 still safe to use?

No. Since February 2025, Umbraco 8 has received no security patches. Any vulnerabilities discovered since that date remain unpatched on your site. If your site handles contact forms, user accounts, or payment data, you have an obligation under UK GDPR to keep your software up to date. The longer you wait, the higher the risk.

How much does it cost to migrate from Umbraco 8?

Typical UK migration costs: £3,000–£5,000 for simple sites (under 50 pages, no custom integrations), £5,000–£8,000 for medium complexity, and £8,000+ for large or heavily customised installations. We scope every project individually and provide a fixed quote — start a conversation for an honest assessment.

Can I upgrade Umbraco 8 directly to version 13?

Not directly. Umbraco 8 runs on .NET Framework 4.x while Umbraco 13 runs on .NET 8 — they are fundamentally different platforms. In practice, most migrations involve rebuilding the templates and data layer while migrating your content. Our upgrade guide breaks down the full process step by step.

Related Reading

• Umbraco Upgrade Guide: v8 to v13 — Costs, Timeline & What to Expect
• Umbraco vs WordPress: Which CMS Should Your Business Use?
• Should You Upgrade Your Umbraco Website?
• Umbraco Development Costs in the UK