While the technical step from Optimizely 12 to 13 is incremental, the move from CMS 11 to the modern .NET-based platform is transformational. If you are still on version 11, the impact goes far beyond IT, it affects your entire organisation.
When your platform holds you back
In conversations with stakeholders, we often hear the same concerns.
From an executive perspective, questions revolve around compliance with the European Accessibility Act, security standards, and whether digital investments are delivering expected business value.
From a technology perspective, maintenance consumes budget that should fund innovation. Aging frameworks increase security exposure, make integrations harder, and complicate recruitment.
From an editorial perspective, years of patches and customisations result in a CMS that feels heavy and inefficient, with limited support for AI, automation, and modern workflows.
Over time, technical debt becomes organisational friction.
What you gain by upgrading
Upgrading to CMS 12 or 13 is effectively a modernization initiative.
The platform runs on modern .NET, designed for cloud performance, security, and long-term support. This provides a stronger technical foundation with improved stability and scalability. Performance improves significantly, leading to faster response times, better SEO outcomes, semantic search capabilities and more efficient infrastructure usage.
You also unlock updated or totally new functionality in the broader Optimizely ecosystem including Opal AI orchestration, updated experimentation, personalisation, improved headless delivery, and improved integrations.
With CMS 13, the editorial experience continues to evolve, introducing usability improvements and a more flexible working environment for content teams.
Importantly, upgrading reduces long-term cost. The longer organisations wait, the more dependencies become outdated and the more complex — and expensive, the transition becomes.
Optimizely’s position as a Leader in the 2025 Gartner® Magic Quadrant™ for Digital Experience Platforms further reinforces the importance of staying aligned with the platform’s innovation roadmap.
From 11 to 13 — choosing the right path
It is technically possible to move directly from CMS 11 to CMS 13. However, the right approach depends on your solution’s complexity, integrations, and business criticality. Many organisations choose to validate internally on version 12 before going live on 13, enabling a controlled migration while reducing risk.
An upgrade is not just a version shift. Done correctly, it aligns technology, business goals, and editorial workflows and creates a future-proof foundation for growth.
Version comparison overview
| Area | CMS 11 | CMS 12 | CMS 13 |
| Technical foundation | .NET Framework 4.x | .NET Core (.NET 6/8) | .NET 10 |
| Architecture | Legacy ASP.NET MVC | Modern ASP.NET Core | Optimized Core architecture |
| Cloud readiness | Limited | Full cloud support | Optimized for cloud & DXP |
| Performance | IIS dependent | Faster, platform independent | Further optimized |
| Headless & APIs | Limited | REST, GraphQL support | Expanded headless focus |
| Editorial experience | Traditional block model | Improved UI | Enhanced editing experience |
| AI enablement | Limited | Supported | Expanded opportunities |
| Support lifecycle | Aging | Long-term support | Latest innovation track |
How to upgrade to Optimizely 13
A structured, low-risk approach
Upgrading is not just a version shift, it is a modernization decision. The quality of preparation determines whether the transition is controlled and efficient or complex and costly.
We typically work in three phases.
First, we conduct a structured Upgrade Assessment to evaluate architecture, integrations, technical debt, accessibility, and editorial workflows. We also evaluate the need of the organization and how your solution currently is used. This creates a clear decision foundation to understand needs and potential for improvement in different areas.
Second, we define the right path: a focused technical upgrade, a modernization of the frontend alongside the backend upgrade, or a full rebuild when long-term value requires a new foundation.
Third, we execute in controlled environments. Dependencies are validated and refactored, migrations run in parallel test setups — never production-first — and content freeze is carefully planned to ensure business continuity.
Direct 11 → 13 migration
A direct migration from CMS 11 to 13 is technically possible once version 13 is released (target release date is late March 2026). However, the right strategy depends on complexity, integrations, customizations, and business criticality.
In many cases, validating internally on version 12 reduces risk while still enabling a single controlled production move. The goal is always predictable delivery with minimized uncertainty.
Upgrade is a business decision
An upgrade must align technology, business objectives, and editorial workflows.
Done correctly, it reduces long-term maintenance cost, strengthens security and compliance, accelerates innovation, and improves editor productivity. It creates a platform that supports growth, not one that limits it.
Efficiency through structured tooling
We combine automated upgrade tooling with structured delivery processes to reduce manual effort, shorten timelines, and control cost. Each upgrade is carefully scoped and risk-assessed to ensure clarity from start to finish with defined milestones, predictable timelines, and no surprises.
Our Proxima Content Migration tooling further accelerates the process and reduces dependency-related risk compared to fully manual upgrades.
Epinova Upgrade Assessment
When it is time to upgrade, improve, or rebuild, clarity is critical. Our Upgrade Assessment provides a structured evaluation of your current solution, identifies risk areas, estimates complexity and cost, and outlines alternative paths forward. The result is reduced uncertainty and a clear, data-driven roadmap tailored to your organisation.
Depending on your situation, we help you:
- Upgrade efficiently where technical debt is low
- Modernize frontend performance, accessibility, and UX if needed
- Rebuild using our Proxima Web Accelerator when long-term value requires a new foundation
Across all alternatives, our focus is risk control, cost transparency, and long-term sustainability.
Ready to evaluate your upgrade path?
If you are running CMS 11 — or planning your move to 13 — now is the time to establish a clear strategy.
Book an Upgrade Assessment to receive:
- A structured technical and business evaluation
- Risk and complexity overview
- Recommended upgrade strategy
- High-level time and cost estimate
