How to integrate HubSpot and Pipedrive: setup, sync rules and limits

Short answer: what the integration is for

The integration is useful when each tool keeps a clear job. A typical split is marketing in HubSpot (forms, email, lifecycle stages) and selling in Pipedrive (pipeline, activities, follow-up). The sync passes new leads from HubSpot to sales, and passes deal outcomes back so marketing can report on what actually closed.

It is not a substitute for deciding where work happens. If both teams edit the same fields in both apps, the sync will keep copying those edits back and forth, and someone will eventually overwrite someone else's work. Decide which app owns each object before you switch anything on.

What syncs between HubSpot and Pipedrive (and what does not)

Two details catch most teams. First, only mapped deal stages sync: a deal sitting in a stage you did not map simply stays where it is. Second, events sync one way only, from Pipedrive into HubSpot, and only for contacts that already exist in HubSpot.

Before you start: a 20-minute checklist

• Permissions. In HubSpot you need to be a Super Admin or have App Marketplace permissions. You also need to log in to a paid Pipedrive account. (The HubSpot listing still names Pipedrive's older plans, Essential to Enterprise; any current paid plan is the equivalent.)
• Owners. Owners are matched by email and must exist as users in both apps. Invite missing users first, or deals will arrive without an owner.
• Pipelines and stages. Create the HubSpot pipeline that will receive Pipedrive deals, with a stage for every Pipedrive stage you want to sync. Matching stage names make auto-mapping work.
• Duplicates. Merge duplicate people and organizations in both apps. Contacts match on email and companies on name or domain, so duplicates on either side multiply after the first sync.
• Ownership rules. Write down which app wins for each object. If HubSpot owns contacts and Pipedrive owns deals, set the directions to match instead of syncing everything both ways.
• Automations. List workflows in both apps that change owners, stages or lifecycle fields. Two automations reacting to each other's synced edits is the classic cause of sync loops.

How to connect HubSpot and Pipedrive: step by step

1. Install the app from the HubSpot Marketplace

   In HubSpot, click the Marketplace icon, open the HubSpot Marketplace and search for Pipedrive. Click Install, then Next, log in to Pipedrive, review the requested permissions and click Allow. You can also start from Settings → Import & Export → Go to import → Connect an app.

2. Open the sync settings

   Go to Settings → Integrations → Connected Apps, choose Pipedrive and click Set up your sync. You configure each object pair separately: start with organizations/companies, then people/contacts, then deals.

3. Choose the sync direction

   Pick Data syncs between apps (two-way), Data syncs only to HubSpot or Data syncs only to your third-party app. One-way sync is the safer default for any object that only one team should edit.

4. Set data conflict resolution

   For two-way syncs, pick the default app that wins when both records hold different values. This does not override the direction you chose, and a blank value in the winning app does not wipe out a value in the other one.

5. Map pipelines, stages and fields

   For deals, map each Pipedrive pipeline to a HubSpot pipeline and use Auto-map to pair stages by name. Then review field mappings: click Generate mappings for suggestions or Add a mapping for custom fields (Data Hub Starter or above; a Try out custom mappings option lets you test before paying).

6. Limit what syncs, then save

   By default only contacts with an email address sync. Add filters if, for example, only customers or one region should flow into Pipedrive. Filters apply to the initial sync; records that sync once keep syncing. Click Save and sync. HubSpot emails you when the historical sync finishes.

How HubSpot matches records with Pipedrive

During the first sync HubSpot pairs existing records so it does not create duplicates. After that, it tracks the pair by record ID, so later changes to an email or name do not break the link.

Field types must be compatible: text to text, number to number, dropdown to picklist, checkbox to boolean. Read-only fields and addresses can only sync one way. Dropdown options are captured when you create the sync, so if you add a new Pipedrive option later, save and restart the sync to pick it up.

Fixing common HubSpot Pipedrive sync errors

Open the app's CRM syncs tab. Each object shows records as In sync, Failing or Excluded. Excluded means the record failed a filter or lacks a unique identifier; failing records list a reason and can be retried with Rerun sync.

If you need to stop changes while you investigate, open the sync's More menu and choose Turn off sync. Deleted records can be resynced from the Failing view to recreate them.

Zapier, Make and the API: when the native sync is not enough

The native app keeps records aligned. Workflow tools are better for single events and for data the sync does not cover.

Be careful running Zapier or Make alongside a two-way native sync on the same fields. Every automated write is a change the native sync will copy back, so give each field exactly one writer.

Should you integrate the two CRMs or migrate to one?

Paying for two CRMs makes sense when each one is genuinely better at its part of the job and the sync stays simple. It stops making sense when you are mostly paying to keep duplicate records consistent.

• Integrate if marketing depends on HubSpot features (forms, email, lifecycle reporting) and sales is productive in Pipedrive. See our HubSpot vs Pipedrive comparison for what each does best.
• Move to HubSpot if you want one customer record across marketing, sales and service. Follow our Pipedrive to HubSpot migration guide.
• Move to Pipedrive if HubSpot's seat and onboarding costs outgrew a sales-only use case. Follow the HubSpot to Pipedrive migration guide and compare the real costs for your team size.