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

On February 19, 2026, SAP renamed its omnichannel marketing platform from SAP Emarsys Customer Engagement to SAP Engagement Cloud. They also introduced a second tier: Enterprise Edition. For a product that serves thousands of brands across retail, e-commerce, and travel, this is a significant strategic repositioning — not just a cosmetic touch-up.

We’ve been implementing Emarsys since it became part of the SAP CX portfolio, and the rename tells us something important about where SAP is taking its customer engagement story. Here’s our full breakdown of what happened, what it means, and what you should do about it.

TL;DR: SAP renamed Emarsys to SAP Engagement Cloud on February 19, 2026. Two editions now exist: Emarsys Edition (the existing product, unchanged) and Enterprise Edition (new, with cross-cloud orchestration, real-time ERP signals, and Joule AI). Existing customers keep the same features, APIs, and integrations. The biggest action item: if you’re on SAP Marketing Cloud, its support ends December 2026 — start planning your migration now.

What Happened on February 19, 2026

SAP published the announcement through its official channels on February 19, 2026 (SAP News Center, 2026). The core message: SAP Emarsys Customer Engagement becomes SAP Engagement Cloud, effective immediately. The emarsys.com domain and SAP product documentation were updated within the same week.

This wasn’t a merger or an acquisition. No new company was involved. The product team, the codebase, and the infrastructure remain the same. What changed is the branding, the positioning, and the introduction of a new edition.

Two editions now exist under the SAP Engagement Cloud umbrella:

• Emarsys Edition — the existing SAP Emarsys product, now rebranded. Everything you know and use today continues unchanged.
• Enterprise Edition — a new tier built on top of the Emarsys foundation, adding cross-cloud engagement orchestration, deeper SAP CX integration, and AI capabilities through Joule.

SAP framed the rename as a reflection of the product’s expanded scope. Emarsys started as a marketing automation platform. SAP Engagement Cloud is positioned as the engagement orchestration layer across the entire customer journey — marketing, commerce, service, and loyalty included.

Why “Engagement Cloud”?

The word “marketing” is conspicuously absent from the new name. That’s deliberate.

When SAP acquired Emarsys in 2020 for approximately USD 600 million, the platform served primarily as an email and omnichannel marketing tool. It excelled at campaign management, segmentation, and pre-built marketing tactics. Six years later, the platform has evolved. It handles loyalty triggers, commerce-driven personalisation, service-informed engagement, and ad audience management. Calling it a “marketing” tool undersells what it does.

The rename to “Engagement Cloud” signals three things:

Full-lifecycle positioning. SAP wants the platform to own customer engagement across every touchpoint — not just the marketing department’s campaigns. When a service interaction triggers a retention offer, or a commerce event drives a personalised push notification, or a loyalty milestone sparks a cross-sell campaign — that’s engagement orchestration, not marketing automation.

SAP CX suite alignment. The naming now mirrors the pattern SAP established with Sales Cloud V2, Service Cloud V2, and Commerce Cloud. “Engagement Cloud” slots into that family cleanly. It signals that the product is a first-class citizen of the SAP CX portfolio, not a bolted-on acquisition.

Competitive repositioning. Salesforce restructured its marketing products under “Marketing Cloud” and “Data Cloud” branding. Adobe has Journey Optimizer. The term “engagement” positions SAP differently — less about campaign execution, more about orchestrated customer relationships. Given that Gartner has recognised Emarsys as a Leader in Personalisation Engines for seven consecutive years (Gartner, 2025), SAP has the credibility to make this positioning stick.

Emarsys Edition vs Enterprise Edition

This is where the practical implications live. The two editions serve different customer profiles, and the distinction matters for budgeting and roadmap planning.

Emarsys Edition: who is it for?

If you’re an existing Emarsys customer, this is your edition. Nothing changes operationally. You keep the same features, the same interface, the same integrations. The rename is purely cosmetic from your perspective.

It’s also the right starting point for organisations that need a solid omnichannel marketing platform with pre-built tactics, AI segmentation, and native SAP integration. For most mid-market companies running SAP Commerce or SAP S/4HANA, Emarsys Edition covers 80-90% of engagement use cases out of the box.

