Is Umbraco 13 still supported?

Partly: security fixes only, until 14 December 2026. Bug fixes ended on 14 December 2025. After 14 December 2026 Umbraco 13 LTS gets no patches at all, so plan the move to Umbraco 17 LTS now.

Can we upgrade from Umbraco 13 straight to 17?

Yes. Umbraco supports upgrading directly from one LTS to the next, so you do not install 14, 15 and 16 first. The breaking changes from those versions still apply, and we handle them in the same project.

How long does the upgrade take?

Usually 2 to 6 weeks. A standard content site sits at the low end. Custom property editors, dashboards, packages and integrations push it higher. The audit gives you the exact scope.

Will our content, media and URLs survive?

Yes. Content, media, members and URLs move with the database. We check every URL and redirect before go-live, so search rankings are not affected.

Do we need to change hosting?

Only if your host cannot run .NET 10. Umbraco 17 runs on .NET 10, which Azure App Service and Umbraco Cloud support. On your own servers we install the .NET 10 hosting bundle.

Do editors need retraining?

A little. The new backoffice looks different but works the same way. We include a one-hour walkthrough for your editors before go-live.

Upgrade Umbraco 13 to 17: Changes & Timeline

Upgrade Umbraco 13 to 17 LTS

Short answer

Umbraco 13 gets its last security fixes until 14 December 2026. Microsoft ends support for .NET 8, which it runs on, even earlier: 10 November 2026. Umbraco 17 LTS runs on .NET 10 and is supported until 27 November 2028. For most sites the upgrade takes 2 to 6 weeks; the main work is rebuilding custom backoffice code for the new Web Components backoffice.

What changes between Umbraco 13 and 17

Four major versions sit between them. Most of the work comes from Umbraco 14, which replaced the backoffice.

Area	Umbraco 13	Umbraco 17	What it means for you
Runtime	.NET 8	.NET 10	Update the solution, NuGet packages and hosting. Usually the easy part.
Backoffice	AngularJS	Web Components (Lit)	Custom property editors, dashboards and content apps are rebuilt as extensions. `package.manifest` becomes `umbraco-package.json`.
Macros	Supported	Removed	Replace them with blocks in the rich text editor or the Block Grid.
Legacy grid, Nested Content	Available	Removed	Content moves to Block Grid and Block List.
Rich text editor	TinyMCE	Tiptap	Custom editor plugins and style formats need rework.
Content cache	NuCache	HybridCache	Code that relies on cache internals needs a review.

How long it takes

Your site	Typical duration
Standard content site, few packages, no custom editors	2 to 3 weeks
Custom property editors or dashboards, several packages	3 to 5 weeks
Many customisations, integrations or a multi-site setup	5 to 8 weeks

Your fixed quote comes from the audit, not from this table.

How we run the upgrade

Audit. A free 30-minute call, then a review of your code, packages, content types and hosting.
Fixed plan. Scope, risks and one price, agreed before work starts.
Upgrade on a branch. We upgrade to 17, replace or update packages and keep schema and content in step between environments with uSync.
Rebuild backoffice extensions. Custom editors and dashboards are rebuilt in TypeScript and Lit for the new backoffice.
Verify. Visual regression tests, redirect and URL checks, SEO parity and performance checks on a staging site you can click through.
Go live. A zero-downtime cut-over, then 30 days of hypercare.

Should you go to Umbraco 18 instead?

Usually not. Umbraco 18 is a short-term release supported until 25 June 2027, while Umbraco 17 is supported until 27 November 2028. Go to 17 now; the step from 17 to the next LTS will be much smaller than this one.

What it costs

A fixed price, agreed after the free audit and before any work starts. It covers the upgrade, the extension rebuilds, testing, go-live and 30 days of hypercare, so the number does not change halfway through.

Sources: Umbraco version status (recalculated daily) and Microsoft's .NET support policy.