How to Connect HubSpot CRM with Pipedrive (2026)

Why Connect HubSpot and Pipedrive

HubSpot and Pipedrive are both popular CRM platforms that serve different segments of the market. Pipedrive is known for its sales-focused simplicity and visual pipeline management, while HubSpot offers a broader platform with marketing, sales, service, and CMS tools. Teams connect these two platforms for two main reasons: migrating from one CRM to the other, or keeping them in sync when different departments or teams use different systems.

This integration guide is most relevant for operations teams managing a CRM migration, companies that have acquired or merged with teams using a different CRM, and organizations where sales uses Pipedrive while marketing uses HubSpot. Whether you are consolidating onto one platform or need ongoing synchronization, understanding how these two CRMs connect is essential for maintaining data integrity during the transition.

What This Integration Does

The HubSpot-Pipedrive connection can serve two primary use cases:

• Data migration: Move all contacts, companies, deals, activities, and notes from Pipedrive to HubSpot (or vice versa) as a one-time transfer when switching CRMs.
• Ongoing sync: Keep both CRMs in sync by bidirectionally synchronizing contacts, companies, deals, and activities in real time or on a schedule. This is useful during a transition period or when different teams legitimately need different CRMs.
• Contact and company sync: Map Pipedrive People and Organizations to HubSpot Contacts and Companies, with all associated fields.
• Deal sync: Map Pipedrive Deals to HubSpot Deals, including pipeline stages, amounts, close dates, and owners.
• Activity sync: Transfer emails, calls, notes, and tasks between systems so the full activity history is available in both CRMs.

Native Integration vs Third-Party

HubSpot and Pipedrive do not have a native, first-party integration. They are competing CRM products, so there is no direct connector built by either vendor. You will need to use third-party tools.

Step-by-Step Setup

Option A: One-Time Migration (Pipedrive to HubSpot)

Step 1: Audit Your Pipedrive Data

Before migrating, audit your Pipedrive data to identify what needs to move:

1. Count your People (contacts), Organizations (companies), and Deals records
2. List all custom fields in Pipedrive that contain important data
3. Identify which pipeline stages in Pipedrive map to which stages in your HubSpot deal pipeline
4. Check for duplicate records and clean them up before migration
5. Note any integrations connected to Pipedrive that will need to be reconnected to HubSpot

Step 2: Prepare HubSpot

In HubSpot, create the infrastructure to receive Pipedrive data:

• Create custom contact and company properties in HubSpot that match your Pipedrive custom fields
• Set up your deal pipeline in HubSpot with stages that correspond to your Pipedrive pipeline stages
• Create any necessary dropdown/select property values to match Pipedrive's options

Step 3: Export Data from Pipedrive

In Pipedrive, navigate to each data section and export:

• People: Go to Contacts > People, click the filter/export icon, and export as CSV. Include all fields.
• Organizations: Go to Contacts > Organizations and export as CSV.
• Deals: Go to Deals, filter for all deals (or specific pipelines), and export as CSV.
• Activities and notes: Export activities and notes separately. These may require Pipedrive's API or a migration tool, as the standard CSV export may not include full activity history.

Step 4: Import into HubSpot

In HubSpot, navigate to Contacts > Import. Choose Import file from computer. Upload your Pipedrive CSV files one at a time, starting with Companies, then Contacts, then Deals. During import, map each Pipedrive column to the corresponding HubSpot property. HubSpot's import wizard allows you to create new properties on the fly if you missed any during preparation.

For deal imports, make sure to map the Pipedrive deal stage to the correct HubSpot deal stage, and associate deals with the correct contacts and companies using email addresses or company names as matching keys.

Step 5: Verify and Clean Up

After import, verify data quality in HubSpot. Check a sample of records to confirm fields mapped correctly. Run HubSpot's duplicate detection tool. Verify that deal-to-contact and deal-to-company associations are correct.

Option B: Ongoing Sync via Zapier

Step 1: Connect Both Accounts to Zapier

Create a Zapier account (or log in). Connect your Pipedrive account by going to My Apps and adding Pipedrive (you will need your Pipedrive API token from Settings > Personal preferences > API). Connect your HubSpot account via OAuth authorization.

Step 2: Create Contact Sync Zaps

Create two Zaps for bidirectional contact sync:

• Pipedrive to HubSpot: Trigger = "New Person in Pipedrive" > Action = "Create or Update Contact in HubSpot." Map fields between systems. Add a filter step to prevent loops (e.g., skip if the contact was just created by the HubSpot-to-Pipedrive Zap).
• HubSpot to Pipedrive: Trigger = "New Contact in HubSpot" > Action = "Create Person in Pipedrive." Apply the same anti-loop filter.

Step 3: Create Deal Sync Zaps

