PipedriveHubSpot

Pipedrive to HubSpot migration

Migration specialists move your organizations, persons, deals and activities into HubSpot, check a sample with you first, and count every record on both sides.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.

Last updated November 2026 · 8 object types mapped

  • 1000+migrations
  • 15 yearsof collective experience
  • AICPA SOC 2 Type IISOC 2 Type IIGDPR compliantHIPAA compliant

Pipedrive to HubSpot at a glance

A Pipedrive to HubSpot migration moves your sales pipeline into Smart CRM: persons become contacts, organizations companies, and deals keep their pipeline, stage and value. Activities and notes land on the right timelines at their original time, and Pipedrive keeps running until a final delta sync.

Objects mapped
8
in this route's mapping
Typical timeline
About 10 business days end to end
3 phases
Free sample
100 records
checked by your team first
Quote
Fixed
within 24 hours
Who it is for
Sales and revenue operations teams outgrowing Pipedrive who want deals, contacts and companies in HubSpot next to marketing and service, with every deal history intact.
What does not move
Pipedrive automations, email sequences and templates, saved filters, reports, dashboards, goals and permissions. We document each one so your admin can rebuild it as a HubSpot workflow, template, list or report.
What sets the scope
Persons, organizations and deals, activities and notes per deal, synced email and file volume, the number of pipelines, and your Pipedrive plan and seats, which decide the daily token pool.

What moves

What moves from Pipedrive to HubSpot

Pipedrive persons move to HubSpot as contacts, organizations as companies, deals as deals in matching pipelines and stages, activities as calls, meetings and tasks, notes as notes, and custom fields as custom properties.

  • 8 included
PipedriveHubSpot
  • PersonsContacts

    Matched on email, so a person already in HubSpot is updated, not duplicated. Where a person has several emails or phones, one becomes primary by a rule you set.

  • OrganizationsCompanies

    Matched on company domain where Pipedrive has a website. Each person is linked to their organization through a shared ID column.

  • DealsDeals

    Title, value, currency, status, owner and expected close date, linked to the contact and company, with the Pipedrive deal ID in a unique property.

  • Pipelines and stagesDeal pipelines and stages

    Built in HubSpot before deals load, with a stage-name table you approve because two pipelines can reuse a stage name.

  • ActivitiesCalls, meetings and tasks

    Each Pipedrive activity type gets a HubSpot type. The due time becomes the Activity date and the done flag becomes task status.

  • NotesNotes

    Pipedrive stores notes as HTML. Each one is loaded with its body and linked to its person, organization or deal.

  • Custom fieldsCustom properties

    Single-option, multi-option, date and text fields are created as matching properties first, with their option lists.

  • UsersOwners

    Matched to HubSpot users by email. A user must exist in HubSpot first, because owners are created from users.

Looking for another object?Field-level mapping is reviewed with you during scoping.

What does not move

What does not move from Pipedrive to HubSpot as-is

Automations, sequences, templates, saved filters, reports and permissions are Pipedrive configuration, so they are documented for your admin to rebuild in HubSpot.

LeadsOn request
In HubSpot: Contacts at a lead stage, or dealsPipedrive keeps leads in their own inbox. The target is one rule agreed on the scoping call.
Synced emailsOn request
In HubSpot: Email activitiesRead through the Pipedrive Mailbox API only, and loaded with body, direction and original time.
FilesOn request
In HubSpot: Files attached to recordsDownloaded by URL and attached to the HubSpot record. Files kept in Google Drive are scoped during the free sample.
Products and deal productsOn request
In HubSpot: Products and line itemsDeal-product rows are rebuilt as line items on each deal.
LabelsOn request
In HubSpot: Property values or listsPipedrive labels have no single HubSpot object, so each becomes a property value or a list, agreed per label.
Call logsOn request
In HubSpot: CallsMoved with their duration and outcome when the call log is in scope.
ProjectsOn request
In HubSpot: Scoped during the free samplePipedrive exports projects only on Premium and above or with the Projects add-on. Where they land in HubSpot is scoped with you during the free sample.
Automations and email sequencesNot migrated
In HubSpot: Workflows and sequencesEach automation is listed with its trigger and actions, then rebuilt by your admin in HubSpot.
Email templates and saved filtersNot migrated
In HubSpot: Templates, snippets and listsTemplate text and filter conditions are documented, so they can be recreated.
Reports, dashboards and goalsNot migrated
In HubSpot: Reports and dashboardsRebuilt on the migrated properties, with the Pipedrive ID kept on every record for matching old figures.
Visibility groups and permissionsNot migrated
In HubSpot: Teams and permission setsSet up again in HubSpot by your admin before users start work.

