SAP Emarsys Is Now SAP Engagement Cloud: What Changes, What Stays, and What It Means

On 19 February 2026, SAP renamed SAP Emarsys to SAP Engagement Cloud and introduced a second edition, the enterprise edition. For existing customers the technical impact is close to zero. For companies still on SAP Marketing Cloud, the rename is a reminder that their own platform reaches end of support in December 2026.

TL;DR: SAP Emarsys has been called SAP Engagement Cloud since 19 February 2026. The existing product continues as the Emarsys edition, unchanged; the new enterprise edition adds governance for multi-brand, multi-region organisations. Existing customers keep their features, integrations and contracts. The real action item concerns SAP Marketing Cloud: support ends in December 2026, and anyone who has not started moving has about three months left.

What happened on 19 February 2026?

SAP announced in Walldorf that SAP Emarsys becomes SAP Engagement Cloud. The announcement frames engagement as an enterprise capability: personalised, AI-supported engagement powered by SAP Business Data Cloud, connecting customer insight with operational execution. SAP also points to the platform’s recognition in the 2026 Gartner Magic Quadrant for Personalization Engines.

This was no merger and no replatforming. The product, the team and the infrastructure remain; what changed is the name, the positioning and the edition structure:

• Emarsys edition: the existing SAP Emarsys product. SAP states explicitly that existing capabilities remain available and customers adopt new ones incrementally.
• Enterprise edition: available from 19 February 2026, with “advanced administration, governance, and content and data-control capabilities for organizations operating across multiple brands, regions, and teams”, in SAP’s words.

Why “Engagement Cloud”?

The word “marketing” is missing from the new name, and that is deliberate. Emarsys started as an email and omnichannel marketing tool. Today the same platform reacts to commerce events, loyalty milestones and service signals, and SAP wants it to be read as the engagement layer of the whole customer lifecycle rather than the marketing department’s campaign tool. We see the same shift in our projects: a growing share of the automations we build are triggered by an order, a delivery or a service case, not by a campaign calendar.

The name also completes the family. SAP Sales Cloud, SAP Service Cloud, SAP Commerce Cloud and now SAP Engagement Cloud read as one portfolio, and the link to Business Data Cloud signals where the data for personalisation is meant to come from.

Emarsys edition vs enterprise edition

The two editions share one platform. The differences are packaging, a small number of exclusive capabilities and price mechanics:

	Emarsys edition	Enterprise edition
Core channels, automation, segmentation, personalisation	Included	Included
Packaging	Core plus individually licensed options	One subscription without separate option SKUs
Several brands or entities	Additional business units (separate tenants)	Business Areas inside one tenant
Joule for campaign management	Not available	Exclusive (early adopter)
Consumption metric	Contacts (plus option-specific metrics)	Contacts plus capacity units

The enterprise edition’s scope is documented in its feature scope description on the SAP Help Portal. We compare the two editions, including the price gap by contact volume, in SAP Engagement Cloud: Emarsys edition vs enterprise edition. The short version: below roughly 5 million contacts, and for companies with one or a few brands, the Emarsys edition is usually the better choice.

What changes for existing Emarsys customers?

Almost nothing technical. Renames generate more anxiety than they deserve, and this one is benign.

What stays the same:

• Features, automations and the tactics library
• APIs and existing integrations with SAP Commerce Cloud, SAP CDP and third-party systems
• Your contract terms until renewal, and your support channels

What changes:

• The product name in documentation, on invoices and in SAP communication
• Branding in the application and in new documentation, which references “SAP Engagement Cloud”

What you should do:

• Update internal documentation and training material to the new name
• Tell stakeholders that the rename has no technical impact
• Use the next renewal to check whether the enterprise edition fits your brand and governance structure; for most mid-market companies it will not change the answer

If you are in the middle of an implementation, carry on. Nothing in your architecture needs to change.

SAP Marketing Cloud: about three months left

This is the urgent part. SAP Marketing Cloud, SAP’s earlier cloud marketing solution (not to be confused with Emarsys), reaches end of support in December 2026. As of late September 2026 that is two to three months away. SAP positions SAP Engagement Cloud as its strategic engagement platform, and it is the natural target for Marketing Cloud customers who want to stay in the SAP portfolio.

The two products are different architectures, so this is not a lift-and-shift:

What can be carried over:

• Contact data and segments, via export and import or through SAP CDP
• Historical performance data, via export

What has to be rebuilt:

• Campaigns and marketing plans, using Engagement Cloud automations and pre-built tactics
• Integrations, against the Engagement Cloud APIs and connectors
• Custom extensions and analytics connections
• The consent model, in Engagement Cloud’s own consent framework

What typically improves: pre-built tactics shorten the time to the first live campaign, push, in-app and web personalisation are native, and commerce integration is closer to real time.

In our experience a Marketing Cloud migration takes roughly 8 to 14 weeks depending on the number of campaigns and integrations. With about three months left, the order of work matters more than the plan’s elegance:

1. This month: inventory every active campaign, integration and segment, and clarify with SAP what your contract says about the transition period.
2. Next: rebuild revenue-critical and legally required communication first (transactional messages, consent handling, the top revenue automations).
3. Before year end: run old and new in parallel for the critical flows, then switch off.

Anything that is not business-critical can follow in the new year on the new platform. If you are in this position, contact us: the parallel-run phase is where the surprises appear, and it is better to find them in November than in January.

What this means for the competition

The rename positions SAP Engagement Cloud more directly against the large engagement platforms. Salesforce spreads its offering across several marketing products plus Data Cloud; Adobe Journey Optimizer builds on Adobe Experience Platform; HubSpot and Klaviyo dominate the mid-market and Shopify ecosystem; Braze is strong for app-first brands. SAP’s argument is not the best email editor. It is the proximity to commerce, ERP and service data: for companies that already run SAP, engagement decisions can use order, delivery and service information without a second data ecosystem.

For the detailed comparisons see SAP Engagement Cloud vs HubSpot, SAP Engagement Cloud vs Klaviyo and our pricing guide.

What Spadoom clients should do now

Existing Emarsys customers:

• Inform marketing and IT that the rename is a branding change, not a migration
• Update internal documentation to “SAP Engagement Cloud”
• Put the edition question on the agenda of your next renewal

SAP Marketing Cloud customers:

• Complete the inventory of campaigns, segments and integrations this month
• Clarify the transition terms with SAP
• Rebuild critical flows first and plan a parallel run before December 2026

The bigger picture

SAP is building its customer experience portfolio into a connected suite: SAP Sales Cloud V2, SAP Service Cloud V2, SAP Commerce Cloud, SAP Customer Data Platform, SAP Loyalty and now SAP Engagement Cloud, with Business Data Cloud as the shared data foundation. The value of Engagement Cloud rises with every connection to the systems that know what the customer ordered, received or complained about. That is also why we implement it together with the commerce and ERP side: engagement projects rarely fail in the campaign tool, they fail where the data comes from.

For an overview of what the platform does, read SAP Engagement Cloud (formerly SAP Emarsys) explained, or visit our SAP Engagement Cloud solution page. If you have questions about your setup, get in touch.