Why staying on CMS 11 is a growing risk

End of support does not switch your site off. Optimizely does not disable CMS 11 environments, but severe vulnerabilities are now handled case by case rather than through routine patching (WAYF). Meanwhile, add-ons, integrations and NuGet dependencies drift further out of vendor coverage every month (umage.ai). As Optimizely's John Håkansson put it, "Every month you postpone upgrading puts you back a month in tech debt." Timing matters too: Microsoft ends support for both .NET 8 and .NET 9 on 10 November 2026, while .NET 10, a long-term support release, is supported until 14 November 2028 (Microsoft). Any migration starting now should target .NET 10 from day one. For security and compliance teams, an unpatched content platform holding customer data and form submissions deserves a dated remediation plan, not open-ended deferral.

What you gain on modern .NET

The move is not only defensive. When Optimizely upgraded its own website to CMS 12, response times improved threefold, with some pages ten times faster, and a Nordic financial-services customer cut response times by more than 70 percent (Håkansson, Optimizely World). Optimizely also reports that CMS 12 and Commerce 14 handle three times more server requests. Modern .NET is cross-platform, so solutions can be hosted on Linux and in containers as well as Windows (Optimizely World upgrade guide; Netguru). ASP.NET Core adds built-in identity provider support, improved secret storage and defense-in-depth mitigations. Above all, it is where innovation lives: extended headless APIs, Optimizely Graph and CMS 13 all build on modern .NET, while CMS 11 receives no new features. A modern stack also makes it easier to recruit and retain the developers who maintain your platform (Håkansson, Optimizely World).

Migration of Optimizely solutions: what actually changes

The good news is that your content survives the journey. Upgrading to CMS 12 requires no data migration, and most Optimizely packages and APIs stay identical (Optimizely documentation); user tables are the main exception, moving from the ASP.NET Identity scheme (Optimizely World upgrade guide). The real work is in the code around the platform. Optimizely describes three phases: run the Upgrade Assistant, fix the remaining code issues, then upgrade the service environment. In practice, developers move configuration from web.config to appsettings.json, replace global.asax with startup code, swap OWIN authentication for OpenID Connect, convert block controllers to view components, and adopt the built-in dependency injection, logging and JSON serialization (Optimizely World upgrade guide). WebForms templates must be rebuilt in MVC, and incompatible NuGet packages need replacing. Note that Microsoft's .NET Upgrade Assistant was deprecated in late 2025 in favor of GitHub Copilot app modernization, so expect AI-assisted tooling plus careful human review (Legacyleap). Practitioners report that this runtime jump is the largest single bucket of CMS-side effort, bigger than content migration or visual rebuild, and that custom plugins almost always need rewriting (umage.ai).

CMS 12 first, or straight to CMS 13?

Owners now face a routing decision. Optimizely's FAQ confirms a direct CMS 11 to CMS 13 upgrade is supported, with effort comparable to an 11-to-12 upgrade because the .NET change dominates both (WAYF). However, CMS 13 requires .NET 10 and does not support Search & Navigation (Find), making a move to Optimizely Graph mandatory, usually with a six-month overlap period (WAYF). The alternative is CMS 12 on .NET 10, which Optimizely confirmed in 2026 for CMS 12 and for Commerce 14 from version 14.46.0 (WAYF). That keeps Find working, puts you on an actively maintained version and defers the Graph rewrite to a planned later phase. Sites with heavy search customization often benefit from the staged route; leaner solutions can go directly to CMS 13.

A pragmatic migration roadmap

A low-risk plan starts with an audit of add-ons, custom code, integrations, search queries and plugins before any budget is fixed. Next, spike the runtime move and, where relevant, the Graph migration on a slice of the codebase to validate your route, and retire unused plugins rather than porting them (umage.ai). Treat the project as a chance to rethink the content model into composable, editor-friendly sections. DXP customers use the PaaS portal migration tool to move environments and hostnames, and Optimizely keeps the old CMS 11 environment for 14 days after the final go-live as a safety net. Optimizely also recommends completing the migration within one year of starting (Optimizely documentation), so plan steady delivery rather than an open-ended program.

Conclusion

CMS 11 has left Optimizely's support window and .NET 8 reaches end of support on 10 November 2026, so the safest path for existing owners is a well-scoped move to modern .NET that targets .NET 10. A planned migration of Optimizely solutions closes the security gap of an unpatched platform, delivers measurable performance gains and opens the door to Optimizely Graph, headless delivery and CMS 13. The sooner you start, the smaller the leap.

Call to action

MDR Solutions is a Belgrade-based team of Optimizely certified developers building Optimizely CMS and Commerce solutions on Microsoft .NET and Azure. We help existing Optimizely clients audit their CMS 11 estates, choose between CMS 12 and CMS 13, and deliver the move from .NET Framework to modern .NET with minimal disruption. Book an upgrade assessment through mdrsolutions.rs/contact and get a clear migration plan.