A Pardot to HubSpot migration requires 6 to 12 weeks and involves seven phases: audit, field mapping, automation translation, lead scoring rebuild, asset recreation, parallel validation, and cutover. Budget $15,000 for mid-market teams to $80,000+ for enterprise environments with complex Engagement Studio programs and deep Salesforce dependencies.
TL;DR
|
In 2022, Salesforce renamed Pardot to "Marketing Cloud Account Engagement." Fourteen syllables to say what used to take two. That rebrand tells you more about the product direction than any changelog.
The roadmap has drifted deeper into the Salesforce stack each quarter since. Your marketing team once ran Pardot independently. Now basic campaign changes require admin access and Salesforce permissions. That is not a platform serving marketers. That is a platform serving Salesforce's architecture.
HubSpot Marketing Hub went the opposite way. CRM, automation, content, and reporting under one roof that marketers control. For teams paying $1,250+ monthly for Pardot plus Salesforce licensing, the pardot vs hubspot cost comparison has become the spreadsheet nobody argues with.
The trigger for most teams that switch from pardot to hubspot is not a single failure. It is death by a thousand syncs. Each disconnected tool is another integration to maintain, another place where attribution leaks. HubSpot eliminates the duct tape. That is the business case, and it fits on one slide.
We have a name for what we find inside most Pardot instances: the archaeological layer.
Three years of automation rules stacked on each other, each a monument to a campaign manager who has since left. A scoring model everyone references and nobody trusts. Dynamic lists filtering on fields deprecated two cleanups ago.
The instinct when starting a Pardot to Hubspot migration is to export everything, import everything, recreate the structure. That instinct imports every broken process you accumulated. You move houses and bring the junk drawer.
Marketing automation migration done right is not a copy. It is an edit. And unlike a
replatform where the risk is broken URLs, here the risk is invisible: scoring that silently stops qualifying, workflows firing on wrong contacts, attribution that looks fine but maps to nothing.
|
Pardot → HubSpot |
What Catches Teams Off Guard |
|
Prospects → Contacts (CRM-native) |
Sales sees everything marketing sees. If you hid unqualified contacts, that curtain is gone. |
|
Engagement Studio → Workflows |
Different branching logic. Every program gets redesigned. This is where timelines blow up. |
|
Automation Rules → Workflows + Active Lists |
Pardot rules split across two HubSpot systems. Mismap and you get ghost automations. |
|
Scoring + Grading → HubSpot Score |
One default scoring model. Grading (A-D) must be custom-built. Tell sales before go-live. |
|
Campaigns (single-touch) → Campaigns (multi-touch) |
Historical campaign data does not translate. Fresh start, not carryover. |
|
Form Handlers → No direct equivalent |
Rebuild with HubSpot forms or non-HubSpot form capture. Surprises everyone. |
|
Dynamic Content → Smart Content |
Different rule logic: list membership, device, lifecycle stage. |
|
Variable Tags → Personalization tokens |
Different syntax. Ctrl+H will not save you. |
Pardot and HubSpot have fundamentally different data models. Pardot uses Prospects as a separate object syncing with Salesforce Leads/Contacts. HubSpot uses a unified Contact inside the CRM natively. No separate marketing database. That changes everything downstream.
Your Pardot contract is expiring. Your marketing automation shouldn't expire with it. We map your Pardot instance to HubSpot and tell you what moves, what gets rebuilt, and what gets left behind.
[Get a Free Migration Assessment →]
Most guides list 19 steps because long lists look thorough in a table of contents.
Our Pardot to HubSpot Migration playbook highlights 7 phases because that is how the work sequences when you are running it, not writing about it.
Every Pardot instance carries 30% to 50% more assets than the team uses. Engagement Studio programs running on churned contacts. Automation rules that conflict with each other. Lists segmented by fields nobody remembers creating.
Export the full inventory. Flag what is active versus what has been untouched for 18 months. Then decide what dies. Migrating dead workflows into HubSpot gives them a new zip code, not a new purpose.
Field mapping is the broccoli of migration work. Skip it and everything downstream tastes wrong.
Build a four-column mapping document: Pardot field, Salesforce field, HubSpot target property, action (map/merge/archive/create). Run data cleaning in parallel.
If your database has 100,000 contacts, plan to migrate 40,000 to 60,000 after deduplication and hygiene. That is not a loss. That is a haircut. HubSpot pricing scales with contacts.
This phase has a body count. More migrations stall here than anywhere else.
The translation from engagement studio to hubspot workflows is a redesign. Engagement Studio uses linear listener-action-rule nodes. HubSpot uses if/then branches with broader actions per step. Start with your 3 to 5 highest-value programs. Document triggers, logic, wait steps, and actions. Then rebuild for HubSpot's engine.
Most teams need fewer workflows in HubSpot than they had Engagement Studio programs in Pardot. Fewer moving parts, fewer 2 AM "why did that contact get enrolled?" Slack messages.
One difference worth designing around: Pardot wait steps measure delays in days or calendar dates. HubSpot supports time delays, specific dates, and event-based triggers. If your Pardot nurture has a 14-day gap between touches and your sales cycle is 30 days, that timing has been costing pipeline velocity. Fix it in the rebuild. Replicating the gap because "that is how Pardot had it" is not migration. It is nostalgia.
If your scoring sends 200 MQLs monthly and sales follows up on 30, the problem was never Pardot. The model is broken. Fix it now. You will not get a better opportunity.
Create two custom HubSpot score properties: engagement and fit. Rebuild criteria from scratch. Do not copy Pardot's point values. The platforms weigh actions differently.
No automated export path exists for Pardot email templates. None. Zero.
Identify your top 10 to 15 templates by send frequency and performance. Rebuild in HubSpot's editor. Templates not sent in 6 months get a quiet funeral. Landing pages get rebuilt, not cloned. HubSpot's builder is more capable. Direct recreation would be a downgrade.
Run both platforms simultaneously for 2 to 4 weeks. New leads enter HubSpot. Existing nurtures finish in Pardot.
Validate: contact sync, scoring outputs, workflow triggers, email deliverability, form submissions. Do not cut over until you have sent at least two live campaigns from HubSpot and confirmed reporting. Sales notices discrepancies before marketing does. Validate first. Celebrate third.
Cutover is mechanical. The 30 days after cutover is where silent failures surface.
Deactivate Pardot, update DNS, replace forms, swap tracking codes. Then monitor daily. Not weekly. Daily. Keep Pardot in read-only for 90 days. Historical data lives nowhere else. We have seen teams lose three years of performance data because someone decommissioned 48 hours too early. Not a pleasant Friday.
|
Complexity |
Contacts |
Timeline |
Cost |
|
Standard |
Under 50K, <15 workflows |
4–6 weeks |
$15K–$30K |
|
Mid-market |
50K–200K, 15–40 workflows |
8–10 weeks |
$30K–$55K |
|
Enterprise |
200K+, 40+ workflows |
12–16 weeks |
$55K–$80K+ |
Dual migrations (Pardot + Salesforce CRM to HubSpot) add 3 to 4 weeks and $15K to $25K. The Hubspot marketing hub migration complexity comes from deal pipeline mapping and Salesforce report recreation.
Engagement Studio activity history dies with Pardot. Opens, clicks, program step data do not transfer. Export every summary report before decommissioning.
We have watched teams lose this data because the admin assumed someone else backed it up. Nobody had.
Pardot campaigns and HubSpot campaigns are different species. Pardot: single-touch, one campaign per prospect. HubSpot: multi-touch containers across all assets. Mapping one to the other produces fiction, not attribution. Start fresh.
Your Salesforce integration changes silently.
TheHubSpot-Salesforce connector runs different sync rules than Pardot's.
Field direction, conflict resolution, inclusion lists all need deliberate setup. We have seen contact records wiped from default sync settings during a marketing automation migration. Four hours to fix. Four weeks to rebuild sales trust.
Your team will resist the change, even if they championed it. Train before cutover, not after. Teams that train before adopt in 30 days. Teams that skip training spend 90 days using spreadsheets on the side.
The difference is not the platform. It is the approach.
Failed migrations copy everything. Clean migrations edit ruthlessly. They fix the scoring model sales never trusted, kill workflows nobody can explain, and consolidate tools.
OneMetric scopes the risk, runs the migration, and stays through the 30-day post-cutover window when silent failures surface.
Your Pardot renewal is approaching. Your marketing automation should get smarter, not more expensiveWe review your Pardot instance and deliver a migration roadmap in 5 business days.
[Talk to a Migration Specialist →]