Pipedrive to HubSpot
Sales-pipeline CRM with deals, leads, people, organizations, activities, products and projects.
Pipedrive data can move into HubSpot, landing mainly in Sales Hub. 3 of 8 mapped objects move directly (People, Organizations and Deals, pipelines and stages); 4 items need manual work and 2 do not move. Plan roughly 1-2 weeks for a small move and 6-12 weeks for a large one.
Migration checklist for Pipedrive
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 6 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
under 5,000
CSV import of contacts, companies and deals.
Mid migration
5,000-100,000
Adds activities, notes and a pipeline rebuild.
Large migration
100,000+
Custom API/ETL with files, products and automation rebuild.
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 Pipedrive: what you need to get in, what lands in HubSpot, and what will not.
REST/JSON (v1 and v2) with webhooks
API token from a user's personal preferences, or an OAuth app registered with Pipedrive. The token inherits the permissions of the user who created it.
Global admin for the Export data tab; other users need export permission and see only what their visibility group allows.
Daily token budget shared across the account, scaled by plan and seats, with 429 errors once it is spent. Burst limits per token over 2 seconds: API token 20 to 120 and OAuth 80 to 480, depending on plan. Search API: 10 requests per 2 seconds.
Choose your route
How will you move the data?
No native connector was found.
- You need: API token from a user's personal preferences, or an OAuth app registered with Pipedrive. The token inherits the permissions of the user who created it.
- Permission: Global admin for the Export data tab; other users need export permission and see only what their visibility group allows.
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.
- Export data tab (Tools and apps > Export data): one file per item type, CSV or XLSX
- List view export combining deal, person and organization columns
- Single deal export as XLSX
- Insights report exports (PDF/PNG for charts)
- REST API extraction
Limits: Daily token budget shared across the account, scaled by plan and seats, with 429 errors once it is spent. Burst limits per token over 2 seconds: API token 20 to 120 and OAuth 80 to 480, depending on plan. Search API: 10 requests per 2 seconds.
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: 6-12 weeks, usually phased.
Talk to a partnerWhere each object lands
In Pipedrive
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| People | Contacts | yes | Multiple emails and phones are arrays in Pipedrive. HubSpot dedupes on primary email. |
| Organizations | Companies | yes | Direct mapping. Address fields may need restructuring. |
| Deals, pipelines and stages | Deals | yes | Pipelines and stages must be created in HubSpot first. Owners must be mapped to HubSpot users. |
| Leads | Contacts | partial | Map to lifecycle stage or lead status. HubSpot Leads object needs Sales Hub Pro or Enterprise. |
| Activities (calls, meetings, tasks) | Tasks | partial | Activities are in the Export data tab, but CSV import does not carry activities. API or a migration tool is needed. |
| Notes | Notes | partial | Notes export from the Export data tab and import via API or tool. Keep the parent record and original timestamp. |
| Products and deal products | Products | partial | Products and line items need careful association with deals. |
| Files | Files | partial | The export gives download links in a CSV, not the raw files. Files must be fetched and re-uploaded. |
What to expect
Synced emails are not an exportable type and come back through the mailbox.
Insights exports give charts and data, not configuration. These must be rebuilt in HubSpot.
Configuration does not transfer with data exports.
Files are exported as links only.
These are needed before import so associations and owners resolve.
Smart Docs are proprietary, so the generated PDFs must be exported and uploaded.
Export as a global admin and reconcile counts against the Pipedrive UI.
Use list view exports or the linked-record columns in Export data tab files, and retain Pipedrive IDs.
Prefer v2 endpoints, throttle requests, and check the plan's budget and top-ups.
Use a dedicated admin or OAuth credential for the migration.
Pause workflows and customer-facing automation during import.
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.
Export paths, API auth and rate limits are backed by Pipedrive docs and guides. Object mapping rests on third-party migration guides. No HubSpot-native Pipedrive connector was found. Governance, certifications and residency were not researched.
Sources
Related migrations
Frequently asked questions
How do I migrate Pipedrive to HubSpot?
1. Confirm a global admin account for Tools and apps > Export data. 2. Audit custom fields, multi-currency and visibility groups in Pipedrive. 3. Create HubSpot properties with a Pipedrive ID field, pipelines, stages and users. 4. Decide how Leads map: contacts with lifecycle stage, or the HubSpot Leads object.
What data can move from Pipedrive to HubSpot?
These objects move directly: People, Organizations and Deals, pipelines and stages. Check the mapping table for partial and manual items.
What does not move from Pipedrive to HubSpot?
Synced emails via the Export data tab and Automations, permission sets and Insights reports/dashboards. Plan to rebuild or retire these.
How long does a Pipedrive to HubSpot migration take?
Small (under 5,000): 1-2 weeks. Mid (5,000-100,000): 3-6 weeks. Large (100,000+): 6-12 weeks. These are planning estimates, not a quote.
What access do I need to export from Pipedrive?
API token from a user's personal preferences, or an OAuth app registered with Pipedrive. The token inherits the permissions of the user who created it. Global admin for the Export data tab; other users need export permission and see only what their visibility group allows.
What compliance issues apply when moving Pipedrive data?
Check: Files may contain sensitive content; the Pipedrive guide mentions screening them.. Agree consent, retention and access rules before exporting.
Moving Pipedrive 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