Three kinds of history, three routes
The Pipedrive threads on HubSpot Community nearly all hit the same snag: people expect “emails” to come across with activities, and they don’t. Pipedrive holds three different kinds of history, and each needs its own route.
| Pipedrive data | Smart Transfer | Pipedrive export | Route that works |
|---|---|---|---|
| Activities (call, meeting, task, email-type) | Yes; needs Data Hub | Yes, exported separately | Smart Transfer, or export and import as HubSpot activities |
| Notes | Yes | Yes, as HTML or plain text, exported separately | Either one; import needs Note body plus an association |
| Logged emails (mailbox sync, BCC) | No: “not logged emails” | Not an export type | Pipedrive API, then HubSpot import or API |
| Files | One-time post-sync transfer | Yes, separately | Upload to HubSpot, then link them |
What the native tools do / where they stop
Smart Transfer is the quickest route for activities and notes. It needs a Super Admin, and Data Hub if you want activities and custom field mappings. It’s also one-way and one-time, so anything logged in Pipedrive after the transfer is up to you. Pipedrive’s export gives you activities, notes and files, but Pipedrive says items “linked to deals and contacts must be exported separately”. You join them back to their parents yourself, by Pipedrive deal and person ID.
Steps for the logged emails
- Pull mail threads and messages from Pipedrive’s API, with the linked person and deal IDs.
- Make sure HubSpot contacts and deals carry a “Pipedrive ID” property.
- Build a file with Email body, Email direction (Incoming or Outgoing), Activity date, subject and the parent’s Pipedrive ID.
- Import into HubSpot as email activities associated with the contacts and deals. Imported emails can’t be updated later, so test on a sample first.
- Reconcile: email counts per deal in Pipedrive compared with HubSpot for a dozen deals.
Where FlitStack AI fits
FlitStack AI reads activities, notes, files and logged emails through the Pipedrive API and writes them to HubSpot timelines with original timestamps and owners, without needing Data Hub. See Pipedrive to HubSpot or HubSpot migrations.