Can you integrate Pipedrive with Salesforce?

Stacksync connects Pipedrive and Salesforce with two-way sync for supported records. Authorize the accounts, select the record types, and map compatible fields. Both connectors support reading and writing; object permissions determine the available fields. Use the Issues dashboard to inspect and resolve rejected updates.

Can Pipedrive and Salesforce sync in both directions?

Stacksync supports two-way sync between writable records in both systems. The chosen objects and fields must permit updates in both directions. Read-only fields can supply values but cannot receive updates. Stacksync can read database views; it does not write back to the view.

What should be ready before the Pipedrive and Salesforce initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Create a Pipedrive connection in Stacksync and complete the Allow and Install authorization flow. Authorize a Salesforce user with API access. Check whether the selected objects can use Apex triggers or require polling. Use the pair worksheet to record ownership and acceptance criteria.

How fast does the Pipedrive to Salesforce sync run?

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.

Will existing duplicates merge automatically?

No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.

How do I map Pipedrive fields to Salesforce?

Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.

What should I do if a record fails to sync?

Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.

What does a Pipedrive and Salesforce integration cost?

Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.

Which records should the Pipedrive and Salesforce pilot start with?

Start by reviewing Organizations in Pipedrive and Accounts in Salesforce. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.

CRM · Two-way sync platform

Pipedrive and Salesforce integration — two-way sync

Keep supported Pipedrive and Salesforce records aligned with two-way sync. Give each team access to current data while controlling which system can update each field.

Field mappings and sync direction under your control
Inspect and resolve record errors in one dashboard

Two-way sync for supported objects

stacksync.com

Pipedrive

Salesforce

Explore record coverage

Built for teams where self-serve, reliability and scale matter

Case study

Migrated from MuleSoft

Case study

Migrated from Celigo

Migrated from Heroku Connect

Migrated from Matillion

Case study

Migrated from Fivetran

Case study

Migrated from Celigo

Example workflow

Company sync test

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Starting eventA change involving Pipedrive Organizations or Salesforce Accounts needs a defined result in the other system.

Start with Pipedrive Organizations and Salesforce Accounts. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve parent organizations, business units, and currency references before dependent transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyUse two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.

Review records and field ownership

Mapping essentials

Records and field ownership

Match records by stable IDs and assign an owner for each field. The record notes identify the coverage to check.

Download the mapping worksheet

CSV · No email required

Example record relationships between Pipedrive and Salesforce
Pipedrive record	Salesforce record	Record matching	Field ownership
OrganizationsDocumented record: SupportedRecord matching	AccountsProposed record; confirm Stacksync object support.	Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient.	Assign ownership separately for relationship details and finance-controlled billing details.
PersonsDocumented record: SupportedRecord matching	ContactsProposed record; confirm Stacksync object support.	Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key.	Keep consent and communication preferences under an agreed authority; a general contact update must not silently resubscribe someone.
DealsDocumented record: SupportedRecord matching	OpportunitiesProposed record; confirm Stacksync object support.	Keep the opportunity/deal ID separate from any later order or invoice ID.	The sales process owns qualification and stage changes; downstream financial records have their own state and approval rules.

Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.

Why teams connect Pipedrive and Salesforce

Put your Pipedrive and Salesforce data to work

Start with the work your team needs to complete: keep records up to date, make operational data available for reporting, or move data to a new system. Choose one Pipedrive and Salesforce workflow to test, define what success looks like, and decide who handles failed updates.

Sync deals, persons, and organizations to a database for reporting beyond the built-in Insights views.
Write enrichment or product usage data into Pipedrive custom fields so reps prioritize with live signals.
Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.

What records can you sync?

Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.

Pipedrive

Read and write support varies by record

Record types covered in the setup guide

Record types	Coverage and requirements
Deals Persons Organizations Activities MailThreads MailMessages	✅ Supported. Confirm field permissions and sync direction.
CallLogs Files Goals Leads Notes Pipelines Products Subscriptions Tasks Users	✍️ On Request. Confirm field permissions and sync direction.

