Is Marketing Cloud Account Engagement “Next” a Migration?

Someone forwards your CMO a Salesforce email about Marketing Cloud Next. By the afternoon you’re being asked whether Pardot is being turned off, whether the eight Engagement Studio programs you rebuilt last quarter are about to become landfill, and whether anyone should be building anything new in Account Engagement at all. Meanwhile the vendor language isn’t helping. “Marketing Cloud Next,” “Account Engagement+,” “Growth Edition,” and “Data 360” all show up in the same paragraph without anyone explaining which one you already own. Is Marketing Cloud Account Engagement “Next” actually a migration you need to plan for? Here’s the short version: nobody is taking Account Engagement away from you, and the work you should do this quarter looks less like a migration project and more like a data hygiene project. This is exactly the kind of vendor-terminology confusion Cloud Nexus untangles for Pardot admins before it turns into a stalled campaign or an accidental compliance problem.

What Actually Changes Between Account Engagement and Marketing Cloud Next?

The real difference is the data model, not the feature list. Account Engagement is prospect-based. A prospect record maps to a Lead or Contact, and the Salesforce connector keeps the two in step. Marketing Cloud Next builds on Data 360’s unified profile instead, which stitches records from multiple systems into one view before you segment against it.

Everything else follows from that one difference. Rules-based nurture becomes agentic campaign creation, where you describe an audience in plain language instead of stacking automation rules. Segmentation stops being limited to fields you remembered to map. Messaging extends past email and forms into SMS and WhatsApp natively, without a third-party sending platform bolted on the side.

Do You Have to Migrate Off Pardot?

No. The framing of “migration” is what causes bad decisions here. Account Engagement customers get next-gen capability provisioned alongside their existing instance. Your campaigns, assets, forms, and engagement programs keep running exactly as they are while you evaluate the new surface.

In practice, this means you can put one campaign in Marketing Cloud Next and leave the other forty where they are. Ideally that one campaign is multichannel, something you couldn’t have run in Account Engagement alone. That’s a pilot, not a cutover. Teams that treat it as a cutover end up rebuilding assets they had no reason to touch.

Why Does Your Sync Error Queue Matter More Now, Not Less?

Because Marketing Cloud Next segments against data that ultimately traces back to your CRM records. Your connector is the front door. A prospect sitting in the sync error queue isn’t just a stalled record anymore. It’s a record that never reaches the unified profile you’re about to build audiences from.

If you’re already fighting a growing queue, fix that before you provision anything. Our walkthrough on why your Pardot sync keeps failing and how to clear the error queue covers the five root causes behind most queues. The same underlying hygiene items apply here: validation rules blocking the connector user, field-level security missing on newly created fields, and duplicate rules rejecting legitimate records. Adding a unified data layer on top of a broken connector doesn’t unify anything. It just moves the confusion one layer up, where it’s harder to see. This is the same connector audit we run first in every Cloud Nexus org review, before we let a client provision anything new on top of it.

What Should You Actually Do This Quarter?

Five concrete steps cover what most teams need before piloting anything in Marketing Cloud Next, roughly in order of urgency.

1. Confirm what you already have. Check your Account Engagement edition and whether Account Engagement+ PSLs are provisioned. Many teams are entitled to more than they’ve turned on.
2. Clean the connector first. Clear the sync error queue and close the intake gaps that refill it.
3. Enable Salesforce Foundations and provision Data 360. Foundations is the prerequisite, and it’s self-enabled in My Account.
4. Plan consent deliberately. Consent isn’t shared between the two products by default. Map your static public lists to Marketing Cloud Next subscriptions before you send anything, and start with one small subscription rather than your whole database.
5. Pilot one campaign, not forty. Pick something you genuinely couldn’t do in Account Engagement — a multichannel journey, an agent-built audience — so the pilot answers a real question.

Frequently Asked Questions

Is Pardot being retired?

No. Marketing Cloud Account Engagement continues as its own product, and next-gen capability is provisioned alongside it rather than replacing it. There is no announced forced end date for existing Account Engagement instances. There is no requirement to rebuild your assets to keep them running.

Do we have to buy Data 360 separately?

Data 360 is a prerequisite for Marketing Cloud Next, and Salesforce Foundations gives you access to it along with a baseline allocation of messaging and Einstein credits at no cost. Heavier usage means purchasing additional credits. That’s where cost planning actually belongs — credits, not licenses.

Will our existing engagement programs work in Marketing Cloud Next?

They keep running in Account Engagement exactly as built. Marketing Cloud Next uses a different data model and a different campaign-building approach. Treat new work there as new work rather than expecting a one-to-one port of an Engagement Studio program.

What breaks first when a team turns this on without preparation?

Consent. Because subscriptions aren’t shared by default, a team that provisions and starts sending can email people who opted out on the Account Engagement side. Map consent before the first send, not after the first complaint.