Sitecore vs Umbraco: which to choose

Sitecore vs Umbraco: when each option fits

A .NET team facing a Sitecore renewal or a lifecycle decision usually wants two things at once: a platform that is supportable for the next several years and a stack where its C# developers stay productive. Sitecore fits best when the organization values an integrated marketing suite, can accept SaaS-only delivery through SitecoreAI, and is ready to rebuild front ends on Next.js. Sitecore's migration guide notes that SitecoreAI requires Headless SXA and that existing MVC sites must be ported, so that path is a rebuild, not a configuration change. Teams that depend on Sitecore's bundled personalization, Marketing Automation or EXM should weigh those features as part of the purchase, not as optional extras.

Umbraco fits best when the organization needs to host the CMS in its own data center or cloud account, wants an MIT-licensed core, and intends to keep .NET skills in place. The Umbraco-CMS repository is MIT licensed, the current documentation requires .NET 10.0 or higher, and installation supports SQLite or SQL Server. Headless delivery is available through the opt-in Content Delivery API, so a Next.js or other front end can be built without abandoning the .NET back end. Confirm with your architects that the chosen database, hosting model and .NET version match your standards before comparing costs.

The decision turns on three checks. First, personalization requirements: Umbraco Engage covers personalized experiences, A/B testing and targeted campaigns, but it is a separately licensed add-on, so map each XP personalization rule to a feature before assuming parity. Second, hosting constraints: self-hosting keeps infrastructure under your control, while Umbraco Cloud on Microsoft Azure takes on backups, CDN, HTTPS and environment promotion. Third, add-on licensing: Umbraco Engage and Umbraco Forms are licensed per production domain, including subdomains, so count domains across brands and regions when you model the total cost of ownership.

Which platform fits which scenario

This table matches common Sitecore exit scenarios to the platform that fits best, with the reason tied to supplied facts about SitecoreAI, Umbraco Cloud and self-hosted Umbraco. Read each row against your own hosting, personalization and skills requirements, then confirm the open points with Umbraco, Sitecore or your implementation partner before deciding.

Scenario	Better fit	Reason
Need a SaaS headless CMS with no servers to run	SitecoreAI or Umbraco Cloud	SitecoreAI is a SaaS CMS, and Umbraco Cloud is a managed service on Microsoft Azure with backups, CDN and environments included.
Must host in your own data center	Self-hosted Umbraco	Umbraco CMS is MIT licensed and runs on SQL Server or SQLite, so it can run on infrastructure you control. SitecoreAI is SaaS only.
Need xDB-style personalization and analytics	Sitecore XP or a rebuild with separate tools	Sitecore's guide says xDB, email marketing content and personalization do not migrate to SitecoreAI. Umbraco Engage covers personalization and A/B testing, but it is a licensed add-on, so confirm its feature fit.
Team has .NET and C# skills but no PHP or Python	Self-hosted Umbraco	Umbraco runs on .NET 10.0 or higher, so existing C# and .NET staff can build and maintain it without moving to another language stack.
Need a managed Azure host with staging and live environments	Umbraco Cloud	Umbraco Cloud provides Development, Staging and Live environments, automatic backups and Umbraco Deploy for syncing content and structure.
Headless front end on Next.js or another framework	Umbraco with the Content Delivery API, or SitecoreAI	The Content Delivery API is opt-in and returns JSON, so enable it in configuration. Confirm preview and member authentication needs before design.
Need a long support runway	Umbraco 17 LTS	Umbraco 17 is LTS, published November 27, 2025, with end of life on November 27, 2028 and XLTS ending November 27, 2030.
Public-facing forms or marketing add-ons on a public domain	Umbraco with licenses, or confirm alternatives	Umbraco Forms and Umbraco Engage require valid licenses on public domains. Ask Umbraco for the license cost for your domain count.

What Umbraco 17 covers and what it does not

The core Umbraco CMS is published under the MIT license, and its source sits in the public Umbraco-CMS repository, so your team or a partner can review, host and maintain the code that runs your site. Umbraco 17 is a long-term support release published on November 27, 2025, with end of life on November 27, 2028. Current documentation requires .NET 10.0 or higher and supports installation on either SQLite or SQL Server.

