Account Engagement to Marketing Cloud Next: when is the right time to move?

Account Engagement does not require any additional platform. It connects directly to Salesforce through the connector, and once that is set up, the day-to-day experience feels like you are working in one system, even though you are technically in two different products.

The complications sit under the surface. There is a sync delay between the two systems, and sync errors are a genuine operational risk. Validation rules and other Salesforce configuration can block records from syncing: a lead might submit a form and never update in the CRM, and records can quietly fail to come across. If you use Leads as an 'inquiry' record, and a person can have multiple, you have to get creative with External Actions to continue that process. Things get missed, and the misses are the kind that cost you a sale.

Marketing Cloud Next takes a different approach. Rather than syncing through a connector, it works from data that is expressly available in Salesforce. Whether the data lives in Sales Cloud, Service Cloud, or another cloud, it will be available to you, effectively as a copy or view of what already exists. Your Marketing Cloud Next form can update an existing lead, or create a new one each time. You get to decide. And you are not exposed to connector-style sync failures in the same way.

One important caveat: the current sync delay for Marketing Cloud Next and Data 360 is longer than Account Engagement's, but there are generally workarounds. If sync speed is your concern, Account Engagement wins. If it is about data access and sync reliability, Marketing Cloud Next does.

Account Engagement, in my opinion, is easier to learn. Once you have a good grasp of the data structure in Salesforce and can apply that knowledge when navigating Account Engagement, things fall into place. Learning the nuances takes time, but the UI and processes are relatively simple. Want to add a new field and populate it on a form? Easy. Need to sync a new field from Salesforce? Also straightforward for the most part.

That is not the case with Marketing Cloud Next, but there are reasons why. It is built for the agentic experience, and AI is built around data. Data 360 is the driver behind that, so to use Marketing Cloud Next, you need to learn Data 360. The basics will get you started, but it is worth getting familiar with the data structure and how fields in Salesforce 'plug' into Data 360. That structure also helps you build segments, because information gets split into different categories.

Because of Data 360 and the two platforms working together, tasks that are simple in Account Engagement are more involved here. A form cannot go live without a published form and an activated flow. Sending a single email requires a flow. Everything has a draft and published status, including lists. Even after a list is published, anyone new sits in it as 'draft' until the list is published again, so publish your list before the flow runs to make sure everyone gets the email.

It is a lot to take in at first, but once you have your head around it, the system is a powerful one.

Account Engagement gives you no way to email multiple people who share the same email address, not without doing multiple sends, and certainly not out of the box. Marketing Cloud Next has that capability.

That sounds niche until you hit a real use case. Compliance communications often need to reach each individual, not just one person per inbox. Businesses with multiple divisions or different price lists sometimes need to send updates to everyone at once, and several contacts at the same company may legitimately share an address. If this describes you, this single capability may outweigh several of the considerations below.

This is where migration timing decisions most often get made, so it deserves the detail.

Account Engagement: pay for the database

Bringing records into Account Engagement does not consume credits, and there is no limit on how many emails you send, though once you send more than 200K per month, you need a dedicated IP address. What you pay for is your mailable database, capped at 10,000 records, with additional 10,000-record contact blocks purchased as you grow. Go over the cap, and it is not long before your monthly contract price goes up.

You can manage the cap with automation, for example marking unengaged records as do-not-email so they stop counting, and flipping them back if they interact. It works, but it is ongoing upkeep that needs planning.

Marketing Cloud Next: pay for activity

Marketing Cloud Next flips the model. You purchase credits, and activity consumes them. Every email sent draws down your balance, so sending frequency matters. An email to 2,000 people every few weeks is not much of an issue. A heavy sending program will need a meaningful credit allowance, and you should factor that in when comparing costs.

There is also a less obvious credit cost. Getting data from Salesforce into Data 360 no longer consumes credits (it originally did), but once the data lands, it needs to be mapped into data model objects, which are essentially tables in the format Data 360 expects. Data 360 then runs an identity resolution rule set across that data once a day, and that run does consume credits. The data movement is free; the daily processing of it is not.

Marketing Cloud Next can send SMS natively. Account Engagement cannot without a third-party tool.

You can technically run both products together, using Account Engagement for email and Marketing Cloud Next for SMS. But that means completely separate flows built for each channel, so your email and SMS programs end up working in isolation. It is more straightforward to be wholly in one platform, sending both email and SMS from a single flow. If SMS matters to you and you are considering Marketing Cloud Next, my recommendation is to commit to it as a whole rather than splitting channels across products.

The concepts map across, but the cost behaviour does not.

Static lists in Account Engagement are called standard lists in Marketing Cloud Next, where they have no publishing schedule. That is a direct comparison.

Dynamic lists exist in both, always looking for people who match the rules. In Marketing Cloud Next, that always-on evaluation consumes more credits, because segment building itself uses credits. You also cannot create activations (audiences for paid media, for example) from a dynamic list.

The middle ground is a Marketing Cloud Next standard list with a publishing schedule. The list republishes at whatever frequency you set, picking up new people who match each time. For many use cases it gives you most of the benefit of a dynamic list at a fraction of the credit cost, and you can create audiences with it.

If your Account Engagement instance leans heavily on dynamic lists, rethink which ones genuinely need real-time evaluation before you migrate, not after the credit bill arrives.

Where Marketing Cloud Next clearly pulls ahead is segmentation capability. Account Engagement limits you to one rule group; Marketing Cloud Next lets you nest groups within groups, which allows for much more complex segmentation logic.

At the moment, Marketing Cloud Next supports fairly limited styling for preference centres. A recent update allowed for more than one per channel, though email and SMS preferences cannot yet be combined into a single centre. Account Engagement is trickier to set up but can be completely customised.

If you run the two products in tandem, and your preference centre setup in Account Engagement involves multiple lists, you may also need to sync that preference data into Data 360 so it is available in Marketing Cloud Next. It can get complicated quickly. There is a function to sync one list to another, but only to a single list, so it needs some tinkering when you have different types of communications.

Account Engagement gives you Automation Rules, which have no quick equivalent in Marketing Cloud Next. They let you act the moment data meets criteria: someone hits a score of 100, has a phone number and a mailable email, and you can assign the lead or notify the owner it is qualified. The only way to do something similar in Marketing Cloud Next is via a Flow.

For nurture programs, Account Engagement has Engagement Studio: useful, fairly simple to learn, with some limitations. You cannot do anything with custom objects or opportunities within a program without a workaround. But you do not need to be technology savvy to master it, and that is a real benefit.

Marketing Cloud Next uses Flows for everything. Flows are powerful, but they can be technical. When a flow updates values, you need to consider whether other processes are affected at the same time, which is why flows are generally the territory of System Administrators or similar. There is a 'non-admin' flow interface on the campaign record, though behind the UI it is just a normal flow. It makes building easier, but flows can become very complex fast. And a lot of things need one: a one-off email blast requires a flow, so does a form, and complex nurtures certainly will.

Once you master flows, though, the world is your oyster.