Read the Pipedrive connector guide

Salesforce

Read and write support varies by record

Record types covered in the setup guide

Record types	Coverage and requirements
Writable standard objects (subject to detection mode) Writable custom objects (subject to detection mode)	See connector requirements. Confirm field permissions and sync direction.

Read the Salesforce connector guide

Connection essentials

Review how each system connects, detects changes, and permits access to your records.

View setup requirements and limits

Connection requirement	Pipedrive	Salesforce
Integration interface	REST API	REST, SOAP, and Bulk APIs
Authentication	Guided authorization in the Stacksync connection flow; the saved guide does not name the authentication protocol.	OAuth login via a Salesforce user
Change detection	The saved Stacksync guide does not specify the change-detection mechanism.	Stacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used.
Read access	Available for supported records	Available for supported records
Write access	Available for supported records	Available for supported records

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

Pipedrive

Integration interface: REST API
Authentication: Guided authorization in the Stacksync connection flow; the saved guide does not name the authentication protocol.
Change detection: The saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Read access: Available for supported records
Write access: Available for supported records

Setup requirements

Create a Pipedrive connection in Stacksync and complete the Allow and Install authorization flow.
Confirm access for any object marked On Request before designing a dependency on it.

Limitations to check

Many objects are On Request. Two-way sync is documented at connector level; confirm writable fields and detection behavior for each selected object.

Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

Pipedrive setup guide

Salesforce

Integration interface: REST, SOAP, and Bulk APIs
Authentication: OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection: Stacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used. Confirm the selected mode for each object.
Read access: Available for supported records
Write access: Available for supported records

Setup requirements

Authorize a Salesforce user with API access. Check whether the selected objects can use Apex triggers or require polling.
Test in a sandbox and make the intended objects and fields visible to the connected user.

Limitations to check

Object eligibility depends on write access and the selected detection mode. Non-triggerable objects cannot use trigger mode.
Read-only and formula fields need separate handling; a Salesforce platform capability does not establish support for every object.

Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

Salesforce setup guide

Prepare Pipedrive and Salesforce access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

Pipedrive setup checklist

Create a Pipedrive connection in Stacksync and complete the Allow and Install authorization flow.
Confirm access for any object marked On Request before designing a dependency on it.

Setup guides: Authorize Pipedrive

Salesforce setup checklist

Authorize a Salesforce user with API access. Check whether the selected objects can use Apex triggers or require polling.
Test in a sandbox and make the intended objects and fields visible to the connected user.

Setup guides: Authorize Salesforce

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the Pipedrive and Salesforce planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

See Stacksync in action · Review current pricing

Record identity and field ownership

Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.

Download the mapping worksheet · CSV, no email required

Record matching

Organizations / Accounts

Compare whether Pipedrive Organizations and Salesforce Accounts describe the same company in your business.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Pipedrive: Documented record · ✅ Supported
Salesforce: Object support to establish
Record identity: Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient.
Field ownership: Assign ownership separately for relationship details and finance-controlled billing details.

Fields to include

Source record ID
Legal or display name
Business-unit reference
Lifecycle status

Record dependencies: Resolve parent organizations, business units, and currency references before dependent transactions.
Validation: Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
Recovery: Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.

References: Pipedrive: Organizations documentation Salesforce: Accounts documentation

Record matching

Persons / Contacts

Compare whether Pipedrive Persons and Salesforce Contacts describe the same contact in your business.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Pipedrive: Documented record · ✅ Supported
Salesforce: Object support to establish
Record identity: Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key.
Field ownership: Keep consent and communication preferences under an agreed authority; a general contact update must not silently resubscribe someone.

Fields to include

Source person ID
Display name
Email address
Organization reference
Consent state

Record dependencies: Resolve the organization relationship and any owner or consent references required by the destination.
Validation: Test an email change, two records sharing an email, and a person associated with multiple organizations.
Recovery: Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.