Licensing: The MIT license covers the CMS itself. Confirm with your counsel how it applies to your custom components and to the licensed add-ons, which carry their own terms.
Lifecycle: Umbraco 17 LTS ends on November 27, 2028, and extended support runs to November 27, 2030. Plan the next upgrade well before those dates.
Database: SQLite suits development and small deployments, while SQL Server fits estates that already have backup and high availability tooling. Confirm supported SQL Server versions for your release.
Runtime and hosting: When self-hosted, your operating system, .NET runtime patching, web server and database operations stay with your team or your provider.

Check the requirements page before sizing hosts, because supported database and operating system combinations are the details most likely to change between releases.

Capabilities compared against supplied facts

This table sets Sitecore's SitecoreAI path against Umbraco on the points that decide a .NET migration: licensing, runtime, headless delivery, personalization, forms, hosting and lifecycle. Where the sources do not settle a point, the cell tells you what to confirm with the vendor or in a proof of concept before you commit.

Capability	Sitecore (XP or XM, SitecoreAI)	Umbraco
Licensing of the core	Commercial licensing for XP and XM. SitecoreAI is a SaaS subscription. Confirm terms with Sitecore.	Core CMS published under the MIT license on GitHub. Add-ons carry their own licenses.
Runtime and database	SitecoreAI is SaaS only. Self-hosted XP or XM runs on Sitecore's own supported stack. Confirm versions with Sitecore.	Requires .NET 10.0 or higher. Installs on SQLite or SQL Server.
Headless API	SitecoreAI requires Headless SXA, so existing MVC sites must be ported to Next.js.	Content Delivery API returns JSON. It is opt-in and must be enabled in configuration.
Personalization and A/B testing	Built into XP. SitecoreAI has no xDB, so personalization rules must be rebuilt, not migrated.	Umbraco Engage is a licensed add-on for personalization, analytics and A/B testing. Confirm feature fit.
Forms	Sitecore Forms is part of the XP estate. Confirm which forms features survive the move.	Umbraco Forms runs unrestricted locally. A license is required on a public domain, sold per domain.
Hosting models	SitecoreAI is SaaS only, which may conflict with a requirement to host in your own data center.	Self-host on your own infrastructure, or use Umbraco Cloud, a managed service on Microsoft Azure.
Lifecycle dates	Confirm the current support dates for the XP version you run with Sitecore's lifecycle documentation.	Umbraco 17 is an LTS release published November 27, 2025, end of life November 27, 2028.

Where your content and data live under each model

Each model places your content database, backups, identity and audit trail in a different party's hands. The four cards below set out who operates each layer, which facts are fixed in the vendor documentation, and what your compliance team should confirm before choosing.

Self-hosting on your own infrastructure

With Umbraco self-hosted on your own cloud account or data center, your team controls the SQL Server or SQLite database, the media files, backup schedules and the identity provider in front of the back office. Umbraco is MIT licensed, so no vendor holds custody of the content. The trade-off is that your staff own patching, failover and restore testing. Confirm which SQL Server edition and backup retention your policy requires, and who holds the keys to the database host.

Umbraco Cloud on Azure

Umbraco Cloud is a fully managed service on Microsoft Azure that includes automatic backups, a global CDN, HTTPS and Development, Staging and Live environments, with Umbraco Deploy moving content and structure between them. Your content sits in a vendor-operated Azure tenancy, so data residency, sub-processor lists and the Azure region must be checked against your requirements. Ask how restores are tested and who can access production backups.

SitecoreAI as a SaaS service

SitecoreAI is a composable SaaS CMS, so content, the editing experience and delivery run on Sitecore's platform rather than infrastructure you choose. Sitecore's migration guide states that xDB data, email marketing content and personalization do not migrate, so any visitor data held in XP must be exported or rebuilt before cutover. Ask Sitecore where content and logs are stored, how export works during an exit, and which contractual terms apply to data deletion.

