Umbraco 18 Upgrade Checklist for Australian Businesses
A practical Umbraco 18 upgrade checklist covering release status, STS timing, package checks, staging QA, SEO protection, editor testing, and go-live planning for Australian business websites.
Umbraco 18 is available, but an upgrade decision should be based on evidence rather than version numbers alone. The official Umbraco releases page lists Umbraco 18.0.2 as the latest Umbraco 18 release, published on 7 July 2026, and lists Umbraco 17 LTS 17.5.3 as the recommended release for most users on the same date.
That distinction matters for Australian businesses planning CMS work in the second half of 2026. Umbraco 18 gives teams access to the newest major line, including platform cleanup, Global Elements work, Delivery API and OpenAPI changes, and backoffice improvements introduced in 18.0.0. Umbraco 17 remains the current LTS release and has a longer support runway.
This checklist is for teams that need a practical decision process: what to check, what to test, what to protect, and when to wait. For a broader feature overview, read our Umbraco 18 new features and migration guide. For implementation support, see our Umbraco website development services.
The Upgrade Decision
Umbraco 18 can be the right target, but only when the compatibility and support trade-offs are clear.
Use 18 for new builds
Consider Umbraco 18 when required packages support it, the build is already going through full QA, and STS timing is acceptable.
Test 18 for existing sites
Run a staging upgrade before changing production. Use real content, integrations, users, redirects, forms, media, and editor workflows.
Stay on 17 for stability
Umbraco 17 remains the LTS choice. It is usually safer when long support, lower change risk, and package maturity matter most.
Check packages first
Forms, Deploy, search, SEO, ecommerce, workflow, property editors, and custom backoffice packages can decide the upgrade path.
Protect SEO early
Before go-live, crawl URLs, validate redirects, metadata, canonicals, structured data, sitemaps, analytics, and conversion tracking.
Decide from evidence
The right result may be upgrade now, stage and wait, remain on LTS, or rebuild with a cleaner content model.
What Has Changed Since Umbraco 18.0.0?
Umbraco 18.0.0 was released on 25 June 2026. The release overview lists 177 bug fixes and feature additions, four notable features, and 36 breaking changes. The official releases page now lists Umbraco 18.0.2 as the latest 18 release, published on 7 July 2026. It also shows 18.1.0 as an upcoming release targeted for 6 August 2026.
The practical lesson is simple: if your team is evaluating Umbraco 18, test against the latest 18.0.x patch rather than the initial 18.0.0 release. Also avoid building a project plan that assumes 18.1.0 behaviour until that version has actually been released and tested in your environment.
| Item | Status checked | Planning meaning |
|---|---|---|
| Umbraco 18.0.0 | Released 25 June 2026 | Major release baseline with notable features and breaking changes. |
| Umbraco 18.0.2 | Latest 18 release on the official releases page checked 26 July 2026 | Use this patch line for assessment instead of testing only 18.0.0. |
| Umbraco 18.1.0 | Upcoming target release date of 6 August 2026 | Track it, but do not rely on it for production planning before release. |
| Umbraco 17 LTS | Recommended for most users on the official releases page | Use as the conservative production benchmark when long support matters. |
What to Check Before Choosing Umbraco 18
A useful Umbraco 18 assessment covers the CMS, the frontend, the editor experience, and the operational parts around launch.
Support window
Confirm that STS timing is acceptable. Umbraco lists version 18 as STS, with security phase from 25 March 2027 and EOL on 25 June 2027.
Package support
Check every package, including Forms, Deploy, search, SEO tools, ecommerce, workflow, custom dashboards, and paid add-ons.
Custom code
Review controllers, APIs, backoffice extensions, property editors, OpenAPI clients, background jobs, authentication, and integrations.
Content model
Assess blocks, reusable content, Global Elements opportunities, rich text, media, variants, permissions, tags, and redirects.
Editor workflow
Ask real editors to test creating, editing, previewing, publishing, rollback, multilingual work, media upload, and approval paths.
Go-live safety
Prepare backups, rollback, deployment checks, monitoring, logs, uptime alerts, analytics validation, and post-launch support coverage.
Step 1: Confirm the Business Reason
Before any technical upgrade work begins, write down why Umbraco 18 matters for this specific website. Good reasons include a planned rebuild, an integration-heavy architecture that benefits from the newer API work, a reusable content model that can use Global Elements, or a new project where the team is comfortable with STS timing.
Weak reasons include simply wanting the latest version, assuming a major release is a routine patch, or trying to solve unrelated content governance problems with a platform upgrade. A CMS upgrade can create the opportunity to improve content models and workflows, but it does not automatically fix ownership, approval, SEO, or editor training issues.
Step 2: Decide Whether 17 LTS or 18 Is the Target
Umbraco's lifecycle page lists Umbraco 18 as STS and Umbraco 17 as LTS. It also states that the most recent LTS is Umbraco 17, supporting .NET 10 LTS. For organisations that need the longest support window and the most conservative production target, Umbraco 17 LTS remains the default comparison point.
Umbraco 18 can still be the right target. It is especially reasonable for new builds, rebuilds, staged modernisation projects, and teams that need the newest major line. The point is not that 18 should be avoided. The point is that the support model should be understood before budgets, timelines, and launch commitments are made.
Step 3: Create a Real Compatibility Inventory
A useful inventory includes the current Umbraco version, .NET runtime, hosting model, database, NuGet packages, backoffice packages, Forms, Deploy, search, ecommerce, authentication, member areas, custom property editors, dashboards, scheduled jobs, APIs, frontend framework, CI/CD, DNS, CDN, analytics, consent tools, and business-critical integrations.
Do not rely only on a developer saying the site is simple. Many older CMS builds contain small customisations that become important during a major version upgrade: data type assumptions, undocumented property editors, hard-coded redirects, custom Examine indexes, form handlers, scheduled imports, old packages, and integrations that only fail under production-like data.
Step 4: Run a Staging Upgrade with Real Content
Umbraco's upgrade documentation recommends using the guide that fits your upgrade situation and reviewing upgrade topics before proceeding. For a business website, the practical version of that advice is to create a staging copy that is close enough to production to expose real problems.
Use a realistic database, media library, user permissions, redirects, forms, members, content variants, integrations, and frontend deployment pipeline. A clean install can prove that Umbraco 18 starts. It cannot prove that your website, editors, integrations, and launch process are ready.
Step 5: Test the Areas Most Likely to Break
| Area | Test examples | Why it matters |
|---|---|---|
| Backoffice extensions | Dashboards, manifests, custom sections, property editors, UI Library assumptions, permissions, localisation. | Umbraco 18 includes breaking changes and backoffice platform changes that can affect custom admin experiences. |
| APIs and integrations | Delivery API usage, OpenAPI clients, custom controllers, webhooks, CRM, ERP, search, ecommerce, payment, and forms integrations. | API contract changes can break external systems even when the CMS UI appears healthy. |
| Content and media | Blocks, rich text, media crops, reusable content, Global Elements, variants, tags, redirects, and publishing workflows. | Editors need confidence that day-to-day publishing works after the upgrade. |
| Frontend behaviour | Navigation, templates, search pages, forms, scripts, tracking, caching, accessibility, and mobile rendering. | Customers experience the frontend, not the CMS version number. |
| Operations | Deployment scripts, backups, rollback, logs, cache invalidation, build agents, hosting runtime, and monitoring. | Production safety depends on being able to deploy, observe, and recover the platform. |
Step 6: Protect SEO Before Launch
SEO risk is one of the easiest upgrade risks to underestimate. Before go-live, crawl the existing website and export important URLs, titles, descriptions, canonicals, headings, structured data, image references, XML sitemaps, redirects, high-traffic pages, conversion pages, and analytics events.
After the staging upgrade, crawl again and compare. Look for missing pages, changed slugs, broken redirects, duplicate metadata, missing schema, noindex mistakes, canonical changes, lost form events, consent tag issues, and differences in rendered content. If the upgrade includes a frontend rebuild, add accessibility and Core Web Vitals checks to the same go-live plan.
Step 7: Make a Clear Go, Wait, or Stay-on-LTS Decision
At the end of the assessment, the answer should be written down in plain business language. A good decision note says whether to upgrade to Umbraco 18 now, keep testing in staging, stay on Umbraco 17 LTS, or run a larger rebuild/migration discovery first. It should also list known blockers, accepted risks, rollback steps, and the next review date.
For many Australian businesses, the sensible plan will be to evaluate Umbraco 18 in staging while keeping production on Umbraco 17 LTS until packages, editors, integrations, and operational checks are all clear. For new builds and rebuilds, Umbraco 18 can be a strong candidate once the team accepts the STS support window and proves the implementation with real QA.
Umbraco 18 Upgrade Checklist
- Confirm current state. Record current Umbraco version, .NET version, hosting, packages, content volume, integrations, custom code, frontend stack, and support constraints.
- Choose the target deliberately. Compare Umbraco 17 LTS and Umbraco 18 against support window, project timing, package readiness, and business appetite for change.
- Check official release status. Use the latest 18.0.x patch listed by Umbraco and track upcoming releases without assuming unreleased behaviour.
- Audit packages and custom extensions. Confirm compatibility before committing to production migration.
- Create a production-like staging copy. Include real content, media, forms, permissions, redirects, members, analytics, and integrations.
- Run editor workflow testing. Include normal publishing work, edge cases, media, reusable content, variants, rollback, and approvals.
- Run technical regression testing. Include APIs, OpenAPI clients, controllers, scheduled jobs, search, forms, authentication, deployments, logs, and cache behaviour.
- Protect SEO and analytics. Crawl before and after, compare URLs, redirects, metadata, schema, sitemaps, tracking, consent, and conversion events.
- Plan rollback and support. Define backup, restore, deployment freeze, monitoring, support hours, and incident ownership.
- Document the final decision. Choose upgrade now, wait, stay on LTS, or rebuild based on evidence.
Sources Checked
Umbraco 18 Upgrade FAQs
Short answers for teams deciding whether Umbraco 18 is a production upgrade, a staging test, or a later roadmap item.
Plan Your Umbraco 18 Assessment
VaniTech can review your Umbraco version, packages, custom code, integrations, editor workflows, SEO risk, and hosting setup before you commit to an Umbraco 18 upgrade.