References: Pipedrive: Persons documentation Salesforce: Contacts documentation

Record matching

Deals / Opportunities

Compare whether Pipedrive Deals and Salesforce Opportunities describe the same deal or opportunity in your business.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Pipedrive: Documented record · ✅ Supported
Salesforce: Object support to establish
Record identity: Keep the opportunity/deal ID separate from any later order or invoice ID.
Field ownership: The sales process owns qualification and stage changes; downstream financial records have their own state and approval rules.

Fields to include

Source deal ID
Stage
Amount and currency
Expected close date
Company reference

Record dependencies: Map the customer and sales pipeline before the opportunity; map stage values deliberately.
Validation: Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.
Recovery: Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.

References: Pipedrive: Deals documentation Salesforce: Opportunities documentation

Record matching

Leads / Leads

Compare whether Pipedrive Leads and Salesforce Leads describe the same prospect or lead in your business.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Pipedrive: Documented record · ✍️ On Request
Salesforce: Object support to establish
Record identity: Retain the lead ID and record its relationship to any converted contact or company.
Field ownership: Choose which system may qualify or convert the lead; do not infer identical lifecycle stages.

Fields to include

Source lead ID
Qualification status
Owner reference
Conversion reference

Record dependencies: Resolve owner and campaign references and decide how conversion changes the identity relationship.
Validation: Convert a test lead after the first load and verify that it does not create a duplicate person or orphan its activity.
Recovery: Repair the lead-to-contact conversion link before replaying later updates.

References: Pipedrive: Leads documentation Salesforce: Leads documentation

Business process

Tasks / Cases

Support-to-work-item handoff: Salesforce Cases provides context for Pipedrive Tasks. These are related records, not equivalent entities.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Pipedrive: Documented record · ✍️ On Request
Salesforce: Object support to establish
Record identity: Retain separate ticket and task IDs with an explicit relationship; several tasks may resolve one ticket.
Field ownership: Choose which ticket conditions create a work item and which task outcomes may update the support case.

Fields to include

Source record reference
Destination record reference
Approved handoff state
Duplicate-detection key

Record dependencies: Resolve requester, organization, team, and status references before ticket updates.
Validation: Escalate the same ticket twice, close one of several tasks, and verify that private ticket content is not copied into a public work item.
Recovery: Check whether a reply or notification was already sent before replaying ticket actions.

References: Pipedrive: Tasks documentation Salesforce: Cases documentation

Record matching

Products / Products and Price Books

Compare whether Pipedrive Products and Salesforce Products and Price Books describe the same product or catalog item in your business.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Pipedrive: Documented record · ✍️ On Request
Salesforce: Object support to establish
Record identity: Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
Field ownership: Assign ownership for catalog content, price, and stock separately.

Fields to include

Source product ID
SKU or variant reference
Description
Unit of measure
Price-list reference

Record dependencies: Resolve units, variants, categories, and applicable price lists before order lines.
Validation: Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
Recovery: Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.

References: Pipedrive: Products documentation Salesforce: Products and Price Books documentation

Compare integration approaches

This pair can involve both record sync and process handoffs. Keep the Tasks / Cases relationship explicit: copying fields and creating a downstream business transaction require different validation.

Stacksync managed sync

Best fit: Two-way sync for supported objects. Choose the records, writable fields, and permissions for your workflow.
Operating responsibility: Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose: Check record matching: Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit: A vendor-built integration may fit if it supports your Pipedrive and Salesforce record types.
Operating responsibility: Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose: First check whether either vendor offers this integration. If available, verify Organizations / Accounts, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider explicit orchestration for the Tasks / Cases handoff.
Operating responsibility: Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose: Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery.

File or scheduled snapshot

Best fit: Consider for a one-time Pipedrive / Salesforce migration or a reporting need with an explicit freshness window.
Operating responsibility: Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose: Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Company sync test

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Starting event: A change to the selected Organizations or Accounts record needs a defined result in the other system.

