Marketing Cloud Next vs Marketing Cloud Engagement: how to decide, and when
Two products, one name, very different futures. A consultant's guide to which Salesforce marketing platform you should be on, and how to read the release cadence.
Salesforce sells two marketing platforms with almost the same name, and the most common question we get is some version of: are we on the wrong one?
The honest answer is that it depends less on features than on three things — what your data already looks like, how much custom logic you have accumulated, and how long your current build has to keep earning. Here is how we work through it.
What they actually are
| Marketing Cloud Engagement | Marketing Cloud Next | |
|---|---|---|
| Lineage | The ExactTarget platform, matured over a decade | Built on the core Salesforce platform and Data Cloud |
| Data model | Data Extensions, Shared Data Extensions, subscriber keys | Salesforce objects and Data 360 |
| Scripting | AMPscript, SSJS, Guide Template Language | Handlebars, and AMPscript since Summer '26 |
| Where it lives | Its own stack, integrated with CRM | Inside the Salesforce org |
| Agentic features | Limited | Central to the product |
The deepest difference is the third row and the one under it. Engagement keeps a marketing database beside your CRM. Next assumes your data is already in the Salesforce platform. That single distinction drives most of the migration effort, and it is why "we will move next year" is a data project wearing a marketing project's clothes.
How to read the release cadence
Salesforce has not announced an end of life for Marketing Cloud Engagement, and we are not going to predict one. But release notes are a public record of where engineering effort goes, and the recent pattern is consistent:
- Spring '26 — Next got business units, Handlebars, content extensions, in-app messaging, two-way email and reporting. Engagement got multi-channel improvements and a compatibility bridge.
- Summer '26 — Next got AMPscript, RCS, signup forms, three Agentforce agents and engagement history on Opportunities. Engagement got MCP support, which is plumbing.
The four questions that actually decide it
1. Where does your customer data already live?
If your customer record is already well-modelled in Salesforce and Data Cloud, Next is a short step. If your marketing truth lives in Data Extensions that never fully reconciled with CRM, you have a data project first. Do that honestly — a migration that carries a messy data model across just relocates the mess.
2. How much custom logic have you accumulated?
AMPscript support in Next materially reduced this barrier, but support for a language is not support for your implementation of it. Audit your ten highest-volume emails and sort every function call into three buckets: direct equivalents, needs a data model change, needs a rethink. The size of that third bucket is your real migration estimate.
3. How many business units do you run?
Next caps business units at 50 per org. Most organisations are nowhere near it. If you used Engagement business units as per-client or per-franchise containers, you may be well past it, and the answer is a different information architecture rather than a like-for-like move.
4. What has to keep running while you move?
This is the question teams skip. Nobody gets to pause their marketing calendar for two quarters. The Engagement compatibility bridge introduced in Spring '26 — lockable templates, unified campaign records, legacy data compatibility — makes a phased move more realistic than the all-or-nothing cutover most teams imagine when they put it off.
Three positions, and what we would advise in each
| If you are… | Our advice |
|---|---|
| New to Salesforce marketing | Start on Next. There is no reason to adopt a platform in maintenance, and you have no migration debt to carry. |
| On Engagement, heavily invested, running well | Do not panic-migrate. Freeze new strategic build, keep running what runs, and start the data work that a future move will need regardless. The data model is the long pole, and it is useful on its own. |
| On Engagement, at a renewal or replatform decision | This is the moment to model it properly. The cost of moving is dominated by your data and your custom logic, not by licences — get both audited before the commercial conversation, not after. |
What we would not do
- Migrate because of a feature. Individual features are rarely worth a platform move. Data model alignment is.
- Rewrite every AMPscript template on principle. Bridge what exists; build new work in Handlebars.
- Treat it as a marketing-only project. If your data model needs work, this belongs to whoever owns the customer record, and marketing is a stakeholder rather than the owner.
- Wait for certainty. Salesforce is unlikely to publish the date you are waiting for, and the preparatory work — cleaning the data model, auditing custom logic — pays off whether you move this year or in three.
Where to start this month
If you do one thing, do the AMPscript audit described above. It takes about half a day, it needs no budget approval, and it converts the vaguest and most anxiety-inducing part of this decision into a number you can put in front of a CFO.
How Blueport can help
We have delivered more than 100 Salesforce implementations since 2018, across banking and finance, health, government and travel, and we work in both platforms. If you want a second opinion on which side of this line you should be on, we will give you a straight one — including when the answer is "stay where you are for now".
Sources
Planning your Marketing Cloud roadmap?
Blueport is a Sydney-based Certified Salesforce Consulting Partner with 100+ implementations since 2018. If you are weighing up a move to Marketing Cloud Next, or getting more out of Engagement while you wait, we are happy to talk it through.
Talk to our team