Platform
Is Pardot dead? Account Engagement and the path to Marketing Cloud Growth
No, Salesforce hasn't announced an end date for Account Engagement. It's converging into Marketing Cloud Growth through add-on licenses, not a cutover, and there's no automated migration. Here's what convergence means, what a rebuild costs you, and why most B2B teams should wait.
Every few months a keynote convinces a B2B marketing team that Pardot is being switched off, and the migration panic starts. Say this part plainly, because the panic drives bad decisions: Salesforce has announced no end-of-life, no end-of-sale, and no end-of-roadmap for Marketing Cloud Account Engagement.
Salesforce still sells it, still supports it, still patches it. The product formerly called Pardot is not going anywhere on a date anyone can point to.
What is true is quieter and more useful. New marketing investment, the agents and the Data 360 grounding, is landing in a different product, Marketing Cloud Growth, and Salesforce is building a bridge from Account Engagement to it rather than a forced march. My read for most B2B teams: understand the bridge, and do not cross it this year unless something specific is pushing you.
This post is what the bridge is, what a real migration involves, and how to decide.
The names, because Salesforce made this hard
Three products share the words “Marketing Cloud,” and confusing them is how teams migrate the wrong thing.
Account Engagement is Pardot, renamed, the B2B marketing automation tool with prospects, nurture programs, scoring and grading, and a connector to your CRM. Marketing Cloud Engagement is the old ExactTarget platform, the B2C sending engine with data extensions and its own scripting. The two are unrelated under the hood, and neither has an announced sunset. This post is about the first one.
Marketing Cloud Growth, and its larger sibling Advanced, is the newer thing: marketing built directly on the core Salesforce platform with Data 360 as the data layer. Growth is the same core-platform line Salesforce has branded as Marketing Cloud Next and, lately, Agentforce Marketing.
When a keynote shows a campaign built from a sentence, it is showing Growth or Advanced, not Pardot. We covered what that agentic layer does, and does not do, in the Agentforce for Marketing breakdown. This post is the B2B migration question underneath it.
Convergence means an add-on license, not a cutover
The word Salesforce uses is “convergence,” and it is not spin. The mechanism is a set of permission-set licenses, marketed as Account Engagement+, that give an existing customer access to Marketing Cloud Growth or Advanced capabilities alongside their current org rather than in place of it.
Reporting on the path maps Account Engagement Growth customers to Marketing Cloud Growth, and the Plus and Advanced tiers to Marketing Cloud Advanced. The design means you are not forced to choose on day one. You can keep Account Engagement as your system of record, turn on the new capabilities where they earn their place, and move workloads over on your timeline.
Salesforce’s own framing is “no migration required,” and taken literally that is accurate. You can adopt the new surface without decommissioning the old one.
Taken as reassurance that moving is easy, it misleads. “No migration required” describes the licensing. It says nothing about the work of running your program on the new platform, and that work is a rebuild.
“No migration required” is a statement about licensing, not about effort. Nothing forces you to move. Nothing moves your program for you either.
There is no migration tool, and the data model changed
Start with the fact that surprises people most. No automated path lifts your Account Engagement assets into Marketing Cloud Growth. As of 2026, Salesforce has not shipped tooling that carries templates, forms, or automations across.
Every asset is rebuilt by hand on a different data model. The one official “migration” utility moves Pardot-only user records to Salesforce user records, which is identity housekeeping, not a program migration. Do not mistake one for the other.
The reason it is a rebuild and not an export is architectural. Account Engagement keeps its own Prospect object, synced to your Leads and Contacts, partitioned into Business Units that act as separate databases inside one instance. Marketing Cloud Growth has no Prospect object.
Growth segments against the unified Data 360 profile on the core platform. Your Prospect activity can flow into Data 360 as a data stream and feed the newer engagement scoring, but the model your program assumes, Prospects in Business Units, does not exist on the other side. That single difference ripples through everything you built.
Walk the inventory and each piece needs re-creating:
- Engagement Studio nurture programs have no equivalent object. You rebuild them as journeys in Salesforce Flow, through the marketer-facing Campaign Flow layer, and Completion Actions become triggered Flows. The logic does not transfer.
- Forms work on landing pages, but practitioners report no direct form-handler equivalent yet, which matters if you post to external endpoints. Verify this against current release notes for your use case before you commit a date.
- Scoring and grading is the gap that catches B2B teams hardest. Account Engagement gives a numeric engagement score and a fit grade against your ideal profile. Growth leans on Einstein and Data 360 engagement scoring and does not ship Pardot’s native grading, and the score does not land on the Lead for reps the way Pardot’s does.
- Personalization written in Handlebars Merge Language does not carry over. You rebuild dynamic content in the core-platform builders.
- API integrations built on the Account Engagement REST API point at endpoints that do not exist in Growth. They get re-pointed to standard core-platform APIs, which is a development task, not a settings change.
What the rebuild costs, roughly
There is no Salesforce price on the migration itself, because Salesforce does not perform it. The figures come from consultancies who do, and they should be read as illustrative rather than quoted.
Reported cost bands for 2026 cluster around $15,000 to $50,000 for a small B2B team, $50,000 to $150,000 for mid-market, and $150,000 to $300,000 or more for a complex multi-Business-Unit enterprise. One firm frames a typical three-year total between $25,000 and $200,000 depending on complexity. Reported timelines run 60 to 90 days for a standard B2B rebuild and 120 or more for multi-cloud complexity.
The effort tracks the asset count. Every email template, every nurture program, every form is a unit of manual work, and the consultancy benchmarks that circulate put each at somewhere between fifteen minutes and half an hour before testing. Multiply that by your library and you have the real number, which is almost always larger than the license conversation suggested.
On the license side, multiple 2026 sources list Marketing Cloud Growth at around $1,500 per org per month and Advanced at around $3,250, both billed annually and priced per org rather than per user, with Agentforce and Data 360 capabilities included. Treat those as reported figures and pull the current pricing page before you build a business case, because Salesforce revises marketing SKUs often.
The larger point holds regardless of the exact number: the subscription is the small line, and the rebuild is the budget.
Who should move, and who should wait
The consultants closest to this are unusually blunt for a vendor ecosystem. Most existing Account Engagement customers should not migrate in 2026, because there is no prize for going first and there is real risk in leaving a mature product for a younger one mid-flight.
The drivers that make moving now defensible are specific. You already have a Data 360 commitment and want your marketing data unified with it. You have an Agentforce strategy and want the campaign agents grounded in that same profile. Your contract is up for renewal and the timing lets you avoid paying twice.
Two more make the case: you are a net-new org with no Pardot legacy to carry, or you need B2B and B2C on one platform, which Growth is built for and Pardot never was.
The reasons to wait are just as concrete. Your sales handoff depends on Pardot’s grading and Prospect-level scoring landing on the Lead. You run several Business Units with real separation. You have deep Engagement Studio, form-handler, or Handlebars investments that would cost more to rebuild than the new capabilities return this year.
If two or more of those describe you, the sensible move is to adopt Account Engagement+ where a specific new capability helps, keep your program where it works, and let the newer product mature another release or two. The Advertising Studio retirement taught the same lesson from the other direction: a Salesforce transition is a data and identity project long before it is a feature swap, and the teams that rushed it paid twice.
What I would do
If you are on Account Engagement today, do three things this quarter, and none of them is “start migrating.”
Inventory what you run: the live nurture programs, the forms that still convert, the scoring your reps trust, the integrations pointed at the Pardot API. Most orgs discover the real program is a fraction of what accumulated, and the rebuild is scoped against the fraction, not the archive.
Then price the rebuild against a genuine driver, a Data 360 or Agentforce plan, a renewal, a B2B-plus-B2C need, rather than against a fear the product is ending, because it is not. If a driver is real, treat it as a data and AI strategy engagement with a sequenced plan, not a go-live you discover the week before launch.
If no driver is real, turn on the convergence license where it helps and wait. Waiting is a strategy here, and this year it is usually the right one.
Understanding the basics
Is Pardot being discontinued?
No. Salesforce has announced no end-of-life, end-of-sale, or end-of-roadmap for Marketing Cloud Account Engagement, the product formerly called Pardot. It continues to be sold, supported, and updated. Salesforce is converging it toward Marketing Cloud Growth through optional add-on licenses rather than retiring it, so there is no deadline forcing a move in 2026.
What is Account Engagement+?
Account Engagement+ is the marketing name for permission-set licenses that give an existing Account Engagement customer access to Marketing Cloud Growth or Advanced capabilities alongside their current Pardot org. That add-on is the “convergence” path: you gain the newer, core-platform and Data 360 features without decommissioning Account Engagement, and Salesforce describes it as requiring no migration. That describes the licensing, not the effort of rebuilding your program on the new platform.
Is there an automated migration from Pardot to Marketing Cloud Growth?
No. As of 2026 there is no Salesforce tool that moves Account Engagement templates, forms, nurture programs, or automations into Marketing Cloud Growth. The move is a manual rebuild on a different data model, because Growth has no Prospect object or Business Units and segments against the unified Data 360 profile instead. The one official migration utility moves Pardot-only user records to Salesforce users, which is unrelated to migrating your marketing assets.
Should I migrate from Pardot to Marketing Cloud Growth in 2026?
For most B2B teams, not yet. Migrate now if you have a concrete driver: an existing Data 360 or Agentforce strategy, an imminent contract renewal, a net-new org with no legacy, or a real need for B2B and B2C on one platform. Wait if your sales handoff depends on Pardot’s grading and Prospect scoring, you run multiple Business Units, or you have heavy Engagement Studio, form-handler, or Handlebars investments. There is no forced deadline, so the timing is your decision, not Salesforce’s.
Weighing an Account Engagement move against a Data 360 and Agentforce roadmap, and want the sequence costed before you commit? Talk to us. Scoping the rebuild realistically, and telling you when to wait, is the advisory work we do for B2B teams on Salesforce.
