Pardot to HubSpot Data Migration
Leaving Salesforce's marketing stack? Settle automates the mapping between Pardot's prospect model and HubSpot's contact-campaign architecture — preserving lead data, scoring history, list segmentation, and engagement records.
Working with enterprise teams on active migration programs
Days
to production-ready mappings
Roughly half
the cost of consulting-led delivery
Every row
validated before go-live
Enterprise migrations routinely run months behind schedule. Yours doesn't have to.
This guide is for VPs of IT, data architects, and migration leads at companies moving data from Salesforce Marketing Cloud Account Engagement to HubSpot — whether you're scoping, planning, or mid-program.
Pardot (Salesforce Marketing Cloud Account Engagement) stores marketing data in prospects with list memberships, engagement histories, scoring models, and automation rules tied to the Salesforce CRM. HubSpot uses contacts with lifecycle stages, workflows, and native CRM integration. Settle translates Pardot's prospect-centric model to HubSpot's unified marketing-sales architecture.
Based on the founding team's enterprise migration experience
Last updated July 2026
How Settle automates your Salesforce Marketing Cloud Account Engagement to HubSpot migration
Settle maps Pardot prospects to HubSpot contacts with grade-and-score translation — converting Pardot's combined grading and scoring model to HubSpot's lifecycle stages and lead score with threshold mapping you approve.
Engagement history is preserved — email opens, clicks, form submissions, and page views are mapped to HubSpot's activity timeline with timestamps and attribution data intact.
List segmentation criteria are documented and translated — each Pardot dynamic list's filter conditions are converted to HubSpot active list syntax for faster recreation.
Scoring rules and Engagement Studio programs are cataloged field-by-field — generating workflow rebuild documentation for the HubSpot marketing team.
Get your Salesforce Marketing Cloud Account Engagement to HubSpot mapping analysis — see results in under an hour
Migration timeline: manual vs. Settle
Traditional approach
Timeline
2–4 months
Estimated cost
$75K–$250K
Team size
2–4 consultants
Typically requires
×Manual field mapping in spreadsheets
×Custom ABAP/SQL extraction scripts
×3–5 mock migration cycles
×Dedicated source system consultants
×Manual reconciliation testing
With Settle
Enterprise benchmarksTimeline
Days
Estimated cost
A fraction of consulting cost
Team size
1 internal resource
Included
✓Schema profiling & analysis
✓AI-generated field mappings
✓Transformation SQL
✓Validation & readiness reports
✓Production-ready load files
Common challenges migrating from Salesforce Marketing Cloud Account Engagement to HubSpot
Prospect to Contact with lifecycle staging
Pardot prospects have grades (profile quality) and scores (engagement level) that together determine lead readiness. HubSpot uses lifecycle stages and lead scores as separate concepts. Translating Pardot's grade+score model to HubSpot's lifecycle stage + lead score requires defining new qualification thresholds.
Explore related migrations →Scoring model translation
Pardot's scoring uses page view points, email engagement points, form submission points, and custom scoring rules. HubSpot's lead scoring (available on Professional+) uses different criteria structures. The scoring rules must be rebuilt in HubSpot — Settle documents every Pardot scoring rule for the rebuild.
Explore related migrations →List segmentation recreation
Pardot's dynamic lists use criteria based on prospect fields, activities, and custom scoring thresholds. HubSpot's active lists use different filter syntax with AND/OR logic. Each Pardot dynamic list must be analyzed and recreated as a HubSpot active list with translated criteria.
Explore related migrations →Engagement Studio to HubSpot Workflows
Pardot's Engagement Studio programs (multi-step nurture sequences with branching logic) must be rebuilt as HubSpot workflows. The automation logic doesn't migrate — Settle documents the program structure, trigger conditions, and field references for each Engagement Studio program.
Explore related migrations →Salesforce CRM data coordination
If migrating both Pardot and Salesforce CRM to HubSpot, the data must be coordinated — Salesforce Leads/Contacts synced with Pardot prospects need unified migration to avoid duplicates. Settle handles the deduplication across both data sources.
Explore related migrations →Salesforce Marketing Cloud Account Engagement to HubSpot field mapping — what data moves
10 data objects typically migrated
| Source Object | → | Target Object |
|---|---|---|
| Prospect | → | Contact |
| Prospect Score | → | HubSpot Score / Custom |
| Prospect Grade | → | Custom Property |
| List Membership | → | List / Campaign |
| Email Engagement | → | Email Activity |
| Form Submission | → | Form Submission |
| Page View | → | Page View Activity |
| Custom Fields | → | Custom Properties |
| Tag | → | Custom Property / List |
| Campaign | → | Campaign |
Typical enterprise migrations include 500K–10M+ records across these objects. Settle handles profiling and mapping at enterprise scale.
The cost of manual Salesforce Marketing Cloud Account Engagement to HubSpot migration
Pardot to HubSpot migrations happen when companies leave the Salesforce ecosystem — typically moving both CRM (Salesforce to HubSpot) and marketing automation in the same transition. They also happen when companies that already use HubSpot CRM want to consolidate marketing automation from Pardot into HubSpot's all-in-one platform. The drivers are cost reduction (Pardot + Salesforce licensing is expensive), simplification (one platform instead of two), and HubSpot's superior marketing user experience.
The migration maps Pardot's prospect-centric model to HubSpot's contact model. Pardot prospects become HubSpot contacts with property translation. Pardot's scoring model (based on engagement and profile criteria) needs recreation in HubSpot's lead scoring. List segmentation, email engagement history, and form submission data all require structural translation. Pardot's automation rules and engagement studio programs must be rebuilt as HubSpot workflows.
Companies typically handle this with CSV exports from Pardot and HubSpot's import tool. The scoring model rebuild, list recreation, and engagement history preservation require significant manual effort.
Consulting-led delivery for migrations in this class typically runs $75K–$250K. Settle prices it fixed and scoped — read the full cost breakdown.
Frequently asked questions
Exceptions surface before the first load, not after the third.
Built by the team that ran Fortune 500 migrations by hand. Currently onboarding enterprise design partners on active migration programs.
Ready to migrate from Salesforce Marketing Cloud Account Engagement to HubSpot?
Tell us about your migration and we'll show you how Settle can help.
No commitment required. We'll review your migration scope and share a preliminary assessment within 48 hours.