Free sample migration of 100 of your records. Fixed quote within 24 hours.

Scope my migration

Timeline

Pipedrive to HubSpot migration timeline

Estimated total

About 10 business days

end to end

  • MigrateXwe run it
  • Youyour team acts
  • Bothon a call together
  1. Preparation

    Day 1-2

    • Scoping call

      Both0.5 day

      We agree which pipelines, date ranges and record types move, how leads are treated, and which HubSpot owner each Pipedrive user becomes.

    • Connect both accounts

      You0.5 day

      You approve API access to Pipedrive and install a HubSpot app with contact, company, deal and file scopes. Your sales users are added to HubSpot first, so every owner exists.

    • Pipeline and property build

      Both1 day

      Pipedrive pipelines and stages become HubSpot deal pipelines and stages. Custom fields, the original created dates and the Pipedrive ID become properties before any record loads.

  2. Migration

    Day 3-7

    • Free sample

      MigrateX1 day

      100 of your records, chosen for deals with the most activities, a won deal, a lost deal, a synced email thread and a large file, loaded into HubSpot with notifications off.

    • You review the sample

      You1 day

      Your sales lead opens the deals and checks stages, values, owners, activity dates, notes and the original date properties.

    • Full load

      MigrateX2-3 days

      Organizations first, then persons, deals, activities, notes, emails and files, then the associations between them, paced to your Pipedrive token pool and HubSpot's daily limit.

    • Delta sync

      MigrateX0.5 day

      Records changed in Pipedrive since the full load are updated on the same Pipedrive ID, and only new activities and notes are added, so nothing appears twice.

  3. Validation

    Day 8-10

    • Reconciliation report

      MigrateX1 day

      Pipedrive against HubSpot for persons, organizations and deals by pipeline stage, open and closed-won value by month, activities by type, and files against attachments.

    • Sign-off

      You1-2 days

      Your team spot-checks a random set, workflows and sequences go live in HubSpot, and Pipedrive stays available as the fallback until you sign off.

An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.

Known risks

