Pardot (Marketing Cloud Account Engagement) to HubSpot Migration

Reporting continuity is the casualty here, not a side effect: everything you segment on today, email opens, clicks, page views, form submissions and every Engagement Studio step someone completed, has no path out of Pardot. The Data Sync connector carries prospect field values and nothing else, which one HubSpot marketplace reviewer puts bluntly: the app 'doesn't move contact activity or campaign information'. Of everything lost in a Pardot migration, this is the loss buyers underestimate most often, because behaviour-based segmentation and the reports built on it stop working the moment the switch flips.

Workaround: Before decommissioning, export every Pardot activity report and summary to CSV, and hold Pardot in read-only for at least 90 days past cutover rather than switching it off on day one. Where a segment is built on historical engagement, export the audience itself and load it into HubSpot as a static list: the segment survives that way even though the activity behind it does not.

No machine-readable export exists for an Engagement Studio program at all, so every one of them has to be read off the screen, written down, and rebuilt in HubSpot as a Workflow by hand. The two canvases do not think alike either: Engagement Studio steps through wait, trigger, action and rule nodes, while a HubSpot workflow runs on enrollment triggers and if/then branches. This single gap is where a Pardot migration timeline most often runs long, so size it generously in whatever estimate you are given.

Workaround: Screenshot and document every active program before HubSpot is touched at all, and rebuild only the ones actually running and producing results: a dormant program is scope you get to retire rather than recreate. For anyone mid-flight through a program at cutover, use workflow jump steps that check which email a contact already received and enrol them at the matching stage rather than from the start.

Two separate models collapse into one on the HubSpot side. Pardot keeps behavioural intent as a numeric score and demographic fit as a letter grade from A through F, set by a profile and scoring categories, while HubSpot ships a single HubSpot Score property. Moving the values across is the easy part; moving the model behind them needs a deliberate redesign, and that redesign is the work that actually matters here.

Workaround: Split the model back into two custom score properties, one for engagement and one for fit, and on Marketing Hub Professional and above clone the HubSpot Score property to give the second category somewhere to live. Treat the migration as the chance to fix the model rather than reproduce it: if the current scoring hands sales far more MQLs than the sales team is actually working, rebuilding it exactly as it stands only moves the same problem into the new system.

A Pardot form handler is what lets a form built and owned by your website post its data into Pardot without Pardot ever holding the markup, and HubSpot has nothing that does the same job directly. The nearest substitutes are a native HubSpot form, or non-HubSpot form capture, which needs the tracking code installed and does not give you the same explicit field mapping contract the handler did.

Workaround: Before cutover, inventory every form handler and the source posting into it. Where the markup can be changed, replace it with a native HubSpot form; where it cannot, pair non-HubSpot form capture with a workflow instead. Plan the budget around the fact that almost every one of these replacements means someone touching a website template, not just a settings screen.

The moment the Pardot instance is switched off, every Pardot-hosted form, landing page and iframe embed stops collecting anything at all, and nobody is told. Unlike a data sync gap, this failure makes no noise: the page keeps rendering, the form keeps appearing exactly as before, and every submission after that point simply disappears.

Workaround: Crawl the live site for every Pardot form iframe, form handler endpoint and hosted landing page URL before cutover, never after: this is not a check you get to run late. Replace and test each one on staging first, then put 301 redirects in place from every Pardot landing page URL to wherever its HubSpot replacement now lives.

Pardot and HubSpot each run their own connector into Salesforce, with different field direction rules, different conflict resolution and a different inclusion list from one another. Stand the HubSpot-Salesforce integration up while the Pardot connector is still live and you put two systems in a write race over the same Salesforce records, and a default sync configuration is entirely capable of overwriting good data. Where a deal has been worked over months through a committee of stakeholders, the Salesforce record is frequently the only complete account of who agreed to what, which is exactly the record this race can corrupt.

Workaround: Set the order of operations down explicitly: name which system owns which field, and the exact moment the Pardot connector pauses. Configure the HubSpot inclusion list before the first sync runs, not after, and scope selective sync as its own piece of work rather than a subtask, since HubSpot Support will not walk you through implementing it.

Pardot has always tied a prospect to one connected campaign, whichever represented first touch, while HubSpot lets a contact carry many campaign associations under a configurable attribution model. That is not a setting you can change retroactively: your historical Pardot campaign membership cannot be reshaped into HubSpot's multi-touch model after the fact, because Pardot never stored the intermediate touches multi-touch attribution needs.

Workaround: Accept the clean break on attribution reporting rather than fighting it. Export Pardot campaign performance to CSV to preserve the historical record, and let HubSpot attribution start fresh from cutover. Tell the stakeholders who read the quarterly numbers about the discontinuity before go-live, so the first report that looks strange is not the moment they find out.

One Pardot automation rule, a criteria-plus-action pair evaluated over and over, splits into two HubSpot concepts once it crosses over: the criteria becomes an active list, the action becomes a workflow. Get that split wrong and the result does not fail loudly; it keeps running and quietly acts on the wrong contacts, which is a harder problem to catch than an automation that simply stops.

