Migration guides

Pipedrive to HubSpot Migration: Deals, Activities and Email History

Pipedrive to HubSpot migration: how deals, activities, notes and synced email history move, what HubSpot does to their dates, and what to test first.

Ayush BothraFounding Member, MigrateX

Published 6 min read

Paper deal cards, envelopes and calendar cards travelling from a Pipedrive tile to a HubSpot tile, for a Pipedrive to HubSpot migration
On this page

A Pipedrive to HubSpot migration keeps deal history only when deals, activities and emails move as three separate jobs. Pipedrive exports one item type per file and documents no export for synced email, and HubSpot gives any activity without an Activity date the time of the import. Each needs its own read, mapping and single load.

This guide is for sales and revenue operations leads who have chosen HubSpot and are deciding how the history gets there. For the full object mapping, limits and timeline, see the Pipedrive to HubSpot migration page.

Why does deal history split up in a Pipedrive to HubSpot migration?

Because Pipedrive stores and exports it as separate item types. Its export article lists leads, deals, organizations, people, products, activities, projects, notes and files, each downloaded alone as Excel or CSV. Email is one step further out: the article does not mention it, and synced messages live in the Mailbox API as threads and messages.

Where each piece of deal history is read and what it must carry:

Piece of deal historyWhere it is read in PipedriveWhere it lands in HubSpotWhat each record must carry
DealDeals export or API v2DealPipeline, stage, status with its won, lost or close time, value, currency, owner, person and organization
ActivityActivities export or API v2Call, meeting or taskType, due date and time, done flag, the deal it belongs to
NoteNotes export or APINoteHTML body, author, original time, parent record
Synced emailMailbox API onlyEmail activityBody, direction, original time, deal or contact
FileFiles API, by download URLAttachment on the recordParent record

What does a Pipedrive deal need to look right in HubSpot?

Its pipeline, stage, status and status time, written together. Pipedrive's API gives a deal a status and separate close_time, won_time and lost_time fields, plus a lost_reason. If the status arrives without its time, closed-won revenue by month in HubSpot no longer matches Pipedrive.

Two decisions sit behind every deal row:

  • The original created date. HubSpot's knowledge base says "the Create date property is read-only for all objects except deals". A deal can keep its Pipedrive creation date in Create date itself; the contacts and companies beside it need a separate date property.
  • Archived and lost deals. Pipedrive marks archived deals with is_archived and keeps a lost reason. Decide whether they move, and into which stage, before volumes are counted.

How do Pipedrive activities keep their dates in HubSpot?

Only if the original time is mapped on every row. HubSpot's import guide says that when the Activity date is left out, the value is set to the date and time of the import. Through the API, hs_timestamp does the same job: HubSpot's developer docs say it decides where an email or note sits on the record timeline.

The mapping has two parts:

  1. Type. A Pipedrive activity carries a type. HubSpot holds calls, meetings and tasks. List every activity type in your account, including custom ones, and give each a HubSpot home.
  2. Time and state. The due_date and due_time become the activity date. For completed activities, Pipedrive's v2 API also returns marked_as_done_time, which can be kept beside it.

Notes add two rules. HubSpot's developer docs limit a note body to 65,536 characters and use hubspot_owner_id to decide who shows as the note's creator, so each Pipedrive user has to exist as a HubSpot user first.

One HubSpot rule shapes the whole plan. Its import documentation says existing emails, meetings, notes and tasks cannot be updated by import. A load with the wrong type, owner or date cannot be patched. It is deleted and loaded again.

Can Pipedrive email history move to HubSpot?

Yes, when it is read through the Pipedrive API and loaded as HubSpot email activities. Pipedrive's Mailbox endpoints need the mail:read scope and return the message body only with include_body. In HubSpot, an imported email activity needs an Email body and an Email direction, and the original send time goes in as the activity date.

Check two things before you count on it:

  • Your Pipedrive plan. Email sync needs Growth or higher, so a Lite account has no synced mailbox to read.
  • Direction. Every message has to be marked incoming or outgoing, because HubSpot requires it.

What moves is the history. The mailbox connection itself is set up again in HubSpot.

What should you check on the HubSpot sample?

Open real deals in HubSpot beside Pipedrive and check five things:

  1. A won deal shows the right stage and the close date it had in Pipedrive.
  2. No activity on the deal timeline carries the day of the import.
  3. A note shows its original author, not the person who ran the load.
  4. An email thread shows the right direction, body and send time on each message.
  5. The count of activities, notes and emails on each sampled deal matches Pipedrive.

History loads after the records it belongs to: users and pipelines, then companies and contacts, then deals, then activities, notes, emails and files. For the full sign-off method, see our guide to data migration validation. Scope for each side is on the Pipedrive and HubSpot platform pages.

Facts checked November 15, 2026 from Pipedrive: Exporting data from Pipedrive, Pipedrive API v2 (OpenAPI), Pipedrive API v1 (OpenAPI), Mailbox and Notes, Pipedrive: Rate limiting, Pipedrive changelog: deprecated API v1 endpoints out of support, HubSpot: Format import files, HubSpot: Import records for multiple objects, HubSpot: Edit a property value for a record, HubSpot developer docs: Email activities, HubSpot developer docs: Notes, HubSpot developer docs: Pipelines and HubSpot developer docs: Owners. No vendor paid for this article. How we research

Pipedrive to HubSpot migration FAQ

Can I export Pipedrive emails to a CSV file?

Not through any route Pipedrive documents. Its export article covers leads, deals, organizations, people, products, activities, projects, notes and files, and does not mention email. Synced messages are read through the API's Mailbox endpoints, so email history needs a scripted or managed extract.

Do attachments on synced Pipedrive emails move to HubSpot?

Unconfirmed until a sample shows them. HubSpot's email activity can hold attachments in hs_attachment_ids, but the Pipedrive pages we read say nothing about attachments on synced emails. If email attachments matter to you, include a deal with them in your free sample and check the result.

Can we keep the date each deal changed stage?

Yes, as a separate read. Pipedrive keeps a per-field change history for deals, persons and organizations on its own changelog endpoints. Say at scoping if you report on time in stage, because it adds a call per deal and needs HubSpot properties to hold the dates.

Does my Pipedrive plan change how fast history can be read?

Yes. Pipedrive's rate-limiting page sets a daily API token budget of 30,000 multiplied by a plan factor (Lite 1, Growth 2, Premium 5, Ultimate 7) and by the number of seats. A small Lite account with years of activities may need its extract spread over several days.

Is Pipedrive's API v1 still safe for an export script?

Not for core records. Pipedrive's changelog says the v1 endpoints for deals, persons, organizations, activities, products, pipelines and stages have been out of support since 1 August 2026, with no fixes. The v2 endpoints replace them and return timestamps in a different format, so mixing the two breaks date columns.

Get your Pipedrive history checked before you commit

MigrateX is a managed data migration service on its own AI migration platform, SOC 2 Type II, GDPR and HIPAA compliant. Send us your record counts by type (persons, organizations, deals, activities, notes) and whether email sync is on. You get 100 of your own deals and their history in HubSpot, free, and a fixed quote within 24 hours. Start with a free sample. Leaving Salesforce for HubSpot instead? See 9 things that set the scope of a Salesforce to HubSpot migration.

Written by

Ayush Bothra

Founding Member, MigrateX

Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.