An Umbraco upgrade for an enterprise publishing platform, involving legacy content editors, linked content, member accounts and a new application built for Umbraco 13.
Your website may be running well on an older Umbraco version. But what happens when you need newer CMS features, improved editorial tools or an upgrade to a supported .NET release?
For a company in the energy, publishing and B2B events sector, this question led to an Umbraco upgrade from version 8 to version 13.
The existing platform supported an extensive publishing operation. Its content used DTGE and Nested Content, with relationships between content nodes and an established member database.
Phases was entrusted with upgrading the platform while protecting the content and functionality the company had developed over the years.
The engineering team used a staged database migration and built a new Umbraco application for the destination version.
Today, we apply that experience to websites running Umbraco 7, 8, 10, 13 and other earlier releases, helping companies plan upgrades to supported versions, including Umbraco 17 LTS and Umbraco 18 STS.
The Umbraco upgrade project
| Project detail | Description |
|---|---|
| Industry | Energy, publishing and B2B events |
| Original version | Umbraco 8 |
| Upgraded version | Umbraco 13 |
| Migration approach | Staged database migration |
| Application | New Umbraco application |
| Content | DTGE and Nested Content |
| Additional requirements | Content node relationships, members and credentials |
The company's established publishing platform had been developed using Umbraco features available at the time.
During the upgrade, the challenge was to transfer that information into the newer application while protecting the editorial content and data relationships already in use.
How Phases handled the Umbraco 8 to 13 upgrade
Database migration through the required versions
Umbraco 8 and Umbraco 13 belong to different generations of the CMS.
A database migration needs to follow the supported intermediate steps, including the migrations introduced in Umbraco 10.
For this project, the team upgraded the database in stages while creating a new Umbraco application for version 13.
The approach allowed developers to work through the necessary database changes and prepare the application for the destination release.
Migrating DTGE and Nested Content
An important part of the project involved content stored in DTGE and Nested Content.
Both had served the publishing platform over several years. Their data needed special attention because the newer Umbraco generation uses different content editing capabilities.
Our developers examined the existing content structures and handled their migration as part of the database and application upgrade.
This work was essential to preserving the company's published information and preparing it for the upgraded CMS.
Preserving relationships between content nodes
Many publishing websites rely on relationships between articles, pages and related content.
Those references need attention during migration, especially where database records or content structures change.
The project included handling relationships between Umbraco nodes so the upgraded application could continue using the associated content.
Migrating member accounts and credentials
The website also had an established member database.
Member records and credentials formed part of the migration scope, alongside the content and application changes.
For organisations with registered users, this can be a significant part of an upgrade. Authentication compatibility, password handling and member functionality all need testing against the destination version.
Building the new Umbraco application
The database was only part of the upgrade.
Umbraco 8 used the older ASP.NET framework, while later versions use ASP.NET Core.
That change affects templates, custom code and package compatibility.
For this project, Phases built a new Umbraco application and migrated the required information into it.
The company received an upgraded CMS foundation while retaining the valuable information developed through its existing publishing operation.
The result: Umbraco 8 upgraded to Umbraco 13
The company successfully upgraded from Umbraco 8 to Umbraco 13.
The completed work included the staged database migration, handling of DTGE and Nested Content, content node relationships, member information and development of the new Umbraco application.
The project demonstrates how an established enterprise website can progress through several Umbraco generations while retaining its existing content and data.
For Phases, the same engineering experience informs how we approach upgrades from earlier Umbraco releases today.
Running Umbraco 7, 8, 10 or 13? Your website can be upgraded.
Your website may contain years of articles, landing pages, media, custom features, member records and integrations.
All of that deserves careful treatment during an Umbraco upgrade.
Even if your website is running a much older release, Phases can assess the existing application and plan its migration to a supported Umbraco version.
The route depends on the starting version.
For example, an Umbraco 8 website can follow staged database migrations through Umbraco 10 and later releases. Templates, custom code and incompatible packages need separate development work.
An Umbraco 13 website has a different upgrade path because it already uses the modern .NET platform.
Our Umbraco upgrade services cover both situations, from the initial technical assessment through migration, testing and deployment.
Can an Umbraco upgrade be completed without losing content or data?
Data preservation is a central part of our upgrade planning.
Before production deployment, the engineering team assesses content structures, database records, media, members and integrations.
Migration rehearsals and validation help identify issues before the upgraded website goes into production.
The work can include database backups, content comparisons, member authentication tests, URL checks and verification of linked information.
That preparation allows us to establish how the existing information will be preserved and how the migrated data will be verified.
Can the website continue operating during the upgrade?
For organisations running active publishing platforms, website availability is a priority.
We can prepare and test the upgraded application in a separate environment while the existing website continues serving visitors.
The production release is then planned around the website's hosting, database activity, integrations and deployment requirements.
Where the technical environment supports it, a zero downtime deployment can be planned. Otherwise, the release plan should specify the expected interruption, rollback procedure and validation steps in advance.
Why upgrade to Umbraco 17 LTS or Umbraco 18 STS?
If your website is using an older Umbraco release, upgrading provides access to newer platform capabilities and ongoing security updates.
The choice between Umbraco 17 and 18 depends on your requirements.
Umbraco 17 LTS: A longer support window
Umbraco 17 runs on .NET 10 LTS and is supported until 27 November 2028.
It includes newer CMS capabilities and backoffice improvements, including support for load-balanced backoffice environments.
For enterprise websites, the longer support period provides time to plan future product development and subsequent LTS upgrades.
Umbraco 18 STS: Library and Elements
Umbraco 18 was released on 25 June 2026, with support scheduled until 25 June 2027.
Its main addition is Library and Elements.
Editors can create reusable content items in the Library and select those items where needed through the Element Picker.
For websites that need this feature now, Umbraco 18 is an option worth evaluating.
Full integration of reusable Elements into Block Editors is planned for Umbraco 19, scheduled for December 2026.
What about the next LTS release?
Umbraco 21 is currently scheduled for 9 December 2027.
Umbraco 17 receives support until November 2028, giving organisations time to evaluate the next LTS release before their existing support period expires.
For websites already running unsupported releases, upgrading now can provide access to current security updates and newer product capabilities while allowing future migrations to follow a planned schedule.
Preparing your Umbraco website for AI capabilities
Umbraco is developing AI features for its newer CMS releases, including editor assistance and integrations using the Model Context Protocol (MCP).
These capabilities introduce opportunities to improve content workflows, assist editors and allow approved AI tools to interact with Umbraco.
Upgrading to a supported CMS version gives your company a technical foundation for evaluating these features.
The next step is deciding which AI applications would benefit your business and how they should access content, data and editorial workflows.
Phases can support this work through Umbraco development, including custom functionality, integrations and future CMS improvements.
How do you know what your Umbraco upgrade will involve?
Before recommending a destination version, our developers examine the existing application.
The review covers your Umbraco and .NET versions, database, content editors, packages, custom code, integrations, member functionality, hosting and deployment process.
From there, we can identify which components can be migrated, which need changes and which require rebuilding.
You receive a proposed upgrade approach based on your website rather than a generic version recommendation.
Planning an Umbraco upgrade? Talk to our developers.
Your website has valuable content, established workflows and functionality that people depend on.
Phases has worked with Umbraco since 2011. Our engineering team handles upgrades, migrations and enterprise application development, including projects involving older CMS generations and complex content structures.
Whether you are running Umbraco 7, 8, 10, 13 or another earlier release, we can examine the existing website and recommend a route to Umbraco 17 LTS, Umbraco 18 STS or another suitable supported release.
Request an Umbraco upgrade assessment
Share your current version and website URL. A senior Umbraco engineer can review the migration requirements, data preservation approach and production deployment options with you.
