Pardot (Marketing Cloud Account Engagement) to HubSpot Migration

Email opens, clicks, page views, form submissions, and Engagement Studio step completions stay locked in Pardot. The Data Sync connector moves prospect field values only. One HubSpot marketplace reviewer states plainly that the app 'doesn't move contact activity or campaign information'. This is the most commonly underestimated loss in a Pardot migration, because reporting continuity and any behaviour-based segmentation depend on it.

Workaround: Export every Pardot activity and summary report to CSV before decommissioning, and keep Pardot in read-only for at least 90 days after cutover. Where historical engagement drives segmentation, export the resulting audiences and load them into HubSpot as static lists so the segment survives even though the underlying activity does not.

There is no way to export an Engagement Studio program in any machine-readable form. Every program must be read on screen, documented, and rebuilt as a HubSpot Workflow. The branching models differ: Engagement Studio is a step-based canvas with wait, trigger, action, and rule nodes, while HubSpot workflows use enrollment triggers plus if/then branches. This is where Pardot migration timelines most often overrun.

Workaround: Screenshot and document every active program before touching HubSpot. Rebuild only programs that are actually running and producing results; treat dormant programs as an opportunity to retire scope rather than recreate it. For contacts mid-flight at cutover, use workflow jump steps that check whether a given email was already received and enroll the contact at the right stage.

Pardot separates behavioural intent (a numeric score) from demographic fit (a letter grade A through F driven by a profile and scoring categories). HubSpot ships one HubSpot Score property. Migrating the model, not just the values, requires deliberate redesign.

Workaround: Rebuild as two separate custom score properties: an engagement score and a fit score. On Marketing Hub Professional and above, clone the HubSpot Score property to create the second scoring category. Use the migration as the moment to fix a bloated model rather than replicate it: if the current model produces far more MQLs than sales actually works, rebuilding the same criteria just moves the problem.

Pardot form handlers let an externally hosted form post data into Pardot while the form markup stays owned by the website. HubSpot has no direct analogue. The closest options are a native HubSpot form, or the non-HubSpot form capture feature which requires the tracking code and does not offer the same explicit field mapping contract.

Workaround: Inventory every form handler and its posting source before cutover. Replace with native HubSpot forms where the markup can be changed, or use non-HubSpot form capture plus a workflow where it cannot. Budget for the fact that each replacement usually means touching a website template.

Pardot-hosted forms, landing pages, and iframe embeds stop collecting the moment the Pardot instance is switched off. Unlike a data sync gap, this failure is silent: the page still renders, the form still appears, and submissions simply go nowhere.

Workaround: Crawl the live website for every Pardot form iframe, form handler endpoint, and hosted landing page URL before cutover, not after. Replace and test each one on staging. Add 301 redirects from every Pardot landing page URL to its HubSpot replacement.

Pardot syncs to Salesforce through its own connector. HubSpot syncs to Salesforce through a different one with different field direction rules, different conflict resolution, and its own inclusion list. Standing up the HubSpot-Salesforce integration while the Pardot connector is still live puts two systems in a write race against the same Salesforce records. A default sync configuration can overwrite good data.

Workaround: Decide the order of operations explicitly: which system owns which field, and when the Pardot connector is paused. Configure the HubSpot inclusion list before the first sync rather than after. Treat selective sync as a separate scoped piece of work; HubSpot Support does not guide its implementation.

Pardot historically assigns each prospect a single connected campaign representing first touch. HubSpot supports multi-touch attribution with contacts associated to many campaigns and configurable attribution models. Historical Pardot campaign membership cannot be reshaped into HubSpot's multi-touch model after the fact, because the intermediate touch data was never stored.

Workaround: Accept a clean break on attribution reporting. Export Pardot campaign performance to CSV for the historical record, and start HubSpot attribution fresh from cutover. Communicate the reporting discontinuity to stakeholders before go-live, not when the first quarterly report looks wrong.

A Pardot automation rule is a persistent, repeatedly evaluated criteria-plus-action pair. In HubSpot that logic lands partly in active lists (the criteria) and partly in workflows (the action). Mapping a rule to the wrong one produces automations that appear to work but silently act on the wrong contacts.

