SAP Engagement Cloud: Emarsys Edition vs Enterprise Edition, Compared Properly

Since SAP renamed Emarsys to SAP Engagement Cloud in February 2026, every licensing conversation we’ve had includes the same question: which edition? The rename itself was straightforward. The choice between the Emarsys edition and the enterprise edition is not, because SAP publishes neither a feature matrix nor prices, and most comparisons online stop at “enterprise has more AI”.

We went through the current SAP price list (August 2026), the official announcements, and the Q2 2026 release notes. Here’s the comparison we wished existed, including the price gap in percent and a crossover point that surprised us.

TL;DR: Same platform, two packaging philosophies. The Emarsys edition is modular: a lean core plus a dozen individually licensed options. The enterprise edition is all-in: one subscription without separate option SKUs, plus exclusive Joule AI and Business Areas governance, positioned by SAP around native Business Data Cloud integration, with a consumption metric (capacity units) on top. At entry volumes the enterprise edition lists at roughly double a comparably equipped Emarsys stack; from about 5 million contacts it flips and becomes 20 to 35 percent cheaper. Below that line, most companies are better served by the Emarsys edition.

Two Editions, One Platform

First things first: this is not two products. SAP’s own release notes deliver features “to all editions unless otherwise noted”, and partner sources describe moving from one edition to the other as chiefly a commercial and governance change rather than a replatforming. What differs is packaging, a handful of exclusive capabilities, and the pricing model.

SAP Engagement Cloud, Emarsys edition is the product formerly known as SAP Emarsys Customer Engagement, continued unchanged; SAP’s own announcement stresses that everything customers know and use today carries on as before. It stays the modular offering it always was.

SAP Engagement Cloud, enterprise edition became generally available on February 19, 2026. It targets corporations with several brands, regions, or subsidiaries, and companies that want their engagement platform wired deep into the SAP stack.

Feature and Module Comparison

The shared core covers what made Emarsys strong: email, web, SMS, mobile push and in-app, mobile wallet, digital ads, the Automation Center, segmentation, and personalization.

* SAP publishes no side-by-side feature matrix, but the enterprise edition has an official Feature Scope Description on the SAP Help Portal. It documents channels, automation, segmentation, personalization, content management, B2B corporate accounts, analytics, Business Areas, and external database access; it does not (yet) mention Predict recommendations, Smart Insight, Loyalty, or the industry accelerators. The remaining starred “Included” cells are an informed inference from the price-list structure (the enterprise edition has no separate option SKUs) and SAP’s release policy of shipping features to all editions unless noted, not a verified entitlement. Validate the exact scope for your scenario with SAP before contracting.

Two structural points deserve attention, because they change architectures, not just invoices.

Multi-Entity: Business Units vs Business Areas

The Emarsys edition scales to multiple brands or subsidiaries with additional business units: separate tenants, licensed per tenant. Clean isolation, but the costs stack up fast, and cross-tenant governance is your problem.

The enterprise edition takes the opposite stance. Extra tenants aren’t offered as an enterprise add-on; the current price list attaches exactly two things to the enterprise edition, a test tenant and capacity units. Multi-entity setups run through Business Areas: one tenant, central brand governance, local execution, access control per area, which SAP’s own material describes as structuring data and access within a single account. For a group with dozens of business units this is the single biggest functional argument for the enterprise edition. The flip side: if your compliance team demands hard tenant separation per entity, that becomes a bespoke conversation with SAP rather than a line item on the price list.

Capacity Units: the Fine Print

The enterprise edition adds a consumption metric on top of the contact-based subscription: capacity units, a ratio of services consumed. Nota bene: SAP’s public materials specify neither the included volume nor how channels convert to capacity units. Before signing an enterprise edition contract, get both in writing. We’ve seen enough consumption-based cloud contracts to know that an undefined metric is where budgets go to die.

The Price Gap, in Percent

SAP doesn’t publish absolute prices and neither will we (our pricing guide covers typical ranges). But relative comparisons at list price are fair game, and they’re more useful anyway. We compared the enterprise edition against an Emarsys edition stack equipped with the two options most enterprise buyers would license anyway (advanced integration and omnichannel), at identical contact volumes:

Against a bare-bones Emarsys core (no options), the enterprise edition costs 1.7 to 4.5 times as much depending on volume. That comparison flatters nobody, but it matters: if all you need is email plus automation, the modular edition is in a different price class entirely.

The pattern is no accident. The enterprise edition’s price curve starts high and falls steeply; the Emarsys edition starts low and falls gently. The curves cross at roughly 5 million contacts. Below the line, modularity wins. Above it, the bundle wins, and by a margin that grows with scale.

When to Choose Which

Choose the Emarsys edition when:

• Your contact volume is below roughly 5 million and you don’t need every module
• You run one brand, or a small number of brands that tolerate separate tenants
• You want to start lean and add options as the program matures
• You are an existing Emarsys customer and nothing is pushing you to change: nothing changes for you

Choose the enterprise edition when:

• You manage many brands, regions, or subsidiaries and want central governance with local execution (Business Areas)
• Your engagement strategy depends on live SAP data: Business Data Cloud, CDP audiences, real-time ERP signals like delivery delays triggering communication
• You’d license most of the optional modules anyway, and your volume sits near or above the crossover
• Joule-driven campaign management is on your roadmap

The honest summary: prima vista the enterprise edition looks like the premium choice for everyone, but the numbers say it’s a scale product. Mid-market B2C brands, which is exactly where Emarsys has always been strongest, will usually get more value per euro from the modular edition.

No Forced Migration

One more thing worth stating plainly, because we keep hearing the worry: there is no forced migration. SAP’s official line is that existing capabilities remain available and customers adopt new capabilities incrementally. No announced deadline, no published upgrade guide, and for existing customers an announced supported transition including asset migration; partner sources describe the switch as primarily organizational, with manageable technical work rather than a replatforming. If you’re happily running the Emarsys edition today, the sensible move is to stay put and re-evaluate when your volume or your governance needs approach the thresholds above.

Key Takeaways

• Two editions, one platform: the difference is packaging, governance features, and price mechanics, not technology
• The Emarsys edition stays modular; the enterprise edition is a single all-in subscription that adds Joule and Business Areas and is positioned by SAP around native BDC/CDP integration
• Extra tenants exist only on the Emarsys edition; the enterprise edition handles multi-entity through Business Areas in one tenant
• At list price, the enterprise edition runs about double a comparable Emarsys stack at entry volumes, comes within roughly 5 to 12 percent between 500,000 and 2 million contacts, and wins by 20 to 35 percent above roughly 5 million
• Capacity units are undefined in public documentation: clarify included volumes before signing
• No forced migration between the editions has been announced

If you’re weighing the two editions for a concrete scenario, we’ll gladly run the numbers with you, including the discount conversation with SAP. That part of the exercise is, de facto, where most of the money is made or lost.