Create Zaps for deal synchronization. This requires mapping deal stages between systems and handling deal-to-contact associations. Use Zapier's lookup steps to find matching contacts before associating deals.

Step 4: Test Thoroughly

Create test records in both systems and verify they sync correctly. Test updating a record in one system and confirm the change appears in the other. Watch for sync loops where a change triggers an update that triggers another update indefinitely.

Best Automation Workflows

1. Phased Migration with Parallel Running

During a CRM migration, run both systems in parallel with bidirectional sync for 30-60 days. This allows teams to gradually transition to the new CRM while maintaining data integrity. Set up Zapier or Make to sync contacts, deals, and activities in both directions. After the transition period, deactivate the old CRM and disconnect the sync.

2. Marketing-Sales Split Sync

If marketing uses HubSpot for campaigns and lead management while sales uses Pipedrive for deal management, sync only qualified leads from HubSpot to Pipedrive (trigger: lifecycle stage changes to SQL). Sync deal outcomes back from Pipedrive to HubSpot (trigger: deal stage changes to closed-won or closed-lost). This gives marketing attribution data without requiring sales to change their CRM.

3. New Customer Onboarding Bridge

When a deal closes in Pipedrive, automatically create or update the contact in HubSpot and enroll them in a HubSpot onboarding email sequence. This bridges the gap between sales closing in Pipedrive and customer success/marketing managing the relationship in HubSpot.

4. Merged Team Data Consolidation

After a company acquisition where the acquired team uses Pipedrive, perform a one-time migration of all Pipedrive data into HubSpot. Use a dedicated migration tool (Import2 or Trujay) to handle the full dataset including activities, notes, and custom fields. Post-migration, set up a temporary sync to catch any records updated in Pipedrive during the transition period.

5. Lead Source Tracking Across Systems

When syncing contacts from HubSpot to Pipedrive, include the HubSpot original source and lead source fields as custom fields in Pipedrive. This ensures that when sales closes a deal in Pipedrive, the lead source data is available for ROI analysis, even though marketing tracked it in HubSpot.

Data Sync Details

Conflict handling: Since there is no native integration, conflict handling depends on your middleware tool. In Zapier, use filter steps and timestamps to determine which update is newer. In Make, build conditional logic that checks modification dates. For migration scenarios, designate one CRM as the "winner" for all conflicts. For ongoing sync, designate the system of record per data type (e.g., HubSpot owns marketing data, Pipedrive owns deal data).

Common Issues and Troubleshooting

1. Sync Loops

A record updated in one CRM triggers a sync to the other CRM, which triggers a sync back, creating an infinite loop. Fix: Add filter steps in your Zapier/Make workflows that check for a "sync source" tag. When a record is created or updated by the sync, tag it (e.g., "synced_from_pipedrive"). Add a filter that skips records with this tag to break the loop. Alternatively, use timestamps to only sync records modified more than 5 minutes after the last sync ran.

2. Deal Stage Mapping Errors

Deals sync with incorrect stages because Pipedrive and HubSpot use different stage names. Fix: Create a mapping table that translates each Pipedrive deal stage to its HubSpot equivalent. Implement this mapping in your Zapier/Make workflow using lookup tables or conditional logic. Test with deals in every possible stage.

3. Missing Activity History After Migration

Contacts and deals migrate successfully, but the associated emails, calls, notes, and tasks are missing. Fix: Standard CSV export/import often does not include activity history. Use a dedicated migration tool (Import2, Trujay, or Data2CRM) that handles activity migration, or use the Pipedrive API to export activities and the HubSpot Engagements API to import them. This typically requires developer assistance.

4. Duplicate Records Post-Migration

After importing Pipedrive data into HubSpot, you find many duplicate contacts and companies. Fix: Before migration, run deduplication in Pipedrive. During import, use HubSpot's duplicate detection (match by email for contacts, match by domain for companies). After import, use HubSpot's Manage Duplicates tool to identify and merge any duplicates that were created.

Alternatives

• HubSpot's built-in migration support: HubSpot offers onboarding assistance that includes data migration from other CRMs. If you are moving to HubSpot's paid plans, ask about migration support included in your onboarding package.
• Import2: A dedicated CRM migration tool that supports Pipedrive-to-HubSpot (and vice versa) with full data mapping, including activities and notes. Pricing is based on data volume.
• Trujay (Data2CRM): Another specialized migration service that handles CRM-to-CRM transfers with data mapping and verification.
• Make (Integromat): More flexible than Zapier for complex migration workflows with data transformation, conditional logic, and error handling. Better for large-volume one-time transfers.
• Custom API scripts: For organizations with developer resources, writing custom scripts using both APIs provides maximum control over the migration process. Both HubSpot and Pipedrive have well-documented REST APIs.