Optimizely sells its CMS as a managed SaaS and as CMS 12 and CMS 13, .NET applications customers host themselves or on Optimizely DXP. Pages here cover replacing it with Umbraco or Drupal.
Comparing Optimizely CMS with Umbraco for .NET teams: content modeling and blocks, editing and visual building, headless delivery, licensing against MIT software with paid add-ons, SaaS or DXP hosting against self-hosting or Umbraco Cloud, and upgrade cadence.
Comparing Optimizely CMS with Drupal for large multi-site and multilingual estates: content architecture, editorial workflow, the move from .NET to PHP and what that means for the team, hosting freedom, licensing and the partner market for support.
Moving Optimizely CMS 11, 12 or SaaS content to Umbraco: exporting packages or reading content through APIs, mapping page and block types to document types and blocks, moving media, rebuilding visitor-group personalization, and redirecting URLs.
What Optimizely CMS export packages contain: content items, content types, categories, files and visitor groups in .episerverdata format, why permissions do not survive import, the linked-files option, and why a migration to another CMS usually needs API extraction as well.
Cost of ownership by component: Optimizely licenses and DXP or SaaS subscriptions against free Umbraco CMS with optional paid add-ons, hosting, migration, upgrades between LTS releases and the .NET developers who maintain the site.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.