Pipedrive leads export — schema (migration reference)
What this is: the column schema of the real Pipedrive leads export Empire shared (
leads-15084451-91.xlsx, received 2026-09-13). This is the migration/intake source-of-truth for F11 (lead intake), F17 (lead-source tracking) and the Pipedrive → CRM migration. Only the structure is recorded here. The file itself holds ~692 real leads with contact PII and lives outside the repo (client data) — it is never committed. Use this doc to design field mapping; use the file (out-of-band) for the actual migration run.
Shape
- One sheet,
lead list— 692 leads, all “Not archived”. The first export (2026-09-13) has 20 columns; the re-export of 2026-09-28 (leads-15084451-97.xlsx, every hidden column ticked) has the same 692 leads and 21 columns — the one addition,Lead - Archive reason, is empty in every row. A list view may hide archived leads, so “all not archived” does not prove none exist (F4-a Q-4).
Columns (Pipedrive export field → migration note)
| Export column | Migration / CRM note |
|---|---|
Lead - ID |
Pipedrive lead id — keep as the external key for idempotent migration + traceability |
Lead - Title |
Lead display title |
Lead - Organization |
→ Account (org). One primary account per lead; see OQ-57 (multiple parties on a lead) |
Lead - Contact person |
→ Contact. See OQ-57 for the participants (N:N) question |
Lead - Value / Lead - Currency |
Estimated value + currency |
Lead - Owner |
Not matched to a user — every imported lead is owned by the import owner and the Pipedrive owner’s name is kept (PRD Rev 44, F4-a spec) |
Lead - Creator |
Who created it |
Lead - Visible to |
Pipedrive visibility — informs the F5 scope mapping, not copied verbatim |
Lead - Labels |
Free-form tags — candidate for lead labels/segmentation |
Lead - Source origin / Lead - Source origin ID |
Every row reads “Manually created” (Pipedrive’s technical note, not a business source); the ID is empty — not stored (F4-a spec) |
Lead - Source channel / Lead - Source channel ID |
Empty in every row — not stored |
Person - Trade Fairs |
Person custom field — ties leads to trade shows; relevant to the capture app (F36) and source attribution |
Lead - Next activity |
Next scheduled activity (follow-up) |
Lead - Lead created / Lead - Update time |
Timestamps — preserve for history/ordering |
Lead - Archive status / Lead - Archive time |
Archived vs open — the migration must carry archive state, not silently revive dead leads |
Lead - Archive reason |
Re-export only; empty in every row |
Linking (checked 2026-09-28 against the re-exported organisations and people): the leads export names its organisation and contact person but carries neither’s ID, and Pipedrive’s list-view export offers no linked ID — the re-export with every hidden column ticked has none. Every organisation and person name matches at least one record, but 52 of the 632 organisation names and 47 of the 637 person names match more than one. The column-by-column mapping onto the lead record is in the F4-a spec.
What this confirms / raises
- Lead source is not in the lead’s own columns — the four
Source *columns are “Manually created” or empty; the business source comes from the person’sTrade Fairscustom field (F4-a spec). - Custom fields exist on the person (
Person - Trade Fairs); custom fields are not migrated (PRD Rev 44), and this one is read only to fill a lead’s source. - Volume: 692 leads is the intake/migration sizing input for F11/F17.
- Open: participants on one lead (OQ-57), owner-initiated sharing (OQ-58) — both interact with how
Organization/Contact person/Visible tomigrate.