Marketing Cloud Next: Your First 60 Days With Engagement Still Running

Oct 15

6 min read

TL;DR: Salesforce's adoption path adds Marketing Cloud Next on top of Engagement, through the Engagement+ (MCE+) licence. Your campaigns keep running while you connect one or two business units, sync the out-of-the-box data and launch one low-lift use case within 60 days. The bigger change is commercial. Credits and licensing shift when you add Plus, so get those answers before you start.

Why this matters now

Your Salesforce rep keeps saying "next-gen." Your CMO asks the obvious question: do we have to migrate?

Salesforce's own plan says no, at least to start. Its adoption deck tells existing customers to keep campaigns, channels and data running with no migration or disruption. The Spring '26 release notes point the same way. Salesforce Ben's summary says Engagement customers can send Engagement emails directly from flows in the Marketing app. They can also unify legacy Engagement data with Next for features like Marketing Performance reports.

Two third-party sources, Salesforce Dictionary, say Salesforce has announced no sunset date for Engagement. Treat that as their reading and confirm it with your account team.

So the real question changes. It's no longer "when do we move?" It's "what do we add first, and who owns it?"

A note on names. Salesforce's deck says Marketing Cloud Next. Its newer materials also say next-gen marketing and Agentforce Marketing. We use Marketing Cloud Next here, and you'll hear all three.

What MCE+ is, and what it changes on the bill

Community guides report that new and existing Engagement customers can use Next by buying the "+" licence, with availability dating to late 2025. MCE+ as adding Marketing Cloud Advanced on top of your current Engagement subscription. Everything in Engagement stays. You build new work in Next. Salesforce's own deck titles its timeline "first 60 days with MCE+" and its setup assistant walks admins through "MCE Plus" initialization: enable Data Cloud, connect to MCE, install data bundles and the analytics app.

The licence also changes how you pay for sending. Architect Mateusz Dabrowski warns that moving to Plus ends Super Messages, even for Engagement, and moves you to shared credits across both products. Salesforce's deck points the same way. It says Salesforce Message Credits cover outbound messages, Flex Credits cover Agentforce and Data 360 usage, and a Digital Wallet dashboard tracks consumption and forecasts budget.

Ask your account team	Why it matters
How do our current Super Messages convert to credits?	Your Engagement send cost may change
Which of our sends use Message Credits and which use Flex Credits?	Agentforce and Data 360 usage bills differently from outbound messages
Can we forecast spend in the Digital Wallet before launch?	You can set alerts before the bill surprises you
What does our Data 360 licence include?	Data 360 is the foundation for everything in Next

Get these answers in writing before kickoff. They're the real cost of your first 60 days. Packaging and pricing differ by contract, so nothing here is verified for your account.

Two ways to adopt, and the one Salesforce recommends

Path	What it means	Salesforce's view
Gradual adoption	Keep building on Engagement. Adopt Next for selected use cases and processes.	Marked as the recommended strategy
Accelerated adoption	Build all new campaigns and processes on Next. Keep Engagement for existing campaigns.	Offered as an alternative

Gradual adoption fits most teams. You get new capabilities without touching live programs. Your sends keep going while you learn.

What sits on top of what

Salesforce's architecture slide says Next builds on top of your existing journeys and data. Read it from the bottom up.

Layer	What it holds
Marketing Cloud Engagement	Journeys, content and channels, data extensions, AMPscript
Data 360	A built-in data layer that lets Engagement objects work across Customer 360
Marketing Cloud Next	Flow tied to journeys, channels and data. AI analytics and agents. Central campaign search
Agentforce	Marketing agents on top

Your Engagement work stays where it is. Next reaches into it through Data 360.

The 60-day timeline

Days	Focus	What happens
1 to 20	Build the foundation	Install Data 360. Create the Engagement admin user. Deploy data bundles and map business units. Install the Marketing app and data kits. Set up identity resolution, sync key data extensions and create a data graph. Create users and assign permission sets.
21 to 40	Configure your use case	Review the out-of-the-box Digital Wallet and Marketing Performance dashboards. Connect journeys to campaigns. Pick your first use case. Build and test version one.
41 to 60	Execute and review	Launch the first use case. Monitor its impact. Start on additional low-lift cases.

Salesforce also says you don't need a full Data 360 implementation. Admins sync the out-of-the-box bundles, use default settings, and expand later.

Pick a first use case that fits

Salesforce's advice is blunt. Start with something your team already understands, reuse existing Marketing Cloud data and components, stick to the recommended features and use standard configuration. It lists five starting options.

Use case	Why start here	Watch out for
Custom and unified reports	Drag-and-drop reports across email, SMS, push, WhatsApp and CRM data	The first connection backfills 90 days of send and engagement data
Flow orchestration	Chain or trigger existing Engagement journeys from Flow	Salesforce suggests audiences under 1 million an hour. Engagement events arrive with a 15-minute to 1-hour delay
Segments and event triggers	Build audiences by clicks, with no SQL	Check that subscriber keys tie back to CRM contacts. Otherwise plan identity resolution
Campaign workspace	One place for campaign activity, analytics and Slack collaboration	Changes to Salesforce objects may need CRM admin help
Agentic journey decisioning	Agentforce picks the next best journey	Salesforce calls this its most complex starting case. It suits segments under 20,000, consumes Flex Credits and needs unified individuals and a data graph

Most teams should start with the first three. Our take: leave agentic decisioning for after day 60, once your data is clean.

The four people you need named

Salesforce's checklist asks for two or three stakeholders plus one executive sponsor, formally assigned and given time.

Executive sponsor secures resources for the 60-day goal.
Engagement admin connects business units, data bundles and users.
CRM admin handles Data 360 provisioning, identity resolution and platform permissions.
Marketing champion defines the low-lift use case and validates results.

Our suggestion: name the CRM admin before kickoff. The marketing team often owns Engagement while a different team owns Data 360.

When to wait

Hold off if any of these are true:

Nobody can own Data 360, and no one has time for the first 20 days.
You're heading into your biggest sending season and can't spare the admin hours.
You can't name a first use case your team already understands.

The choice has less to do with technology and more to do with how mature your data practices are. Staying on Engagement for now can be the right call.

If you later plan a deeper move, expect real rebuild work. Salesforce Dictionary reports that no automated migration tool exists, and that data extensions and SQL activities need new equivalents. Confirm that with Salesforce before you budget.

FAQ

Do we have to migrate from Engagement to Marketing Cloud Next?
Salesforce's adoption plan recommends gradual adoption that keeps your existing campaigns, channels and data running with no migration or disruption. Ask your account team about the long-term roadmap.
Do we need a full Data 360 implementation first?
No, according to Salesforce. Admins sync the out-of-the-box data bundles, use default settings and expand later, for example by syncing data extensions and custom settings.
How long until we see value?
Salesforce's timeline puts the first use case launch between days 41 and 60, after about 20 days of setup and 20 days of configuration.
What should our first use case be?
Salesforce suggests low-risk work built on what your team already knows. Custom reports, Flow orchestration and segments are the usual starting points.
What is Marketing Cloud Engagement+ (MCE+)?
Third-party guides describe it as a licence that adds Marketing Cloud Advanced to your existing Engagement subscription. Engagement stays as it is, and you build new work in Next. Confirm the packaging and price with your account team.

Next step

Planning your first 60 days? Talk to our Salesforce team about the licence and credit questions above, plus business unit mapping, team roles and your first use case. If you're not sure whether to rebuild or repair what you have, start with our rebuild vs. repair framework. If agentic decisioning is on your roadmap, read what you should never hand to an AI agent first.