Optimizely CMS 11 vs 12 vs 13: What Changed?

Understanding what changed across Optimizely CMS versions is critical for migration planning. The CMS 11 to 12 jump was the most disruptive upgrade in the platform’s modern history. The CMS 12 to 13 path is significantly lighter.

Version Comparison

Feature	CMS 11 (.NET Framework)	CMS 12 (.NET Core)	CMS 13 (.NET 10, Preview)
.NET Version	.NET Framework 4.8	.NET 8	.NET 10
Performance	Baseline	3x faster	Similar to CMS 12
DI Pattern	Unity (ServiceLocator)	.NET Core DI	.NET Core DI
Routing	System.Web routing	ASP.NET Core middleware	ASP.NET Core middleware
Content Delivery	MVC rendering	MVC or Content Graph (optional)	Content Graph (mandatory)
Hosting	IIS, Azure (Windows)	Azure, AWS, Linux	Azure, AWS, Linux
Migration Effort	N/A	High (4-12 months)	Medium (CMS 12 to 13 lighter)
Recommendation	Upgrade if possible	Production-ready	Preview only (GA mid-2026)

CMS 11 to CMS 12 Migration Reality

Community Consensus: CMS 11 to CMS 12 is a rebuild, not an upgrade.

Breaking Changes:

• Dependency injection: Unity to .NET Core DI (all ServiceLocator calls must be refactored)
• Routing: System.Web to ASP.NET Core middleware
• Authentication: ASP.NET Membership to ASP.NET Identity
• Configuration: web.config to appsettings.json
• Hosting: IIS to cross-platform (Azure, AWS, Linux)

Migration Effort Estimate:

• Small site (10-50 pages): 2-4 months
• Medium site (100-500 pages): 4-8 months
• Large site (1,000+ pages): 8-12 months

Many organizations stay on CMS 11 (now end-of-life) because migration cost > business benefit. Consider competitive platforms (Sitecore, Umbraco) if facing CMS 11 technical debt.

CMS 12 to CMS 13 Migration

Lighter upgrade than CMS 11 to 12:

• Framework bump: .NET 8 to .NET 10
• Content Graph becomes mandatory (requires credentials)
• API changes: IUrlHelper.ContentLinkTarget() removed, identity management decoupled
• Estimated effort: 2-4 weeks (vs. 4-12 months for CMS 11 to 12)