Marketing Cloud Next Doesn't Have to Mean Starting Over

There's a migration story circulating around Marketing Cloud Next that doesn't match what Salesforce is actually saying. Salesforce's own Get Started with Marketing Cloud Next guidance is direct: existing Marketing Cloud Engagement and Account Engagement customers can adopt Marketing Cloud Next features inside the orgs they already run, with "no migration required." Email Studio, Journey Builder, Content Builder, and Automation Studio have no published end-of-life, no sunset date, and no mandatory cutover.

The practitioner read across our product team is even more direct: customers may start thinking about migration sooner, but real migration traction won't arrive until 2028 at the earliest.

If there's no migration to worry about, what is actually happening, and what should marketing teams be doing about it now?

What Marketing Cloud Next actually is

Marketing Cloud Next is the biggest architectural shift in Salesforce's marketing stack since the ExactTarget acquisition in 2013. Salesforce unveiled it at the Connections conference in June 2025, consolidating nine prior marketing-tech acquisitions (ExactTarget, Pardot, Datorama, and Evergage among them) into a single platform built on Data Cloud, with Agentforce as the autonomous AI layer.

Two editions ship the capabilities: Marketing Cloud Growth (the first edition built on Data Cloud as its foundation) and Marketing Cloud Advanced (the same capabilities scaled for larger teams). The platform also unifies B2B and B2C marketing in a single application. The long-standing split between Marketing Cloud Engagement (B2C) and Account Engagement (B2B, formerly Pardot) collapses into one environment running on one data foundation.

The architecture sits across four pillars Salesforce uses to describe the platform:

• Create: AI-assisted campaign creation through Agentforce (Campaign Creation, Personalization Decisioning, Segment Intelligence, Paid Media Optimization), including the new Marketing MCP Server that exposes marketing capabilities to AI agents
• Engage: real-time, event-driven journeys powered by Data Cloud
• Qualify: autonomous lead nurturing through Agentforce Lead Management and the SDR Agent
• Optimize: AI-driven spend and targeting decisions

Salesforce's positioning emphasizes speed, with the company promising to "launch campaigns in days, not weeks" by having agents draft briefs, generate audiences, and produce content collaboratively alongside marketers.

Data Cloud is the connective tissue underneath all of it. Instead of customer information living in siloed Marketing Cloud data extensions, Marketing Cloud Next works against a unified profile fed by data across Salesforce and external systems, with Agentforce sitting on top to generate campaigns, respond to customer messages, and orchestrate journeys.

That's a meaningful architectural shift, and it's also entirely additive. Marketing Cloud Engagement keeps running, Account Engagement keeps running, and Email Studio, Journey Builder, Content Builder, and Automation Studio all continue to ship and receive updates. Customers turn on Marketing Cloud Next features inside the orgs they already operate, with no separate platform to migrate data into.

Marketing Cloud Next is a new way of thinking about how marketing connects to customer data and to AI, rather than a new system to migrate to.

Why the real work is getting agent-ready

Salesforce rearchitected the platform so that anything a human can do in the UI, an agent can do through an API, the API is the new UI. For marketing teams, the practical consequence is less about migrating and more about whether the tools in your stack can speak agent.

Salesforce's Marketing MCP Server is the clearest signal. The Model Context Protocol (MCP) is the standard for how AI agents discover and use the capabilities that other systems expose. When Salesforce ships a Marketing MCP Server, it's saying Marketing Cloud is now a destination AI agents can read from and write to. Agentforce becomes a first-class consumer of marketing capabilities, and other agents can do the same.

This changes what "integration" means. The old model was point-to-point: System A pushes data to System B through a known API. The new model is agent-mediated: an agent reasons about which capability to call across multiple systems, in real time, in response to a customer signal or campaign goal. APIs and MCP servers become first-class infrastructure rather than back-office plumbing, the surface marketing operates against. Marketing production is, in this model, a connectivity problem, and the systems designed around that orientation are easier to plug into agentic workflows than the ones designed around isolated functionality.

The work to take this seriously isn't a six-month replatform. It's a rewiring of how marketing teams think about their stack: which tools speak agent, which tools expose clean APIs, which tools were designed for the kind of orchestration agentic workflows need. The practitioner question shifts from "when does my data have to move" to "is my stack agent-ready when I'm ready to use it that way."

How to think about Marketing Cloud Next today

For teams sorting through what Marketing Cloud Next means for them, four moves are worth making now, and none of them require slowing marketing down:

• Don't panic. There is no forced migration on the table. Continue building campaigns, running journeys, and shipping work the way you do today. Anything you read suggesting a 2026 or 2027 deadline is reading well past what Salesforce has actually published.
• Invest in learning how agentic workflows actually run. Read the documentation for Salesforce's Marketing MCP Server and Agentforce campaign creation. Find one workflow in your current operation where an agent could orchestrate across multiple systems (briefing intake to creative production to approval routing, say) and sketch what it would look like.
• Audit your stack for agent-readiness. For each platform you use, ask three questions: does it expose a clean API, does it have an MCP server or a roadmap to one, and was the team behind it thinking about agentic workflows when they designed it. The tools that anticipated this shift are easy to plug into agentic orchestration. The ones that didn't will become friction.
• Start with a hackathon, then pilot. A hackathon is a low-commitment way to get hands on agentic workflows, and the excitement it creates often sparks a real pilot: a single Agentforce-driven campaign workflow, an event-triggered journey through Data Cloud, an agent-orchestrated handoff between two systems. Either one teaches the team faster than a planning exercise.

Treat Marketing Cloud Next as a slow-moving invitation with a long runway, and use the time well.

How Knak is ready for Marketing Cloud Next

Knak is the first marketing production platform with day-one support for Marketing Cloud Next. The integration is in Alpha now: customers can build emails in Knak, sync them directly into Marketing Cloud Next, and resync updates when content changes. The full setup guide walks through the External Client App configuration and OAuth setup in Salesforce.

The underlying reason matters more than the announcement itself. Knak was designed around the idea that marketing production is a connectivity problem. Design lives in Figma, personalization lives in marketing automation, approval lives in workflow tools, and performance data lives in analytics. The production platform's job is to coordinate all of that without forcing the team to rebuild assets at every handoff. That design point, production as connective infrastructure, is the same shape as the agentic-marketing shift.

The Knak MCP is part of why we're ready early. Marketing production capabilities are exposed to AI agents through MCP, which means custom agentic workflows can include Knak alongside Marketing Cloud Next, Agentforce, or any other agent-aware system without bespoke integration work. Combined with the Knak API, teams configuring custom workflows have what they need to build with Knak as a participating capability in the agent surface, rather than a passive endpoint waiting to be called.

For customers ready to start exploring Marketing Cloud Next, the production layer is already in place and waiting.

Marketing Cloud Next is a real shift, but a slow-moving one. The way to be ready is to make sure the tools in your stack are connected, agent-aware, and easy to plug into the agentic workflows that will define the next few years of marketing. See how Knak fits.