Pardot to Marketing Cloud Next: 2026 Migration Decision Framework

Salesforce announced Marketing Cloud Next at Connections '25 in June 2025 — the Data Cloud-native, Agentforce-powered successor to the broader Marketing Cloud portfolio. Within weeks, Salesforce consulting partners began pitching Pardot-to-MCN migrations to anyone listening. Most of those pitches were premature.

The question isn't whether Marketing Cloud Next will eventually replace Pardot for most B2B teams. The trajectory points that direction. The question is whether your team should be among the first to migrate in 2026 — and that question deserves a rigorous decision framework, not vendor enthusiasm.

This guide provides that framework. It's written from the perspective of someone who has spent 7+ years architecting Salesforce + Pardot ecosystems and has been actively researching MCN architecture and migration patterns since the announcement. Based on patterns from 10+ B2B Pardot audit engagements across SaaS, fintech, insurance, and professional services, most teams I assess should wait. A few should migrate now. The framework below tells you which group you're in.

The Marketing Cloud Next Reality (2026)

Three facts shape the migration conversation in 2026, and most pitches you'll receive obscure all three.

Fact 1: Salesforce calls it "convergence, not migration"

The official Salesforce position is that Marketing Cloud Next represents architectural convergence across Marketing Cloud Engagement, Pardot/MCAE, and the broader portfolio — not a forced migration of existing customers. This isn't marketing spin. Salesforce maintains a substantial Account Engagement customer base that has been on the platform for over a decade, and the company has explicitly committed to a parallel coexistence approach where existing investments are preserved.

What this means practically: Pardot/MCAE continues to receive updates, support, and security patches. Salesforce has not announced any end-of-life or sunset date for Account Engagement. Existing customers face no contractual obligation to migrate, and Salesforce explicitly frames the transition as "convergence, not migration."

More importantly: Salesforce has built a specific pathway for Account Engagement customers to access Marketing Cloud Next features without a full migration. The mechanism is called Account Engagement+, which provides Permission Set Licenses (PSLs) granting access to Marketing Cloud Growth and Advanced edition functionality alongside your existing Pardot environment. This is a fundamentally important detail that many migration pitches obscure: for many Pardot teams, the right move in 2026 is enabling Account Engagement+ rather than migrating off Pardot entirely.

Fact 2: New feature investment is shifting toward MCN

While Pardot remains supported, the trajectory of new feature development clearly favors Marketing Cloud Next. Agentforce integration, Data Cloud-native architecture, unified B2B-B2C journey orchestration, and the AI-first roadmap all live in MCN. Pardot's roadmap is increasingly maintenance-mode.

This creates a slow squeeze rather than a hard cutoff. Pardot users won't lose their platform, but they'll lose access to the new capabilities Salesforce is building. For teams whose competitive position depends on AI-first marketing automation, this matters by 2027. For teams whose Pardot setup already meets their needs, it doesn't matter much in 2026.

Fact 3: MCN itself is still maturing

Marketing Cloud Next is real, shipping, and used by Salesforce reference customers — but the platform is in its first year of general availability. Feature gaps versus Pardot exist. Best practices are still being codified. Implementation patterns vary across consulting partners. Migration tooling from Pardot to MCN is incomplete.

This is the most underdiscussed fact in 2026 migration conversations. Migrating to a product still finalizing its migration story is operationally risky. Most teams should let MCN go through 2-3 quarterly release cycles before committing to a complex migration project.

Who Should Read This Guide

This framework is built for three specific personas. The right answer for each differs significantly.

Persona 1: Existing Pardot user with active deployment

You run Pardot today. Your team uses it. Lead scoring works (or works enough). You have a Salesforce sync, Engagement Studio programs, and email templates. The platform isn't perfect, but it's functional. Now you're hearing about Marketing Cloud Next and wondering whether you need to plan a migration.

