Skip to content

Migration guide · Marketing Automation

Pardot (Account Engagement) to HubSpot migration

Marketing Cloud Account Engagement (Pardot)HubSpot Marketing Hub

Short answer

Moving from Pardot (Marketing Cloud Account Engagement) to HubSpot Marketing Hub migrates prospects, lists, forms, email templates, scoring and engagement programs into HubSpot contacts, lists, forms, workflows and lead scoring, with HubSpot syncing to Salesforce through its native connector.

Why firms make this move

Firms switch to gain ease of use, stronger content and website tools, and simpler reporting, while keeping Salesforce as the CRM. The work is mostly rebuilding assets and automation cleanly rather than copying everything.

What moves

  • Prospects and their consent status
  • Lists and segments
  • Forms and landing pages
  • Email templates
  • Scoring and grading as HubSpot lead scoring
  • Engagement programs as workflows

How the data maps

FromTo
ProspectContact
ListList or segment
Engagement programWorkflow
Score / gradeLead score properties
Form handlerHubSpot form or non-HubSpot form capture

See the field-by-field map ↓  ·  Migration architecture ↓

What to watch out for

  • Opt-outs that must carry over before the first send
  • Email authentication and sending domains
  • Salesforce sync rules and field ownership
  • Historical engagement data that does not migrate

How Vantage Point runs the migration

  1. Inventory assets and automation
  2. Set up HubSpot–Salesforce connector and field mapping
  3. Migrate contacts, opt-outs and lists
  4. Rebuild forms, emails and workflows
  5. Authenticate sending domains
  6. Parallel run and cutover

Typical timeline

Typically 4 to 8 weeks.

Frequently asked questions

Do opt-outs transfer?

Yes, and they must. We import unsubscribes and preferences before any email is sent from HubSpot.

Does historical email engagement migrate?

Not as native HubSpot engagement history. Key metrics can be stored as properties for reference.

Last reviewed October 2, 2026 by the Vantage Point team. Browse all migration paths →

Migration architecture

How data flows: Pardot (Account Engagement) to HubSpot migration

CRM Middleware / connector layer Connected system
What syncs between systems
FromToWhatDirectionTimingHow
Account EngagementHubSpotvia Export & map Prospects, lists & opt-outs → one-way test loads, then cutovermigration tooling
HubSpotSalesforcevia HubSpot–Salesforce connector Leads, contacts & campaign dataReplaces the Account Engagement connector. ⇄ two-way real-timenative connector

A typical pattern, simplified. Your design depends on licenses, data ownership and volumes, which we settle in discovery.

Field-level map

Pardot (Account Engagement) to HubSpot: field by field

12 mappings we start from on this migration, 8 of which need a transform, a lookup or a decision. Every project gets its own signed-off version; this is the baseline.

FromToHowNotes
ProspectEmail / first name / last name Contactemail / firstname / lastname req direct Email is the de-duplication key.
ProspectOpted out ContactSubscription status req manual review Load opt-outs before the first send.
ProspectScore ContactCustom score property manual review Rebuild the scoring model in HubSpot. Keep the old score for reference.
ProspectGrade ContactCustom property direct
ProspectCustom fields ContactCustom properties direct
Static listMembers Static listMembers direct
Dynamic listRules Active listFilters rebuild
Engagement Studio programSteps and rules WorkflowActions and branches rebuild
Form / form handlerFields and completion actions HubSpot formFields and follow-up workflow rebuild
Email templateContent Marketing email templateContent rebuild
Custom redirectTracked link Tracking URL— rebuild
Prospect activitiesVisits, opens, clicks —— drop History does not load natively. Export it if you need to keep it.

Field names are the platforms' standard API names; your org's custom fields are mapped during discovery. What the "How" labels mean

How labels
direct
Value copies across unchanged.
picklist map
Each source value is mapped to a target value.
lookup
Matched to an existing record, such as a user by email.
association
Becomes a relationship between records, loaded in a later pass.
derive
Calculated or cleaned during the load.
split / concat
One field becomes several, or several become one.
rebuild
Configuration or automation that is rebuilt rather than moved.
drop
Not migrated, deliberately.
manual review
Needs a decision with your team before the load.