Workaround: Classify every automation rule before any rebuilding starts: criteria defining membership becomes an active list, criteria triggering a one-time action becomes a workflow enrollment trigger. Test enrollment against a small static list first, and only turn a workflow loose on the full database once that test has held.

What Smart Transfer moves is a snapshot of list membership, never the rules that produced it, so those rules have to be rebuilt by hand from scratch. Rebuild against a field that an earlier Pardot cleanup deprecated and the filter fails quietly: the list looks perfectly valid and simply never populates, which is a harder fault to spot than an error message would be.

Workaround: Audit field usage before a single list is rebuilt. Once dynamic lists become HubSpot active lists, check the membership count against the original Pardot count for each one: a rebuilt list sitting at zero, or wildly off the original number, is the tell that a filter is still pointing at a dead field.

Default fields are as far as the free Data Sync connector reaches; mapping a single custom prospect field needs Data Hub Starter or above, and even then the field types have to cooperate. Many third-party field types will only map one way, into a HubSpot text field, and a field carrying multiple labelled values, an email, a phone number, an address, cannot be mapped to a custom field at all.

Workaround: Put Data Hub Starter in the budget from the outset if you have meaningful custom fields, and nearly every account does. Audit field types and dropdown values for an exact match before sync is switched on, and know going in that HubSpot captures dropdown options at the moment sync is created: an option added afterwards will not appear without a resync.

Every Pardot custom redirect, the tracked link sitting in an email, a social post, a PDF or a third-party property, resolves through Pardot's own infrastructure, so all of them 404 the day the instance is retired, including the ones embedded in assets nobody on your team can still edit.

Workaround: Export the full custom redirect list along with its click counts, then rebuild the high-traffic ones as HubSpot tracking URLs or CTAs and put permanent redirects in place for what is left. A link buried in an already-sent email or printed collateral cannot be saved at any price, so let click volume decide the order you work through the rest.

Pardot business units partition prospects, assets and users inside a single account, and they turn up most in organisations running several brands or several regions, a pattern common to a Gulf group with more than one operating entity under one holding structure. HubSpot's equivalent, Business Units, sits behind Marketing Hub Enterprise; on a lower tier the separation has to be approximated with teams, partitioning and property-based segmentation, none of which holds entities apart as cleanly as a true partition does.

Workaround: Confirm the target HubSpot tier before anyone promises equivalent separation to the business. Where Enterprise is out of scope, design a naming convention and an asset partitioning approach early: retrofitting one onto a portal that already has data in it is significantly more work than building it in from the start.

Pardot landing pages sit on layout templates written in Pardot's own HML merge syntax and stylesheet model, and none of that structure has anywhere to go inside a HubSpot template or the drag-and-drop builder. Hosted files carry Pardot-domain URLs of their own, and those URLs die with the instance too.

Workaround: Rebuild only the pages still carrying live traffic or an active campaign link, and use the migration as licence to retire the rest. Re-upload hosted files to the HubSpot Files tool and redirect the old URLs to them, and route anything custom-coded to a developer rather than the drag-and-drop builder, which will not reproduce it.

Of everything in a Pardot migration, the Salesforce connector cutover is the highest-risk single step, so treat the sequencing as deliberate rather than incidental: configure the inclusion list and confirm it before the first sync ever runs, not after.

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

Email templates and lists DO transfer through Smart Transfer, which contradicts most published migration guides outright, and quoting a full manual template rebuild on the strength of those guides can overstate a quote by tens of hours

Prospect activity history has no path across at all, and once Pardot is decommissioned it exists nowhere else, so treat the export step as the only chance to keep it

Leave the Pardot connector live while standing up the HubSpot-Salesforce connector and you put two systems in a write race against the same Salesforce records, with no guarantee the right one wins

the page still renders, the form still appears exactly as before, and every submission after cutover simply vanishes

A custom redirect sitting inside an already-sent email or printed collateral cannot be saved at any price, so do not budget time trying

it is almost always still referencing a field an earlier Pardot cleanup deprecated

The Prospect object maps to Salesforce Leads and Contacts both, so any mental model that treats one Prospect as one Contact breaks on the very first duplicate it meets

Custom field mappings require Data Hub Starter, and it is a line item most first-pass quotes leave out, so check for it specifically in any estimate you are given

Business units need Marketing Hub Enterprise, full stop, and promising equivalent separation on Professional is a commitment nobody can actually deliver

Attribution reporting breaks at cutover regardless of how carefully everything else is run, because Pardot never stored the intermediate touches HubSpot's model needs to work with

A HubSpot email template's type, one-time or automated, is locked in the moment it is created and cannot be changed afterwards, so get it right the first time

the audit tends to surface years of undocumented automation that nobody in the organisation wants to put their name on owning, and reaching a decision on each one is what actually eats the calendar