Enterprise Edition: who is it for?

Enterprise Edition targets large organisations that want engagement orchestration across the full SAP CX suite. Think: a global retailer where a service complaint about a delayed shipment should automatically suppress the next marketing campaign and trigger a personalised retention offer — all in real time, with the offer value calculated based on customer lifetime value from S/4HANA.

That level of cross-system engagement orchestration is what Enterprise Edition enables. It’s not about sending more emails. It’s about making every customer interaction informed by every other customer interaction, across every SAP cloud.

SAP has not published definitive public pricing for Enterprise Edition at the time of writing. Based on our conversations with SAP and early partner briefings, expect a per-contact base (similar to Emarsys Edition) plus an orchestration fee that scales with cross-cloud event volume. We’ll update this section as official pricing becomes available.

What Changes for Existing Emarsys Customers

The short answer: almost nothing technical.

Here’s what we know from SAP’s communications and our own testing:

What stays the same:

• All existing features, workflows, and automations continue to function
• API endpoints remain unchanged (backward-compatible)
• The Emarsys UI and dashboard are the same, with updated branding
• Existing integrations with SAP Commerce Cloud, CDP, and third-party systems are unaffected
• Your contract terms remain as negotiated
• Support channels and SLAs stay the same
• The pre-built marketing tactics library continues to grow on its existing cadence

What changes:

• Product name in documentation, invoices, and SAP marketing materials
• The emarsys.com website now redirects to SAP Engagement Cloud pages on sap.com
• Login portal branding has been updated
• New documentation will reference “SAP Engagement Cloud” rather than “SAP Emarsys”
• SAP partner certifications will gradually adopt the new naming

What you should do:

• Update internal documentation and training materials to reference the new name
• Inform stakeholders that the rename has no technical impact
• Review your contract renewal timeline — this may be a good moment to evaluate the Enterprise Edition
• Update any marketing collateral or partner pages that reference “SAP Emarsys”

If you’re in the middle of an implementation, keep going. Nothing in your technical architecture needs to change. The APIs you’re integrating with today will be the same APIs tomorrow.

What’s New in Enterprise Edition

Enterprise Edition isn’t just Emarsys with a premium label. It introduces capabilities that didn’t exist before:

Cross-cloud engagement orchestration

The headline feature. Enterprise Edition can consume events from SAP Sales Cloud V2, SAP Service Cloud V2, SAP Commerce Cloud, and SAP Customer Data Platform — and use those events as triggers for engagement workflows.

A deal reaches the “negotiation” stage in Sales Cloud? Enterprise Edition can automatically enrol the contact in a nurture journey tailored to their industry and deal size. A service ticket is resolved with a positive CSAT score? The system can trigger a review request, followed by a cross-sell recommendation three days later.

This isn’t theoretical. The orchestration engine routes events across clouds in near-real time, with configurable rules for priority, suppression, and timing. It’s the kind of connected experience that previously required custom middleware or a dedicated integration platform.

Real-time ERP signals from S/4HANA

This is new territory for a marketing engagement platform. Enterprise Edition can receive signals directly from S/4HANA — inventory changes, order status updates, credit limit adjustments, delivery confirmations. These signals can drive engagement decisions.

Low inventory on a popular product? The system can automatically shift campaign emphasis to alternatives. An order ships? Trigger a delivery confirmation with personalised cross-sell recommendations based on what’s in the package. A customer’s credit limit is adjusted? Suppress high-value product promotions until the situation is resolved.

The S/4HANA integration uses SAP’s event mesh infrastructure, which means events flow in real time without batch processing delays. For retailers and manufacturers running S/4HANA, this connects the back office to the customer experience in a way that wasn’t previously possible without significant custom development.

Joule AI for engagement

SAP’s AI assistant, Joule, now extends into engagement orchestration. In Enterprise Edition, Joule can:

• Recommend engagement strategies based on customer segment behaviour patterns
• Suggest optimal channel selection for specific customer cohorts
• Generate engagement workflow templates from natural language descriptions
• Analyse campaign performance and suggest data-driven optimisations

