The Spring '26 release was the one that made Marketing Cloud Next real for enterprise teams. Salesforce delivered on two requirements that larger B2C organizations had been waiting for: Business Units and Dedicated IPs are now generally available. For teams that had been evaluating the platform from the sidelines that changes the conversation.
Here is what keeps coming up in those conversations, and what tends to catch teams off guard when deciding about Salesforce Marketing Cloud Next.
The data architecture is fundamentally different
Marketing Cloud Engagement was built on ExactTarget infrastructure, which meant data lived in parallel to the Salesforce core. Contact records here, campaign data there, constant synchronization in between. A significant portion of implementation effort historically went into managing that gap.
Marketing Cloud Next is built natively on Salesforce Core, with Data Cloud (Data 360) providing identity resolution, unified profiles and real-time data access across the stack. That means an email send can draw on a support ticket that closed this morning, or Personalization Decisioning can work from current behavioural signals rather than a batch export from last week.
That's a meaningful shift in what becomes possible, and it carries a practical implication worth understanding early. While foundational Data Cloud access is included to power Marketing Cloud Next, it operates on a consumption model - so forecasting your expected data usage belongs in the budget conversation from the start. We've seen projects where the MC Next license was approved, but the underlying data scaling strategy became an afterthought; it tends to resurface mid-implementation, at a point where it's harder to address cleanly. The zero-copy model also changes what data quality means here. Because data is referenced in place rather than moved or copied across systems, the quality of your existing identity resolution flows directly into decisioning outputs. Patchy data produces patchy personalization, just in real time.
What spring '26 delivered
Business Units are now generally available, up to 50 per org, each with isolated campaign and audience views. Dedicated IP support arrived for high-volume senders. Combined, those two additions mean Marketing Cloud Next can support serious B2C operations on its own.
A few other Spring '26 additions worth knowing. Campaign Creation can now ground briefs in existing documents: upload a PDF brand guide or strategic brief to Salesforce Files, reference it in the prompt, and the agent builds from it. Brand Settings apply tone of voice and visual identity guidelines across everything Agentforce generates. Conversational Email enables two-way dialogue inside email threads, so a customer who replies to a promotional email with a product question gets a handled response without routing to a human queue.
The agent capabilities that have been generally available since the original release - Campaign Creation, Personalization Decisioning, Lead Management, Segment Intelligence - are maturing steadily with each seasonal update.
The migration path is more gradual than most initial plans assume
There is no sunset date for Marketing Cloud Engagement. Salesforce built this as a parallel evolution. The Marketing Cloud Engagement+ tier gives existing customers access to agentic capabilities while keeping current data models, AMPscript logic and established automations in place.
And Summer '26, which is weeks away, is also bringing AMPscript support to Marketing Cloud Next, which is a meaningful step for teams migrating from Marketing Cloud Engagement. The first iteration has some gaps, but the direction significantly reduces the scripting work that would otherwise need to be rebuilt from scratch.
In practice, the right entry point depends on where the pressure is. Teams constrained by launch speed tend to get the fastest return from Agentforce Campaign Creation. Segment Intelligence is the better starting place when audience precision is the gap. Lead Management makes sense when the friction is in the marketing-to-sales handoff, where leads are getting lost between the two teams. Whatever the entry point, getting the data foundation right first and running a focused pilot before expanding scope consistently reaches value faster than planning a full migration from the start. The first win also has to be visible and specific, or broader adoption tends to stall.
Three things worth locking down before any MC Next initiative moves to planning:
We are building on the platform with several clients now. If you are in the evaluation or planning phase, happy to share what we are finding.
