What your editorial team actually gains when you upgrade to Umbraco 17

The conversation about upgrading from Umbraco 13 to Umbraco 17 usually starts with compliance deadlines and security risks. Those matter. But if you’re a Marketing Director or Digital Director being asked to support this investment, the question you probably care about most is simpler: what will actually be different for my team on Monday morning after go-live? 

More than you might expect. The upgrade crosses an architectural boundary that Umbraco introduced in version 14 — a complete rebuild of the editorial backoffice’s underlying technology. The day-to-day CMS workflow will feel familiar, but the platform underneath is modern, faster, and opens up capabilities that weren’t previously possible. 

The technology underneath has been rebuilt 

Umbraco 13’s editorial interface was built on AngularJS — a framework Google stopped maintaining in 2022. It worked, but the underlying technology had reached its limits in terms of what Umbraco could build on top of it. 

Version 17’s backoffice has been rebuilt from the ground up using modern web standards. The important thing for editorial teams is that Umbraco designed this deliberately to feel familiar. The core CMS workflow — creating content, publishing, managing media — follows the same patterns your team already knows. Visual styling has been refreshed, and there are targeted improvements in areas like displaying large content trees and managing complex site structures, but this isn’t a case of learning an entirely new system. 

The real difference is in what the new architecture makes possible. The rebuilt foundation is faster, more extensible, and opens up customisation options that simply weren’t available on the old framework. Your team gets a cleaner, more responsive interface with room to grow. 

What does ‘customisable backoffice’ actually mean? 

This is the feature most often quoted in upgrade discussions and least often explained. Umbraco 17’s backoffice is built on an Extension First architecture. In practical terms, this means the interface your editorial team sees can be shaped to match how they work, rather than your team adapting to the interface. 

A publishing team that primarily manages news articles can have a streamlined view focused on content creation and scheduling. A product team maintaining hundreds of catalogue pages can have dashboards surfacing the data they need. An approvals team can see workflow status at a glance without navigating through content trees. Property-level permissions — introduced in version 16 and carried into version 17 — mean specific fields can be locked or hidden for particular user groups, reducing errors and simplifying the editing experience for different roles. 

The customisation requires development work. This isn’t a drag-and-drop interface builder. But once configured, it means your editorial team gets a CMS that reflects their workflows rather than imposing a generic one. 

Your content comes with you 

One of the most common concerns about any CMS upgrade is whether existing content survives the transition. For the Umbraco 13 to 17 path, the answer is straightforward: your content models and data migrate directly. The upgrade includes automatic database migrations that carry your existing content across. 

What doesn’t carry across automatically is custom backoffice code. If your version 13 implementation includes bespoke dashboards, custom property editors, or tailored backoffice sections, these will need rebuilding for the new architecture. This is typically the most significant part of the upgrade effort and the area where your agency partner’s experience matters most. 

Templates, views, and front-end code are largely unaffected — the backoffice rebuild is a back-end change. Your website’s public-facing appearance doesn’t change unless you choose to redesign alongside the upgrade. Many organisations treat the migration as a platform-only project and plan any front-end improvements as a separate phase. 

The integration picture changes significantly 

Umbraco 17 includes the Management API — a standardised interface for connecting external systems to the CMS. If your current Umbraco 13 implementation relies on custom integration code to pull data from CRM systems, product databases, or other business tools, the Management API provides a cleaner, more maintainable approach. 

For editorial teams, this translates to fewer workarounds. Product information that currently requires manual re-entry or batch imports could be surfaced within the CMS. Customer data from CRM systems becomes accessible without switching between platforms. The specifics depend on your integration requirements, but the underlying capability is materially stronger than what version 13 offered. 

It’s worth noting that integration still requires development effort. The Management API provides the framework; someone still needs to build the connections for your specific systems. But the foundations are now standardised rather than bespoke, which typically means lower cost and easier maintenance over time. 

How disruptive is the transition for your team? 

Less than you might fear. The CMS workflow in version 17 is very similar to version 13. Creating and editing content, managing media, publishing pages — the core tasks your editorial team does every day follow the same patterns. The visual styling has been updated, and there are some new features in areas like content tree navigation for large sites, but the fundamental way of working in the CMS hasn’t changed. 

That said, any interface change takes a little adjustment. Even when the workflow is familiar, updated visuals and repositioned elements can slow people down for a day or two. A short walkthrough with your team — even half a day — makes a noticeable difference to adoption speed compared to simply switching over and expecting people to find their way. 

The migration itself can run alongside your live site. Your existing Umbraco 13 installation continues operating while the upgrade is developed and tested in a separate environment. The cutover happens when everything is validated, which means minimal disruption to your publishing schedule. 

When the upgrade is also a design opportunity 

Some organisations use the Umbraco 13 end-of-life deadline as the trigger for a broader refresh. If your website’s design, content structure, or user journeys are overdue for attention, combining a platform upgrade with a front-end redesign can be efficient — one period of managed disruption rather than two. 

Others deliberately keep the two separate. Upgrade the platform first, stabilise, then invest in front-end improvements from a solid foundation. Both approaches work. The right choice depends on your budget cycle, your team’s capacity for change, and how urgently your digital presence needs visual or structural improvement. 

If you’re unsure which approach fits, an experienced Umbraco partner can assess your current implementation and recommend a phased or combined approach based on what they find. 

Getting started 

The upgrade from Umbraco 13 to 17 is a genuine improvement for editorial teams, but it’s not a trivial project. Understanding what’s involved early — particularly the custom backoffice work and integration changes specific to your implementation — is the difference between a controlled transition and a rushed one. 

MSQ DX has been delivering Umbraco implementations for over fifteen years, including major version transitions across financial services, professional services, manufacturing, and hospitality. We offer a free upgrade complexity assessment: an hour spent examining your current setup and advising on realistic timelines and investment. 

Book an upgrade complexity assessment with MSQ DX

For the full picture on planning your Umbraco 13 migration strategically, our planning guide covers timelines, compliance considerations, and what to look for in an agency partner. 

Download the Umbraco 13 EOL Planning Guide