Identity and compliance evidence

Each model splits identity, logging and evidence differently. Self-hosting puts sign-in, back-office access logs and backup encryption in your scope, and your assessor will expect those controls to be documented. Umbraco Cloud and SitecoreAI keep much of that operation with the vendor, so you must request their assurance reports and map them to your own controls. DeployOpen prepares systems, controls and evidence for assessments, but it does not issue audit reports, attestations or certifications; independent auditors and certification bodies do that work.

How Umbraco lifecycle dates affect a plan

The first decision is which Umbraco release a new build targets. Umbraco 17 is the current long-term support release, published on November 27, 2025, with end of life on November 27, 2028, end of Extended Long-Term Support (XLTS) on November 27, 2030 and end of service on Umbraco Cloud on November 27, 2031. Umbraco 13 is the previous LTS release from December 14, 2023. It reaches end of life on December 14, 2026, with XLTS ending December 14, 2028 and Umbraco Cloud service ending December 14, 2029. A site still on Umbraco 13 therefore has a hard support deadline within the same year as a typical Sitecore planning cycle, so it should not be the target for new work.

Between end of life and the final end of service, the policy has phases that change what you pay for and where the site runs. Extended Long-Term Support is a phase of up to 24 months during which hosting continues on Umbraco Cloud. After XLTS ends, a project can run on dedicated resources for 12 months. Those 12 months are a bridge, not a plan. Model the self-hosted run cost, security patching and staffing for the dedicated-resource period as a recurring line item from day one, and do not assume the bridge will carry you through a later Sitecore 10.4 retirement window.

Map these dates against your own Sitecore 10.3 and 10.4 timelines in one table: the Umbraco release you will launch on, its end of life, XLTS and Cloud end dates, and each Sitecore support milestone. Then ask your implementation partner and Umbraco directly to confirm every date, since the policy can change and a quote should state which version and support tier it assumes. Also confirm which Umbraco version your add-ons, such as Umbraco Engage and Umbraco Forms, support, because licensing and compatibility can differ from the core release schedule.

Cost components on each side and what drives them

Sitecore and Umbraco costs fall into different buckets: licenses or SaaS subscriptions, partner fees, add-on domain licenses, hosting, and the one-time build and migration work. Compare each bucket on both sides, then ask every vendor and partner to price the same scope, environments and domain count.

Sitecore license or SaaS subscription

Sitecore XP and XM are licensed products, while SitecoreAI is sold as a SaaS subscription. Both are recurring, and the cost depends on the edition, the product set and the number of environments you need. Ask whether Sitecore's subscription covers the marketing, personalization and forms modules you use today, and whether it changes at renewal. Because SitecoreAI does not carry xDB, personalization or email marketing over, check which of those modules you would still pay for elsewhere.

Umbraco license and add-on domain fees

The Umbraco CMS core is MIT licensed, so the recurring fee is for add-ons, not the CMS itself. Umbraco Engage and Umbraco Forms need valid licenses on public domains. Forms licenses are sold per domain, cover subdomains and include two development or testing domains, with one license per installation. Engage covers one production domain and up to two development or testing domains. Count public domains, subdomains and test domains before you request a quote.

Hosting on your infrastructure or Umbraco Cloud

Self-hosting on your own Windows, Linux or cloud accounts means you pay for compute, SQL Server or SQLite storage, CDN, backups, monitoring and staff time. Umbraco Cloud is a managed Azure service with backups, a global CDN, HTTPS and Development, Staging and Live environments, billed as a recurring service. Ask each option for its environment count, backup retention, traffic assumptions and what happens at the end of the Umbraco version support window.

Build and migration effort

This is usually the largest one-time cost. Rebuilding Sitecore renderings as Umbraco views or a headless frontend, mapping templates to document types, moving media, and replacing personalization and forms all take skilled .NET time. Sitecore's migration guide notes that xDB data, email marketing content and personalization do not carry over, so budget for rebuilding those separately. Ask partners to price each content type, site and integration as a line item.

