When to Choose Umbraco v14/v17 (and When Not To)

Umbraco v14+ (and especially v17 LTS) is a strong platform for certain organizations and a poor fit for others. This page provides a decision framework, getting started guidance, and answers to frequently asked questions.

Choose Umbraco v14/v17 When

• Starting a new Umbraco project in 2026+ — v17 LTS provides stable foundation
• Want modern, maintainable backoffice — Web Components replace legacy AngularJS
• Need headless capabilities — Content Delivery API + Management API
• Prefer open-source with active community — free core, optional Cloud/Heartcore tiers
• Budget-conscious — free self-hosted option (only pay for hosting)
• .NET developer team — C#, .NET 10, modern .NET patterns

Don’t Choose Umbraco v14/v17 When

• Have extensive custom AngularJS property editors — migration cost high (4-8 hours per editor minimum)
• Depend on community packages not yet v14-compatible — check package compatibility first
• On v8 and can’t justify rebuild effort — v8 to v17 requires rebuild
• Need enterprise personalization out-of-the-box — Umbraco lacks built-in personalization (requires external integration with Sitecore Personalize, Optimizely, or custom solutions)

Real-World Context

• Many v8 sites stayed on v8 LTS until September 2025 end-of-support — now face security risk
• v13 to v17 migrations happening actively in 2026 (v14 users upgrading to LTS)
• v10 sites deciding: upgrade to v17 or migrate to competitor platform?

Getting Started with Umbraco v14/v17

Installation

Install Umbraco v17 LTS via .NET CLI:

dotnet new umbraco --name MyUmbracoProject
cd MyUmbracoProject
dotnet run

Navigate to http://localhost:5000/umbraco to complete setup.

Hosting Options

Option	When to Use
Self-Hosted	Full control, budget-conscious, have DevOps capability
Umbraco Cloud	Managed hosting, environment promotion, reduced DevOps
Azure	Enterprise Azure commitment, integrate with Azure services
AWS	Enterprise AWS commitment, multi-region requirements

Learning Resources

• Umbraco Documentation: docs.umbraco.com
• Umbraco Community Discord: Active community support
• Codegarden Conference: Annual Umbraco conference (Europe)
• Umbraco Official Training: Certification programs available

Next Steps

• If on v13: Plan v13 to v17 migration (audit AngularJS property editors)
• If on v8: Plan rebuild on v17 LTS
• If starting new: Choose v17 LTS, plan content architecture using Block List/Block Grid

Frequently Asked Questions

Q: Should I upgrade to v14 or wait for v17 LTS?

A: Use v17 LTS (released January 2026). v14 introduced Bellissima, but v17 is the mature, LTS-supported version with 3-year support through 2028.

Q: Can I upgrade directly from v8 to v17?

A: Technically yes, but community consensus is rebuild. v8 to v17 has massive breaking changes:

• Umbraco Forms schema incompatible (manual recreation required)
• Nested Content to Block List/Block Grid (data migration required)
• AngularJS property editors to Web Components (full rewrite)

Rebuilding is often faster and produces cleaner architecture than multi-step migration.

Q: Are my custom AngularJS property editors compatible with v14+?

A: No. All custom property editors must be rewritten as Web Components. Budget 4-8 hours per simple property editor, 16-24 hours for complex editors with state management.

Q: What’s the difference between Umbraco CMS, Umbraco Cloud, and Umbraco Heartcore?

A:

• CMS: Open-source core (free) — self-host on any infrastructure
• Cloud: Hosted CMS with Deploy (PaaS, paid) — managed hosting + environment promotion
• Heartcore: Headless-only SaaS (separate product) — API-first, no traditional backoffice

Q: Is Bellissima just a UI refresh?

A: No. Bellissima is a complete rewrite of the backoffice using Web Components. It’s the biggest breaking change in Umbraco history, requiring all custom AngularJS code to be rewritten.