Every known risk on this route, with how we handle it

  • 2 solved
  • 6 handled
  1. 01HandledMost critical

    A small Pipedrive account can run out of tokens mid-extract

    The problem

    The daily pool scales with seats, so a Lite account with a handful of users has the smallest budget while holding years of deals. A full read of persons, deals and activities by list calls can end in HTTP 429 and stop until midnight server time.

    How we handle it

    We count records per type from your account first, read through v2 with the biggest pages, and spread the extract over the days the pool needs. You can also buy token top-ups for a one-off read, and the free sample shows the real spend.

    Source: Pipedrive developer documentation, checked 15 Nov 2026

  2. 02HandledMost critical

    Pipedrive created dates would turn into the load date

    The problem

    HubSpot sets Create date itself on contacts and companies. A person added to Pipedrive in 2019 and loaded into HubSpot would show the migration day as its start, and a report on contacts created per quarter would put everyone in one quarter.

    How we handle it

    Each person, organization and deal gets its Pipedrive creation date in a dedicated date property that lists and reports can use. Deals also take it in Create date, the one object whose Create date HubSpot lets you edit, and whether contact and company Create date can take it is confirmed during your free sample.

    Source: HubSpot Knowledge Base, checked 15 Nov 2026

  3. 03Solved

    Won and lost deals need their status and close time together

    The problem

    Pipedrive records a deal as open, won or lost, and keeps won, lost and close times beside the status. If status and times are loaded in separate passes, a won deal can sit in HubSpot with the wrong date, and closed-won revenue by month comes out wrong.

    How we handle it

    Each deal is written once, with its stage, status, value, currency and close date in the same record. The reconciliation report totals closed-won value by month on both sides so any gap shows before sign-off.

    Source: Pipedrive developer documentation, checked 15 Nov 2026

  4. 04Handled

    The Pipedrive Leads inbox has no single HubSpot home

    The problem

    Pipedrive keeps leads apart from deals, each tied to a person or an organization. HubSpot has contacts with a lifecycle stage and deals, and loading every lead as a deal would inflate your pipeline while loading it as a contact would drop its value and label.

    How we handle it

    On the scoping call we agree one rule for leads: contacts at a lead stage, or deals in a named pipeline stage. The lead's value, source and label go into properties either way, and the rule is tested on the free sample.

    Source: Pipedrive Knowledge Base, checked 15 Nov 2026

  5. 05Handled

    Synced email can only be read through the Pipedrive API

    The problem

    Pipedrive's export article never mentions email. Messages sit in the Mailbox and come out through API calls with the body switched on, and nothing read describes their attachments. Email sync also exists only on Growth and above.

    How we handle it

    We read each deal's and person's messages through the Mailbox endpoints and load them as HubSpot email activities with body, direction and original time. Whether message attachments can be pulled is confirmed during your free sample.

    Source: Pipedrive developer documentation, checked 15 Nov 2026

  6. 06Handled

    Pipedrive files arrive as links, and Google Drive files are skipped

    The problem

    The Pipedrive API gives file metadata and a URL to download from, not an archive, and lists files 100 at a time. Files stored in Google Drive are left out of the global export, so a person or deal can lose attachments without any error.

    How we handle it

    We download every file Pipedrive holds and attach it to its HubSpot record. What happens to files kept in Google Drive, and to very large files, is scoped with you during the free sample.

    Source: Pipedrive developer documentation, checked 15 Nov 2026

  7. 07Handled

    Every Pipedrive activity type needs a HubSpot home

    The problem

    A Pipedrive activity has a type, a due date and time, a done flag and links to a deal, lead or organization. HubSpot holds calls, meetings and tasks, so every Pipedrive activity type without a HubSpot equivalent needs a mapping rule before the load.

    How we handle it

    Every activity type in your account is listed and given a HubSpot home before load, with custom types mapped as tasks or calls by your rule. Done flags become task status, and one verified extract is loaded once.

    Source: HubSpot Knowledge Base, checked 15 Nov 2026

  8. 08Solved

    Mixed v1 and v2 timestamps break date columns

    The problem

    Pipedrive v1 writes a time as 2024-07-01 05:46:33 and v2 as 2024-07-01T05:46:33Z. An extract that mixes the two endpoints puts both shapes in one column, and HubSpot rejects or misreads the rows that do not match its date format.

    How we handle it

    The whole extract is read through v2 and converted to one format before it reaches the HubSpot files, and a date check runs on every date column of the free sample.

    Source: Pipedrive developer documentation, checked 15 Nov 2026

Technical profile

What makes this route technical

Pipedrive limits an extract with a daily token pool that shrinks on small plans, and HubSpot sets its own Create date on every object except deals.

Exporting from Pipedrive: a daily token pool, not a request count
Pipedrive gives a company 30,000 tokens a day, multiplied by its plan (Lite 1, Growth 2, Premium 5, Ultimate 7) and by its seats. Reading a list costs 20 tokens and reading one record costs 2, and once the pool is spent every call returns HTTP 429 until midnight server time.

Source: Pipedrive developer documentation, checked 15 Nov 2026

Exporting from Pipedrive: read through v2, not v1
Since 1 August 2026 Pipedrive gives no support or fixes for its v1 deals, persons, organizations and activities endpoints. The v2 replacements page by cursor, up to 500 items at a time, and return RFC 3339 timestamps.

