If you’re responsible for an Umbraco website, an upgrade can feel like a difficult thing to schedule. The site still works, there are campaigns to deliver, and nobody wants a booking or checkout problem halfway through a busy week.

But leaving it alone has a cost too. Small changes become harder, editors find workarounds and the support deadline gets closer.

AI can help with some of the time-consuming work involved in an upgrade, from reviewing older code to preparing tests. An AI-assisted Umbraco upgrade uses those tools within a development process led by people who understand the platform. They still decide what changes, check the results and take responsibility for the release.

The aim is straightforward: keep the parts your business relies on working, while making the website easier to maintain and improve.

Why AI-Assisted Upgrades Matter

An established Umbraco website can contain years of custom development, third-party packages and integrations. Documentation may cover the original build while missing the changes made since. Before upgrading, someone needs to establish how those pieces fit together.

AI can help developers work through that material and spot areas worth investigating. For example, it might flag several templates that appear to do the same job. A developer can then check whether they really are duplicates or whether one handles a detail that matters to a particular brand or region.

Performance, Security and Support Lifecycles

Support deadlines are a practical reason to plan ahead. Umbraco 13 reaches standard end of life on 14 December 2026. Umbraco explains that standard security updates end at that point, with extended support available separately for eligible projects. Check Umbraco’s official support guidance when setting your timetable.

A newer CMS also provides a foundation for improvements to performance and the editing experience. Those improvements still depend on your implementation. Slow queries, oversized images or an unreliable booking integration will not necessarily disappear when the version number changes.

At dotcraft, our Umbraco Gold Partner expertise informs how we look at those decisions. The version you move to matters, but so does the work needed to keep it supported over the next few years.

When to Upgrade Your Umbraco

Start planning while you still have time to choose a sensible delivery window. Waiting until support is about to expire can leave little room for package replacements, testing or changes to third-party systems.

Common Red Flags in Day-to-Day Use

An upgrade assessment is worth considering when:

• Your CMS or underlying software is approaching the end of its support period.
• Routine changes take longer because developers are working around older custom code.
• Editors struggle with publishing workflows or depend on development support for straightforward updates.
• Packages or integrations restrict the changes you can make.
• You want new AI or personalisation capabilities that your current setup cannot support cleanly.
  

Business plans matter too. An automotive group bringing several brand websites under shared management may need a more consistent content model. A hospitality operator may want to test booking journeys more frequently without risking its reservation system. These are different upgrade programmes, even if both start on the same Umbraco version.

What “AI-Assisted Upgrade” Actually Means

In practice, AI assistance is useful for specific tasks within the project. It might help make sense of unfamiliar code, suggest a refactor or draft tests for a developer to review. The scope should be clear before the work begins.

Using AI to Analyse Content and Templates

Useful tasks include reviewing template patterns, highlighting potentially duplicated components and suggesting how older code could be refactored. AI can also help draft dependency maps and test scenarios from the material supplied to it.

Each output is a starting point for review. A tool may miss a dependency stored in configuration or suggest an API that does not exist in the target version. Developers need to verify recommendations against the relevant Umbraco documentation and the working application.

The same care applies to what the tool can access. Agree which repositories and content it may process, use approved environments and keep credentials and unnecessary customer data out of prompts.

Who Makes the Decisions?

Decisions about replacing a package, restructuring content or changing an integration affect more than code. They can alter editorial responsibilities, customer journeys and the cost of future maintenance.

Someone needs to own those decisions and explain them in terms the business can act on. If replacing a package changes how editors publish content, for example, the editorial team needs to be involved before that choice is made.

A Practical Upgrade Path, Step by Step

The right route depends on where you’re starting. A relatively recent site with a few standard packages is a different job from an older build with custom editors and several business systems attached. The following stages help make the work manageable.

1. Discovery and Audit

Record the CMS version, hosting setup, packages, custom editors, content types and integrations. Identify the journeys the business depends on, including forms, bookings, checkout and sign-in.

Set a baseline for performance and existing defects. Otherwise, it becomes difficult to tell whether an issue was introduced during the upgrade or was already present.

2. Agree the Upgrade Plan

Choose a supported target version after checking compatibility and the expected maintenance window. Establish which components can be upgraded, which need replacing and which should be rebuilt.

