Pipedrive to HubSpot migration
Moving from Pipedrive to HubSpot gives sales teams access to HubSpot's native marketing hub, service hub, and Operations Hub alongside the CRM — but the data model differences matter. FlitStack AI maps Pipedrive People, Organizations, Deals, and Activities to HubSpot Contacts, Companies, Deals, and engagement history, preserving original create dates, owner assignments, and pipeline stage transitions so your HubSpot instance reflects the full sales record from day one.
FlitStack AI migrates contacts, companies, deals, deal pipelines and calls from Pipedrive to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 50,000 records.

What moves from Pipedrive to HubSpot?
Pipedrive organizes sales data around People, Organizations, Deals, and Activities — a flat, sales-first model optimized for pipeline visibility.
Read the full summary
HubSpot uses a richer object graph that includes Contacts, Companies, Deals, Tickets, and Custom Objects (Enterprise only), with lifecycle_stage as the unifying contact property that tracks a prospect's journey from first touch to customer. The migration carries Pipedrive People to HubSpot Contacts, Organizations to HubSpot Companies, Deals to HubSpot Deals, and Activities (calls, emails, meetings, notes) to HubSpot's engagement timeline. Custom fields on Pipedrive Person, Organization, and Deal objects translate to HubSpot custom properties, with type-aware mapping for pick-lists, dates, numbers, and arrays. HubSpot's pipeline model maps directly to HubSpot Deal pipelines with stage-by-stage translation. Workflows, automations, and Sequences do not migrate — FlitStack exports your Pipedrive automation definitions as a rebuild reference for HubSpot Workflows and Sequences. Reports, dashboards, and integrations must be rebuilt in HubSpot. The migration runs via HubSpot's Bulk Import API with API-based association linking to preserve the relational integrity that flat-file imports lose.
Person → Contact
Pipedrive Person maps to HubSpot Contact.
How it maps
Name, email, phone, job title, and address fields translate directly. Custom fields on Person migrate to HubSpot custom properties on Contact, with type-aware mapping for text, number, date, and pick-list fields. The Pipedrive Person's org_id links to HubSpot Contact.CompanyId lookup. Original create dates, owner assignments, and stage transitions are preserved so your HubSpot instance reflects the full sales record from day one.
Organization → Company
Pipedrive Organization maps to HubSpot Company.
How it maps
Company name, domain, address, industry, employee count, and annual revenue fields translate directly. Parent-child org hierarchies in Pipedrive map to HubSpot's Parent Company ID field, preserving company group structures. All organizational associations to people and deals are maintained during the migration to HubSpot.
Deal → Deal
Pipedrive Deal maps to HubSpot Deal.
How it maps
Deal name, value, stage, expected close date, owner, and custom fields translate directly. Pipedrive's rottert date has no HubSpot equivalent and is preserved as a custom datetime property. Pipeline stage transitions, activity history, and deal associations are maintained in HubSpot's engagement timeline.
Pipeline → Deal Pipeline
Each Pipedrive pipeline becomes a HubSpot Deal pipeline.
How it maps
Stage names, probabilities, and forecast categories map value-by-value. Pipedrive stage-entered timestamps are preserved as HubSpot custom datetime fields for stage-transition reporting in analytics dashboards.
Activity (Call) → Call
Pipedrive call activities migrate to HubSpot Calls.
How it maps
Original timestamp, duration, owner, direction (inbound/outbound), outcome, and linked record (deal or person) are preserved. HubSpot Call records attach to the corresponding Contact, maintaining full communication history.
Activity (Email) → Email
Pipedrive email activities sent via Pipedrive email sync migrate to HubSpot Emails.
How it maps
Subject, body, direction, timestamp, and associations to Contact and Deal are preserved. Emails logged directly in Pipedrive map to HubSpot's engagement timeline for complete communication records.
- PersonContact1:1
- OrganizationCompany1:1
- DealDeal1:1
- PipelineDeal Pipeline1:1
- ActivityCall1:1
- ActivityEmail1:1
+ 8 more in the mapping below
How Pipedrive and HubSpot differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Pipedrive | HubSpot |
|---|---|---|
| Contact object naming | Pipedrive calls contact records 'People' — a flat object with name, email, phone, and custom fields | HubSpot calls them 'Contacts' with a separate lifecycle_stage property tracking prospect journey stage |
| Company object | Pipedrive 'Organizations' store company data; contacts have a single linked org via org_id | HubSpot 'Companies' are separate objects with an N:N relationship to Contacts via association labels |
| Pipeline model | Pipedrive Pipelines contain Deals with stage names, probabilities, and rottert dates per pipeline | HubSpot Deal pipelines use stage names, forecast category, and probability per stage — no rottert dates |
| Activity tracking | Pipedrive Activities cover calls, emails, meetings, tasks, and notes attached to deals or people | HubSpot separates engagement into Calls, Emails, Meetings, Tasks, and Notes with timestamps and owners |
| Automation scope | Pipedrive Sequences handle outbound email cadences; Automations handle trigger-based workflows | HubSpot Workflows cover both inbound automation logic and Sequences handle outbound email cadence — no direct equivalent to Pipedrive's combined model |
| Custom object model | Pipedrive allows custom fields on Person, Organization, Deal, and Product objects | HubSpot custom properties exist per object; true Custom Objects require Enterprise tier with separate schema setup |
| Lead handling | Pipedrive has a dedicated Lead inbox separate from the CRM pipeline | HubSpot routes leads through lifecycle_stage on Contact or a separate Leads object (Enterprise) — no native lead inbox |
Pipedrive to HubSpot field mapping
The 30 most-used fields of 46 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
namePersonfirstnameContact -
namePersonlastnameContact -
emailPersonemailContact -
phonePersonphoneContact -
mobilePersonmobilephoneContact
| Pipedrive field | HubSpot field | Mapping | Note |
|---|---|---|---|
Person.name | Contact.firstname | transformed | Pipedrive stores full name as one field; split into firstname and lastname using space delimiter. |
Person.name | Contact.lastname | transformed | Second part of Pipedrive full name becomes lastname; single-name records become lastname only. |
Person.email | Contact.email | direct | |
Person.phone | Contact.phone | direct | |
Person.mobile | Contact.mobilephone | direct | |
Person.org_id | Contact.associatedcompanyid | transformed | Pipedrive org_id links to HubSpot Company object ID; resolved during migration using ID mapping table. |
Person.owner_id | Contact.hubspot_owner_id | transformed | Owner resolved by email match against HubSpot users; unmatched owners flagged before migration. |
Person.jobtitle | Contact.jobtitle | direct | |
Person.add_time | Contact.original_create_date | custom_field_required | HubSpot CreatedDate is set at migration time; original Pipedrive add_time preserved as custom datetime field. |
Person.update_time | Contact.original_last_modified_date | custom_field_required | Original Pipedrive update_time preserved as custom datetime; enables delta-pickup de-duplication. |
Person.pipedrive_id | Contact.source_system_id | custom_field_required | Pipedrive internal ID stored for traceability and delta-run de-duplication across migration runs. |
Organization.name | Company.name | direct | |
Organization.domain | Company.domain | direct | |
Organization.address | Company.address | direct | |
Organization.city | Company.city | direct | |
Organization.state | Company.state | direct | |
Organization.country | Company.country | direct | |
Organization.industry | Company.industry | value_mapping | Industry pick-list values mapped value-by-value; HubSpot default values applied where no match exists. |
Organization.number_of_employees | Company.numberofemployees | direct | |
Organization.annual_revenue | Company.annualrevenue | direct | |
Organization.owner_id | Company.hubspot_owner_id | transformed | Owner resolved by email match; unmatched owners flagged for fallback assignment. |
Organization.pipedrive_id | Company.source_system_id | custom_field_required | Pipedrive internal ID stored for association resolution and delta de-duplication. |
Deal.title | Deal.dealname | direct | |
Deal.value | Deal.amount | direct | |
Deal.currency | Deal.deal_currency_code | direct | |
Deal.stage_id | Deal.dealstage | value_mapping | Stage ID maps to HubSpot pipeline stage ID via per-pipeline mapping table; includes probability. |
Deal.pipeline_id | Deal.pipeline | value_mapping | Pipedrive pipeline maps to HubSpot Deal pipeline; each pipeline requires pre-created HubSpot pipeline. |
Deal.expected_close_date | Deal.closedate | direct | |
Deal.owner_id | Deal.hubspot_owner_id | transformed | Owner resolved by email match; unmatched owners flagged before migration. |
Deal.person_id | Deal.contact_ids | transformed | Primary person link becomes HubSpot Deal.ContactId; additional linked contacts via Deal contact roles. |
What to watch for in a Pipedrive to HubSpot migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Pipedrive Leads route differently depending on HubSpot tier
Pipedrive's Lead inbox is a separate object from the main CRM.
How we handle it
In HubSpot Starter through Professional, there is no native Lead object — all leads land as Contacts with lifecycle_stage set to 'lead'. Enterprise portals can use HubSpot's Leads object, which requires separate schema setup. We map unqualified Pipedrive leads to lifecycle_stage 'lead' Contacts and qualified leads (from the Pipedrive lead inbox) to lifecycle_stage 'MQL' or 'SQL' depending on your qualification criteria. The routing decision must be made before migration so the mapping logic is consistent.
Pipedrive multi-phone arrays collapse to HubSpot primary and mobile fields
Pipedrive allows a single Person record to hold multiple phone numbers as an array (labeled phone types: work, home, mobile, other).
How we handle it
HubSpot prefers a 'Primary Phone' and 'Mobile Phone' structure on the Contact record. If a Pipedrive Person has more than two phone numbers, the excess numbers are preserved as a custom multi-line text property rather than native HubSpot phone fields. The primary phone (typically the most recently used or work type) becomes HubSpot Phone; the next logical type becomes MobilePhone. Teams relying on click-to-dial need this transformation to work correctly — concatenated strings break that functionality.
HubSpot's marketing-contact billing model has no Pipedrive equivalent
HubSpot charges based on Marketing Contact count in addition to portal access.
How we handle it
Pipedrive has no equivalent billing distinction — all contacts are treated equally. Teams moving to HubSpot from Pipedrive where marketing lists were not tightly managed may face unexpected HubSpot billing tier jumps. We preserve a 'was_marketing_contact_in_pipedrive' flag as a HubSpot custom property so RevOps can segment and suppress records to control marketing-contact counts, but the financial model adjustment is a HubSpot-side governance decision your team must make post-migration.
Pipedrive deal rottert dates require a custom HubSpot property
Pipedrive's rottert feature automatically marks deals as 'rotting' if no activity occurs within a configurable number of days.
How we handle it
HubSpot has no native rottert mechanism. We preserve the rottert status as a custom datetime property (last_rottert_check_date__c) and custom checkbox (is_rotting__c) so your team can rebuild the logic in HubSpot Workflows using a 'days since last activity' calculation. Without this custom property, the rottert concept is lost entirely during migration. This preservation enables RevOps teams to continue monitoring deal health without manual re-entry.
Association labels between contacts and deals need HubSpot contact roles
Pipedrive lets you label a person's role on a deal (Decision Maker, Influencer, Champion, etc.) via the deal-person association.
How we handle it
HubSpot's built-in Opportunity Contact Roles cover the most common case (Primary and Secondary), but HubSpot has no general-purpose role-labeling equivalent for deal-contact associations. We map recognized role labels to HubSpot Opportunity Contact Roles and surface non-standard labels as a custom multi-select property on the deal-contact association. Your team decides whether to use a custom junction object or collapse labels to standard roles.
How the migration runs
Extract Pipedrive data via API with full object graph
FlitStack AI pulls the complete Pipedrive dataset via the Pipedrive REST API v1/v2, capturing People, Organizations, Deals, Activities (calls, emails, meetings, notes, tasks), Products, Pipeline configurations, and Labels.
What this step covers
We extract the full JSON payload including system fields that Pipedrive's visual interface hides, such as follower lists, file metadata, and custom field keys. API-based extraction preserves the relational structure (person_id on activities, org_id on deals) that CSV exports lose. The extraction runs with scoped read access — your team keeps working in Pipedrive throughout.
Clean, deduplicate, and normalize data before mapping
We run a data-quality pass across the extracted dataset: deduplicate contacts by email (keeping the record with the most recent activity), normalize phone number formats to E.164, standardize country and state values, and flag records with missing required fields.
What this step covers
For multi-value phone arrays, we apply the primary/secondary splitting logic. For Pipedrive's follower lists, we map follower IDs to HubSpot Owner IDs by email match. The cleaned dataset is staged in our migration environment before field mapping begins.
Map and transform fields per object with type-aware logic
Our migration engine applies the field mapping defined in your migration plan: Person fields to Contact properties, Organization fields to Company properties, Deal fields to Deal properties.
What this step covers
Custom fields on Pipedrive objects are translated to HubSpot custom properties, with type-aware handling (pick-lists get value-mapping tables, multi-select arrays get HubSpot multi-checkbox or text properties). Pipeline stages are mapped per pipeline using the per-pipeline stage tables. Activities are mapped to their HubSpot equivalents (Calls, Emails, Meetings, Tasks, Notes) with original timestamps and owner assignments preserved.
Run sample migration with field-level diff before full run
A representative slice — typically 100–500 records spanning contacts, companies, deals, and activities — migrates first.
What this step covers
We generate a field-level diff showing source value versus destination value for every mapped field. You verify lifecycle_stage routing for leads, pipeline-to-stage mapping, owner resolution, and association integrity before the full run commits. Any mapping errors are corrected in the migration engine, and the sample is re-run until the diff passes your acceptance criteria.
Execute full migration with delta-pickup window and audit log
The full dataset migrates to HubSpot via the Bulk Import API with API-based association linking for relational integrity.
What this step covers
A delta-pickup window (typically 24–48 hours) captures any Pipedrive records modified during the cutover so HubSpot reflects Pipedrive's final state at go-live. Every operation is logged to an audit trail. One-click rollback is available if reconciliation fails — the rollback reverts HubSpot to its pre-migration state without data loss.
Deliver reconciliation report and automation rebuild reference
Post-migration, we deliver a reconciliation report comparing record counts per object, field-level match rates, and association integrity.
What this step covers
Records that failed to migrate or had partial data are surfaced with root-cause notes. We also deliver an exported JSON/PDF of your Pipedrive automation definitions (Sequences and Automations) formatted as a rebuild reference for your HubSpot admin to use when recreating workflows in HubSpot Workflows and Sequences. Integration rebuild guidance is scoped separately based on your connected tools.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with three drivers: record count determines API extraction and bulk-import volume; custom field count on Person, Organization, and Deal objects drives type-aware transformation work; pipeline complexity (number of Pipedrive pipelines and their stage configurations) affects HubSpot pipeline setup planning. HubSpot's marketing-contact billing model has no Pipedrive equivalent, so teams moving from Pipedrive Advanced or Professional tiers where automation limits were a pain point fall into the upper range. Simple migrations under 10,000 records with under 20 custom fields land at the lower end; multi-pipeline setups with 100k+ records and 50+ custom properties reach the upper bound. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Pipedrive to HubSpot →Why teams move from Pipedrive to HubSpot
- Pipedrive's per-seat pricing with low workflow caps on lower tiers has frustrated growing teams — reviews on G2 and Reddit consistently cite 'expensive for what you get' once the team adds automation-heavy workflows beyond Essential. HubSpot's tiered hub model lets teams pay for only the features they use at a given scale.
- Teams running both sales and marketing hit Pipedrive's marketing limitations — no native landing pages, limited email campaign tools, and the inability to track marketing attribution without third-party integrations. Reddit threads in r/CRM show teams migrating to HubSpot specifically for the all-in-one inbound marketing stack.
- Service and support teams needed separate tools outside Pipedrive — the lack of a native service hub forced operations to build workarounds or buy additional tickets tools. Capterra reviews show teams switching to HubSpot for the combination of Sales Hub and Service Hub under one portal.
- Pipedrive's reporting depth on Advanced and below was cited as insufficient for RevOps teams needing cross-object attribution, multi-touch revenue reporting, and cohort analysis. Teams noted that pipeline analytics and custom dashboards required tier upgrades without delivering the depth expected from enterprise reporting tools. Moving to HubSpot's analytics with Operations Hub Enterprise offers deeper reporting without Pipedrive's tier-gating.
- M&A activity consolidates multiple CRM instances — companies already running HubSpot as their standard CRM needed acquired companies' Pipedrive data migrated in. The migration is part of a post-acquisition data consolidation rather than a platform evaluation, requiring careful mapping of Pipedrive objects to HubSpot's data model to preserve historical context.
Questions, answered
Pipedrive to HubSpot migration questions
How long does a Pipedrive to HubSpot migration take?
Most Pipedrive-to-HubSpot migrations complete in 48–72 hours of clock time for under 50,000 records. Larger setups with 500k+ records, multiple pipelines, or complex custom-field configurations extend to 5–7 days. The longest planning step is setting up HubSpot pipelines and stages to match Pipedrive's pipeline configuration; the actual data transfer via HubSpot's Bulk Import API runs in hours for most datasets. Pipedrive's API rate limits (token-based, introduced December 2024) affect extraction speed for large volumes.
Will my Pipedrive workflows and Sequences migrate to HubSpot?
No. FlitStack AI migrates data and schema only — Pipedrive workflows, automations, and Sequences do not have a migration path to HubSpot. They must be rebuilt in HubSpot's Workflows (for automation logic) and Sequences (for outbound email cadences). The logic is different enough that automated conversion is not reliable. We export your Pipedrive automation definitions as a structured JSON/PDF rebuild reference your HubSpot admin can use to recreate the logic in HubSpot's automation tools. Reports, dashboards, and integrations also do not migrate and must be rebuilt in HubSpot.
What happens to my Pipedrive Leads in HubSpot?
Pipedrive's Lead inbox maps to HubSpot Contacts with lifecycle_stage set to 'lead' if your HubSpot portal is on Starter, Professional, or Enterprise without the Leads object configured. If your HubSpot portal is on Enterprise with the Leads object enabled, Pipedrive leads can map to HubSpot Leads as a separate object. Qualified leads (those moved out of the Pipedrive lead inbox into the pipeline) map to Contacts with lifecycle_stage set to 'MQL' or 'SQL' based on your qualification criteria. The routing must be decided before migration begins so the mapping logic is applied consistently across all records.
Can I migrate Pipedrive custom fields to HubSpot custom properties?
Yes. Pipedrive custom fields on Person, Organization, and Deal objects migrate to HubSpot custom properties on Contact, Company, and Deal respectively. Field types map type-by-type: text, number, date, and boolean have direct HubSpot equivalents. Pick-list (enum) fields require a value-by-value mapping table. Multi-value arrays in Pipedrive (such as multiple phone numbers on one Person) collapse to HubSpot's primary/secondary structure with excess values preserved as a custom multi-line text property. Custom fields must be pre-created in HubSpot before the migration runs, or FlitStack can create them as part of the migration scope.
What happens to my Pipedrive deal pipelines in HubSpot?
Each Pipedrive pipeline becomes a HubSpot Deal pipeline. Stage names, probabilities, and forecast categories are mapped value-by-value per pipeline using a per-pipeline mapping table. Pipedrive stage-entered timestamps are preserved as HubSpot custom datetime fields so your team can build stage-transition reports in HubSpot. HubSpot does not have Pipedrive's rottert-date feature — rottert status is preserved as a custom property (is_rotting__c and last_rottert_check_date__c) so your HubSpot admin can rebuild the logic in a HubSpot Workflow using a 'days since last activity' calculation.
Does the migration affect my Pipedrive account during cutover?
No. FlitStack AI uses scoped read access on Pipedrive — your team continues working in Pipedrive during the migration. No data is modified in Pipedrive. A delta-pickup window (24–48 hours) captures any records created or modified in Pipedrive during the cutover, so HubSpot reflects Pipedrive's final state at go-live. After the migration is verified and you confirm go-live, you can set Pipedrive to read-only or decommission it. We recommend keeping Pipedrive accessible for at least 30 days post-migration for reference in case reconciliation issues surface.
How are Pipedrive activities (calls, emails, meetings, notes) handled?
Pipedrive calls, emails, meetings, tasks, and notes migrate to HubSpot's corresponding engagement objects (Calls, Emails, Meetings, Tasks, Notes). Original timestamps, owners, directions, outcomes, and linked record associations are preserved. HubSpot calls link to the Contact record; meetings show attendees and duration; notes attach to the correct deal or contact. The engagement timeline in HubSpot will show the full activity history from Pipedrive. Emails must have been logged in Pipedrive's email sync to be captured — emails sent outside Pipedrive (directly from Gmail or Outlook) are not in Pipedrive's data and do not migrate.
Will my HubSpot marketing-contact billing change after migration?
HubSpot bills based on Marketing Contact count in addition to portal access. Pipedrive has no equivalent distinction — all contacts are treated equally regardless of marketing involvement. After migration, your HubSpot marketing-contact count will depend on how your team manages suppression lists and contact properties in HubSpot. We preserve a 'was_marketing_contact_in_pipedrive' custom property on each Contact so your RevOps team can segment and suppress records to control the marketing-contact count. The actual billing impact depends on your HubSpot subscription tier and marketing contact management strategy.
Related migrations
HubSpot implementation
Set up HubSpot and migrate into it as one engagement.
See the service → HubSpot to PipedriveThe same pair in reverse Mailchimp to HubSpotMapping · history · rollbackZoho CRM to HubSpotMapping · history · rollbackZendesk Sell to HubSpotMapping · history · rollbackSalesforce to HubSpotMapping · history · rollbackEspoCRM to HubSpotMapping · history · rollbackGoCanvas to HubSpotMapping · history · rollback Pipedrive to SalesforceMapping · history · rollbackPipedrive to Odoo CRMMapping · history · rollbackPipedrive to Zoho CRMMapping · history · rollbackSources: official documentation
- Format import files — HubSpot Knowledge Base
- Create and edit custom objects — HubSpot Knowledge Base
- Import objects programmatically — HubSpot Knowledge Base
- Understand property field types in HubSpot
- Importing data into Pipedrive with spreadsheets — Knowledge Base
- Updating Pipedrive data with a spreadsheet — Knowledge Base
- 5 Simple CRM Data Migration Methods — Pipedrive Blog
Get a quote
Moving from Pipedrive to HubSpot?
Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.
Get a quote