Source: Pipedrive developer documentation, checked 15 Nov 2026

Exporting from Pipedrive: one item type per export
Pipedrive's Export data tab downloads leads, deals, organizations, people, products, activities, notes and files one type at a time, as Excel or CSV. Activities, notes and files linked to a deal or contact are not inside the deal or contact file.

Source: Pipedrive Knowledge Base, checked 15 Nov 2026

Exporting from Pipedrive: original times are readable on every record
Pipedrive's v2 API returns each person, organization, deal and note with its creation time in RFC 3339 format, and a deal also carries close, won and lost times. The original dates can be read in full, so the open question is where they sit in HubSpot.

Source: Pipedrive developer documentation, checked 15 Nov 2026

Importing into HubSpot: an activity without a date takes the import time
When an imported call, meeting, note or task has no Activity date, HubSpot stamps it with the date and time of the import. The Pipedrive due or done time is mapped into that column on every row.

Source: HubSpot Knowledge Base, checked 15 Nov 2026

Importing into HubSpot: custom pipelines share one allowance
A seat-based HubSpot account can hold 15 custom pipelines on Starter, 100 on Professional and 350 on Enterprise, counted across all objects, with up to 100 stages in a deal pipeline. A Pipedrive account with many pipelines is checked against that count first.

Source: HubSpot Knowledge Base, checked 15 Nov 2026

Facts checked 15 Nov 2026 against Pipedrive and HubSpot documentation. Each fact links its source.

Pipedrive to HubSpot questions

Still unsure? Ask the engineer who would run this migration, not a sales rep.

How do I migrate from Pipedrive to HubSpot?

Build HubSpot's pipelines and properties first, then load in link order. Users and pipelines come first; then companies and contacts, deals, activities, notes, emails and files; then a delta sync at cutover. Our default plan takes about 10 business days, and the free sample shows the real pace on your own deals.

Which Pipedrive created dates survive in HubSpot?

All of them, in dedicated HubSpot date properties your reports can use. Pipedrive deals also keep their original date in HubSpot's Create date, while Create date on contacts and companies is confirmed during your free sample.

Can you move Pipedrive notes and activities, not just persons and deals?

Yes. Pipedrive exports activities, notes and files apart from the person and deal files, so we read each type and join it back to its parent. Notes arrive as HubSpot notes and activities as calls, meetings and tasks, each at its original time and with its original owner.

What happens to emails synced in Pipedrive?

They move as HubSpot email activities, read through the Pipedrive API. Pipedrive documents no export button for synced email, so the Mailbox endpoints are the only route, and each message is loaded with its body, direction and original time. Whether message attachments can be read is confirmed during your free sample.

Do Pipedrive files and attachments move to HubSpot?

Files stored in Pipedrive do, attached to the HubSpot contact, company or deal they belonged to, within HubSpot's 2 GB file size on paid plans. Files kept in Google Drive sit outside Pipedrive's export, so what happens to them is scoped with you during the free sample.

How are Pipedrive pipelines and stages mapped to HubSpot deal stages?

One to one, built before any deal loads. Each Pipedrive pipeline becomes a HubSpot deal pipeline and each stage a deal stage, using a mapping table you approve. If you have many pipelines, we check them against your HubSpot tier's custom pipeline allowance first, because Starter allows 15.

Do Pipedrive custom fields become HubSpot custom properties?

Yes. Each custom field on persons, organizations and deals is created as a HubSpot property of the matching type, with its dropdown or multi-select options, before records load. A field with no home in HubSpot is listed for you to keep, merge or drop, so no value is lost without your decision.

Will HubSpot notify owners or enrol imported records in workflows?

Owners are not notified: HubSpot sends no assignment notice to users who are made owners through an import. Whether existing workflows enrol imported records is checked with your admin before the load, and the sample is run with those workflows off so you can see the result.

Can my team keep using Pipedrive while the data moves?