Older implementations may need a migration into a new solution. Even between more recent versions, backoffice extensions and packages can require substantial work. Umbraco’s guidance on moving from version 13 to 17 describes different routes, reinforcing the need to assess the existing build first.

3. Test the Upgrade Before It Reaches Customers

Rehearse the upgrade in an isolated environment using an appropriate copy of the site. Review AI-assisted code changes through the same process as other development work.

Automated checks should cover important application behaviour and integrations. Manual testing should include editorial workflows, accessibility and the customer journeys that matter commercially. Confirm that content, media, redirects and tracking have survived the transition as intended.

4. Prepare the Release and Recovery Plan

Agree the release window, sign-off responsibilities and any content freeze. Where editors need to keep working, define how changes made during the migration will be reconciled.

Take backups and rehearse recovery. Rolling back application code alone may be insufficient after database changes. The plan needs to explain how data will be restored and how any new transactions will be protected or reconciled.

5. Monitor After Go-Live

Check error logs, response times, integrations and critical journeys immediately after release. Give editors a clear route to report problems.

Our website support and maintenance services cover ongoing monitoring, patching and platform improvements, with support arrangements agreed around the needs of the business.

Risk Management for Complex Umbraco Estates

Some of the easiest things to miss sit outside the page templates. A form may send enquiries into a CRM. A scheduled job may refresh vehicle stock overnight. A booking service may depend on a setting that never made it into the documentation. Each needs an owner and a test.

For a group of websites, separate shared components from local differences. A common template can reduce repeated work, but each brand may still have its own permissions, languages, tracking and integrations. A pilot site is useful only if it represents the complexity of the wider estate.

Commerce and High-Traffic Sites

A checkout can look perfectly normal while an order fails to reach the fulfilment system. Test the whole journey, including pricing, promotions, payments and notifications. Then test what happens when a payment fails or an external service is slow to respond.

For high-traffic sites, test with realistic volumes and review caching and background processing. A migration that performs well with a small content sample may behave differently with the full catalogue or media library.

AI can help suggest edge cases and review logs. Release decisions should rest on observed results, agreed acceptance criteria and a recovery plan the team has tested.

Preparing for AI-Driven Experiences After the Upgrade

Using AI to assist an upgrade and introducing AI features into the website are separate decisions. You can use development tools to review an older codebase without installing AI features in that CMS.

Umbraco.AI provides an AI integration layer for Umbraco. Umbraco’s Developer MCP server connects AI tools to CMS capabilities through the Model Context Protocol. Each has its own version and configuration requirements, so compatibility needs checking against the specific release you intend to use.

An upgrade alone does not enable these capabilities. Allow for implementation, permissions, provider costs and review of what an AI tool is allowed to read or change.

Measuring Impact with Engage and Analytics

Once the upgraded site has settled in, pick one useful improvement. You might help editors prepare a first draft more quickly, or test whether a clearer landing page brings more completed enquiries. Start with a question you can answer from the results.

Umbraco Engage supports analytics, personalisation and A/B testing, subject to its compatibility, licensing and configuration requirements. Its A/B testing documentation explains how tests can be configured around a defined objective.

Establish the baseline before starting an experiment. Measure the outcome that matters, such as completed bookings or time spent preparing a page, and retain human review where content or decisions require it. Personalisation and A/B testing do not need to involve generative AI to be useful.

Work With Dotcraft on Your Upgrade

You don’t need a complete technical brief before starting the conversation. Knowing what is frustrating your team, what the business has planned and when the site is busiest gives us a useful starting point. From there, the assessment can establish what to keep and what needs work.

Our development and technology services bring platform development and integration work together. Our strategy and research services help connect those technical decisions to customer journeys and business priorities.

Outcomes to Agree Before Work Begins

For a multi-brand automotive group, success might mean a consistent upgrade approach with fewer separate custom components to maintain. For a hospitality operator, it might mean preserving booking continuity while making content changes easier to test and release.

Set those expectations early. If easier publishing is part of the reason for upgrading, ask editors to try the new workflow before launch. If booking continuity is the priority, make the booking journey central to testing and release planning.

Planning an Umbraco upgrade? Book a discovery conversation with dotcraft to review your platform, dependencies and next steps.