Pardot was renamed to Marketing Cloud Account Engagement (MCAE) in 2022, but the technology, the editions, and the underlying contract conventions have been steadily evolving ever since. Customers running on the legacy Pardot infrastructure are now being migrated—on a Salesforce-managed timeline—onto the unified MCAE platform hosted on Hyperforce. The migration is technically a platform change, but commercially it is also a renegotiation opportunity that most customers fail to recognize.
This briefing covers the four commercial conversations a buyer should have during the Pardot-to-MCAE transition: edition mapping, the contact-count recalculation, the Hyperforce regional pricing question, and the renewal uplift that almost always accompanies the migration. Across 500+ Salesforce engagements, customers who treated the migration as purely technical paid an average 18% more over the following three years than customers who treated it as a commercial inflection point.
How the editions map (and where the trap is)
The legacy Pardot editions—Growth, Plus, Advanced, and Premium—do not map cleanly onto the current MCAE editions, which have been re-bundled around Engagement Studio capability, custom object support, and analytics access. The "natural" migration path Salesforce will propose pushes most customers up one edition. Pardot Plus typically becomes MCAE Advanced; Pardot Advanced typically becomes MCAE Premium. The reasoning offered is feature parity, but the financial effect is a 25-40% list-price increase on the same logical product.
| Legacy Pardot | Default MCAE Mapping | List Delta | Negotiable down to |
|---|---|---|---|
| Growth | MCAE Growth | +5–10% | Lateral or +0% |
| Plus | MCAE Advanced | +25–35% | MCAE Plus (lateral) |
| Advanced | MCAE Premium | +30–45% | MCAE Advanced (lateral) |
| Premium | MCAE Premium | +10–18% | +0–5% |
In every recent migration negotiation, we have been able to hold the customer on a lateral edition—Pardot Plus migrating to MCAE Plus, for example—provided the feature inventory analysis was completed before the conversation. The analysis required is not heroic: list the features your team actually uses in production, map them to MCAE edition entitlements, and prove that the lateral edition covers them. Salesforce will resist the lateral mapping verbally but rarely in writing once the feature mapping is on the table.
The contact-count recalculation
Pardot has historically billed on a "prospect" definition that included contacts that had been touched at any point in their history. MCAE has shifted to a more rigorous "Mailable Contact" definition aligned with the broader Marketing Cloud Contact framework. For most enterprise customers, the recalculation works in the buyer's favor: 15-30% of historical Pardot prospects are no longer counted under the MCAE Mailable definition, because they have been inactive or hard-bounced. This is a real reduction in the billable baseline.
Salesforce will not raise this proactively in the migration conversation. The default order form recalculates Mailable Contacts at the same headline number as the historical prospect count, and the saving evaporates. Insist on a fresh calculation from the actual MCAE tenant during the cut-over window, and use the lower number as the contract baseline.
Hyperforce regional pricing
The Hyperforce transition is, in most regions, a no-incremental-cost change. There are two important exceptions. In APAC and Latin America, certain Hyperforce regions carry a premium versus the legacy hyperscaler infrastructure—typically 4 to 8 percent. This premium is usually absorbed in the migration without explicit disclosure. If you are migrating into a region with a Hyperforce premium, negotiate explicit recognition of that premium in the order form, with a fixed-dollar cap rather than a percentage that could grow at renewal.
The second exception is regulated workloads. Customers with data residency requirements—financial services in certain jurisdictions, healthcare in the EU, public-sector workloads in the US and UK—may be migrated into Hyperforce regions with a stated compliance posture that does not actually meet the customer's regulatory obligation. Verify the Hyperforce region's compliance certifications against your specific regulatory requirement before the migration; do not rely on Salesforce's general public statements about Hyperforce compliance.
The renewal uplift the migration carries
The migration paperwork almost always includes a clause that the migration "does not constitute a renewal" and therefore the renewal uplift is calculated against the next anniversary as if no change had occurred. This is the seller-friendly default. The buyer-friendly position is to treat the migration as a renewal opportunity: reset the term, lock the renewal uplift cap, refresh the contact baseline, and request a multi-year price hold in exchange for the commitment.
Salesforce will resist this framing because the migration paperwork is typically simpler internally than a full renewal, and the account team would prefer to defer the full renewal conversation to the original anniversary. The buyer should push back on this. The migration is being scheduled on Salesforce's timeline; the negotiation leverage that creates should be used.
The four migration conversations to run in parallel
1. Edition mapping conversation
Owned by the marketing operations team. Output: a documented feature inventory mapped to MCAE edition entitlements, with a recommended lateral or upgraded mapping and a justification for each.
2. Contact baseline conversation
Owned by the data team. Output: a fresh Mailable Contact count from the MCAE tenant, dated within 30 days of the order form, with the legacy Pardot prospect count for comparison.
3. Hyperforce region conversation
Owned by IT security and compliance. Output: a documented mapping of MCAE workloads to Hyperforce regions, with each region's compliance posture verified against your regulatory obligations.
4. Commercial conversation
Owned by procurement and finance. Output: a renegotiated order form with the lateral edition, the lower contact baseline, the regional pricing clarified, and a refreshed renewal uplift cap.
What the post-migration contract should look like
A well-negotiated MCAE migration contract has six distinguishing features. The edition is laterally mapped from the legacy Pardot edition unless the customer affirmatively wants more capability. The Mailable Contact baseline is set from a fresh count taken during cut-over, not from the historical prospect number. The Hyperforce region is explicitly named, with its compliance posture confirmed in writing. The renewal uplift is capped in dollars, with a 3-5% maximum. A true-down right is included tied to a Salesforce-produced usage report. And the term is structured to position the next renewal alongside the broader Marketing Cloud Engagement contract, so that both can be negotiated together with full leverage.
Benchmark outcomes
Across recent Pardot-to-MCAE migration engagements, the median three-year TCV reduction was 24%. The top-quartile outcomes—reserved for buyers who started the conversation 90+ days before the proposed migration date and ran all four parallel conversations above—reached 38-45% reductions. The bottom-quartile outcomes were customers who accepted the Salesforce-proposed default mapping and signed the migration paperwork without amendments; they typically saw a 15-20% net cost increase over the following three years.
Where to start
If a Pardot-to-MCAE migration is on your calendar, the most immediately useful step is the feature inventory. List every Pardot feature your team actually uses in production—not every feature licensed, but every feature with active workflows behind it. Map each feature to MCAE entitlements. That document is the foundation of the edition conversation and, by extension, of the entire migration negotiation. Without it, the default mapping wins. With it, the lateral mapping is achievable in roughly 80% of cases we have advised on.
The Pardot-to-MCAE migration is a rare opportunity: a Salesforce-initiated contractual reset that opens up renegotiation rights without requiring the buyer to manufacture a forcing function. Buyers who recognize this opportunity and prepare for it routinely save more than they would save at an ordinary renewal. The migration is happening on Salesforce's timeline. The savings are available on the buyer's terms.
The technical migration steps and the contract steps that shadow them
The technical migration from legacy Pardot to MCAE on Hyperforce typically follows a defined Salesforce-managed sequence: tenant provisioning on Hyperforce, data migration, integration re-pointing, user re-provisioning, parallel-run validation, and cut-over. Each technical step has a corresponding contractual step that, if missed, costs the buyer leverage.
Tenant provisioning is the moment to lock the Hyperforce regional pricing question. Once the tenant exists, the region is decided; the contract should reflect the region's compliance posture and any regional premium in writing.
Data migration is the moment to lock the Mailable Contact baseline. The migration window is the only time a fresh count from the new tenant naturally exists; capture it, document it, and use it as the contract baseline.
Integration re-pointing is the moment to inventory active connections. Many legacy Pardot tenants accumulate connections to systems no longer in use; the migration is the cleanest opportunity to decommission them, and the inventory becomes the foundation for accurate sizing of the post-migration data flow.
User re-provisioning is the moment to right-size the user count. Legacy Pardot tenants frequently have users licensed for roles that no longer exist; the re-provisioning is the cleanest opportunity to return unused licenses.
Parallel-run validation is the moment to measure the actual data volume the new tenant will process. The measured volume becomes the foundation for the Data Cloud capacity sizing (if Data Cloud is in scope) and for any Marketing Cloud Contact recalibration.
Cut-over is the contractual reset. The order form amendment effective at cut-over should reflect all of the above: regional pricing, contact baseline, user count, connection inventory, data volume sizing.
The Engagement Studio rewrite question
One of the technical complications of the Pardot-to-MCAE migration is the Engagement Studio rewrite. Engagement Studio is the workflow engine that powers most Pardot automations; the MCAE platform has expanded the engine substantially, but the migration is not a perfect lift-and-shift. Most enterprise customers find that 15-30% of their existing Engagement Studio workflows need meaningful rework during the migration—either because the underlying API calls have changed, or because the new platform supports patterns that the old workflows worked around.
The cost implication is real. A full Engagement Studio rewrite for an enterprise tenant typically requires 200-600 hours of marketing operations effort, either internal or contracted. Salesforce Professional Services will offer to scope and execute this work; the per-hour rates are at the higher end of the market, and the negotiation flexibility on Professional Services is materially better when the services scope is sized at the same time as the license amendment.
The custom object considerations
Custom objects in legacy Pardot were a relatively constrained feature, with edition-tied limits and a sometimes-quirky relationship to the underlying CRM. MCAE has expanded custom object support substantially, and the migration is the natural moment to revisit how custom objects are structured. Customers with significant custom object usage should plan for a custom object schema review during the migration, with explicit attention to whether the new schema falls within the edition's custom object entitlement.
This is one of the situations where the lateral-edition strategy can run into a real constraint. If your legacy Pardot deployment uses custom objects beyond the MCAE Plus or Advanced entitlement, the lateral mapping may not be operationally viable. The right time to discover this is during the feature inventory exercise, before the commercial negotiation begins. The wrong time is at cut-over.
The Salesforce CRM integration version
The Salesforce CRM connector for legacy Pardot has been through multiple versions over the years, and the MCAE platform requires the most recent version. For customers running an older connector, the migration is effectively a forced connector upgrade. The upgrade carries some operational risk—field mappings, sync behaviors, and dedupe logic can all behave differently—and should be planned as a discrete workstream rather than as a side effect of the platform migration.
The commercial implication is that customers with older connector configurations may need additional Salesforce Professional Services or partner support to navigate the upgrade safely. That cost should be modeled in the migration business case, alongside the license cost, the Engagement Studio rework, and the custom object work. Customers who model the full migration cost—not just the license line—make better-informed commitment decisions and negotiate more effectively, because the full cost view creates real pressure on each individual line item to justify itself.
The customer-side runbook
The customers we advise who execute the Pardot-to-MCAE migration most effectively follow a defined runbook. Three to four months before the proposed migration date, they assemble the feature inventory, the user-by-role analysis, and the Engagement Studio workflow inventory. Two to three months before, they engage the commercial conversation with the four parallel tracks described earlier. One month before, they sign the amended order form with the lateral edition, the recalibrated contact baseline, the regional pricing clarity, and the renewal uplift cap. At cut-over, they execute the technical migration with the contractual reset already in place. Post-cut-over, they validate that the actual operational footprint matches the contractual commitments.
This sequence works because it puts the buyer's preparation ahead of Salesforce's timeline, rather than racing to catch up after the migration has been scheduled. The customers who follow this sequence consistently land in the top-quartile outcomes—the 38-45% TCV reductions that look impossible to customers who treat the migration as primarily a technical event. The migration is a technical event. It is also the rarest negotiation opportunity in the Salesforce portfolio: a vendor-initiated reset that opens up renegotiation rights without requiring the buyer to manufacture a forcing function. The buyers who recognize that opportunity capture the value; the buyers who do not, pay for it.