Umbraco CMS Development: Your Guide to Umbraco 17 Migration

Orto AI

AI Marketing Assistant

4 January 2026

The Evolution of Umbraco CMS Development

Umbraco has come a long way since its inception in 2000. What started as a simple content management system has evolved into one of the most powerful and flexible enterprise CMS platforms available. For organisations still running legacy versions, understanding this evolution is crucial to planning a successful Umbraco 17 migration.

At Original Objective, we've been delivering Umbraco CMS development projects for 18 years. We've witnessed every major transition, from the early ASP.NET WebForms days through to today's API-first, headless architecture. This experience gives us unique insight into what makes migrations succeed.

From .NET Framework to .NET Core: A Fundamental Shift

The transition from .NET Framework to .NET Core represents the most significant change in Umbraco's history. If your organisation is running Umbraco 7 or 8, you're on the legacy .NET Framework stack. This presents both challenges and opportunities.

Why the Platform Change Matters

.NET Framework limitations. The traditional .NET Framework was Windows-only, slower to evolve, and increasingly difficult to maintain. Microsoft's focus shifted entirely to .NET Core (now simply .NET), meaning security patches and performance improvements concentrate on the modern platform.

.NET Core advantages. The modern .NET platform offers cross-platform deployment, dramatically improved performance, better containerisation support, and a faster release cadence. For Umbraco CMS development, this translates to faster websites, more deployment options, and better long-term support.

Migration complexity. Moving from .NET Framework to .NET isn't a simple upgrade - it requires careful planning, code review, and often significant refactoring. This is where experienced Umbraco CMS development partners prove invaluable.

The Umbraco 9 Watershed

Umbraco 9 marked the first version built entirely on .NET Core. This release fundamentally changed how Umbraco operates:

• Dependency injection throughout - cleaner, more testable code
• Modern hosting model - better performance and scalability
• Cross-platform support - deploy on Linux, macOS, or Windows
• Container-ready architecture - perfect for Docker and Kubernetes

Every subsequent version builds on this foundation, making Umbraco 9+ a completely different proposition from Umbraco 8 and earlier.

Umbraco Courier and Umbraco Deploy: Content Deployment Evolution

Content deployment between environments has always been a critical aspect of enterprise Umbraco CMS development. Understanding the tools available - and how they've evolved - is essential for any migration project.

The Legacy: Umbraco Courier

Umbraco Courier was the original content deployment solution for Umbraco. It allowed editors and developers to transfer content, media, and document types between Umbraco environments - development, staging, and production.

Courier enabled:

• Content transfers - move pages and content between environments
• Media synchronisation - keep images and files in sync
• Document type deployment - push schema changes across environments
• Revision tracking - understand what changed and when

For organisations running Umbraco 7 or earlier, Courier was often the backbone of multi-environment workflows. At Original Objective, we've implemented and maintained countless Courier deployments over the years, understanding its capabilities and limitations intimately.

The Modern Solution: Umbraco Deploy

Umbraco Deploy is Courier's successor, built from the ground up for modern Umbraco versions. It powers the deployment infrastructure on Umbraco Cloud and is available as a standalone package for self-hosted installations.

Umbraco Deploy improves upon Courier with:

• Git-based workflows - schema changes tracked in source control
• Improved conflict resolution - clearer handling of deployment conflicts
• Better performance - faster transfers and reduced overhead
• Modern architecture - designed for .NET Core and containerised environments
• Umbraco Cloud integration - seamless deployment through the Cloud portal

Migration Considerations

If your current Umbraco installation relies on Courier, migrating to Umbraco 17 means transitioning to Deploy. This isn't simply a package swap - it requires:

• Workflow review - understanding how your team currently deploys content
• Process adaptation - adjusting procedures for Deploy's approach
• Training - ensuring editors understand the new tools
• Integration updates - modifying any automated deployment scripts

Our team has extensive experience with both Courier and Deploy. We've handled dozens of transitions, helping organisations maintain their deployment workflows whilst upgrading to modern Umbraco. Whether you're on legacy Courier or need to implement Deploy for the first time, we can guide you through the process.

The New Backoffice: Umbraco's Modern Interface

Umbraco 14 introduced an entirely rebuilt backoffice using the Lit framework and web components. This wasn't cosmetic - it represents a fundamental architectural shift that impacts how editors and developers interact with the CMS.

What Changed

Technology stack. The legacy AngularJS backoffice has been replaced with modern web components. This brings better performance, improved accessibility, and a more maintainable codebase.

Extension model. Developers now create backoffice extensions using a standardised, documented approach. If you've built custom property editors or dashboard widgets for Umbraco 7 or 8, these will need rebuilding for the new architecture.

User experience. Content editors benefit from a more responsive, intuitive interface. Tasks that previously required multiple clicks now flow more naturally.

Migration Considerations

For organisations with significant backoffice customisations, the new interface requires planning. Our Umbraco CMS development team helps clients:

• Audit existing customisations and assess migration paths
• Identify standard features that replace custom solutions
• Rebuild essential custom functionality using modern patterns
• Train content teams on the new interface

API-First and AI-First: The Modern Approach

Modern Umbraco CMS development increasingly centres on the Content Delivery API. Rather than rendering pages server-side, Umbraco serves structured content to any frontend - websites, mobile apps, kiosks, or AI systems.

The Content Delivery API

Umbraco's built-in Content Delivery API provides:

• RESTful endpoints for all content types
• Flexible querying with filtering, sorting, and expansion
• Media delivery with automatic optimisation
• Preview support for draft content

This API-first approach enables headless architectures where Umbraco handles content management whilst specialist frontends - like Next.js - handle presentation. The result? Better performance, improved SEO, and the flexibility to deliver content anywhere.

