Optimizely CMS 13: What Changes and Why It Matters

1. Graph is the new foundation. Full stop.

If you take nothing else from this article, take this: CMS 13 is built around Optimizely Graph, and almost every new sparkling feature depends on it. Optimizely have been careful to frame Graph as opt-in from a configuration standpoint, but they've also been clear that running CMS 13 without it is essentially running with a smaller feature set. ‘Opt-in’ might be technically accurate. Practically, it's not really a choice. Prepare accordingly.

Graph replaces the old content indexing and delivery pipeline and becomes your method for content discoverability, external content integration, and the AI capabilities coming with Opal. So if you're planning to upgrade to the lovely new Content Manager, Visual Builder, push external content, connect to AI, and beyond, then you’re adopting Graph. They simply won’t work without it.

Opti ID comes as part of the same mandatory bundle. It replaces per-product login with a single sign-on layer across the Optimizely One ecosystem. For most developers, this is fairly transparent, but for clients with custom identity stacks, enterprise SSO configurations, or complicated role structures, there's a bit of work here that needs to happen before anything else. Don't underestimate it.

2. Say goodbye to Search & Navigation

This is the change that will cost you the most time, and the one that's probably not getting enough attention in the wider conversation.

Find is gone in CMS 13. Not deprecated in the "it still works but we'd rather you didn't" sense. Gone-gone. You need to migrate to Optimizely Graph for search or bring your own third-party provider.

How much work that is depends entirely on how deeply ingrained Find is in your setup. A simple keyword search on a microsite won’t be much of an issue. But for a large e-commerce or publishing site with custom search pages, complex faceting, boosting rules, synonym configurations, and multiple content type projections, this is going to be a large project that needs to be scoped and planned, not something you squeeze into a package upgrade sprint.

That said, Optimizely have put thought into making the transition less painful. CMS 13 ships a new Graph C# SDK with a fluent API that's deliberately designed to feel familiar. SearchFor() replaces For(), Where() replaces Filter(), Limit() replaces Take(). If you've written a lot of Find code, the muscle memory transfers more than you'd expect.

3. .NET 10, and the dependency audit you probably need to do

The framework upgrade itself isn't the hard part. Bumping your target framework to .NET 10 and updating your Optimizely package references is straightforward, and for a reasonably clean CMS 12 codebase, the compiler will do most of the work of telling you what needs fixing.

What's actually worth your time is auditing your third-party packages and custom add-ons. The Optimizely ecosystem includes a lot of community packages, agency utilities, and client-specific extensions that were built for .NET 8 and haven't necessarily been updated for .NET 10 yet. Some will just work. Others won't. Finding out which is which before you're mid-migration is way better than finding out after.

One practical note that's caught teams out already: if you're upgrading from an older CMS 12 version directly to a CMS 13, there's a known database migration issue. Upgrade to the latest CMS 12 release first, then make the jump.

4. SiteDefinition is out. The Application Model is in.

CMS 13 replaces SiteDefinition with a new Application Model. Sites are no longer resolved in code via SiteDefinition.Current. Instead, they're set up as "applications" through the CMS admin interface, with explicit types (in-process for traditional ASP.NET, headless for decoupled front-ends), hostname configuration, and start page assignment. The migration handles this automatically on the first CMS launch, so you're not rebuilding your site configuration from the ground up.

What does need attention is your code. References to SiteDefinition.Current.RootPage and similar patterns will need updating, and if you're running multiple sites with complex hostname configurations, it's worth mapping those out before you begin.

For headless implementations in particular, this is an improvement. The new Application Model handles multi-application setups, custom preview routing, and media hosts in a far more explicit and manageable way than SiteDefinition ever did. There's work involved in getting there, but the architecture you land on is genuinely better.

5. The API deprecations: manageable on Alloy, more interesting on real sites

CMS 13 means a range of long-standing APIs are obsolete. PageReference and PageData.PageLink are going away, which is part of a push to treat all content generically rather than page-specifically. ContentArea.FilteredItems is replaced by a new filtering interface. Various shell UI utilities have been moved or merged.

On a clean, simple codebase, these are findable and fixable. The compiler surfaces them, you work through the list, and you're done.

On a production codebase with several years of development history, it's a different picture. We've seen real sites where these deprecated patterns are deeply embedded in shared rendering pipelines, base page templates, and utility libraries that everything else depends on. In those cases, the deprecations aren't a tidy checklist and will need a genuine refactoring, which in turn needs time and proper testing coverage.

Our advice is straightforward: start with Optimizely's published list of breaking changes, work through which of those actually affect you specifically, and build a migration plan from there. It sounds obvious, but when you do this upfront, you're going to move faster than finding those breaking changes halfway through.

6. Content Manager, DAM, and the new editorial surface

Content Manager and DAM integration are both now optional packages rather than default inclusions in AddCms(). This is the right call. Not every implementation needs them, and forcing Graph as a dependency for teams not ready to adopt it would create unnecessary upgrade friction.

In practice, if you're upgrading because you want the new capabilities, you're adding both. The explicit opt-in just means being deliberate about it.

The DAM integration deserves a specific mention because it's more involved than a package reference. Before you can wire it up, you need Opti ID in place, an active Graph service provisioned in the DXP portal, and CMP API credentials configured. The integration is built on External Sources, which means DAM assets need to be indexed into Graph before they're even available in the CMS. It's a real integration, not a feature switch on, so, again, set aside proper time to implement it correctly.

Still scratching your head with all the changes in CMS 13, and need some guidance on where to start?

Optimizely partner of the year 2026 might be the best place.

That’s us by the way. Get in touch.

Tobiasz Kulesza: Head of Client Growth; (+48)690806585|tobiasz.kulesza@noaignite.com

Facing complexity? We’re ready to listen.

Big idea? Strategic challenge? Emerging vision? Whether you’re crystal clear or still shaping the path, we’re ready when you are. Leave your details, and we’ll get back to you shortly.

Optimizely CMS 13 is here. These are 6 technical changes you need to know

Still scratching your head with all the changes in CMS 13, and need some guidance on where to start?

Facing complexity? We’re ready to listen.

NoA Ignite wins Optimizely’s Solution Partner of the Year

Sporveien | Built for clarity, made to move

The Royal Mint | From national treasure to digital powerhouse

Optimizely CMS 13 is here. These are 6 technical changes you need to knowOptimizely CMS 13 is here. These are 6 technical changes you need to know

Still scratching your head with all the changes in CMS 13, and need some guidance on where to start?

Facing complexity? We’re ready to listen.

NoA Ignite wins Optimizely’s Solution Partner of the Year

Sporveien | Built for clarity, made to move

The Royal Mint | From national treasure to digital powerhouse

Optimizely CMS 13 is here. These are 6 technical changes you need to know