Developers working

Optimizely CMS 13: What IT leaders need to know

For IT leaders responsible for an Optimizely CMS 12 environment – or considering a move to Optimizely – here is a look at what version 13 involves and how to plan the move sensibly.

Tony Duan

25 May 2026

7 minute read

Optimizely CMS 13 is built on .NET 10, makes Optimizely Graph and Opti ID mandatory for the full feature set, and shares a common codebase with Optimizely’s SaaS CMS product. It went GA on 31 March 2026. For IT leaders responsible for an Optimizely CMS 12 environment, the practical question is what the upgrade involves, what the risks are, and how to plan it sensibly.

One important framing point: Optimizely positions this as an upgrade, not a migration. Your existing content stays in place – there is no content migration required. The work is in updating the platform framework, switching infrastructure dependencies, and optionally adopting new editorial capabilities.

What’s architecturally different in Optimizely CMS 13

CMS 13 targets .NET 10 (up from .NET 6/8 in CMS 12) and represents the PaaS platform converging with Optimizely’s SaaS product. The two now share a common codebase, which is good news for stability – features that have been running in SaaS production for over a year are now available on PaaS.

The most significant change is that Optimizely Graph is now mandatory for the full feature set. Graph is the platform’s GraphQL-based content delivery and search layer, replacing Search & Navigation (which is fully removed in CMS 13). Graph powers Content Manager, External Content integration, AI capabilities via RAG, GEO, and semantic search. A new C# SDK provides a fluent API for querying content.

The second key component is Opti ID, Optimizely’s single sign-on identity layer. Opti ID is required to access Opal AI, Optimizely Connect Platform, and future AI capabilities. However, on-premises customers can technically upgrade to CMS 13 without Opti ID – they just won’t have access to these features. Both Graph and Opti ID are included in the CMS 13 licence at no additional cost.

Graph and the embedded DAM are now included in PaaS pricing with no separate charge – aligned with the SaaS pricing model. The pricing metric has also shifted from page views to visits, with content items and named users as the other key dimensions. Existing customers upgrading to CMS 13 remain on their current pricing until renewal, at which point the new packaging applies.

Other changes include the Application Model replacing SiteDefinition, namespace migration from EPiServer to Optimizely, Visual Builder as the default editing interface, an embedded DAM, Content Manager (a Graph-powered search-first editorial interface), External Content for pulling third-party data into the CMS, and Content Variations for managing multiple published content versions.

The upgrade: Required and optional workstreams

The community consensus – and our own assessment – is that this upgrade is lighter than the CMS 11 to 12 jump (which was a full .NET Framework to .NET Core replatforming), but it is not a routine NuGet update. Optimizely’s own upgrade guidance breaks it into four jobs, two required and two optional.

Required: Opti ID set-up

Opti ID is the authentication foundation for CMS 13 and unlocks Opal, OCP, and future AI capabilities. This is more than a technical task – SSO changes carry organisational implications including IT security review, identity governance, and potentially legal review depending on your data policies. On-prem customers can upgrade without it, but lose access to the AI and platform integration features. Factor in stakeholder alignment time, not just development hours.

Required: Switch from Search & Navigation to Optimizely Graph

Search & Navigation is fully removed in CMS 13. Any implementations using it must be updated. This is widely regarded as the single largest workstream. Complexity scales with how deeply Search & Navigation is embedded – custom facets, filters, boosting logic, and integrations. Out-of-the-box implementations mean moderate effort. Heavily customised search means significant refactoring. A new .NET SDK is provided to ease the transition, and Graph introduces semantic, intent-aware search as a replacement for keyword-based indexing.

The Optimizely Graph schema in CMS 13 contains breaking changes compared to CMS 12. Frontend applications that query Graph will require updates to reflect the new schema.

Optional: Visual Builder and content model adoption

You can migrate some or all pages to Visual Builder, or run a hybrid model – migrating only what makes sense now. Configure preview once and choose which pages to move at what pace. This is not required for the core upgrade.

