Why go straight to 17 and not to Umbraco 13 first?

Umbraco 13 itself reaches end-of-life on 14 December 2026; anyone migrating there now faces the same job again within a year. By going straight to the current LTS, the site is covered by support until 27 November 2028.

What happens to custom code from the old backoffice?

The old backoffice ran on AngularJS, which is gone from the new Umbraco versions. Custom property editors are therefore rebuilt on the new backoffice. In this case that applied to a handful of editors; the CRM integration was upgraded to the current APIs and now runs on .NET 10.

Does the content move over automatically?

Largely. The content was migrated automatically to the new block-based setup and then checked section by section. That check is exactly what makes the difference: a migration is also the moment to clean up a silted-up structure.

How big is the next upgrade after a migration like this?

Considerably smaller. Once you're on the current LTS, you upgrade from LTS to LTS from then on — a series of small, predictable steps instead of one big catch-up.

Back to News

From an expired support window to years of runway

Case study: migrating from Umbraco 10 to 17

Umbraco Case study

For a Dutch B2B organisation we recently migrated a corporate site from Umbraco 10 to Umbraco 17. The reason was practical: version 10's support window had ended, several of the packages in use were no longer maintained, and the underlying .NET version was nearing its end.

The starting point

The site had been running on Umbraco 10 since 2022, with a handful of custom property editors in the old AngularJS backoffice and an integration with an external CRM. Editors worked with a grid setup that had silted up over the years.

The approach

Document types and datatypes were set up fresh around block-based content, replacing the old grid.
The custom property editors were rebuilt for the new backoffice; the AngularJS variants were not carried over.
Content was migrated automatically and checked section by section.
The CRM integration was upgraded to the current APIs and now runs on .NET 10. This is how we approach integrations in Umbraco.

The result

The organisation now runs on the LTS version and receives security and bug fixes again. The editors work with blocks and can update pages on-page with EvolveCMS.Editor. The next big step won't come up until the next LTS — and that step will be considerably smaller than this one was. Curious about the numbers behind such a project? See what an Umbraco migration costs.

Going live is step one, being found is step two: read how we made this site visible to Google.

Also looking to move off Umbraco 10 (or older)? Get in touch via support.

Contactgegevens

Adres

Get in touch

Postbus

Curious what this means for your site? Leave your details and briefly describe what you're running into, and we'll get back to you. We usually respond within one business day.

Prefer direct contact? Feel free to call or email us.

+31 10 270 75 75 hallo@admix.nl

Full name

Email address

Your message

I agree to the processing of my data in accordance with the privacy statement.

Frequently asked questions about this migration

: Umbraco 13 itself reaches end-of-life on 14 December 2026; anyone migrating there now faces the same job again within a year. By going straight to the current LTS, the site is covered by support until 27 November 2028.
: The old backoffice ran on AngularJS, which is gone from the new Umbraco versions. Custom property editors are therefore rebuilt on the new backoffice. In this case that applied to a handful of editors; the CRM integration was upgraded to the current APIs and now runs on .NET 10.
: Largely. The content was migrated automatically to the new block-based setup and then checked section by section. That check is exactly what makes the difference: a migration is also the moment to clean up a silted-up structure.
: Considerably smaller. Once you're on the current LTS, you upgrade from LTS to LTS from then on — a series of small, predictable steps instead of one big catch-up.