HubSpot Solution Blueprint

The Audit-First Pardot Exit: De-Risking a 198,000-Record Migration to HubSpot

Marketing automation migrations fail quietly, through records that never arrive and records that should never have come. For a publicly traded media and entertainment technology company, the move from Pardot and Salesforce to HubSpot started with a full-platform audit of a 198,000-record database, because at that scale the sync boundaries between three systems decide what the new portal contains before anyone imports a thing.

Executive Summary

Context

The client's B2B marketing operation ran on Pardot Advanced Edition wired to Salesforce: roughly 194,000 prospects, 367 lists, 120 automation rules, and 116 forms accumulated over years of campaigns. An audit came first. It inventoried every object and sync relationship and produced the action plan the migration then executed.

What We Built

A full Pardot and Salesforce pre-migration audit covering prospects, data quality, lists, forms, automations, scoring, and reporting, plus the migration controls it prescribed: purge lists, integration-user permissions, a field-mapping workbook, and rebuilt lead scoring in HubSpot.

Tech Stack

HubSpot Marketing Hub Enterprise, Pardot (Advanced Edition), Salesforce

Not a fit for small databases with a single system of record, where an export-and-import handles the move without sync-boundary analysis.

The Challenge

The database told a story of accumulation without governance. Sixty-five percent of the 194,000 prospects were marked never-active against a benchmark of under ten percent, and sixteen percent were unmailable. The opt-in field wasn't reliably used: filtering for records with a name and a true email opt-in returned under 7,000 leads, which meant a naive import could mark contacts as marketable that the company had no permission to email. The sharper risks sat at the sync boundaries. 7,461 Pardot prospects were not syncing to Salesforce and would silently miss the migration; 11,484 Salesforce records were not in Pardot and would silently come over. Neither population had been reviewed.

Our Approach

The audit treated the three-system topology as the migration plan's first draft. Every object got counted and every sync relationship mapped: prospects by mailability status, 367 lists (54 with zero members), 120 automation rules of which only 78 were active, 116 forms triaged into top, middle, and bottom-of-funnel value tiers. Resolving the two silent populations was the hard call. Un-synced Pardot prospects were flagged for review and manual export rather than left to vanish, and integration-user permissions were prescribed to control whether the Salesforce-only records entered HubSpot at all. Unmailable and unsubscribed records were mapped to non-marketing status so the new portal's marketable count started honest, and duplicate leads and contacts sharing an email address were reconciled to HubSpot's one-record-per-email model before import.

Impact

Two Silent Data-Loss Paths Caught Before Import

The audit surfaced 7,461 prospects that would never have arrived and 11,484 records that would have arrived unreviewed, converting both from silent migration defects into explicit review-and-permission decisions.

A Marketable Count the Company Can Defend

Opt-in ambiguity was resolved before import: unmailable and unsubscribed prospects mapped to non-marketing status, and the true opt-in method was determined so no contact entered HubSpot as marketable without permission.

Automation Debt Cut to the 78 That Matter

Of 120 Pardot automation rules, 42 paused and 62 inactive ones were separated from the 78 active rules that defined the real migration scope, so rebuild effort landed only on automation that runs.

Scoring Rebuilt Instead of Transplanted

The lead scoring model had not been touched since 2021 and drove almost no process. Two HubSpot models were built in its place: a best-practice baseline and one mirroring the legacy signals for continuity.

Technical Blueprint

Sync-Boundary Analysis First

Count every record population at each system boundary: in Pardot only, in Salesforce only, syncing between the two. The deltas are the migration risk register; each population gets an explicit keep, block, or manual-export decision.

The Purge List as a Migration Gate

Never-active, test, and internal records enter a purge list reviewed by the client before deletion, and matching records are removed from Salesforce as well, otherwise the integration re-creates what was just purged.

Field Mapping as a Workbook, Not a Default

A field-mapping workbook decides property by property what moves from Pardot through Salesforce to HubSpot, including standardizing free-text titles into workflow-derived department and seniority values the old system never captured.

Funnel-Tiered Form Triage

All 116 forms were classified as top, middle, or bottom of funnel, with required fields, hidden source-tracking fields, and progressive profiling prescribed per tier, so attribution reporting works from the first submission in the new portal.

FAQ

Why audit before migrating instead of just syncing everything to HubSpot?

Because the default sync makes two silent mistakes at once: records that exist only in the marketing platform never arrive, and records that exist only in the CRM arrive unreviewed. At 198,000 records those populations were 7,461 and 11,484 respectively. The audit converts both into deliberate decisions before a single record moves.

How do you keep purged contacts from coming back?

Purge from both systems. Deleting a contact from the marketing platform alone leaves its twin in Salesforce, and the integration will re-create it in HubSpot. The purge list is applied to Pardot and Salesforce together, with the client reviewing the filter logic before anything is deleted.