Nobody wakes up excited about a CMS upgrade.
Well, almost nobody. There are probably a few of us knocking about who do, but we’re aware that makes us slightly odd. For most organisations, an Umbraco upgrade sits somewhere between “important but not urgent” and “please don’t make me think about this until absolutely necessary”.
Fair enough.
But if your website is currently running on Umbraco 13, it is worth starting the conversation now about what comes next. Umbraco 13 Long Term Support ends on 14 December 2026, so there is still time to plan properly, but not enough time to ignore it indefinitely. This is not about panic-upgrading. It is about making sure the move happens in a controlled, well-tested and sensible way.
It’s because Umbraco 13 is a Long Term Support version, and Long Term Support does eventually come to an end. When it does, your site does not suddenly stop working, but the risk profile changes. Security fixes, compatibility, hosting support, package support and future development all become harder to manage.
That is why we are encouraging clients to start thinking about the move from Umbraco 13 to Umbraco 17 before the end-of-support date creeps up like a tax deadline in a false moustache.
First things first: what is Umbraco 17?
Umbraco 17 is expected to be the next major Long Term Support version after Umbraco 13.
In practical terms, that matters because many organisations prefer to move from one LTS version to another. It gives you a longer runway, a more stable support window, and fewer “here we go again” moments than chasing every Standard Term Support release in between.
For clients on Umbraco 13, the move to Umbraco 17 is likely to be the natural next step.
It is not just a routine version bump, though. The Umbraco platform has changed significantly since version 13, especially around the backoffice editing experience. That means the upgrade deserves proper planning, testing and review rather than being treated as a quick patch on a Friday afternoon. Which, for the record, is where good intentions go to be eaten by gremlins.
Why upgrading is a good idea
There are several reasons we recommend planning the move to Umbraco 17, and most of them are pleasantly sensible rather than dramatic.
1. You stay inside the supported Umbraco lifecycle
Supported software is boring in the best possible way.
When your website is running on a supported version of Umbraco, you benefit from ongoing fixes, security updates and compatibility work. That does not mean nothing can ever go wrong, because websites enjoy finding creative new ways to misbehave, but it does mean you are operating within a healthier, safer environment.
Once a version reaches end of support, the responsibility shifts. Fixes become harder. Workarounds become more common. The answer to “can we just update that package?” becomes “maybe, but let’s open the bonnet and have a look first”.
That is rarely where anyone wants to be.
2. You reduce security and compliance risk
An unsupported CMS does not automatically mean an insecure website. But it does mean you are carrying more risk.
For many organisations, especially those with governance, procurement, insurance, accessibility or data protection requirements, running unsupported core software can become difficult to justify. Even if the site appears to be working perfectly, it may raise awkward questions during audits or supplier reviews.
The problem is not always technical. Sometimes the problem is having to explain why a business-critical digital platform is relying on software that no longer receives the same level of support.
And nobody wants to be the person on that call.
3. You avoid the expensive panic upgrade
Leaving upgrades too late usually makes them more painful.
When there is plenty of time, we can assess the site properly, check packages and integrations, review custom code, plan testing, involve your content team, and schedule the work sensibly around your organisation.
When there is no time, everything gets squeezed. Decisions become rushed. Testing windows shrink. Internal teams get dragged in at awkward moments. The whole thing becomes a bit more “controlled slide down a muddy hill” than we would like.
Starting early does not mean upgrading immediately. It means giving yourself options.
And options are lovely. Almost as lovely as a website deployment that behaves itself first time.
4. You can improve the site while you are there
An upgrade is not automatically a redesign, rebuild or big shiny transformation project. Sometimes the right thing to do is a clean technical upgrade with as little disruption as possible.
But it is still a useful moment to ask a few sensible questions:
- Is the content editing experience still working for your team?
- Are there old integrations that need attention?
- Are any packages no longer actively maintained?
- Is the site performing as well as it should?
- Are there accessibility, analytics or SEO improvements worth making while the bonnet is open?
The best upgrades are not just about keeping the lights on. They are a chance to tidy the wiring, remove the mystery switches, and make the platform easier to live with for the next few years.
What happens if you do not upgrade?
This is where we should be candid.
Your Umbraco 13 site will not suddenly disappear the day support ends. The internet does not have a big red “unsupported CMS” button that gets pressed at midnight.
However, over time, things become more difficult.
You may find that:
- Security fixes are no longer available for your version.
- Hosting environments move on and become less compatible.
- Third-party packages stop supporting older versions.
- New development takes longer because the platform is behind.
- Integrations become trickier to maintain.
Technical debt increases. - Future upgrades become larger and more expensive.
It is a bit like putting off servicing a car. You can keep driving it for a while. It may even feel fine. But the longer you leave it, the more likely it is that a simple service turns into a very expensive noise.
That is the bit we are trying to help clients avoid.
What does the upgrade from Umbraco 13 to 17 involve?
The honest answer is: it depends on your site.
A straightforward brochure site with a small number of packages and limited custom functionality will be a very different project from a large, integrated platform with custom workflows, APIs, membership features, multilingual content and years of accumulated “can we just add this quickly?” decisions.
Broadly, though, an Umbraco 13 to 17 upgrade usually involves a few key stages.
1. Discovery and technical review
Before anyone starts upgrading anything, we need to understand what is there.
That means reviewing the current Umbraco setup, hosting environment, custom code, installed packages, integrations, content models, editor workflows and any known pain points.
This stage is where we separate the simple bits from the spicy bits.
It also helps answer the big practical questions: how complex is the upgrade, what might need replacing, what needs testing, and where are the risks?
2. Upgrade planning
Once we understand the site, we can plan the route.
This includes deciding whether the upgrade should be a clean technical migration, a broader improvement project, or something in between. We also look at timing, content freezes, testing responsibilities, launch planning and rollback options.
This is not glamorous work. No one is putting “excellent dependency review” on a billboard. But it is the difference between a calm upgrade and a project that starts making whale noises halfway through.
3. Development and migration
This is where the actual upgrade work happens.
Depending on the site, this may include updating the Umbraco version, adapting custom code, replacing unsupported packages, updating templates, checking integrations, reviewing configuration, and making sure the backoffice behaves as expected.
Because Umbraco has evolved since version 13, some areas may need more attention than others. In particular, editor experience and package compatibility should be looked at carefully.
4. Testing
Testing is where we try very hard to be boring.
We check that pages render correctly, forms submit, integrations work, redirects behave, media loads, permissions make sense, content can be edited, and the backoffice does what editors expect.
For more complex sites, testing may involve several rounds and input from different teams. That is normal. Your website is not just a collection of templates; it is part of how your organisation works.
5. Launch and support
Once everything has been built, tested and approved, we plan the release.
A good launch plan covers deployment, final checks, monitoring, redirects, analytics, search visibility, and what happens if something unexpected appears. Because something unexpected often does appear. Usually wearing a tiny hat and pretending it was there all along.
After launch, we keep an eye on things and help your team settle into the updated platform.
Will the backoffice change?
Yes, there may be changes to the editing experience.
Umbraco has been evolving its backoffice in recent versions, so clients moving from Umbraco 13 to Umbraco 17 should expect some differences in how editors interact with the CMS.
That does not mean everything will feel alien. Umbraco is still Umbraco. But it does mean your content team should be involved early enough to review, test and get comfortable with any changes.
This is one of the biggest reasons not to leave the upgrade too late. Technical changes are one thing. People changes are another. A calm editor is worth protecting.
Is this a rebuild?
Not necessarily.
An upgrade is not automatically a rebuild. In many cases, the goal is to preserve the existing design, content structure and functionality while moving the site onto a newer, supported version of Umbraco.
However, some sites will benefit from more than a straight upgrade.
For example, if your site has ageing templates, awkward editing workflows, old packages, performance issues or integrations that need attention, it may be more sensible to deal with those during the upgrade rather than carry them forward.
That does not mean turning a sensible upgrade into a monster project with seventeen workstreams and a logo refresh nobody asked for. It means being honest about what is worth fixing while you are already doing the work.
When should you start planning?
With Umbraco 13 LTS ending on 14 December 2026, we recommend starting upgrade planning well ahead of that date. The upgrade does not need to happen immediately, but discovery, scoping, scheduling, testing and sign-off all need time - especially for sites with custom functionality or integrations.
You do not need to have every answer now, but you should know:
- When your current Umbraco version reaches end of support.
- How complex your current site is.
- Which packages and integrations may need attention.
- Whether your team expects any design, content or functionality changes.
- How the upgrade fits around wider organisational priorities.
For many clients, the first step is simply a technical review and recommendation. That gives you a clearer view of the size, shape and timing of the upgrade before you commit to the work.
Our recommendation
If your site is on Umbraco 13, we recommend starting the conversation about Umbraco 17 now.
Not because you need to panic. Quite the opposite. We want to avoid panic.
A planned upgrade gives you more control, better visibility of cost, more time for testing, and a much lower chance of being forced into rushed decisions later. It also gives you the opportunity to improve the parts of your website that have become a bit creaky over time.
The key thing is not to wait until support is nearly over and everyone suddenly realises the website is more business-critical than the meeting notes suggested.
We have seen that film. The sequel is never better.
What to do next
If you are a Gecko client on Umbraco 13, we can help you understand what the move to Umbraco 17 is likely to involve for your specific site.
That usually starts with a review of your current setup, including packages, integrations, hosting, custom code and editorial workflows. From there, we can tell you whether your upgrade looks straightforward, mildly fiddly, or “let’s put the kettle on and talk properly”.
Either way, the earlier we look, the better the options.
Because the goal is simple: keep your site secure, supported, useful and ready for whatever comes next. No drama. No panic. No mystery spreadsheet called “urgent upgrade final final v7”.
Just a sensible plan, made in good time.
Get in touch with us to discuss your upgrade today.