Optional: Embedded DAM set-up

All CMS 13 customers get the embedded DAM included. If you’re new to Optimizely DAM, there’s a one-time set-up for existing media assets. If you’re already on DAM, the effort is minimal. If you are using DAM with CMS 12, please refrain from migrating your assets until the dedicated migration tools are released. While core aspects of the CMS 12 to 13 upgrade can proceed now, the specific tools required for asset migration are being prioritised for a release shortly after CMS 13.0.0.

Additional technical workstreams

Beyond Optimizely’s four-step guidance, plan for deprecated and removed API remediation (PageReference, ContentArea.FilteredItems, SiteDefinition, and others require a code audit), the Application Model and namespace changes (EPiServer to Optimizely), and .NET 10 target framework updates for third-party dependencies.

Known risks and blockers for the CMS 13 upgrade

  • Optimizely Commerce is a blocker. Commerce 14 is incompatible with CMS 13 due to hard dependencies on removed APIs. Commerce Connect 15 was not production-ready at GA. If you run Commerce, you cannot upgrade until Commerce 15 is stable.
  • Third-party add-on readiness. Forms, Language Manager, and Content Delivery API are still being updated for CMS 13. Audit your add-on dependencies before committing to a timeline.
  • Undocumented breaking changes. Developers working on real-world upgrades (beyond the Alloy reference template) have reported breaking changes not covered in official documentation. Budget contingency time.
  • Database schema migration sequencing. Direct upgrades from older CMS 12 versions can fail. The recommended path is to update to the latest CMS 12 first, then upgrade to CMS 13.
  • Some Opal agents are ‘coming soon’. Several headline agents including SEO Metadata Optimization, GEO Schema Optimization, and FAQ Creation are announced but not yet available at launch. Confirm availability timelines before factoring them into your business case.

Is there an Optimizely CMS 12 end-of-life date?

No. As of April 2026, Optimizely has not announced a CMS 12 end-of-life date. The March 2026 technical webinar explicitly confirmed there is no timeline, and CMS 12 continues to receive active development and releases. Existing customers remaining on CMS 12 will see no change to their pricing or packaging.

This means you have the space to plan a considered upgrade rather than a reactive one. But ‘no rush’ doesn’t mean ‘no action’. The prerequisite work – learning Graph, planning Opti ID, auditing your codebase – takes months, not weeks. Getting started now means you’ll be ready to move when it makes strategic sense, rather than being caught out later.

Our recommended approach

  • Audit your current implementation against the known deprecated APIs. Understand the scope before estimating effort.
  • Assess your Search & Navigation complexity. This single workstream will likely determine whether your upgrade is a month or a quarter.
  • Engage your security and identity teams early on Opti ID implications.
  • If you run Commerce, park the CMS 13 conversation until Commerce 15 reaches GA and has been validated.
  • Stand up a CMS 13 development environment. Get your developers hands-on with Graph and Visual Builder so planning is informed by experience, not documentation alone.
  • Plan Visual Builder and DAM adoption as a separate phase after the core upgrade. Run a hybrid model and migrate pages at your own pace.

Organisations that approach this as a planned program of work – with proper scoping, stakeholder alignment, and phased delivery – will transition smoothly. Those that wait until CMS 12 support becomes a question will be doing this work under pressure instead of on their own terms.

How Luminary can help with your Optimizely CMS 13 upgrade

Luminary has been working with Optimizely CMS 13 since the early preview releases and has deep experience with CMS 12 upgrade planning across enterprise environments. We provide upgrade assessments, Search & Navigation to Graph scoping, Opti ID implementation planning, and phased upgrade roadmaps.

If you’re weighing up your options, reach out for an honest conversation about what’s involved for your specific environment.

Want to tap into the expertise of a multi-award winning Optimizely Solution Partner?

Get in touch

Keep Reading

Want more? Here are some other blog posts you might be interested in.