Why Your Pipedrive Export Is Missing Custom Fields

The 15-field ceiling

Pipedrive's v2 API, the endpoint a modern export or integration is built on, accepts at most 15 custom field keys per request for deals, people, or organizations. A Pipedrive account that has accumulated dozens of custom fields over time, deal source, product line, renewal date, health score, and so on, runs straight into that ceiling the moment a report tries to include everything the CRM tracks rather than what the report actually needs.

There's a second, smaller trap alongside the count limit: Pipedrive returns custom field values as opaque hashes, not the label a user sees on screen in the deal, person, or organization view. A raw export that skips resolving those hashes looks broken even when every field it asked for came back correctly.

Working within 15 fields per request

1. List every custom field the report actually consumes, not everything the CRM has ever tracked, and cut the rest.
2. If a report genuinely needs more than 15 fields, split it into two saved queries against the same entity and join them on the record ID in a reporting tab, rather than one export trying to carry all of them.
3. Resolve custom field hashes to human labels once per run, using the fields endpoint for that entity, and cache the mapping instead of re-resolving it on every refresh.

Which 15 fields actually matter

The limit is a good forcing function to audit custom fields periodically. A field nobody has filled in for six months, or one that duplicates what a pipeline stage already expresses, is a candidate to leave out of the report and eventually retire in Pipedrive itself. A shorter, deliberate field list also makes the reporting tab easier to build formulas and pivots against.

Where this fits alongside the rest of the export

The field limit applies to exports and scheduled refreshes alike. See scheduling a Pipedrive export to Google Sheets for choosing an entity and cadence, and bulk updating Pipedrive from Google Sheets if the same sheet also needs to push changes back. See exporting Pipedrive to Google Sheets for the broader native-export picture this limit sits inside.