Yes. The full load copies a point in time, and a delta sync then brings across the deals, persons and activities changed since. Pipedrive is frozen only for the short window of the final delta, and stays available as your fallback until you sign off the HubSpot data.

What does a Pipedrive to HubSpot migration cost?

It is priced on what moves: persons, organizations and deals, the activities, notes, emails and files on them, and the number of pipelines and custom fields. A free sample migration of 100 of your records comes first, and your fixed quote follows within 24 hours.

How it compares

Four ways to run Pipedrive to HubSpot

The same data, moved four different ways. This is what changes between them.

Object coverage (accounts, contacts, deals, activities, files)

  • MigrateX

    Every object in the mapping on this page, plus the ones you ask for during scoping.

  • Automated migration software

    Contacts and accounts are covered. Deals, activities and their links often are not.

  • Vendor CSV import

    One object per file, and only the fields the export template exposes.

  • In-house scripts

    Whatever you have time to build before the cutover date.

Activities and notes on each record

  • MigrateX

    Each email, call, meeting and note is loaded on its own and linked to the records it belongs to.

  • Automated migration software

    Activities usually arrive, but their links to contacts, deals and owners can be lost.

  • Vendor CSV import

    Notes collapse into one field on the record, if they come across at all.

  • In-house scripts

    Possible, but it is the part teams most often run out of time for.

Files and attachments

  • MigrateX

    Uploaded and linked to the record they belong to. How files over the HubSpot size limit are handled is confirmed during your free sample.

  • Automated migration software

    Supported up to the destination's file size limit. Larger files are skipped.

  • Vendor CSV import

    Not carried by a CSV import.

  • In-house scripts

    Needs its own download, retry and upload pipeline.

Original IDs cross-referenced

  • MigrateX

    Every source id is stored on the destination record and handed back as a map.

  • Automated migration software

    Often kept as a tag or a single text field.

  • Vendor CSV import

    Lost once the file is imported.

  • In-house scripts

    Only if you design the mapping table up front.

Delta sync before cutover

  • MigrateX

    Included. Anything created or changed during the bulk pass is synced at cutover.

  • Automated migration software

    Usually a paid upgrade on the top tier.

  • Vendor CSV import

    You would re-export and re-import by hand.

  • In-house scripts

    Requires change tracking and idempotent writes on both sides.

Rate-limit handling

  • MigrateX

    Paced to your plan limits, honours Retry-After, and resumes from a checkpoint.

  • Automated migration software

    Backs off, but a long run can still stall and leave partial records.

  • Vendor CSV import

    Not applicable, and the file size limits bite instead.

  • In-house scripts

    The most common reason a home-grown run dies overnight.

Validation report

  • MigrateX

    Counts per object and per status on both sides, with every default and placeholder listed.

  • Automated migration software

    A run log and an error list, rather than a reconciliation.

  • Vendor CSV import

    Row counts in a spreadsheet.

  • In-house scripts

    You write the reconciliation queries yourself.

Rollback plan

  • MigrateX

    Every write is tagged, so a batch can be reversed without touching your own records.

  • Automated migration software

    Some approaches can clear a migration, some cannot.

  • Vendor CSV import

    Manual cleanup of everything the import created.

  • In-house scripts

    Only if you built the tagging in from the start.

Who does the work

  • MigrateX

    A MigrateX engineer runs it and stays on the cutover call.

  • Automated migration software

    You run the software. The vendor's support team answers questions.

  • Vendor CSV import

    Your admins, one file at a time.

  • In-house scripts

    Your engineers, instead of your roadmap.

Guides

Guides for a Pipedrive to HubSpot migration

Related routes

Built for your security review, from the first call.

Read how we handle your data
  • AICPA SOC 2 Type II

    SOC 2 Type II

    Independently audited controls over how we handle your data.

  • GDPR compliant

    Data processing agreement available.

  • HIPAA compliant

    Business associate agreement available.

Start your HubSpot move with 100 of your records.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.