Marketing Cloud Engagement is a dedicated platform connected to the CRM through a connector; Marketing Cloud Next is built on the Salesforce Platform, with Data 360 and journeys in Flow. Salesforce presents Next as a complement, not a replacement. Coexistence is configured; a change of tool is rebuilt, since no conversion tool is documented.
Two products carry the Marketing Cloud name today, and technically they have almost nothing in common. Marketing Cloud Engagement is the historical platform, the one with Journey Builder and Data Extensions. Marketing Cloud Next is the generation built on the Salesforce Platform itself. We are asked the same question in every scoping workshop: which one to choose, and should you leave one for the other? We answer it here criterion by criterion, based on Salesforce documentation read on November 13, 2026. This article contains no prices: the official pricing page is the reference.
01Two products under one name
Marketing Cloud Engagement, formerly ExactTarget, is a dedicated marketing platform. It connects to the Salesforce CRM through a connector, Marketing Cloud Connect. Marketing Cloud Next is built on the Salesforce Platform, with Data 360 (formerly Data Cloud) as its data layer. Both descriptions come from the Trailhead module Channel Marketing Fundamentals for Marketing Cloud Next, which compares the two products.
In terms of editions, Marketing Cloud Next comes in Growth and Advanced. The Engagement pricing page lists Pro+, Corporate+ and Enterprise+ editions, which give access to Next: Growth with Pro+, Advanced with Corporate+ and Enterprise+. The exact content of your contract should be confirmed with Salesforce.
02The comparison, criterion by criterion
Each row states a fact read in the documentation. Where we could not verify a point, we say so.
| Criterion | Marketing Cloud Engagement | Marketing Cloud Next |
|---|---|---|
| Foundation | Dedicated platform, connected to the CRM through Marketing Cloud Connect | Salesforce Platform, with Data 360 as the data layer |
| Data | Data Extensions | Standard CRM objects and unified profiles in Data 360 |
| Journeys | Journey Builder, and Automation Studio for data processing | Flow Builder: flows triggered by a segment or by an event |
| Email and content | Content Builder, personalization in AMPscript and SSJS | Drag-and-drop editor, merge fields, Salesforce CMS |
| Segmentation | SQL queries and filters in Automation Studio | Visual segment builder in Data 360 |
| AI | Einstein features; with a "+" edition, access to the AI features of Next | Agentforce to create a campaign, Einstein for send time; other features are reserved for the Advanced edition |
| Channels | Email, SMS, mobile notifications, WhatsApp from Journey Builder | Email in both editions; SMS, WhatsApp and RCS depending on edition and options, to be confirmed with Salesforce |
| Audience targeted by Salesforce | Primarily B2C | B2B, B2C and hybrid models |
| Testing and deployment | No sandbox: separate business units, and Package Manager to deploy | Sandboxes and the platform's deployment tools |
| Administration | Roles specific to the platform | Salesforce Setup and permission sets |
Sources: the Trailhead module cited above for the foundation, data, journeys, content, segmentation, channels and audience rows; the AI in Marketing Cloud Next module for AI; the help article Configure Test Environments in Marketing Cloud Next for testing. The administration row comes from our reading notes on the documentation, taken in June 2026.
03When Engagement remains the reasonable choice
- Engagement is live and it works. Active journeys, a trained team, established deliverability: nothing forces you to rebuild. The FAQ on the Engagement pricing page states that no end of life, end of sale or end of roadmap is planned.
- Your sends are mostly B2C and high volume. That is the ground Salesforce positions Engagement on. We read no volume limit on the Next side: we draw no conclusion the other way.
- Your personalization relies on code. AMPscript, SSJS and SQL are an asset. Carrying it over to Next is not documented.
In these situations, our recommendation is to clean up what exists, then open Next on a pilot use case rather than switching everything. Our Marketing Cloud Engagement page describes what we set up there.
04When Next is the obvious choice
- You start from scratch and your CRM is already Salesforce. No second tool, no connector to maintain: marketing works on the same accounts, contacts and leads as sales.
- Marketing, sales and service must act on the same data. A flow can be triggered by a sales or service event. In our reading, this is the main argument for Next.
- Your business is B2B or hybrid. Salesforce presents Next for these models, where Engagement is positioned primarily for B2C.
- Your team is small. Visual segments and journeys in Flow Builder: a Salesforce administrator is on familiar ground. This is our deduction, not a promise from the vendor.
- Your IT department requires test environments. Next relies on the platform's sandboxes, which Engagement does not offer.
The details of what we set up are on our Marketing Cloud Next page.
05Running both, or moving from one to the other
Salesforce does not present Next as the replacement for Engagement. Its module Marketing Cloud Next for Marketing Cloud Engagement Foundations describes it as a complement, and suggests two approaches: gradual, with a few use cases in Next while keeping Engagement, or accelerated, with new campaigns in Next and existing ones maintained in Engagement.
What is documented:
- access to Next from the Engagement interface, once the Salesforce administrator has set it up;
- a flow action that enters a person into an existing Engagement journey, and the ability for a flow to trigger an email sent from Engagement;
- data flowing both ways through Data 360, provided the Data Extensions are connected to it.
What is not, in the pages we read: a tool that would convert a Journey Builder journey into a flow, an automatic carry-over of Data Extensions, content or AMPscript code, and an alignment of consents between the two products. We draw a simple rule from this: coexistence is configured, a change of tool is rebuilt.
06What we check before recommending Next
- Consent. In Next, it is checked at send time: without a recorded consent, the message is not sent. Existing consents must therefore be carried over before the first send.
- Data 360 credits. Publishing segments consumes credits, according to the documentation we read in June 2026. We estimate that consumption on your volumes before designing the segments.
- The channels actually included. Only the inclusion of email is stated without ambiguity. For SMS, WhatsApp and RCS, the documentation and the pricing page do not say the same thing: we have Salesforce confirm this point.
- Data freshness. Sales language talks about real time; the documentation describes refreshes at intervals. We check that this pace suits your journeys.
07Our approach
We do not recommend a product, we start from your situation: your CRM, your channels, what your teams already know how to do. If you use Account Engagement (formerly Pardot), Engagement or another tool, our Marketing Cloud Next page describes the paths we propose. A first conversation is often enough to rule out one of the two options: that is the purpose of the free Health Check.