Workaround: Classify every automation rule before rebuilding: criteria that define membership become active lists, criteria that trigger a one-time action become workflow enrollment triggers. Test enrollment on a small static list before enabling any workflow against the full database.

Smart Transfer moves list membership as a snapshot, not the rules that produced it. When rules are rebuilt manually, filters that referenced fields deprecated during earlier Pardot cleanups fail quietly, producing lists that look valid but never populate.

Workaround: Audit field usage before rebuilding lists. Rebuild dynamic lists as HubSpot active lists and verify the membership count against the Pardot count for each one; a rebuilt list with zero or wildly different membership is the signal that a filter references a dead field.

The free Data Sync connector maps default fields only. Any custom prospect field mapping requires Data Hub Starter or above. Field type compatibility is also constrained: many third-party field types map one way only into HubSpot text fields, and fields with multiple labelled values such as emails, phones, and addresses cannot be mapped to custom fields at all.

Workaround: Price Data Hub Starter into the migration from the outset for any account with meaningful custom fields, which is nearly all of them. Audit field types and dropdown values for exact matches before enabling sync, and note that HubSpot captures dropdown options at sync-creation time and will not pick up options added later without a resync.

Pardot custom redirects are tracked links used across emails, social posts, PDFs, and third-party properties. They resolve through Pardot infrastructure, so every one of them 404s when the instance is retired, including links embedded in assets nobody controls any more.

Workaround: Export the full custom redirect list with click counts. Rebuild high-traffic redirects as HubSpot tracking URLs or CTAs, and put permanent redirects in place for the rest. Accept that links inside already-sent emails and printed collateral cannot be saved and prioritise by click volume.

Pardot business units partition prospects, assets, and users within one account, and are common in multi-brand or multi-region organisations. The HubSpot equivalent, Business Units, is a Marketing Hub Enterprise feature. On lower tiers the separation must be approximated with teams, partitioning, and property-based segmentation, which is weaker than true partitioning.

Workaround: Confirm the target HubSpot tier before promising equivalent separation. If Enterprise is out of scope, design a naming convention plus asset partitioning approach early, because retrofitting one across a populated portal is significantly more work.

Pardot landing pages are built on layout templates using Pardot's own HML merge syntax and stylesheet model. Nothing about that structure ports to HubSpot templates or drag-and-drop pages. Hosted files keep Pardot-domain URLs that die with the instance.

Workaround: Rebuild only pages with live traffic or active campaign links; use the migration to retire the rest. Re-upload hosted files to the HubSpot Files tool and redirect the old URLs. Custom-coded landing pages need developer involvement rather than the drag-and-drop builder.

Highest-risk item in the migration. Sequence the cutover explicitly and configure the inclusion list before the first sync.

Confirm the target tier before promising equivalent separation. Retrofitting is significantly more work.

Email templates and lists DO transfer via Smart Transfer, contradicting most published guides; quoting a full manual template rebuild can overstate a quote by tens of hours

Prospect activity history does not transfer and exists nowhere else once Pardot is decommissioned

Running the HubSpot-Salesforce connector while the Pardot connector is still live puts two systems in a write race against the same Salesforce records

the page renders, the form appears, and submissions vanish

Custom redirects inside already-sent emails and printed collateral cannot be saved at any price

Rebuilt dynamic lists that return zero members usually reference a field deprecated in an earlier Pardot cleanup

The Prospect object maps to Salesforce Leads AND Contacts, so a one-to-one mental model of Prospect equals Contact breaks on the first duplicate

Custom field mappings require Data Hub Starter, which is a line item most first-pass quotes omit

Business units need Marketing Hub Enterprise; promising equivalent separation on Professional creates a commitment that cannot be met

Attribution reporting breaks at cutover no matter how carefully the migration is run, because Pardot never stored the intermediate touches HubSpot needs

Email template type in HubSpot, one-time versus automated, cannot be changed after creation

the audit surfaces years of undocumented automation nobody wants to own