Two platforms, one question
Ask a marketer to compare Marketing Cloud Next with Braze and you will usually get a feature list. Braze has Content Cards. Marketing Cloud Next has Agentforce. One does push better, the other does CRM better.
That comparison is not wrong. It is just shallow, and it leads teams to the wrong conclusion, because features are the part you can change. Architecture is the part you inherit.
This series takes sixty concepts, one per article, and does the harder translation. For each capability in Marketing Cloud Next, I will name the Braze equivalent, explain where the two genuinely diverge, and be explicit about the cases where no equivalent exists at all. This first article sets the frame, because every later comparison depends on it.
The four layers, and where they diverge
Both platforms have the same four layers. That is why the comparison feels simple at first.
| Layer | Marketing Cloud Next | Braze |
|---|---|---|
| Experience | Lightning app inside a Salesforce org | Braze dashboard |
| Orchestration | Marketing flows, run off-core | Canvas |
| Data | Data 360 | User profiles plus ingestion pipes |
| Intelligence | Agentforce and Einstein | BrazeAI |
The names line up neatly. The substrate underneath does not.
Marketing Cloud Next is not a marketing application that happens to have a database. It is a Lightning app running inside a Salesforce org, with Data 360 as its data substrate and Flow as its execution engine. That single sentence explains most of what follows in this series.
Braze is a vertically integrated engagement platform with a deliberately shallow data layer. It holds a profile store rather than a lakehouse. Where Marketing Cloud Next runs identity resolution, deduplication, calculated insights and segmentation as native platform services over raw records, Braze expects an external customer data platform or warehouse to do that work and hand it a resolved profile keyed on an identifier you supply.
The missing column
This is the diagram I would put on the wall.
In Marketing Cloud Next, data arrives as a raw record, gets standardised into a data model object, then gets resolved into a Unified Individual through identity resolution. Three layers, each with its own refresh schedule.
In Braze those three layers collapse into one. The profile is raw intake, standardised model and resolved identity simultaneously. There is no raw layer to fall back on, and no resolution engine to appeal to.
| Stage | Marketing Cloud Next | Braze |
|---|---|---|
| Raw intake | Data lake object | The profile |
| Standardised model | Data model object | The profile |
| Resolved identity | Unified Individual | The profile, keyed on external_id |
The consequence is a single sentence worth memorising. In Marketing Cloud Next, identity is a platform output. In Braze, identity is an input contract.
Two engines, two shapes
The orchestration layers diverge in character, if not in purpose.
Marketing Cloud Next makes Flow the single engine for all outbound engagement. It runs off-core on a separate high-scale engine, which is what allows it to escape the governor limits that constrain ordinary Salesforce automation. Both facts matter. The first means there is no send path that bypasses the flow engine. The second means scale is not bounded by CRM transaction limits.
Braze’s Canvas is purpose-built for journeys rather than adapted to them. In practice this makes it faster to iterate and easier to reason about, at the cost of deployment discipline, because a Canvas is not metadata you can promote between environments.
The behavioural difference is sharper than the architectural one. Marketing Cloud Next is batch-shaped with real-time escape hatches. Braze is event-shaped with batch escape hatches.
A concrete example shows it. A customer buys something on Saturday morning. In Marketing Cloud Next, that record might not be flow-eligible until Monday, because identity resolution runs roughly daily and the data graph refreshes on its own schedule. In Braze, the same purchase is message-eligible the moment the tracking call returns. Neither platform is wrong. They are making different bets about where latency belongs.
Where the AI ambition separates
Marketing Cloud Next puts AI at the level of the marketer’s job. Agentforce agents build segments, draft campaign briefs, generate content, choose journeys and discover buying-group members. Because they sit on the core platform, they can also touch Sales, Service and Commerce records. The Einstein Trust Layer supplies toxicity detection, dynamic grounding, PII masking and zero data retention.
Braze puts AI inside the send. It decides when to send, which channel, which variant and which copy. Its models are narrower by design, optimising the delivery decision rather than the business process.
The blunt version. Agentforce changes what the marketer does. BrazeAI changes what the send does.
That is not a ranking. A team that wants fewer marketer hours on campaign assembly needs the first. A team that wants better performance per send from an experienced lifecycle team gets more from the second.
What this costs each side
Marketing Cloud Next requires a heavier footprint before value appears. You need a Salesforce org on Enterprise or Unlimited with Growth or Advanced, Data 360 provisioned, data kits installed, identity resolution rulesets configured and a data graph built. That is weeks of setup before the first email.
Braze needs an SDK key and a segment. The trade is that Braze cannot reconcile three source systems with no shared key. If your customer data is fragmented, you need a resolver upstream.
There is a further asymmetry worth noting. Marketing Cloud Next’s data graph cannot have fields removed once saved, so wrong choices become permanent design debt. Braze’s flexible schema has the opposite problem, where a typo in a payload creates a permanent attribute nobody planned for.
The working model for this series
So here is the frame for the remaining fifty-nine articles.
Every concept gets the same treatment. What it means natively. What the Braze equivalent is, named precisely. Where the two diverge on data, execution and AI. How the marketer’s day actually changes. What the hidden complexities are.
Where Braze has no answer, I will say so plainly rather than inventing a workaround that flatters the comparison. Where Marketing Cloud Next requires far more infrastructure to reach the same outcome, I will say that too.
What to watch for in the rest of the series
Three patterns recur across the sixty concepts, and naming them now saves repetition later.
The first is a shared noun with a different implementation. Both platforms have segments, both have profiles, both have templates. The words align and the mechanics underneath do not, which is where most migration estimates go wrong.
The second is a capability that exists on one side only. Identity resolution, the consent audit trail, the client SDK, Liquid. These are not gaps to be patched with configuration. They are architectural positions, and the honest response is to name the missing component rather than pretend a webhook closes the distance.
The third is a trade that looks like a weakness until you see the cost of the alternative. Braze’s permissive schema is fast and leaves governance to you. Marketing Cloud Next’s curated data graph is safe and makes every field a permanent decision. Neither is a defect once you know which failure mode you can afford.
A quick check for understanding
Two platforms both store a customer profile. One derives that profile from multiple conflicting source records using fuzzy matching. The other receives it as an asserted key.
If your organisation has three systems with no shared identifier, which architecture are you actually able to build on today?
Part two begins with Data 360, the platform that makes the first answer possible.
