Skip to content
Optimizely

When to Choose Optimizely CMS 12 (and When Not To)

Optimizely CMS 12 occupies a specific niche in the DXP market: .NET enterprise organizations that need content management, commerce, and experimentation under one roof. This page provides a decision framework for evaluating whether Optimizely is the right fit.

  • Need experimentation culture — A/B testing, feature flags (Web/Feature Experimentation products)
  • Commerce + content together — Optimizely Commerce integration
  • On Episerver and need to upgrade — .NET Core modernization path
  • Want DXP managed hosting — Azure PaaS, reduced DevOps overhead
  • .NET developer team — C#, .NET 8/10 expertise
  • Mid-market to enterprise — 500-5,000 employees (typical customer profile)
  • On CMS 11 and migration cost > benefit — Stay on CMS 11 until business case clear (or evaluate competitors)
  • Budget-constrained — Optimizely licensing more expensive than Umbraco (open-source)
  • Don’t need commerce or experimentation — Sitecore or Umbraco may be better fit
  • Want fully managed SaaS — Optimizely DXP is PaaS (you still manage app), not SaaS
  • Many CMS 11 sites staying on CMS 11 (migration effort high, end-of-life acceptance)
  • E-commerce-focused organizations favor Optimizely (Commerce + Content + Experimentation)
  • Mid-market companies migrating to lighter-weight options (Umbraco, Contentful) due to cost

Install Alloy demo site (CMS 12 starter template):

Terminal window
dotnet new -i EPiServer.Net.Templates
dotnet new epi-alloy-mvc --name MyOptimizelySite
cd MyOptimizelySite
dotnet run

Navigate to /EPiServer/CMS to complete setup.

  • Optimizely Documentation: docs.developers.optimizely.com
  • Optimizely World: Community forum
  • OMVP Program: Optimizely Most Valuable Professional (expert community)
  • Optimizely Academy: Training and certification
  • If on CMS 11: Evaluate CMS 11 to 12 migration vs. platform switch
  • If starting new: Choose CMS 12 (CMS 13 GA expected mid-2026)
  • If on CMS 12: Monitor CMS 13 GA release for upgrade planning

Q: Should I use CMS 12 or wait for CMS 13?

Section titled “Q: Should I use CMS 12 or wait for CMS 13?”

A: Use CMS 12. CMS 13 is preview-only (GA target: March 31, 2026). CMS 12 is stable, production-ready, and will be supported for years. Upgrade to CMS 13 after GA release.

A: Yes. Episerver rebranded to Optimizely in 2021. CMS 12 is the first major release under the Optimizely brand. When searching for solutions, you’ll find content under both names.

Q: Can I migrate from CMS 11 to CMS 12 without rewriting code?

Section titled “Q: Can I migrate from CMS 11 to CMS 12 without rewriting code?”

A: No. CMS 11 to 12 is a major breaking change (.NET Framework to .NET Core). Expect 4-12 months migration effort depending on site size and complexity. Many organizations treat this as a rebuild.

A: Basic personalization (visitor groups: browser, device, geolocation). Advanced real-time personalization requires ODP (Optimizely Data Platform), a separate product with separate licensing.

Q: What’s the difference between DXP and self-hosted?

Section titled “Q: What’s the difference between DXP and self-hosted?”

A:

  • DXP: Optimizely-managed Azure PaaS (higher cost, managed infrastructure, auto-scaling)
  • Self-hosted: You manage infrastructure (lower cost, full control, requires DevOps team)

A: No, Content Graph is optional in CMS 12. In CMS 13, Content Graph is mandatory (enabled by default, cannot be disabled).