Optimizely CMS vs Umbraco

Optimizely charges recurring fees for the platform itself, and the exact structure depends on whether you run CMS 12 or CMS 13 yourself or use its managed SaaS or DXP offer. Ask the vendor to itemize the license or subscription, the hosting and environments, add-on modules, support tiers and any usage limits. Also confirm what happens to the subscription at renewal, because that is where price changes usually appear. Your own team still pays for developers, infrastructure you manage, and the upgrade work that a managed offer might otherwise cover.

The Umbraco CMS core is published under the MIT license, so there is no per-seat or per-site license fee for the core. Costs remain in three places: optional paid add-ons such as Umbraco Engage and Umbraco Forms, which are licensed per domain, hosting on infrastructure you pay for or on Umbraco Cloud, and the people who build and maintain the site. Before you budget, list which add-ons your current Optimizely features map to, and check the add-on licensing terms for your domain count, including development and test domains.

Migration is a one-time cost. It covers content extraction, mapping page and block types to Umbraco document types and blocks, moving media, rebuilding personalization and setting up redirects, plus integration and testing. Recurring costs begin after go-live: hosting, add-on renewals, maintenance, security patching and upgrades between releases. Ask any implementation partner to quote these as separate line items with the test cycles included, so you can see what is paid once and what continues each year.

Hosting moves from a vendor bundle to a choice. Optimizely SaaS or DXP includes hosting in the subscription, while Umbraco can run on Umbraco Cloud, which is a managed Azure service with environments, backups and a CDN, or on infrastructure you control. The cost driver is who operates the stack: environments, backups, TLS, CDN, monitoring and disaster recovery. Ask for the Umbraco Cloud plan details in writing, and for your own infrastructure, list each component so the comparison covers the same scope.

Upgrades are a recurring cost on both sides, but the timing and the work differ. Umbraco publishes LTS releases with defined end-of-life dates, and Umbraco 13 reaches end of life on December 14, 2026, while Umbraco 17 is the LTS release published on November 27, 2025, according to Umbraco's end-of-service policy. Each upgrade needs .NET work, add-on compatibility checks and regression testing. Ask Optimizely to show its upgrade path and included support for your version, and budget your own team time for each Umbraco LTS cycle.

Both platforms run on .NET, so your existing C# developers carry over, but staffing needs change. Optimizely experience often lives with a partner or specialist agency, while an Umbraco site usually needs in-house or contracted developers who own the codebase, deployments and content model. The ongoing cost is the team that maintains the site. Compare the annual cost of that team, including on-call coverage and the skills needed for security patching, against the vendor and partner fees you pay today.

Ask for a written quote with separate lines for each cost component. For Optimizely, request license or subscription fees, environment counts, add-on modules, support levels, renewal terms and price change conditions. For Umbraco, request the migration scope, add-on licenses by domain count, hosting or Umbraco Cloud plan, environment setup, testing, training and the upgrade plan for the next two years. Ask whether each figure is one-time or annual. DeployOpen plans and implements these migrations under a fixed written scope, so the quote follows from the agreed deliverables.

Several costs appear only after the decision. Teams often miss content rework for block and personalization models, redirect mapping for SEO, visitor group rebuilds, accessibility and performance testing, editor training, and parallel running during cutover. Security monitoring and backups also move onto your side of the line. Ask each bidder how they handle these items and whether they are in scope or excluded, since excluded work tends to return as change requests later.

The switch cost is driven by the size and complexity of the site, not by a single rate. The main components are the migration build (content types, blocks, media, redirects and any personalization rebuild), hosting, the .NET developers who build and maintain the site, and testing. Umbraco CMS itself is MIT licensed and free to download, so the recurring costs sit in hosting, developer time and any paid add-ons such as Umbraco Engage or Umbraco Forms. Ask any partner for a quote built from a written scope that lists each of these components separately, with what is one-time and what recurs.

Duration depends on how many page and block types need mapping, how much media and content must move, how much visitor-group personalization must be rebuilt, and how many integrations sit behind the site. Content volume and the number of templates usually matter more than the platform itself. Ask for a timeline tied to a written scope and a list of assumptions, and check whether the plan includes a parallel run on staging before DNS cutover.

Your team needs to own content governance decisions: which content types survive, how editors will work with blocks, which URLs must be redirected, and who signs off on each environment. Engineering needs access to the current Optimizely code, the database or export files, and the hosting accounts. Editors should be available for acceptance testing. Confirm these roles in the scope before work starts, because gaps here are the most common reason migrations slip.

A team already working in C# and ASP.NET can usually learn Umbraco's document types, composition and Razor views, and can do the migration itself if it has time and clear ownership. The harder parts are reading Optimizely content through its APIs, mapping block structures, and moving personalization logic, which need careful testing. Many teams split the work: internal staff own editorial decisions and frontend templates, while an outside team handles extraction, mapping scripts and hardening. Decide this based on capacity and deadline risk.

Umbraco Cloud is a fully managed service on Microsoft Azure with automatic backups, a global CDN, HTTPS and Development, Staging and Live environments, and Umbraco Deploy to move content and structure between them. Self-hosting gives you control over infrastructure, network placement and cloud account, and lets you run on any host that supports the .NET version Umbraco requires. Umbraco 17 is the current LTS release, and the end-of-service policy sets different hosting end dates for Umbraco Cloud and for extended support. Choose based on your data residency rules, operations capacity and whether you need Azure-specific services.

Umbraco Forms runs without restriction locally, but it needs a valid license on a public domain. Its licenses are sold per domain, also cover subdomains, include two development or testing domains, and apply one license per installation. Umbraco Engage requires a license covering one production domain and up to two development or testing domains. Before you plan staging, list every public hostname, including subdomains and test URLs, and confirm with Umbraco how each one is counted. Check the current licensing pages, since terms are the vendor's to state.

Optimizely visitor groups, experiments and any analytics history do not transfer automatically into Umbraco. Visitor-group rules usually need to be rebuilt as Umbraco logic or as Umbraco Engage segments, and historical analytics stay in the source system unless you export them. Decide early whether you need the historical data, where it will be stored, and who can access it. Ask your provider to document which personalization rules are rebuilt, which are dropped, and which data is archived, so marketing and privacy teams can approve the plan.