Umbraco Migration Paths: v8 to v14 to v17

Upgrading to Umbraco v17 LTS depends heavily on your starting version. This guide covers the three most common migration scenarios, with effort estimates and step-by-step guidance.

Scenario 1: v13 to v17 LTS (Straightforward)

Effort: Low-Medium Breaking Changes: Property editors must be rewritten (Web Components) Database: Compatible (schema changes minimal)

Steps:

1. Audit custom AngularJS property editors and dashboards
2. Rewrite as Web Components (budget 4-8 hours per simple property editor)
3. Test in v14/v17 environment
4. Upgrade database schema (automatic via Umbraco upgrade process)
5. Deploy and verify

Recommendation: Upgrade to v17 LTS (skip v14 unless already on it)

Scenario 2: v10 to v17 LTS (Medium Effort)

Effort: Medium Breaking Changes: Property editors + some API changes Database: Compatible with migration

Steps:

1. Review Umbraco v10 to v13 breaking changes
2. Migrate property editors to Web Components
3. Update notification handlers to v13+ patterns
4. Test thoroughly (v10 to v13 to v17 path recommended)

Recommendation: Upgrade to v17 LTS

Scenario 3: v8 to v17 LTS (Rebuild Recommended)

Effort: High (rebuild often faster than upgrade) Breaking Changes: Massive

Community Consensus: Rebuild, don’t upgrade

Why rebuild instead of upgrade?

1. Forms migration failure: Umbraco Forms v8 to v10+ schema incompatibilities require manual recreation
2. Nested Content to Block List/Block Grid: Content structure changes require data migration
3. AngularJS to Web Components: All custom property editors rewritten
4. Two painful migrations vs. one: v8 to v13 to v14 = two breaking changes; v8 to v17 direct = still one painful migration (but still rebuild)

Rebuild Strategy

1. Content export: Export content from v8 (custom scripts or migration tools)
2. Document Types: Recreate in v17 (schema changes between v8 and v17)
3. Templates: Port Razor views (v8 MVC patterns to v17 patterns)
4. Custom code: Rewrite AngularJS property editors as Web Components
5. Forms: Manually recreate Umbraco Forms (no automated migration)
6. Testing: Full regression testing

Timeline Estimates

• Small site (10-20 pages): 2-4 weeks
• Medium site (50-100 pages): 6-12 weeks
• Large site (500+ pages): 3-6 months

Real-World Context

Many v8 sites stayed on v8 LTS until support ended (September 2025). Organizations now face: stay on unsupported v8 (security risk) or rebuild on v17.