Optimizely CMS 13 readiness checklist: plan your move from CMS 12

Optimizely CMS 13 runs on .NET 10. It makes Optimizely Graph and Opti ID required parts of the licence, and it no longer supports Optimizely Search & Navigation, formerly known as Find (source: CMS 13 release notes). Search has to move to Optimizely Graph or a third-party search provider.

Microsoft ends support for .NET 8 on November 10, 2026. In May 2026, Optimizely confirmed that CMS 12 also runs on .NET 10 (source: Optimizely World). So the .NET 8 deadline does not force CMS 13 on its own. It does force a choice: move CMS 12 to .NET 10 now, or plan the full move to CMS 13 with search rebuilt on Graph.

Use this checklist to make that choice with facts. The search rework is usually the largest item, so give it the most attention.

How to score it

• Give each item 2 points if it is done, 1 point if it is in progress and 0 if nobody has started it.
• Add up your points and divide the total by the maximum (2 points times the number of items).
• A score above 75% means you can schedule the work. Between 40% and 75%, close the gaps this quarter. Under 40%, start with an assessment before you commit to a date.

Framework and versions

• Confirm which .NET version each CMS 12 environment targets.
• If you stay on CMS 12 for now, plan the move to .NET 10 before November 10, 2026.
• If you run Commerce 14, check Optimizely's current .NET 10 support status before you schedule work.
• List every add-on and check that it exists for CMS 13. At general availability, Optimizely listed Forms, Language Manager and the Content Delivery API as coming next.

Search: from Find to Graph

• List every page, block and feature that queries Search & Navigation: site search, listings, facets and related content.
• Export your current search data: top queries, zero-result queries and click-through.
• Map each Find query to Optimizely Graph or to a third-party search tool.
• Try the Optimizely Graph C# SDK on one listing to estimate the rework.
• Rebuild synonyms, best bets and boosting rules in the new search setup.

Identity and licensing

• Plan editor sign-in through Opti ID, which CMS 13 requires.
• Confirm with your account manager what your CMS 13 licence includes and how it changes your contract.

Content and front end

• Decide whether your front end stays on Razor views or moves to headless delivery through Graph.
• Audit content types and remove the ones nobody uses.
• Check that English and French content is complete and correctly linked.
• Show editors Content Manager and the new visual authoring tools, then plan training.

Testing and launch

• Upgrade a copy of production first and compare search results before and after.
• Test forms, personalization and integrations end to end.
• Keep a 301 redirect list and an SEO baseline for every changed URL.

Get a second opinion

Scored under 75%, or unsure whether to stay on CMS 12 for now? Our free Optimizely audit reviews your setup and gives you a go or no-go view on CMS 13.

Sources

1. Optimizely CMS 13 general availability release notes
   docs.optimizely.com
2. Optimizely CMS 12 now fully supports .NET 10 (Optimizely World, May 2026)
   world.optimizely.com
3. .NET and .NET Core official support policy
   dotnet.microsoft.com