Upgrades, testing and support

Both sides recur here. Umbraco 17 is an LTS release with a defined support lifecycle, so plan upgrades on that cadence and fund regression testing for your custom code and add-ons each time. On the Sitecore side, support dates and upgrade paths set the timing. Ask whether your partner's retainer covers security patches, add-on upgrades and test automation, and whether support is priced per hour, per month or per incident.

Team skills and staffing mix

Teams that already know C# and .NET keep most of their existing skills, which lowers the cost of hiring and of maintenance. Umbraco does not need a new language, but it does need developers who understand its document types, Content Delivery API and add-on configuration. Price internal staff time, contractor rates and training separately. Ask partners to state the roles, seniority and hours assumed for build, migration and run phases.

What a move from Sitecore to Umbraco involves

The sequence turns a Sitecore XP or XM estate into an Umbraco site that you host, with each stage ending in a documented check that the content, templates and front end match what was approved. The detailed migration page covers the mechanics in depth.

Inventory templates, items, renderings and media
Your team, with the Sitecore developers and content owners, lists every template, site definition, rendering, placeholder, media library folder and language in scope. Each item is tagged as migrate, rebuild or retire. Analytics, xDB contacts and personalization rules are recorded separately because they do not move as content. The output is a signed inventory that becomes the scope baseline for the rest of the work. Ask the implementation partner to deliver it in writing before build starts.
Map templates to Umbraco document types
Each approved Sitecore template is mapped to an Umbraco document type with its fields, compositions, and content hierarchy. Shared fields become compositions, and multilingual fields are set up as variant properties. Naming, permissions and the editorial tree are agreed with content owners at this stage. The check is a mapping sheet that lists each source template, target document type, and any fields that were merged or dropped, with the owner's sign-off.
Rebuild renderings as views or headless components
Sitecore renderings are rebuilt either as Umbraco Razor views and partial views on the server, or as a separate frontend that reads JSON from the Content Delivery API. The Content Delivery API is opt-in and must be enabled in configuration, so the team confirms that setting and its access rules before the frontend is wired up. Preview of unpublished content requires an API key, and protected content needs member authentication. The output is a component library and a working template for each layout the site uses.
Replace Sitecore Forms and personalization
Sitecore Forms are rebuilt in Umbraco Forms or in the chosen frontend, with submission handling and data retention decided up front. Personalization and A/B testing are different: Umbraco Engage is a licensed add-on, so the team compares its features with the Sitecore personalization rules that were in use and documents any gap. Engage and Forms licences are per domain, so the number of production and test domains is recorded. The check is a feature-by-feature register with each item marked as rebuilt, replaced, licensed or dropped.
Migrate content and media
Content and media are moved with a scripted import that preserves identifiers, URLs, redirects and locale variants. Sitecore content is extracted through the serialization or export route the team has chosen, and media files are copied with their metadata. The team runs the import against a development environment first and records counts per content type and language. The check is a reconciliation report that compares source and target counts and lists every URL that changed, with a redirect plan for each one.
Choose self-hosting or Umbraco Cloud
The hosting decision is made before the production build, because it sets the environments, backups and deployment model. Umbraco Cloud is a managed service on Microsoft Azure with automatic backups, a global CDN, HTTPS, and Development, Staging and Live environments. Self-hosting gives the organization control of the network location, database and patching, and the cost of running it shifts to your team or partner. The check is a written decision record that names the database choice, SQL Server or SQLite, the hosting location, and who owns patching and backups. Umbraco 17 is the LTS release with end of life on November 27, 2028 and Umbraco Cloud service end on November 27, 2031, so the record should show the planned upgrade path.
Run in parallel and cut over
The Sitecore site and the Umbraco site run side by side for a period agreed in the plan, with traffic routed to Umbraco only after acceptance testing passes. Editors use both systems during the overlap, and any content changed in Sitecore during this time is re-synchronized or frozen by agreement. Monitoring, redirects, search engine checks and rollback steps are rehearsed in advance. The cutover is complete when acceptance testing signs off, redirects return expected responses, and Sitecore is set to read-only with its licence and data retention obligations recorded.