Default recommendation: Don't migrate in 2026 unless the framework below identifies a strong driver. For most teams in this profile, the right move is enabling Account Engagement+ to access MCN features incrementally while continuing to operate on Pardot.

Persona 2: New B2B buyer with no Pardot history

You're evaluating marketing automation platforms for the first time, or you're consolidating from a non-Salesforce stack. Salesforce reps are pitching MCN. Other vendors are pitching their platforms. You don't have legacy Pardot to consider.

Default recommendation: Evaluate both Pardot and MCN seriously. The decision depends heavily on your Data 360 strategy, Agentforce roadmap, B2B-versus-unified focus, and timeline pressure. The framework below applies equally to greenfield decisions.

Persona 3: Mid-migration or already-decided team

You've already started migration planning, or your leadership has committed to MCN, or you're evaluating consulting partners for the project. You're past the "should we migrate" question and into "how should we migrate."

Default recommendation: Skip ahead to the migration path options section. The framework still helps validate the approach, but the decision section won't change your direction.

Pardot vs Marketing Cloud Next: Architectural Comparison

Before evaluating the migration decision, understand what's actually different between the platforms. License pricing comparisons miss most of the architectural reality.

The pattern: MCN is architecturally newer and more capable for AI-first, data-unified, B2B-and-B2C teams. Pardot is operationally proven and more mature for pure B2B mid-market with established workflows. Neither is universally better. The right answer depends on which architectural dimensions matter most for your team in the next 3-5 years.

For deeper context on platform pricing differences, see our Pardot Pricing 2026 guide covering the 3-year total cost of ownership model.

Scoring Model: When to Migrate vs Wait

Add up your scores from all seven questions. The total (out of 21) maps to a recommendation tier.

4 Migration Path Options

If your assessment indicates migration makes sense, the next decision is how to migrate. Four patterns dominate, each with distinct tradeoffs. The most overlooked option for existing Pardot users is the first one — staying on Pardot while accessing MCN features.

Path 1: Account Engagement+ (no full migration)

For existing Pardot customers, Salesforce offers the Account Engagement+ pathway: Permission Set Licenses that grant access to Marketing Cloud Growth or Advanced functionality alongside your existing Pardot environment. This isn't a migration — it's an extension. You keep Pardot running for proven B2B workflows while adopting MCN capabilities (Agentforce campaign creation, native SMS/WhatsApp, advanced personalization) selectively.

Best for: Most existing Pardot customers in 2026. The Account Engagement+ path captures MCN value (AI agents, multichannel messaging, Data 360 segmentation) without the operational risk of full platform migration. Teams can experiment with MCN features on real workflows before committing to migration timeline.

Cost profile: Lower than full migration. Pricing depends on Salesforce Foundations enablement (free for baseline Data 360 access), additional credits as needed, and incremental implementation work to enable specific MCN features. Typical investment: $10,000-$50,000 for proper enablement and use case configuration, much less than full migration scope.

Path 2: Big Bang (one-time cutover)

The Big Bang approach migrates everything in a single coordinated cutover. Pardot is wound down on a specific date; MCN takes over the same day. All programs, lists, scoring, and integrations transition simultaneously.

Best for: Small B2B teams with simple Pardot setups, low automation complexity, and acceptable risk tolerance for short-term disruption. Typical timeline: 4-6 months total project, 1-week cutover window.

Avoid if: Complex Pardot setup with many active programs, significant integration dependencies, or business-critical automation that cannot tolerate even brief outages. The risk profile is meaningful for mid-market and enterprise teams.

Path 3: Phased Parallel (recommended for full migrations)

The Phased Parallel approach runs both Pardot and MCN simultaneously for a 3-6 month transition window. New programs launch in MCN while existing Pardot programs continue running. Migration happens program-by-program, allowing teams to validate MCN behavior before retiring Pardot equivalents.

Best for: Most B2B mid-market teams committed to full migration. The parallel approach reduces operational risk, allows learning by doing, and provides natural rollback if MCN encounters issues. Typical timeline: 8-12 months total project, 3-6 months parallel running.

