Chapter 01
Why move from Pardot to HubSpot, and when not to
Teams leave Pardot when the marketing tool feels tethered: bolted to Salesforce, hard to change without help, and separate from where sales and service actually work. HubSpot wins when a company wants marketing, sales, and service in one platform its own team can run, with automation a marketer can build directly.
It is the right move when you value adoption, speed, and a unified view over Salesforce-anchored configurability. It is the wrong move if your business truly runs on deep Salesforce customization that Account Engagement is built to serve. A good partner tells you which case you are in before you rebuild a thing.
INSIDEA is an Elite HubSpot Partner, rated 4.99 out of 5 across 450+ verified reviews, and we hold HubSpot's CRM Data Migration and Custom Integration accreditations, two of the five accreditations we carry. The method below is the one we run, not a generic checklist.
Here is the whole migration at a glance, before we go phase by phase.
Pardot to HubSpot · staged migrationLogic rebuilt, not lost
Chapter 02
What actually moves: the asset inventory
Pardot, now Salesforce Marketing Cloud Account Engagement, is marketing automation that sits on top of Salesforce, so a Pardot move has an extra dimension the others do not: untangling from Salesforce. Migrating Pardot means rebuilding the marketing logic, Engagement Studio, forms, scoring and grading, nurture, inside HubSpot, and deciding how HubSpot and any remaining Salesforce relate. HubSpot Smart Transfer can migrate HTML email templates from Account Engagement, which cuts the manual rebuild.
| In Pardot | Becomes in HubSpot | Watch for |
|---|
| Prospect | Contact | Sync and identity re-modeled in HubSpot |
| Engagement Studio program | Workflow | Logic is rebuilt, not exported |
| Form and Form Handler | HubSpot form | Field mapping and follow-up re-wired |
| Landing page | HubSpot landing page | Templates rebuilt or transferred |
| Email template | Email template | HubSpot Smart Transfer can migrate HTML templates |
| Scoring and grading | Score property plus workflow | Model re-created; grading rethought |
| List and segmentation rule | Active or static list | Rules re-created against HubSpot properties |
| Campaign | Campaign | Attribution re-modeled |
| Custom field | Contact property | Types and values mapped |
Treating this as an export is the trap. Engagement Studio programs and scoring do not move as files; they are re-created in HubSpot workflows. And one Pardot-specific gotcha matters early: there is no clean, customer-facing import for historical marketing email performance and analytics, so plan reporting continuity deliberately rather than assuming it transfers.
Chapter 03
Before you touch anything: the audit
A Pardot migration is decided in the audit of assets and the Salesforce relationship. Mature Account Engagement instances hold layers of Engagement Studio programs, automation rules, and completion actions, plus a sync to Salesforce that shaped how everything behaves.
- Which Engagement Studio programs actually run? Rebuild the live ones; retire the rest rather than re-create them.
- How does the Salesforce sync shape today's behavior? Decide what HubSpot owns and what, if anything, stays in Salesforce.
- What does scoring and grading really reward? Migration is the moment to rebuild a model that reflects real intent.
- Which forms, templates, and lists carry real value? Map those; leave the dormant ones behind.
Agree the marketing definitions and the system-of-record decision here, before you build. Getting the HubSpot-and-Salesforce boundary right up front prevents the most expensive rework later.
Chapter 04
The migration sequence that protects your history
The sequence is rebuild first, transfer and import second, untangle and cutover last. You build workflows, forms, lifecycle, and scoring in HubSpot, transfer templates with Smart Transfer and import prospects as contacts, then run in parallel to validate sends and the Salesforce boundary before switching sending over.
Two facts shape this. HubSpot Smart Transfer can migrate HTML email templates from Account Engagement, so templates are not rebuilt from scratch. And because Pardot has no clean import for historical email performance, reporting continuity is planned as its own step rather than assumed.
Where the native tools stop, and API or custom work begins
Native tools and Smart Transfer do real work, but they do not rebuild your automation or untangle Salesforce. Knowing where they stop keeps a Pardot move on schedule.
What the native tools and Smart Transfer handle
- HTML email template migration via HubSpot Smart Transfer
- Standard prospect and list data as contacts
- Field mapping for migrated properties
- Basic contact-level history where a direct field mapping exists
What needs a deliberate rebuild or custom work
- Engagement Studio programs, re-created as HubSpot workflows
- Scoring and grading, rebuilt as a HubSpot score and logic
- The HubSpot and Salesforce boundary, modeled deliberately
- Historical email performance, which has no clean customer-facing import
- Static files and complex completion actions, moved with custom effort
Chapter 05
Cutover and the first weeks
The riskiest moment is the switch in sending plus the Salesforce untangle. Done well, it is planned: workflows are built and tested, templates transferred, the Salesforce boundary agreed, and a parallel period validates a sample of sends, forms, and the sync before Pardot is switched off.
Set exit criteria in advance. Core nurtures fire in HubSpot, forms route and score correctly, the Salesforce boundary behaves as designed, deliverability holds on the warmed domain, and marketing reporting returns sensible numbers. Only then do you move sending fully to HubSpot.
Chapter 06
Where Pardot to HubSpot migrations break
The failure patterns are specific to Pardot moves. Almost every troubled one traces back to one of these.
!
Ignoring the Salesforce untangle
Rebuilding marketing without deciding the HubSpot and Salesforce boundary, then fighting a two-headed system.
!
Treating it as an export
Expecting Engagement Studio and scoring to move as files. The logic is rebuilt in HubSpot.
!
Assuming analytics transfer
Expecting historical email performance to import cleanly. It does not; plan reporting continuity.
!
Ignoring deliverability
Switching sending without warming the domain, then losing inbox placement.
!
Rebuilding the graveyard
Re-creating dormant programs instead of the automation you actually want.
!
Adoption as an afterthought
A rebuilt engine the team cannot run. Enablement starts before cutover.
None of these are exotic. They are what happens when a Pardot migration is treated as a data transfer rather than a rebuild plus a Salesforce decision.
Chapter 07
How INSIDEA runs a Pardot to HubSpot migration
A Pardot move is a rebuild plus a Salesforce decision, and we treat it as both. We audit the assets, agree the marketing definitions and the system-of-record boundary, rebuild Engagement Studio as clean workflows, transfer templates with Smart Transfer, re-create scoring and forms, plan reporting continuity, warm the domain, and run a validated parallel period.
Because we build across CRM, RevOps, growth marketing, and AI, and hold the Custom Integration accreditation, we handle the Salesforce boundary properly rather than leaving a two-headed system behind. If you want this run as a system rather than a side project, see how we approach HubSpot implementation, or book a strategy call and we will scope your migration against the sequence above.
Chapter 08
Questions people ask
How long does a Pardot to HubSpot migration take?
Most moves run six to twelve weeks, driven by the number of Engagement Studio programs, forms, and templates rebuilt and the complexity of the Salesforce untangle, not by prospect volume. The audit is what lets you forecast it honestly.
Does Engagement Studio come across automatically?
No. Engagement Studio programs and scoring are rebuilt as HubSpot workflows and score properties rather than exported. It is the moment to simplify automation that had grown layered and to rebuild a scoring model that reflects real intent.
What happens to our Salesforce connection?
That is a decision, not an accident. Part of the migration is agreeing what HubSpot owns and what, if anything, stays in Salesforce, then modeling that boundary deliberately so you do not end up running two systems that disagree.
Will we keep our email performance history?
Pardot has no clean, customer-facing import for historical marketing email performance, so reporting continuity is planned as its own step. You keep the source data for reference and start fresh reporting in HubSpot, with historical activity represented on the timeline where it matters.
Should we rebuild ourselves or use a partner?
A simple Account Engagement setup with a clean Salesforce relationship can be rebuilt in-house. The case for a partner grows with automation complexity, the Salesforce untangle, deliverability risk, and the need to keep lead flow uninterrupted.
How INSIDEA works
