Salesforce Marketing Cloud Account Engagement to HubSpot
B2B marketing automation (formerly Pardot) that sits on top of Salesforce CRM. It handles prospects, lists, forms, scoring and Engagement Studio programs.
Salesforce Marketing Cloud Account Engagement data can move into HubSpot, landing mainly in Marketing Hub. 1 of 8 mapped objects move directly (Prospects); 5 items need manual work and 4 do not move. Plan roughly 3-5 weeks for a small move and 10-20 weeks for a large one.
Migration checklist for Salesforce Marketing Cloud Account Engagement
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<25k prospects
Few programs and no Salesforce CRM move.
Mid migration
25k-250k prospects
Dozens of programs and a Salesforce sync to untangle.
Large migration
>250k prospects
Multiple business units, a Salesforce CRM move and activity history.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Salesforce Marketing Cloud Account Engagement: what you need to get in, what lands in HubSpot, and what will not.
REST (Account Engagement API v5, JSON) with an asynchronous Export API
Connected App with the pardot_api scope, plus the Business Unit ID.
Admin access to create the Connected App and to run exports. The exact permissions are not confirmed in the sources I used.
Daily limits by edition: Growth 25,000, Plus 50,000, Advanced and Premium 100,000. Up to 5 concurrent requests. Exceeding the daily limit returns error 122 and exceeding concurrency returns error 66. The Export API counts against these limits, queues exports in order, and allows at most 150 fields per export.
Choose your route
How will you move the data?
HubSpot offers an integration for importing records from Salesforce Marketing Cloud Account Engagement.
- You need: Connected App with the pardot_api scope, plus the Business Unit ID.
- Permission: Admin access to create the Connected App and to run exports. The exact permissions are not confirmed in the sources I used.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- API v5 object queries (paged with a nextPageToken, capped at 100,000 records)
- Export API for large datasets, including relationship fields
- Manual CSV exports of prospects, lists and reports from the UI
- Smart Transfer for HTML email templates
Limits: Daily limits by edition: Growth 25,000, Plus 50,000, Advanced and Premium 100,000. Up to 5 concurrent requests. Exceeding the daily limit returns error 122 and exceeding concurrency returns error 66. The Export API counts against these limits, queues exports in order, and allows at most 150 fields per export.
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 10-20 weeks, usually phased.
Talk to a partnerWhere each object lands
In Salesforce Marketing Cloud Account Engagement
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Prospects | Contacts | yes | A prospect can map to a Salesforce Lead, a Contact, both or neither, so deduplicate before import. Score and grade move as static values only. |
| Salesforce Accounts / company data | Companies | partial | Account Engagement stores accounts through the Salesforce sync, so Companies may need to come from Salesforce itself. |
| Opportunities | Deals | partial | The API exposes opportunities, but the source of truth is usually Salesforce CRM. |
| Lists and segments | Contacts | manual | Rebuild dynamic lists as HubSpot active lists. Load static audiences as static lists. |
| Email templates (HTML) | Files | partial | Smart Transfer can move HTML templates as a one-time transfer. They still need rendering QA and merge-field remapping. |
| Engagement Studio programs and automation rules | Custom objects | manual | There is no machine-readable export, so rebuild them as HubSpot workflows. HubSpot has no object for this logic, so the target is not an object. Custom objects is a placeholder. |
| Campaigns | Custom objects | manual | Recreate the campaign definitions in HubSpot. There is no confirmed direct import. |
| Visitor activity (opens, clicks, form fills) | Notes | partial | Activity can be exported through the Export API. Importing it as notes or timeline events is a custom job, and the native sync does not carry it. |
What to expect
The models do not transfer, so attribution starts fresh in HubSpot.
There is no machine-readable export.
There is no clean import, so export reports to CSV for the record.
Only the resulting values move.
Logic cannot be exported.
Filters need translating into HubSpot list criteria.
Transferred templates still need checking.
Custom-coded pages need developer time, and printed or paid links need updating.
The Salesforce connector shapes the sequencing of the move.
Deduplicate on email and Salesforce ID before import.
Archive activity CSVs and keep Pardot read-only for a period after cutover.
Export opt-out and do-not-email flags and import them before any send.
Use the Export API, paginate, back off on errors, and avoid sharing the budget with other integrations.
Run in parallel and warm the domain.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
API access, auth and limits are backed by Salesforce developer docs. Object mapping and what cannot move rest mainly on third-party migration guides, plus HubSpot community posts. I did not open HubSpot's own docs or Salesforce's help pages on export, consent and residency.
Sources
Related migrations
Frequently asked questions
How do I migrate Salesforce Marketing Cloud Account Engagement to HubSpot?
1. Create a Salesforce Connected App with the pardot_api scope and note the Business Unit ID. 2. Check the daily API allocation for your edition on the usage and limits page. 3. Inventory prospects, custom fields, lists, forms, Engagement Studio programs, scoring and templates. 4. Decide whether Salesforce CRM migrates too, and map Lead, Contact and Account IDs.
What data can move from Salesforce Marketing Cloud Account Engagement to HubSpot?
These objects move directly: Prospects. Check the mapping table for partial and manual items.
What does not move from Salesforce Marketing Cloud Account Engagement to HubSpot?
Campaign influence and attribution history, Engagement Studio program definitions, Historical email performance analytics and B2B Marketing Analytics dashboards and Scoring and grading models. Plan to rebuild or retire these.
How long does a Salesforce Marketing Cloud Account Engagement to HubSpot migration take?
Small (<25k prospects): 3-5 weeks. Mid (25k-250k prospects): 6-10 weeks. Large (>250k prospects): 10-20 weeks. These are planning estimates, not a quote.
What access do I need to export from Salesforce Marketing Cloud Account Engagement?
Connected App with the pardot_api scope, plus the Business Unit ID. Admin access to create the Connected App and to run exports. The exact permissions are not confirmed in the sources I used.
Is there a native HubSpot connector for Salesforce Marketing Cloud Account Engagement?
Yes. Confirm the supported objects in discovery.
What compliance issues apply when moving Salesforce Marketing Cloud Account Engagement data?
Check: Form fields may capture health or financial data and Minors' data possible in education. Agree consent, retention and access rules before exporting.
Moving Salesforce Marketing Cloud Account Engagement into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner