Umbraco 17 is the current long-term support (LTS) release of Umbraco and runs on .NET 10. If your site is still on Umbraco 13, 10 or older, an upgrade is coming whether you plan it or not. This guide covers what changed, how to choose between an in-place upgrade and a migration, and how to protect your search rankings while you do it.
What changed between Umbraco 13 and Umbraco 17
The biggest change happened in Umbraco 14: the back office was rebuilt from scratch on web components. The old AngularJS back office is gone. For editors the concepts are the same, but for developers it means every custom dashboard, property editor and back-office extension has to be rebuilt.
Back office: new UI built on web components (Lit). AngularJS extensions do not carry over.
Packages: any package without an Umbraco 17 version needs a replacement or a rebuild.
Legacy editors: older property editors were removed in favour of the Block List and Block Grid, so some content needs converting.
Runtime: Umbraco 17 runs on .NET 10, so custom code and hosting move to the current .NET runtime.
Upgrade in place or migrate?
From Umbraco 13, an in-place upgrade is usually possible: update the packages, run the database migrations and rebuild the back-office extensions. From Umbraco 8 or older, the data model and APIs are far enough apart that building a fresh Umbraco 17 site and migrating the content is often cleaner and cheaper. Community tools such as uSync Migrations help move content between major versions.
Upgrade in place when you are on Umbraco 13, use few third-party packages and the content model is still a good fit.
Migrate when you are on Umbraco 8 or older, depend on abandoned packages, or want to redesign the content model anyway.
A practical upgrade plan
Audit: list the version, every package, all custom code, integrations and scheduled jobs.
Decide per package: upgrade, replace or rebuild. This decides most of the effort.
Rehearse on a copy: run the full upgrade or migration on a staging copy of production data, never on production first.
Rebuild back-office extensions for the new back office.
Test with editors: let them publish real content on staging before launch.
Cut over: freeze content briefly, sync the final content, switch traffic and monitor.
Protect your SEO during the move
Most traffic lost in CMS moves comes from URLs that change without redirects. Before launch, export every live URL from the sitemap and your analytics, compare it with the new site, and add a 301 redirect for every URL that moves. Check titles, meta descriptions, canonical tags, hreflang and the sitemap on staging, then run a full crawl right after launch.
We learned this on our own site: when we rebuilt splatdev.com on Umbraco 17, the crawls after launch caught problems a manual check would have missed. You can read the details in our case study.
How long does it take?
It depends on the number of document types, templates, packages and integrations. A small brochure site can move in a couple of weeks. Large multilingual sites with custom back-office tools take longer, and most of that time goes into packages and extensions, not content.
Need help?
We plan and run Umbraco 17 upgrades and migrations, and we build Umbraco plugins for Umbraco 13 and 17. Contact us for an upgrade assessment.