A Pardot (Marketing Cloud Account Engagement) to HubSpot migration is a rebuild, not a copy-paste. The work breaks into six streams: prospect and activity data, email templates and assets, segmentation and lists, automation and nurture programs, the Salesforce connector, and deliverability setup (sending domain, IP warm-up, subscription preferences). Teams that treat it as a lift-and-shift end up recreating their old mess in a new tool; teams that treat it as a redesign usually end up with fewer, better programs — and often retire a separate email tool in the process.
Every Pardot-to-HubSpot conversation starts the same way: someone asks "how long does the export take?" — and the honest answer is that the export is the easy part. What takes thought is deciding what deserves to come across, what gets rebuilt, and what gets left behind.
With Salesforce's B2B marketing roadmap increasingly centered on its newer Marketing Cloud architecture, many Account Engagement customers are using this moment of platform uncertainty to evaluate alternatives — and HubSpot is usually on that list. Whether you are switching for usability, cost structure, or consolidation, the migration pattern is the same. Here is what it actually involves.
Three motivations dominate, and knowing yours matters because it shapes the whole project:
| Asset | Moves cleanly? | Reality |
|---|---|---|
| Prospects (as contacts) | Mostly | Fields map well, but use the migration to dedupe and archive stale records — do not import a decade of dust |
| Activity history | Partially | Detailed engagement history has export limits; decide what history is genuinely needed for compliance or continuity |
| Lists and segmentation | Rebuild | Account Engagement lists become HubSpot static or active lists; dynamic rules need translation, not export |
| Email templates | Rebuild | Pardot's markup does not port; rebuild key templates in HubSpot's editor and retire the rest |
| Engagement programs / nurtures | Rebuild | Map each program's logic, then rebuild as HubSpot workflows — usually simpler than the original |
| Forms and landing pages | Rebuild | Rebuild in HubSpot and plan redirects for any indexed or linked URLs |
| Scoring and grading | Rethink | HubSpot scores differently; use the move to simplify a scoring model that grew unwieldy |
| Salesforce integration | Reconfigure | The HubSpot–Salesforce connector replaces the Pardot connector, with its own field mapping and sync rules |
The pattern to notice: data migrates, logic rebuilds, and most teams ship fewer assets than they had. That is a feature, not a failure.
The most consequential design decision is not in HubSpot at all — it is which Salesforce data flows into the marketing platform, and who can see it. Account Engagement's connector and HubSpot's Salesforce integration both sync leads, contacts, and campaign data, but their permission models and field-level behavior differ. Before go-live, answer:
Get these answers signed off before the first record syncs. Retrofitting sync governance after marketers have built audiences on the data is painful.
Regulated organizations often carry a historical objection to changing marketing platforms — sometimes years old, sometimes no longer accurate. Address it head-on with current documentation: HubSpot publishes SOC 2 and SOC 3 reports and ISO certifications, with detailed reports available under NDA. Frame the review around the actual concern (usually data exposure through the CRM sync) rather than a general sense of platform risk, and loop in whoever owns vendor security review early — they control your timeline more than any technical task does.
The failure mode worth naming is the "faithful reproduction" — every legacy program, list, and template recreated exactly in the new platform. It feels low-risk and is anything but. Engagement Studio programs rebuilt node-for-node inherit years of accumulated workarounds. Every outdated suppression list comes along. The scoring model that nobody has reviewed since implementation gets enshrined again. Within a quarter, the new platform feels exactly as heavy as the old one, and the migration gets blamed for what was really a copying decision.
The better instinct is subtraction. Most organizations discover that a minority of their programs produce most of their pipeline; the migration is the one natural chance to retire the rest with evidence instead of politics. Rebuild the programs that perform, archive the ones that do not, and let the new platform start lean.
Plan for a deliberate parallel-run window — typically a few weeks — where the old platform stays readable but sends are frozen, and HubSpot becomes the only system sending. During that window: warm the new sending infrastructure gradually rather than blasting the full database on day one; watch bounce and complaint rates daily; and keep a shared inbox of "where did this go?" questions from the sales team, because the first fortnight surfaces every sync assumption you got wrong. Cut over forms and tracked links on a published schedule, not ad hoc, so nobody wonders which system a lead lives in.
Triage every active program against three questions. Does it produce measurable engagement or pipeline today? Is its logic still how you market — or a workaround for a constraint that no longer exists? And would you build it this way if you started fresh? Programs that pass all three get rebuilt first. Programs that fail the third question but still perform get simplified during the rebuild. Everything else gets archived with its reporting history intact. Expect roughly a third of legacy programs to survive unchanged in spirit — that ratio is normal, and it is what "redesign, don't replicate" looks like in practice.
Vantage Point runs marketing automation migrations as redesigns, not exports: triage workshops, Salesforce connector design with your compliance team in the room, deliverability setup, and rebuilds of the programs that actually drive pipeline. As a HubSpot Solutions Partner, our implementation practice has moved organizations between every major platform pairing, and our HubSpot technology team stays through parallel run and cutover. Senior consultants only — no junior handoffs; the experts you meet are the experts who deliver.
We will map your migration scope — data, programs, connector, compliance — and tell you honestly what to bring, rebuild, and retire.
Yes. Pardot was renamed Marketing Cloud Account Engagement; it is the same product line. Salesforce's newer B2B marketing direction is its Marketing Cloud architecture, which is why many Account Engagement customers are evaluating their options now.
Not directly. Account Engagement templates use platform-specific markup, so templates are rebuilt in HubSpot's editor. Most teams rebuild only their active templates and retire the rest, which usually means far fewer templates than the old system held.
Contact and account data migrates well; granular engagement history is harder to export completely. Decide what history is genuinely required — for compliance, continuity, or scoring — and archive the rest in accessible storage rather than forcing it into the new platform.
HubSpot uses subscription types and a preference center that contacts manage themselves. Multi-brand or multi-audience organizations can offer granular opt-down choices instead of a single unsubscribe, which typically reduces full opt-outs.
Yes — consolidation is one of the strongest reasons to move. One platform for marketing email means one audience database, one preference center, and one set of engagement reporting, provided your contact volume fits your subscription tier.
It depends on program complexity and compliance review more than data volume. A focused mid-size migration with a handful of active nurtures typically runs in weeks; the security review and deliverability warm-up, not the export, set the critical path.