SAP Business AI reached 34,000 customers, with approximately 60% actively using AI features (SAP News Center, 2025). Joule’s integration into Engagement Cloud Enterprise Edition is part of SAP’s broader push to embed AI assistance into every cloud product.

Extended SDK access

Enterprise Edition provides deeper programmatic access for building custom engagement scenarios. The extended SDK includes:

• Webhook-based event ingestion from non-SAP systems
• Custom orchestration logic via serverless functions
• Advanced audience computation APIs for real-time segment evaluation
• Event replay and debugging tools for complex multi-step journeys

For organisations with dedicated development teams, this opens up engagement scenarios that go well beyond what the standard UI can configure.

SAP Marketing Cloud Sunset: The Migration Path

This is the urgent part. SAP announced the end of support for SAP Marketing Cloud (the on-premise and BTP-based marketing solution, not Emarsys) with a final support date of December 2026. Over 2,000 companies currently run SAP Marketing Cloud (SAP Community, 2026). Every one of them needs a migration plan.

SAP Engagement Cloud (Emarsys Edition) is the designated successor for marketing automation within the SAP CX portfolio. SAP has been explicit about this: Marketing Cloud customers should migrate to Engagement Cloud.

The migration timeline

With December 2026 as the deadline, the timeline is tighter than it looks:

• Q2 2026 (now): Assess your current SAP Marketing Cloud usage — campaigns, segments, integrations, custom developments
• Q3 2026: Execute migration — data transfer, integration reconfiguration, campaign rebuilding, user training
• Q4 2026: Parallel run and validation before Marketing Cloud shutdown
• December 2026: SAP Marketing Cloud support ends

A typical migration takes 8-14 weeks depending on complexity. If you haven’t started planning, the window is closing.

What migrates and what doesn’t

SAP Marketing Cloud and Emarsys are fundamentally different architectures. This is not a lift-and-shift migration. Key considerations:

What transfers:

• Customer data and segments (via export/import or CDP bridge)
• Campaign logic (must be rebuilt using Emarsys tactics and automations)
• Integration endpoints (must be reconfigured for Emarsys APIs)
• Historical performance data (via data export)

What requires rebuilding:

• Marketing plans and campaign workflows (Emarsys uses a different orchestration model)
• Custom BTP extensions for Marketing Cloud
• SAP Analytics Cloud connections (different data model)
• Consent management configurations (Emarsys has its own consent framework)

What improves:

• Pre-built tactics significantly reduce time-to-campaign vs. Marketing Cloud’s blank-canvas approach
• Omnichannel reach is broader (push, in-app, web personalisation are native)
• AI capabilities are more mature (predictive segmentation, optimal send time)
• Commerce integration is deeper and more real-time

Migration strategy

We recommend a phased approach:

1. Audit — Document every active campaign, integration, segment, and custom development in Marketing Cloud
2. Map — Match each Marketing Cloud capability to its Emarsys equivalent (or identify gaps)
3. Prioritise — Migrate revenue-critical campaigns first, then secondary automations
4. Build — Reconstruct campaigns in Emarsys, leveraging pre-built tactics where possible
5. Test — Run parallel campaigns during transition to validate parity
6. Cutover — Decommission Marketing Cloud after validation

If you’re a Spadoom client and need migration support, reach out to our team — we’ve been building migration playbooks specifically for this transition.

What This Means for the Competitive Landscape

The rename and edition split position SAP Engagement Cloud more directly against the major marketing and engagement platforms:

vs Salesforce Marketing Cloud

Salesforce’s marketing stack is powerful but fragmented — Marketing Cloud Engagement (formerly ExactTarget), Marketing Cloud Account Engagement (formerly Pardot), Marketing Cloud Personalisation (formerly Interaction Studio), and Data Cloud all serve different functions. SAP’s advantage is tighter native integration with commerce and ERP data. Enterprise Edition deepens this advantage further with real-time S/4HANA signals.

For SAP-first organisations comparing the two, the integration story is compelling. You’re not bridging two ecosystems — you’re working within one.

vs Adobe Journey Optimizer

