For years, the conversation around upgrading a CMS was fairly predictable. A version reached end of life, security updates stopped, and organizations had to decide whether it was finally time to move.
For many teams, that was enough.
For others, it wasn't.
If you're still running Umbraco 7 or 8 today, you've probably already made peace with the fact that those versions are no longer supported. If security updates alone were going to drive an upgrade, that decision likely would have happened years ago.
So why are more organizations looking seriously at Umbraco 17 now?
Because the role of the CMS is changing.
Today, the question isn't simply whether your platform is supported. It's whether your CMS can help your team keep pace with how digital content is being created, reviewed, and optimized.
That's a very different conversation.
The biggest change isn't AI. It's when the work happens.
Think about how most organizations publish content today.
A content editor creates a page, reviews it, and clicks Publish.
Only after that does the real work begin.
An SEO platform identifies missing metadata. An accessibility scanner finds WCAG issues. Someone reviews internal links. Analytics eventually reveal pages that aren't performing. As Answer Engine Optimization (AEO) and Generative Engine Optimization (GEO) become part of everyday digital marketing, another layer of analysis gets added to the process.
None of those tools are doing anything wrong. They're simply working after the content has already been published.
That creates a familiar cycle.
Publish the page. Run the reports. Create tickets. Fix the issues. Publish again.
Most digital teams have accepted this as normal because, until recently, there wasn't another practical way to work.
AI is changing that.
Instead of waiting until after publication to discover problems, organizations can increasingly identify and resolve many of those issues while content is still moving through the editorial workflow.
That changes more than the technology.
It changes how work gets done.
The opportunity isn't that AI reviews your content. It's that AI can become part of the publishing process instead of another tool you use afterward.
What does that actually look like?
Imagine a content editor finishes writing a new landing page and clicks Publish.
Instead of sending that page into the world and waiting for reports to identify problems later, Umbraco can use AI within the publishing workflow to review the page before it goes live.
For example, AI can draft optimized page titles and meta descriptions based on the content that's already been written. Those suggestions aren't just aimed at traditional SEO. They can also help organizations prepare content for the growing importance of AEO and GEO without asking editors to become experts in every new optimization trend.
The same workflow can evaluate the page for common accessibility issues. Missing alt text, heading structure problems, or other WCAG and ADA concerns can be identified before publication. If necessary, the publishing workflow can even pause until those issues have been addressed, allowing editors to resolve problems while they're already working on the page instead of discovering them weeks later during an accessibility audit.
The goal isn't to create more checkpoints.
It's to eliminate unnecessary rework.
Rather than publishing first and fixing later, quality becomes part of the publishing process itself.
This changes the role of the CMS
For years, organizations have added another platform every time a new challenge appeared.
Need better SEO?
Buy an SEO platform.
Need accessibility monitoring?
Add another product.
Need link checking?
Add another one.
Need content quality analysis?
There's a tool for that too.
Over time, digital teams have assembled an increasingly large collection of specialized products, each with its own reports, dashboards, notifications, and workflows.
Individually, each tool makes sense.
Collectively, they create complexity.
Editors spend time moving between systems, interpreting reports, and translating recommendations into changes inside the CMS.
As AI becomes part of the editorial workflow, some of those responsibilities begin moving back to where the work is already happening.
That doesn't mean every specialized platform disappears. Enterprise SEO suites, accessibility monitoring, analytics, and governance tools will continue to play an important role.
What changes is their purpose.
Instead of acting as the primary way organizations discover problems, they increasingly become oversight tools that validate the overall health of the digital experience, while many day-to-day improvements happen before content is ever published.
The goal isn't to eliminate every specialized tool. It's to stop asking editors to jump between five different systems just to publish a single page.
That shift has real business value.
Fewer disconnected workflows mean less context switching for editors, fewer publishing delays, and less time spent fixing issues that could have been prevented in the first place. Over time, organizations may also find opportunities to simplify parts of their technology stack as capabilities move closer to the CMS, reducing both operational complexity and the total cost of ownership of their digital platform.
Why Umbraco 17 makes this possible
This is where Umbraco 17 becomes much more than another Long-Term Support release.
One of the biggest additions is support for the Model Context Protocol (MCP) through Umbraco's official MCP Server.
While the name sounds technical, the idea is fairly straightforward.
It gives AI applications a secure, supported way to understand and interact with the content inside Umbraco. Instead of relying on custom integrations or copying content between systems, organizations can connect their own AI models, whether that's ChatGPT, Claude, Gemini, or another large language model, directly into their content workflows.
Alongside MCP, the new Management API expands what automation and AI tools can do inside the platform.
Together, these capabilities create the foundation for AI to become part of everyday content operations rather than existing as another disconnected application.
This isn't about replacing editors.
It's about giving editors intelligent assistance while they're already doing the work.
Where end of life fits into the picture
Support still matters.
Organizations running Umbraco 7 or 8 are well beyond end of life and no longer receive security updates. Versions 9 through 12 have also reached the end of their support windows, while Version 13 remains supported through December 2026 before its Long-Term Support lifecycle ends.
Those timelines are important because they determine how you'll move forward.
Organizations running Versions 7 and 8 should expect a rebuild due to the move from ASP.NET Framework to ASP.NET Core. Organizations already on newer versions have a much more straightforward upgrade path.
But support windows aren't the whole story anymore.
The more important question is whether your current platform is prepared for how your organization wants to work over the next five years.
The conversation has changed
Five years ago, upgrading a CMS was largely about staying supported.
Today, it's increasingly about creating a platform that helps your organization produce better digital experiences with less manual effort.
AI isn't valuable because it gives you another chatbot or another dashboard.
It's valuable because it allows quality, optimization, accessibility, and governance to become part of the publishing workflow instead of happening after the fact.
That's a meaningful shift.
And it's one that older CMS platforms simply weren't designed to support.
If you're evaluating what comes next for your digital platform, don't just ask whether your version of Umbraco is supported.
Ask whether your CMS is helping your team prevent problems before they happen, or whether it's still relying on reports, tickets, and manual reviews to catch them afterward.
That's the question more organizations are beginning to ask.
And it's why so many of them are looking at Umbraco 17 differently than they would have looked at an upgrade just a few years ago.
