SAP ECC and Pipedrive integration

What moves between them

Customer organizations and contact persons flow from SAP ECC into Pipedrive. SAP ECC customer master records (KNA1, KNB1) map to Pipedrive organizations, and contact persons map to Pipedrive persons linked to those organizations. The sync is pull-driven from the ECC side - ml-connector polls ECC on a configurable schedule, extracts customer and contact changes, and writes or updates the matching Pipedrive organizations and persons. This unidirectional flow ensures Pipedrive always reflects the authoritative customer master from ECC without manual re-entry.

How ml-connector handles it

ml-connector manages the on-premises SAP agent connection on your behalf, handling the credential set and agent endpoint for RFC/BAPI calls to ECC. It polls ECC customer master and contact tables on your schedule, extracts key fields (company name, address, contact name, email, phone), and maps them to Pipedrive organizations and persons via a configurable field map. On the Pipedrive side, ml-connector uses OAuth2 bearer token authentication and respects Pipedrive's daily token budget and request rate limits, backing off if a 429 response indicates plan limits are reached. Customer names and addresses are matched to detect duplicate organizations so updates land on the correct record rather than creating duplicates. Custom fields on both sides are supported but field definitions must be pre-mapped since Pipedrive exposes custom fields as opaque hashes. Every ECC customer record carries an audit trail in ml-connector showing when it was read, what fields were extracted, and what action (create or update) was taken on the Pipedrive side.

A real-world example

A mid-market industrial distributor runs SAP ECC for procurement, inventory, and accounting, and uses Pipedrive as the sales team's pipeline tool. Previously, the sales team manually created customer organizations in Pipedrive when a new account was set up in ECC, and periodically synced contact lists by hand. This led to stale contact information, duplicate organizations when the same customer was entered twice, and sales reps working with incomplete address or billing data. With ECC and Pipedrive connected, new customers created in ECC appear as organizations in Pipedrive within minutes, contact changes flow automatically, and the sales team always sees the billing address and payment terms from ECC without switching back to ERP.

What you can do

• •Sync customer organizations from SAP ECC master records into Pipedrive, keeping billing and shipping addresses current.
• •Sync contact persons and their email and phone details from ECC to Pipedrive persons linked to their organizations.
• •Detect duplicate organizations by company name and address so updates match to the correct Pipedrive record.
• •Poll ECC on a configurable schedule using the on-premises agent, and respect Pipedrive rate limits and daily token budgets.
• •Track every customer and contact sync in an audit trail, showing what was read from ECC and what action was taken in Pipedrive.

Questions

How does ml-connector handle SAP ECC's on-premises agent requirement?

ml-connector stores the connection details for your ECC agent and calls RFC/BAPI functions through it to read customer and contact data. The agent must be installed and running on your network with SAP .NET Connector or Java Connector. ml-connector does not require you to configure BAPI_TRANSACTION_COMMIT or manually manage the agent - it handles all agent communication transparently.

Does the integration write data back to SAP ECC?

No. This integration is unidirectional: customer organizations and contact persons flow from ECC into Pipedrive only. ml-connector does not write deals or sales activity back into ECC. If you need to push Pipedrive sales stage changes into ECC, that would require a separate integration configuration.

How does ml-connector handle Pipedrive's rate limits and token budgets?

ml-connector tracks Pipedrive's daily token consumption and request rate limits by plan tier. When it detects a rate limit response (HTTP 429) or anticipates you are approaching your daily token budget, it backs off and retries later. This ensures the sync does not accidentally consume your budget and trigger blocking errors for the sales team.