Adobe’s strength is in experience management and content delivery. Adobe Journey Optimizer provides real-time journey orchestration, but it requires Adobe Experience Platform as a foundation. SAP Engagement Cloud Enterprise Edition offers similar cross-cloud orchestration but with native ERP connectivity that Adobe can’t match. For companies running SAP for operations, the data advantage is significant.

vs HubSpot

HubSpot remains strong for small and mid-market companies. But it lacks native SAP integration, pre-built industry-specific tactics, and real-time ERP signals. SAP Engagement Cloud Emarsys Edition competes with HubSpot on features; Enterprise Edition is in a different category entirely.

vs Braze

Braze excels at mobile-first engagement and real-time personalisation. For pure-play digital brands without SAP infrastructure, Braze may be more agile. But for organisations already invested in the SAP ecosystem, Engagement Cloud provides comparable channel coverage with the added benefit of commerce, service, and ERP data flowing natively into engagement decisions.

vs Klaviyo

Klaviyo owns the e-commerce marketing space, particularly for Shopify merchants. SAP Engagement Cloud competes directly in the mid-market and enterprise commerce segment. For SAP Commerce Cloud customers, Emarsys Edition offers deeper product catalogue and order data integration than Klaviyo can achieve through its standard connectors.

What Spadoom Clients Should Do Now

Here’s our recommended checklist based on what we know today:

Immediate (this week):

• Inform your marketing and IT teams about the rename — emphasise that it’s a branding change, not a technical migration
• Bookmark the new documentation and support URLs
• Update any internal wikis or training materials that reference “SAP Emarsys”

Short-term (next 30 days):

• Review your current Emarsys Edition contract and renewal timeline
• Evaluate whether Enterprise Edition capabilities (cross-cloud orchestration, ERP signals, Joule AI) align with your engagement roadmap
• If you’re on SAP Marketing Cloud: start the migration assessment immediately — December 2026 is closer than it feels

Medium-term (next quarter):

• Request an Enterprise Edition demo if cross-cloud orchestration is on your roadmap
• Update partner-facing materials and co-marketing content to use the new branding
• Plan training for marketing teams on any new capabilities you intend to adopt

If you’re on SAP Marketing Cloud:

• Conduct a full audit of current Marketing Cloud usage (campaigns, segments, integrations)
• Map Marketing Cloud capabilities to Emarsys Edition equivalents
• Build a migration timeline that allows for parallel running before the December 2026 deadline
• Contact us for a migration assessment if you need guidance

The Bigger Picture: SAP’s Engagement Strategy

Zoom out, and the rename fits into a broader pattern. SAP is systematically unifying its customer experience portfolio into a connected suite:

• SAP Sales Cloud V2 — CRM and sales execution
• SAP Service Cloud V2 — customer service and support
• SAP Engagement Cloud — customer engagement and marketing orchestration
• SAP Customer Data Platform — unified customer profiles and audience management
• SAP Commerce Cloud — digital commerce
• SAP Customer Loyalty Management — loyalty programmes and rewards

Each cloud is designed to operate independently but deliver compounding value when connected. Enterprise Edition is the clearest expression yet of this connected strategy — it’s the first product that explicitly orchestrates across the other clouds in real time.

The introduction of real-time ERP signals is particularly telling. SAP is leveraging its unique position as both a back-office and front-office vendor. No competitor can offer this depth of operational data flowing directly into engagement decisions. A customer’s order history, payment behaviour, return patterns, and credit status can all inform how and when the brand communicates with them.

This is SAP’s competitive moat in the engagement space. Not the best email builder (arguably, it isn’t). Not the most channels (several competitors match it). But the deepest integration between customer engagement and business operations. That’s a differentiation that’s very hard for pure-play marketing platforms to replicate.

The SAP Emarsys to SAP Engagement Cloud rename is more than a name change. It reflects a genuine expansion in what the platform does and where SAP sees customer engagement heading. For existing customers, the immediate impact is minimal. For the broader market — especially the 2,000+ companies facing the SAP Marketing Cloud sunset — it represents a clear signal about SAP’s engagement strategy and the path forward.

We’ll be updating our SAP Engagement Cloud solution page and related resources as more details emerge about Enterprise Edition availability and pricing. If you have questions about what this means for your specific setup, get in touch.