Questions buyers ask before hiring help

How much effort does a move from Sitecore to Umbraco take?

Effort depends mostly on how much of the Sitecore estate has to be rebuilt rather than copied. The main drivers are the number of sites and languages, how many renderings and components need a new Umbraco view or a headless front end, the volume and state of content and media, and how much personalization, forms and marketing automation sit inside the current solution. Sitecore's own migration guidance says xDB data, email marketing content and personalization do not migrate to SitecoreAI, and the same rebuild logic applies to any Umbraco move. Ask for a written inventory of templates, renderings, sites, languages, forms and integrations before any estimate is set. No effort figure is given here because none is supplied for this comparison.

How long does a Sitecore to Umbraco migration usually take?

Timeline is set by scope, not by the platform alone. The longest items are usually the front-end rebuild, content and media quality checks, and replacing personalization or A/B testing that Sitecore provided. Parallel running with the existing Sitecore site, the number of approval cycles for content and design, and any integrations with CRM or identity systems also add time. Umbraco's own release dates do matter for planning: Umbraco 17 is an LTS release published on November 27, 2025, with end of life on November 27, 2028. Confirm the target version and its support window against the Umbraco end-of-service policy before fixing a schedule. A written scope will set the duration for your environment.

What does the client team need to provide during the move?

The client team needs to make decisions and provide access that only the organization can supply. Typical needs include:

Named content owners who can approve structure, copy and sign-off for each site and language.
Access to the current Sitecore environments, serialized items, media libraries and any analytics or forms data that must be retained.
Decisions on which personalization rules, forms and campaigns are rebuilt, retired or moved to a separate tool.
Hosting, identity, DNS, certificate and backup responsibilities, plus a named contact for security review.

Without these inputs, the rebuild stalls at the content and design stages. Confirm the exact list in the written scope.

Can a .NET team run Umbraco without outside help?

Yes, a team with C# and ASP.NET skills can run Umbraco, and it does not need to learn PHP or Python to do so. Current Umbraco documentation requires .NET 10.0 or higher and supports installation with a SQLite or SQL Server database. The MIT license on the Umbraco-CMS repository means the core can be used and modified without a core license fee. Day-to-day operations still need skills in patching the .NET runtime, database administration, backup testing, security hardening, monitoring and upgrade planning across LTS releases. Teams that have not run a public CMS in production before often bring in outside help for the first upgrade cycle and the initial hardening, then keep the work in-house.

Which Umbraco add-ons need a license, and how is it counted per domain?

Umbraco Engage and Umbraco Forms are licensed add-ons, while the core CMS is MIT licensed. For Umbraco Engage, running it on a public domain requires a valid license covering one production domain and up to two development or testing domains. For Umbraco Forms, the license is sold per domain, runs unrestricted locally, covers subdomains, includes two development or testing domains and allows one license per installation. Check each add-on's terms against your domain list, including subdomains and staging hosts, before you commit to a feature set. Pricing for these licenses is not supplied here, so request the current price for your domain count from Umbraco.

Is Umbraco Cloud or self-hosting more expensive to operate?

The answer depends on which operating tasks your team already performs well, and no like-for-like price comparison is supplied here. Umbraco Cloud is a managed service on Microsoft Azure with automatic backups, a global CDN, HTTPS and Development, Staging and Live environments. Self-hosting removes the platform fee but moves hosting, backups, CDN, patching, monitoring and on-call response to your team or a partner, and those costs recur. Umbraco's end-of-service policy also matters: hosting on Umbraco Cloud continues for the duration of Extended Long-Term Support, and projects can then run on dedicated resources for 12 months after XLTS ends. Ask for a cost model that lists hosting, staff hours, licenses, backup storage and upgrade effort by year.

What should the quote for an Umbraco migration include?

A useful quote lists each component separately so that you can compare it with internal effort. Ask for the following in writing:

Discovery and inventory of Sitecore templates, renderings, sites, languages and integrations.
Umbraco build work for document types, views or a headless front end using the Content Delivery API.
Content and media migration, with a validation plan and a record of what is not migrated.
Replacement plan for personalization, A/B testing, forms and analytics, with license lines for any Umbraco add-on.
Hosting setup, backup and restore testing, security review and handover.

DeployOpen plans, implements, hardens, backs up, upgrades and documents self-hosted platforms in your own infrastructure, and work is normally fixed-scope with deliverables and timelines agreed in writing before it starts. A quote follows from that written scope.

Does the Umbraco Content Delivery API expose unpublished or protected content?

No, not by default. The Content Delivery API is opt-in and must be enabled in configuration. It returns unpublished content for preview only when an API key is supplied, and it serves protected content only when member authentication is enabled. Engineers should confirm these settings during design, test them with real preview and member scenarios, and review them as part of the security assessment before go-live. Where a headless front end is built on the API, the front end needs its own caching and access rules as well.

When staying on Sitecore is the better decision

Staying on Sitecore is the better decision when the marketing stack is the reason the platform exists in your organization. Sitecore XP bundles content management with xDB analytics, Marketing Automation, EXM and personalization in one vendor relationship, and if your marketing team runs campaigns, experiments and segmented journeys on those tools every week, replacing them carries a cost that a CMS comparison does not show. Umbraco Engage covers personalization and A/B testing, but it is a separate licensed add-on with its own configuration and data model, so count it as a new integration rather than a like-for-like replacement.

Staying also makes sense when SitecoreAI already meets your requirements and your teams are comfortable with its model. Sitecore describes SitecoreAI as a composable SaaS CMS that requires Headless SXA, and its migration guide states that the SitecoreAI pathway does not migrate xDB data, email marketing content or personalization, which must be rebuilt. Before you decide, list every personalization rule, email flow and form that depends on XP, and ask Sitecore and your implementation partner to confirm which of them have a SitecoreAI equivalent and what each rebuild costs in your own environment. If the answer is a short list, the SaaS path may be the cheaper and lower-risk choice.

Finally, stay on Sitecore if your estate is stable, well supported and run by a team that already operates it well. A move to Umbraco means rebuilding renderings as views or a headless frontend on the Content Delivery API, re-modelling templates as document types, and retraining editors and developers, so the case for leaving should rest on a concrete driver such as a licensing renewal, a hosting requirement or a support date. Ask Sitecore for its current lifecycle commitments for your version, and compare them with the Umbraco 17 LTS dates on your own roadmap before you commit to either path.

How DeployOpen helps evaluate, implement or migrate to Umbraco

DeployOpen is a Chainscore Labs company that plans, implements, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own infrastructure. For Sitecore vs Umbraco, we start with a written scope that fits your Sitecore estate, your .NET team and the hosting model you need, whether self-hosted or Umbraco Cloud.

How we scope

Inventory your Sitecore sites, templates, renderings, languages and media before any comparison of Umbraco options
Confirm which XP features you use, such as xDB, Forms, Engage-style personalization or email, and which must be rebuilt or replaced
Agree the hosting target, SQL Server or SQLite, and the .NET 10 runtime in writing, with fixed scope and deliverables

How we build

Build the Umbraco 17 LTS foundation with document types that mirror your content model and editor workflows
Decide per site whether to render with Umbraco views or a headless frontend on the opt-in Content Delivery API
Assess licensed add-ons such as Umbraco Engage and Umbraco Forms against your domain count and confirm license coverage before go-live

How we hand over

Document architecture, content model, migration mappings, environment configuration and the decisions behind each one
Provide test evidence for content migration, access control, member authentication and API behavior before cutover
Train your .NET and editorial teams on operating, backing up and upgrading the platform in your own environment

How we support

Offer ongoing support, upgrades and continuous testing as a retainer after handover, scoped in writing
Plan upgrade paths around Umbraco's published LTS and end-of-life dates so your estate stays supported
Prepare systems and evidence for compliance assessments, while independent auditors issue any formal reports

Sitecore vs Umbraco