Start with Pipedrive Organizations and Salesforce Accounts. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve parent organizations, business units, and currency references before dependent transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.

If it fails: Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.

Contact sync test

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Starting event: A change to the selected Persons or Contacts record needs a defined result in the other system.

Start with Pipedrive Persons and Salesforce Contacts. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve the organization relationship and any owner or consent references required by the destination.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test an email change, two records sharing an email, and a person associated with multiple organizations.

If it fails: Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.

Deal or opportunity sync test

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Starting event: A change to the selected Deals or Opportunities record needs a defined result in the other system.

Start with Pipedrive Deals and Salesforce Opportunities. Use the record-matching and field-ownership rules from your mapping worksheet.
Map the customer and sales pipeline before the opportunity; map stage values deliberately.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.

If it fails: Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.

Plan the customer lifecycle across Pipedrive and Salesforce

Validate the selected objects and operations even where connector-level direction is documented.

Starting event: A customer-facing change in Pipedrive needs operational context in Salesforce.

Select the relevant Deals or Persons records and identify whether the downstream relationship is a person, a company, a deal, or a reporting row.
Define which lifecycle transitions are informative and which should request a downstream action. Keep conversion and merge history connected to stable IDs.
Choose a representative reopened deal, changed contact identity, or reassigned account to test the handoff before expanding.

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated company change

Investigate

Inspect Pipedrive Organizations and Salesforce Accounts, their IDs, and the destination error.

Next action

Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.

Rejected or repeated contact change

Investigate

Inspect Pipedrive Persons and Salesforce Contacts, their IDs, and the destination error.

Next action

Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.

Rejected or repeated deal or opportunity change

Investigate

Inspect Pipedrive Deals and Salesforce Opportunities, their IDs, and the destination error.

Next action

Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.

A record type or update is unavailable

Investigate

Check the Pipedrive and Salesforce connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between Pipedrive and Salesforce

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

Pipedrive Salesforce Timing depends on the connected systems

Detect changesThe saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.

Apply updatesSelected writable fields update in Salesforce. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.

Salesforce Pipedrive Timing depends on the connected systems

Detect changesStacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used. Confirm the selected mode for each object.

Apply updatesSelected writable fields update in Pipedrive. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.

Update timing and record limits

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.

FAQ

Pipedrive and Salesforce integration FAQ

Guides and resources

Next step

See your workflow in Stacksync

Walk through your Pipedrive and Salesforce records, field mappings, and requirements with an integration engineer.

See Stacksync in action Explore plans and pricing

Pipedrive and Salesforce integration — two-way sync

Built for teams where self-serve, reliability and scale matter

Pipedrive

Salesforce

Compliance and data transfers

SSO & SCIM

Alerts

Secure connection options

Record-level recovery

Authentication, permissions and API limits

Connection requirements and limits

Pipedrive

Setup requirements

Limitations to check

Technical documentation

Salesforce

Setup requirements

Limitations to check

Technical documentation

Pipedrive setup checklist

Salesforce setup checklist

Prepare to go live

Record identity and field ownership

Organizations / Accounts

Persons / Contacts

Deals / Opportunities

Leads / Leads

Tasks / Cases

Products / Products and Price Books

Compare integration approaches

Stacksync managed sync

Native vendor integration

Custom API or workflow

File or scheduled snapshot

Workflow scenarios and expected results

Company sync test

Contact sync test

Deal or opportunity sync test

Plan the customer lifecycle across Pipedrive and Salesforce

Initial load and acceptance testing

Organizations / Accounts

Persons / Contacts

Deals / Opportunities

Leads / Leads

Direction and permissions

Freshness and reconciliation

Failed updates, retries and recovery

Rejected or repeated company change

Rejected or repeated contact change

Rejected or repeated deal or opportunity change

A record type or update is unavailable

Source and destination disagree after a retry

Change detection and update delivery

How updates move between Pipedrive and Salesforce

Update timing and record limits

More connections to explore