AI Integration: The Next Frontier

The Model Context Protocol (MCP) opens new possibilities for AI-assisted content management. At Original Objective, we use MCP daily to:

• Query and analyse content programmatically
• Generate draft content following brand guidelines
• Automate routine content operations
• Power intelligent chatbots with accurate CMS content

This AI-first capability represents the cutting edge of Umbraco CMS development, and it's only available on modern Umbraco versions.

Migration Paths: From Legacy to Umbraco 17

Every Umbraco 17 migration is different. The approach depends on your current version, customisations, content volume, and business constraints.

From Umbraco 7

Umbraco 7 migrations require the most planning. The jump spans:

• .NET Framework to .NET (major platform change)
• Legacy backoffice to new web components interface
• Old property editors to modern equivalents
• AngularJS customisations to Lit-based extensions

We typically recommend a phased approach: migrate to Umbraco 8 first (if not already there), then to Umbraco 10 LTS, and finally to Umbraco 17 LTS. This staged migration reduces risk and allows thorough testing at each step.

From Umbraco 8

Umbraco 8 to 17 still involves the .NET Framework to .NET transition, but with less legacy baggage than Umbraco 7. The content migration tools are more mature, and many packages have direct upgrade paths.

From Umbraco 10, 13, or Later

If you're already on .NET-based Umbraco, migration to 17 is significantly smoother. The main consideration is the new backoffice introduced in Umbraco 14 - any custom extensions need updating, but the content and data models transfer cleanly.

Why Umbraco 17 LTS Now?

Umbraco 17 is a Long-Term Support release. This means extended security updates, bug fixes, and stability - essential for enterprise deployments. Here's why now is the ideal time to migrate:

Security and Support

Umbraco 7 and 8 are end-of-life. They no longer receive security patches. Running these versions exposes your organisation to known vulnerabilities. A Umbraco 17 migration addresses this risk definitively.

LTS stability. Umbraco 17's LTS status means you won't need to upgrade again for years. Your investment in migration pays dividends through extended stability.

Performance and Capability

Modern .NET performance. Umbraco 17 on .NET 9 delivers significantly better performance than legacy versions. Pages load faster, the backoffice responds more quickly, and your infrastructure costs less.

Future-ready features. Access to the Content Delivery API, MCP integration, and modern extensibility opens possibilities that simply don't exist on older versions.

Talent and Ecosystem

Developer availability. Fewer developers maintain .NET Framework skills. Finding talent for legacy Umbraco becomes increasingly difficult and expensive. Modern Umbraco CMS development attracts a larger, more active developer community.

Package ecosystem. The package community focuses on modern Umbraco. Essential packages increasingly drop support for legacy versions.

Our Migration Services

Original Objective provides comprehensive Umbraco 17 migration services tailored to your situation.

Assessment and Planning

We begin every migration project with thorough discovery:

• Current state analysis - version, customisations, content volume, integrations
• Risk assessment - identifying potential issues before they become problems
• Migration strategy - phased approach, timeline, resource requirements
• Cost estimation - transparent pricing based on actual scope

Umbraco Cloud Migrations

For organisations wanting managed hosting, we specialise in Umbraco Cloud migrations. Umbraco Cloud provides:

• Automatic updates - stay current without manual intervention
• Built-in environments - development, staging, and production out of the box
• Baseline security - DDoS protection, SSL, and regular scanning
• Deployment workflows - push content and code through environments safely

CI/CD Integration

Modern Umbraco CMS development demands automated deployment pipelines. We integrate Umbraco into your existing CI/CD processes:

• Azure DevOps - build, test, and deploy pipelines
• GitHub Actions - automated workflows triggered by commits
• GitLab CI - integrated pipelines for GitLab users
• Octopus Deploy - enterprise deployment orchestration

Automated deployments reduce human error, accelerate releases, and provide audit trails for compliance.

API-First Delivery

If you're moving to a headless architecture, we deliver complete solutions:

• Umbraco backend - content modelling, API configuration, media management
• Next.js frontend - server-rendered React applications with excellent SEO
• Mobile apps - native iOS and Android consuming the same content API
• Integration layer - connecting Umbraco with your existing systems

Working With Us

We offer flexible engagement models to suit your needs.

Project Basis

For defined migration projects, we provide fixed-scope engagements with clear deliverables, timelines, and pricing. You know exactly what you're getting and what it costs.

Team Augmentation

If you have in-house developers, we can supplement your team with Umbraco CMS development expertise. Our specialists work alongside your people, transferring knowledge whilst accelerating delivery.

Ongoing Support

Post-migration, we offer support packages covering maintenance, minor enhancements, and consultancy. Your Umbraco investment stays healthy long-term.

18 Years of Umbraco Expertise

Original Objective has delivered Umbraco CMS development projects since the early days of the platform. This longevity means:

We've seen it all. Legacy code patterns, obscure bugs, complex migrations - we've encountered and solved them. Your edge case probably isn't new to us.

We understand the ecosystem. Relationships with Umbraco HQ, package maintainers, and the community give us insight and access that newer agencies lack.

We know what works. After hundreds of projects, we've refined approaches that balance speed, quality, and maintainability. You benefit from accumulated wisdom.

Next Steps

If you're running legacy Umbraco and considering a Umbraco 17 migration, we should talk. The longer you wait, the larger the gap becomes - and the more security risk you accumulate.

Book an intro call with our team. We'll discuss your current situation, outline potential approaches, and give you honest advice on whether and when to migrate.

For more on our software development services or AI integration capabilities, explore our website or contact us directly.

Your content management system underpins your digital presence. Make sure it's on a foundation that will serve you for years to come.