Every field is a Salesforce field
Pardot cannot hold data Salesforce does not know about. A new segmentation field means a Lead field, a Contact field, a Pardot field and a sync mapping. Four changes, one owner, and the owner is not in marketing.
We sell outcomes. Not hours.
Pardot, now Marketing Cloud Account Engagement, was built to sit inside Salesforce. Every field marketing wants to segment on is a Salesforce field first, every sync rule is an admin ticket, and every report worth showing the board is a Salesforce report. So marketing's roadmap runs on the CRM team's sprint. Moving to HubSpot gives marketing its own platform, with its own editor and its own data model, and a native Salesforce connector that carries across only what sales needs. We do it for a fixed, published price, and the fee is the same whether Pardot leaves on its own or with Salesforce.
None of this is a fault in the people running it. It is what happens when the marketing system borrows its data model from the CRM.
Pardot cannot hold data Salesforce does not know about. A new segmentation field means a Lead field, a Contact field, a Pardot field and a sync mapping. Four changes, one owner, and the owner is not in marketing.
Every prospect mirrors a Salesforce lead or contact. Converted leads, duplicate prospects and sync errors pile up in the connector queue, and marketing spends Friday cleaning data it never created.
One nurture builder, one list model, forms and landing pages that need a developer to match the brand. Anything Engagement Studio cannot express ends up as a Salesforce flow, and flows belong to the admin.
Campaign influence, B2B Marketing Analytics and the dashboards all live in Salesforce and need report permissions marketing rarely has. "Did the webinar work" is a request, and the answer arrives next week.
"This was a complex migration, and they handled it with a high level of ownership and care, resulting in a smooth transition."
Igal Zeifman, VP Marketing, CyCognito · marketing automation to HubSpot, Salesforce connector rebuilt, 70,000 contacts, 12 weeks · Read the story →A Pardot instance collects automation rules, completion actions and dynamic lists that exist to patch the sync. Before we scope a migration we sit with the marketing ops owner and sort every program into one of three groups.
Standard behaviour in HubSpot. Nothing to rebuild, less to test and train.
Check the last run date and the match count, then ask the owner to explain it in one sentence.
Rebuilt in HubSpot's shape, without the workarounds.
Mark wrote the method out for Marketo, and it applies to Pardot line for line: Before You Rebuild That Program in HubSpot, Ask What It Does →
Four phases, the same ones in our statements of work. Most mid-market marketing migrations complete within four months, with ongoing support after go-live if you want it.
Freightos moved marketing from Pardot to HubSpot with Penguin and kept its Salesforce pipeline connected, so sales carried on in the CRM it knew while marketing got a system it could build in. Zencity and ECI made the same move from Marketo and Eloqua, Salesforce connector included.

Pardot and Salesforce together cost the same as Pardot alone. Work out the cost →
So every outcome has a price on it, published here, on our pricing page and inside our calculators. Same figures in all three places. Most partners would rather you booked a call before you saw a number. We would rather you saw the number first.
Starts at $40k for one hub, starting fresh. Leaving Pardot adds a flat $25k however many systems you leave, so the smallest Pardot migration is $65k, and Pardot and Salesforce together cost the same as Pardot alone. Each further hub is $25k, and the migration calculator prices your exact stack.
A report and a roadmap for the portal you already have. Every dollar of it is credited if we go on to do the work.
A named team with SLAs, running the portal as part of operations, month to month.
Work out your own figure before you talk to anyone.

Three situations where we will tell you so on the first call.
Prospects become contacts, with lists and activity history. Engagement Studio programs that survive the three-group sort become workflows, forms and landing pages are rebuilt in HubSpot's editor, and scoring and grading are redesigned rather than copied. Dead automation rules stay behind on purpose.
No. HubSpot connects to Salesforce natively and we rebuild the connector with selective field mapping and MQL routing as part of the move, so marketing can go first. If you want to leave Salesforce as well, the migration fee is the same, and we plan the CRM move as the next phase rather than a second project.
Pardot splits fit (grade) from engagement (score). HubSpot handles both, either as one score model or as two score properties, so the rep sees fit and engagement side by side. We rebuild fit from your ICP fields and engagement from behaviour, then check the top 50 against what sales actually called.
Campaign membership and conversion history move with the contacts, and Pardot campaigns map to HubSpot campaigns. Campaign Influence and B2B Marketing Analytics do not have a one-to-one equivalent, so we agree during discovery which reports you need on day one and rebuild those in HubSpot's attribution model.
Most mid-market marketing migrations complete within four months. CyCognito's marketing automation move to HubSpot, with 70,000 contacts and about 50 live campaigns, went end to end in 12 weeks.
From $40k for one hub, starting fresh. Leaving Pardot adds a flat $25k however many systems you leave, so the smallest Pardot migration is $65k. The calculator shows the working without asking for an email.
Work out what the move costs for your instance first. When you want it checked against your actual programs and your Salesforce sync, that is what the call is for.