Summary
The framework underneath Optimizely’s CMS 12 (.NET 8) reaches end of support on November 10, 2026. This is important if your site runs on CMS 12, as Optimizely has confirmed that CMS 12 will not officially support .NET 10, which makes CMS 13 the path to staying on a supported framework. The deadline settles whether you should upgrade, but what your team gains from the upgrade is a separate question.
CMS 13, generally available since March 31, 2026, is where Optimizely is building Mark (formerly Opal, the Optimizely Agent Platform), Optimizely Graph, Visual Builder, and every release that follows. This article covers what changes for your team, what the upgrade involves, and how The C2 Group delivers it as a fixed-price project with activation planned from the start.
A Version Upgrade Changes Little on Its Own
You’ve probably heard about CMS 13 from your Optimizely Account team, likely attached to a capability you wanted. Before you commit your budget, you need to answer these questions: what the upgrade buys your team, what it costs, and whether the value shows up at launch or depends on continued work that comes after the implementation.
A version upgrade on its own changes very little about how your marketing team works. Editors get a new interface and search moves to a new service, but the way content gets planned, built, reviewed, and improved stays the same until someone decides how the new capabilities will be used and who will own them. The value of CMS 13 comes from what the new foundation makes possible and from having a plan to put it to work once the technical upgrade is done. That plan for after implementation is what many upgrade conversations leave out.
The .NET 8 Deadline Sets the Timeline
End of support means Microsoft stops issuing security patches and fixes for .NET 8. Your site will keep running after November 10, but any vulnerability discovered from that point forward stays open on CMS 12, because it has no supported path to .NET 10. If your organization carries security or compliance obligations, an unsupported framework is the kind of finding that surfaces in audits and vendor risk reviews regardless of how well the site performs.
The timing dynamic is important. With our AI-powered approach we’re able to deliver this in just 2–4 weeks, but a team that starts today will still spend some period on an unsupported framework. For planning purposes, the decision comes down to how long that exposure lasts. The window is shortest when the upgrade is scoped before it starts, because the largest source of delay (third-party package compatibility) can be assessed before you commit to anything.
5 powerful reasons to upgrade to CMS 13
1. Your editors can now build and personalize pages without waiting on a dev sprint.
Visual Builder replaces on-page editing as the default experience, giving editors one interface for pages, blocks, experiences, and media. Layout changes, new landing pages, and personalized variants move out of the development backlog and into the marketing team’s workflow.
You don’t have to rebuild the site to get there, since Visual Builder supports your existing CMS 12 pages with blocks and traditional pages that can sit alongside the new model. The primary constraint is your content model: a page type works in Visual Builder only after its content model has been updated, so determining the page types to bring over in the first place is a scoping decision, not a launch-day surprise.
2. You can now “hire” agents to take on drafting, optimization, and governance work inside the CMS.
Mark brings agents for content creation, optimization, and governance into the editing environment, and Optimizely has stated that CMS 13 will include out-of-the-box agents equivalent to those in its SaaS CMS. In practice, work such as producing first drafts or checking pages against your standards can start inside the system where the content lives.
Agents read your content through Graph, so they perform only as well as the content they retrieve; duplicated pages, inconsistent classification, or unowned content types will produce unreliable output regardless of the model behind it. Mark is provisioned separately, runs on credits, and requires Opti ID, so it carries its own budget and hosting considerations.
3. Graph connects your content to every capability you’re upgrading for.
Graph replaces Search & Navigation, which CMS 13 no longer supports, so the move is required, and Graph is included in the CMS 13 license. Your team is unlikely to work in Graph directly. Its value shows up as the reason content variations, external content connections, and agents can function at all.
4. Assets and discoverability move closer to the work.
If you’re on the DXP, CMS 13 includes an embedded DAM, so editors find and place approved assets without switching systems. The platform also adds built-in generative engine optimization to improve how your content is found and represented in AI-driven search.
5. Your site keeps gaining capabilities.
Optimizely fully supports the current major version and backports select fixes, mostly security-related, to the previous one. New features ship on CMS 13; the published roadmap already includes additional agents and tools. A CMS 12 site will keep working, but it will stop gaining what Optimizely releases next, and the distance between your site and a CMS 13 site will widen with each release. That distance isn’t always an emergency on its own, but it will compound over time, and if your organization intends to use Optimizely’s AI capabilities, you will have to close that distance eventually.