Cost consideration: Running both platforms in parallel adds direct license costs during the overlap window. This is a worthwhile risk-reduction investment for most teams. Plan for it explicitly in budget.

Path 4: Hybrid (Data 360 first, MCN later)

The Hybrid approach decouples the Data 360 (Data Cloud) foundation work from the MCN migration. In 2026, the team implements Data 360 properly: data unification, identity resolution, customer 360 architecture. Pardot continues running on top of Data 360 through the Account Engagement: Data 360 Connector. In 2027 or later, MCN replaces Pardot as the activation layer.

Best for: Enterprise teams where Data Cloud strategy is significant on its own merits, and MCN migration is a downstream benefit. Also suitable for teams that want to capture Data 360 value immediately without committing to MCN platform risk in 2026. Typical timeline: 12+ months for Data 360 foundation, additional 6-9 months for MCN activation.

Avoid if: Your Data Cloud business case is weak independent of MCN. The Hybrid path requires Data 360 investment to stand on its own — if MCN is the only reason to deploy Data Cloud, this path doesn't make sense.

MCN Migration Cost Reality Check

License costs are only one component, and Marketing Cloud Next pricing follows a different model than Pardot. Real migration cost includes pre-migration assessment, MCN license, Data 360 (Data Cloud) provisioning, implementation services, parallel running, manual content rebuild, and team enablement. Here's how the numbers actually break down based on publicly available pricing and consulting partner benchmarks.

Marketing Cloud Next license pricing (verified 2026)

Salesforce publishes two MCN editions for new buyers:

• Marketing Cloud Growth: starts at $1,500/month (org-based pricing, 2026) — entry-level marketing automation with core capabilities
• Marketing Cloud Advanced: starts at $3,250/month (org-based pricing, 2026) — predictive AI scoring, journey experimentation, conversational SMS/WhatsApp, advanced analytics

Critically, MCN uses a consumption-based credit model that replaces Pardot's tier-based pricing. License covers a baseline of Messaging credits, Einstein credits, and Data 360 credits — additional usage incurs additional cost. This makes MCN cost projections more variable than Pardot. Heavy email senders, high SMS volume, and AI-intensive workflows can significantly exceed baseline license cost.

For existing Account Engagement customers, the Account Engagement+ pathway provides MCN Growth or Advanced functionality via Permission Set Licenses alongside existing Pardot environment — typically more cost-effective than full migration for teams not ready to leave Pardot.

Cost component 1: Pre-migration assessment ($2,500-$5,000)

Structured 1-2 week diagnostic covering Data 360 readiness, Pardot architecture inventory, contract timing, ROI projection, and recommended migration approach. The cost aligns with established Pardot audit pricing tiers. Skipping this step is the most common reason migrations exceed budget by 30-50%.

Cost component 2: Implementation services

Implementation cost benchmarks for Salesforce marketing automation deployments in 2026 (based on publicly cited consulting partner pricing) follow established patterns:

• Small B2B teams: $5,000-$25,000 for QuickStart-level implementation with simple journeys, basic scoring, limited integrations
• Mid-market deployments: $25,000-$75,000 for proper architecture, multi-program journey design, integration mapping, custom configurations
• Enterprise multi-BU: $75,000-$200,000+ for complex deployments with multiple business units, advanced governance, custom Agentforce flows

MCN-specific implementation tends to land at the higher end of these ranges versus equivalent Pardot implementations because the platform is newer, consulting expertise is still developing, and many implementation patterns are still being codified across the partner ecosystem.

Cost component 3: Data 360 (Data Cloud) provisioning

This is the cost component most underbudgeted in migration planning. Marketing Cloud Next requires Data 360 as its data foundation — it's not optional infrastructure. Teams without existing Data Cloud commitment face additional cost and complexity:

• Data 360 license: usage-based credits — varies significantly with data volume and identity resolution complexity
• Data 360 implementation: $25,000-$100,000+ for proper data unification, identity resolution, customer 360 architecture
• Salesforce Foundations provides baseline Data 360 access at no additional cost — sufficient for some smaller MCN deployments but typically inadequate for mid-market or enterprise needs

Cost component 4: Manual content rebuild ($5,000-$25,000)

Critical detail often missed in migration scoping: as of early 2026, Salesforce has not released automated migration tooling for moving Marketing Cloud Engagement email templates, images, or content files to Marketing Cloud Next. Every template rebuild is a manual exercise. This applies to Pardot template migration as well — teams should budget explicitly for content recreation, not assume tooling will handle it.

Practical timeline benchmarks for asset rebuild work, based on patterns observed across migration engagements:

• Email templates: ~15 minutes per Lightning template, longer for Classic templates that require full rebuild from scratch
• Landing pages: ~30 minutes per page (longer for pages with complex CSS or embedded forms)
• Engagement Studio programs: ~30 minutes per program when mapped to MCN Flows (which use a different builder paradigm than Pardot's visual flow)
• Forms and Form Handlers: ~30 minutes per form, plus additional testing time for every web page that posts to a Form Handler endpoint
• Lists and segments: ~10 minutes per list when migrated 1:1, but most teams should triage lists down 60-80% before migration (most lists in mature orgs are unused)

For a typical mid-market B2B Pardot org with 50-100 active assets, asset rebuild alone runs 60-120 hours of focused work — roughly 2-3 weeks for a dedicated marketing operations resource, or 3-4 weeks when shared with other responsibilities. This is in addition to Data Cloud setup, integration work, and parallel running validation.

Cost component 5: Parallel running period ($10,000-$30,000)

For phased migrations, the overlap window adds direct license costs (running both Pardot and MCN simultaneously) plus operational overhead. Budget 3-6 months of parallel costs. This is a worthwhile risk-reduction investment for most teams.

Cost component 6: Team enablement ($5,000-$15,000)

Training the marketing operations team on MCN paradigms — different from Pardot's mental model. Includes admin enablement, documentation, runbooks, and post-launch support window. Often underbudgeted, leading to slow adoption and team frustration.

For comparison context on existing Pardot operating costs, see our 3-year Pardot TCO breakdown. Migration cost adds to ongoing platform costs — it doesn't replace them in 2026, since most teams will run parallel during transition.

Migration Pitfalls Most Teams Miss

Beyond the strategic decision of whether to migrate, several operational pitfalls consistently cause budget overruns and deliverability disasters. These come from patterns observed across Pardot environments — and validated against published guidance from Salesforce, Salesforce Ben, MarCloud, and Sercante experts. Most are invisible until the migration is well underway, by which point fixes are expensive.

Pitfall 1: List proliferation in mature Pardot orgs

Pardot orgs accumulate lists. Salesforce Ben's Pardot audit guidance and Sercante's published research note that Salesforce officially recommends a limit of 1,000 dynamic lists per Pardot org — a threshold reached by mature 5+ year deployments more often than teams realize. Across the Pardot environments I've assessed, list inventories of 200-400+ lists are typical for mature B2B orgs, with most of those lists either unused, duplicated, or near-duplicates of each other.

This matters for migration scope. Each Pardot list becomes a Data Cloud Segment in MCN, with field-mapping work that wasn't required when the lists existed only in Pardot. Migrating all of them without triage doubles the migration effort. The right sequence: inventory all lists, filter to those with members and active campaign use within the last 12 months, then collapse near-duplicates. Teams that skip this step typically discover the problem in week 4 of migration when the budget is already committed.

Pitfall 2: Apex domain authentication wrecks transactional email

This is a deliverability landmine that affects new MCN deployments specifically. When configuring authenticated email domains for Marketing Cloud Next, the temptation is to authenticate the apex domain (e.g., yourcompany.com) directly. Don't.

Authentication best practices from Cisco, Microsoft, and DMARC industry guidance all recommend using a dedicated subdomain (e.g., email.yourcompany.com or marketing.yourcompany.com) for marketing automation platforms. The reason: bulk email services should not share authentication infrastructure with your corporate transactional email. If you authenticate the apex domain for MCN, you risk overriding the SPF/DKIM/DMARC setup that already protects your Microsoft 365 or Google Workspace transactional sending. The damage typically appears 24-48 hours after authentication, when sales emails, password resets, and case notifications start landing in spam.

The fix is straightforward: use a subdomain. The cost of getting this wrong is reputation damage that takes weeks to repair.

Pitfall 3: Engagement data lookback windows must be set before activation

When connecting Account Engagement to Data Cloud (Data 360) for engagement history migration, the lookback window setting determines how much historical email, form, and page engagement data flows into the Unified Individual model. The default lookback is conservative. For B2B teams that rely on long-tail engagement signals (12-24 month nurture cycles are common), the default isn't enough.

Critically, the lookback setting must be configured before activating the connector. Backfilling historical data after activation requires re-establishing the connection — adding days to the timeline and risking data integrity. Teams often discover this when marketing asks for "everyone who engaged in the last 18 months" three weeks post-cutover and the data isn't there.

Pitfall 4: Form Handler endpoints have more dependencies than marketing remembers

Pardot Form Handlers — the integration mechanism that lets external web forms submit data into Pardot — accumulate dependencies over time. Marketing leadership typically remembers the major forms: lead capture, demo request, content gating. The reality across Pardot orgs I've assessed is that web pages posting to Form Handler endpoints typically number 3-5× higher than marketing recalls, including legacy event registration pages, partner microsites, and forms embedded in third-party tools.

During migration, every Form Handler endpoint must be inventoried, redirected to the new MCN equivalent, and tested. Skipping any single one means a form silently fails after cutover — sometimes for months before anyone notices the lead flow has stopped.

Pitfall 5: Data Cloud consumption costs can escalate quickly

Marketing Cloud Next runs on Data Cloud's consumption-based credit model, which is fundamentally different from Pardot's tier-based pricing. Salesforce Ben's Data 360 guidance notes that Data 360 uses consumption-based pricing where you only pay for what you actually use beyond your free credits.

The risk: configurations that seem reasonable in theory (e.g., refreshing a Data Graph every 15 minutes for "real-time" personalization) can multiply credit consumption 4-10× over the planning estimate. Default to daily refresh schedules; move to hourly or sub-hourly only for use cases where real-time activation drives measurable revenue. Salesforce provides the Digital Wallet for tracking consumption — set credit alerts at 80% of monthly budget and review consumption patterns monthly during the first six months post-launch.

The "Convergence Not Migration" Reality

Salesforce's official position on the Pardot-MCN transition deserves direct examination, because the framing affects every migration decision in 2026.

What Salesforce says

"Marketing Cloud Next represents convergence across our marketing portfolio — not a migration." Public statements emphasize that Pardot continues to receive support, that no end-of-life date has been announced, and that customers can choose their own pace.

What this means in practice

Three things happen simultaneously, even though Salesforce doesn't frame them this way:

• Pardot continues to operate — the platform isn't being shut down, and existing customers won't lose service in 2026 or 2027.
• New feature investment shifts to MCN — capabilities like Agentforce, advanced Data Cloud integration, and unified B2B-B2C orchestration only land in MCN. Pardot's roadmap is increasingly maintenance-focused.
• Renewal-time conversations will favor MCN — Salesforce reps will increasingly position MCN as the strategic platform during contract renewals, especially for customers expanding seat counts or adding products.

How this should affect your decision

"Convergence not migration" gives you time. It does not give you permanent stability on Pardot. The honest interpretation: plan for an eventual transition aligned with your strategic priorities. Don't rush in 2026 unless your specific drivers justify it. Don't ignore the trajectory — Pardot's strategic position weakens each year as Salesforce directs new investment toward Marketing Cloud Next.

For new B2B buyers without existing Pardot, the calculation is different. The "convergence" framing doesn't help you — you're choosing a starting platform. The question becomes whether to start on a mature platform (Pardot) that's slowly becoming legacy, or a newer platform (MCN) that's still maturing but represents the future direction.

When Pardot Still Wins in 2026

Honest analysis includes the cases where staying on Pardot — or even starting on Pardot as a new buyer — is the right answer. These scenarios are common and underdiscussed.

Scenario 1: Mature B2B-only operation with working Pardot

Your team uses Pardot for what it's designed for: B2B lead nurturing, scoring, Engagement Studio programs, Salesforce sync. The setup works. Lead scoring drives MQL handoffs that Sales actually trusts. Reporting answers the questions Marketing leadership asks. Migration would be replacing a working system with a maturing one — a risky exchange for marginal benefit.

Scenario 2: Team without dedicated marketing operations capacity

Migrations require client-side leadership. Without a dedicated marketing operations specialist (or team) who can lead requirements gathering, validate behavior, and own change management, migrations consistently fail to deliver expected outcomes. Teams in this situation should focus on building marketing operations capacity first, then revisit migration when capability exists.

Scenario 3: B2B SaaS under $5M ARR

Small B2B teams typically derive value from Pardot's mature B2B-specific features (scoring, grading, Engagement Studio). MCN's unified B2B-B2C capability, AI agents, and Data Cloud integration are designed for larger, more sophisticated marketing operations. The architectural sophistication of MCN exceeds the operational maturity of small B2B teams — meaning you pay for capabilities you can't yet use.

Scenario 4: No Salesforce Data Cloud commitment

MCN is Data Cloud-native. Without an existing Data Cloud commitment or roadmap, migrating to MCN means deploying Data Cloud as a precondition — adding $30,000-$100,000+ in infrastructure cost that wasn't in the original migration scope. For teams without independent Data Cloud business case, this scope expansion alone justifies waiting.

Scenario 5: Multi-year Pardot contract with significant remaining term

Teams that signed 3-year Pardot contracts in 2024-2025 face significant license sunk cost. Migrating immediately means paying for two platforms during the contract overlap. The economics rarely favor early migration — wait for renewal alignment unless other drivers are overwhelming.

When Marketing Cloud Next Genuinely Wins

Balance requires acknowledging where MCN is the right answer. Four scenarios make MCN migration clearly worthwhile in 2026.

Scenario 1: Existing Data Cloud + Agentforce strategy

Teams already invested in Data Cloud as a strategic platform, with active Agentforce adoption, gain real architectural value from MCN. The platform's native integration with these systems eliminates integration overhead that Pardot would require. For these teams, MCN isn't a migration — it's the natural extension of an existing strategy.

Scenario 2: Unified B2B-B2C orchestration requirement

Some businesses operate across both B2B and B2C contexts: SaaS companies with self-serve and enterprise tiers, financial services with consumer and institutional products, healthcare with provider and patient relationships. Pardot was designed B2B-only. MCN's unified architecture serves these blended models more naturally.

Scenario 3: Greenfield deployment with multi-year transformation budget

New B2B buyers — especially those with multi-year digital transformation initiatives and significant Salesforce investment commitment — should evaluate MCN seriously. Starting on MCN avoids future migration debt. The platform maturity gap is real but closes each quarter, and starting early on MCN positions the team to grow with the platform.

Scenario 4: Pardot setup that needs major rework anyway

Some Pardot teams face a different question: "Should we rebuild Pardot or migrate to MCN?" When the existing Pardot setup is so problematic that it requires substantial reconstruction — broken sync, abandoned scoring, unmanageable program complexity — the rebuild cost approaches migration cost. In this scenario, the rework budget is better spent on MCN than on rehabilitating an aging Pardot deployment.

The Pre-Migration Assessment

Whether the framework above pointed toward immediate migration, planned 2027 migration, or staying on Pardot, the next step is rarely "start the migration project." For teams scoring 12+ on the framework, the right next step is a formal Pre-Migration Assessment.

What the assessment delivers

A Pre-Migration Assessment is a structured 1-2 week diagnostic that produces a 15-25 page written report covering five areas:

• Data Cloud readiness review — current state of data infrastructure, gaps that affect MCN migration scope, recommended Data Cloud sequencing
• Pardot architecture inventory — programs, scoring models, integrations, custom configurations that need migration planning
• Contract timing analysis — how Pardot renewal dates, Salesforce contract structure, and procurement cycles affect migration economics
• ROI projection — financial model comparing 3-year cost of staying on Pardot versus migrating to MCN, including risk-adjusted scenarios
• Recommended migration approach — specific path (Big Bang, Phased Parallel, or Hybrid), timeline, sequencing, and team requirements

Why the assessment matters

Migration projects without a structured assessment typically run 30-50% over budget and 2-4 months over timeline. The assessment cost ($2,500-$5,000) is small relative to the migration project cost ($25,000-$200,000+) but provides the strategic clarity that prevents most cost overruns.

Equally important: the assessment provides a written recommendation that leadership can review. Migration decisions involving $50,000+ in scope deserve a written rationale, not a verbal pitch from a consulting partner. The assessment serves as that rationale — including the honest case against migration if the data doesn't support it.

What "honest assessment" actually means

The most valuable output of a Pre-Migration Assessment is sometimes the recommendation to not migrate. Across the Pardot teams I've assessed since the MCN announcement, roughly 60% should not migrate in 2026 — they score in the 7-11 range and have clear reasons to optimize current Pardot rather than rebuild on MCN. About 25% should plan for 2027 migration with 2026 used for preparation. Only about 15% have the combination of drivers that justifies immediate migration.

An assessment that always recommends migration isn't an assessment — it's a sales pitch with a report attached. The framework above is designed to produce honest answers, including answers that contradict vendor preferences.

How to Apply This Framework

The path forward depends on which persona matches your situation.

If you're an existing Pardot user

Run through the 7-question framework with your team. Score honestly. If your total lands in the 0-11 range (the most common outcome), focus 2026 on optimizing your current Pardot setup rather than rebuilding on MCN. A Pardot audit can identify the optimization opportunities that produce the highest ROI from your existing license investment.

If your score lands in the 12-16 range, use 2026 to prepare: evaluate Data Cloud strategy, assess consulting partners, align timing with Pardot renewal. Don't rush — preparation in 2026 produces better 2027 migration outcomes than reactive migration in 2026.

If your score lands in 17-21, begin the Pre-Migration Assessment now. Migration in 2026 is appropriate, but the assessment ensures the migration approach matches your specific situation.

If you're a new B2B buyer

The framework still applies, but Question 3 (contract lock-in) becomes irrelevant. Focus on Questions 1 (Data Cloud), 5 (Agentforce), 6 (timeline pressure), and 7 (internal capacity). Score above 12 favors MCN as starting platform; below 12 favors Pardot as starting platform with planned MCN migration in 2028-2029.

If you're already mid-migration

The framework helps validate the approach. If your current path matches the recommendations above, continue. If your current path conflicts (Big Bang for a complex enterprise team, for example), consider whether a course correction is worthwhile. Migration projects can be re-scoped mid-flight — it's expensive but cheaper than completing a misaligned project.

Pardot to Marketing Cloud Next migration in 2026 isn't the universal next step Salesforce partners often pitch. For most existing Pardot users, it's premature. For some new buyers, MCN is the right starting platform. The decision deserves rigor — a structured framework, an honest assessment, and a written recommendation. The framework above provides the first step. The assessment provides the rest.