Migrate from CASH to Pipedrive

Direct map. CASH contacts migrate as Pipedrive Person records. Email, phone, name, address, and job title map directly. Pipedrive Person records store all contact-level data. The Person record ID is used as the parent reference for activities and deal associations.

Direct map. CASH companies migrate as Pipedrive Organization records. Name, domain, industry, employee count, and annual revenue map to Organization fields. Pipedrive Organization supports parent-child hierarchy via the Parent Organization ID field, mirroring CASH parent-company relationships. If CASH companies have no parent relationship defined, they are created as standalone Organizations in Pipedrive with no parent organization assigned.

CASH stores company as a property on the contact record. Pipedrive requires an Organization record to exist first, then links the Person to it via org_id. We resolve the organization by name match or domain match — contacts without a matching Organization are created as standalone Persons with a flag set for manual organization assignment.

Direct map. CASH deals migrate as Pipedrive Deals with name, value, stage, and close date preserved. Pipedrive Deal records are linked to one Pipeline and one Person (primary contact). Multiple contacts on a deal use Pipedrive's contact-role association after migration.

Direct map. CASH pipelines map 1:1 to Pipedrive Pipelines. Each CASH pipeline stage value maps to a corresponding Pipedrive stage within that pipeline. Stage order and probability values are preserved as Pipedrive stage configuration parameters. If CASH stage names differ from Pipedrive stage names, we use a value-mapping table to ensure correct stage assignment during migration.

Pipedrive has no native lifecycle stage field. We create a custom pick-list field on the Person object named Lifecycle_Stage__c using Pipedrive's custom field creation API. CASH lifecycle stage values map directly to the pick-list options. Original stage-change timestamps are preserved in a secondary custom datetime field.

CASH activity history (calls, emails, meetings, notes) migrates as Pipedrive Activities. Activity type determines the Pipedrive Activity type field. Original timestamps, owners, and content (subject, body, duration) are preserved. Each Activity is linked to its parent Person, Organization, or Deal.

CASH leads migrate to Pipedrive's dedicated Leads inbox. Leads retain their status, source, and owner. Pipedrive Leads are separate from the Person/Deal flow — they can be converted to Person + Deal records at any time. We migrate lead data and preserve the original lead ID for traceability.

All CASH custom fields are created in Pipedrive before migration runs using Pipedrive's field creation endpoints. Pipedrive assigns a per-account hash key to each field. The migration mapping references these hash keys explicitly. Custom field data types (text, number, pick-list, date, address) are preserved exactly — pick-list values map value-by-value.

CASH products migrate as Pipedrive Products with name, code, unit price, and description. Product variants map to Pipedrive product variations. Products are then linked to Deals via the deal-product association, preserving quantity and pricing data from the source. If CASH products have no pricing defined, they are created with a zero unit price in Pipedrive and flagged for manual pricing assignment.

CASH file attachments on contacts, companies, and deals are downloaded and re-uploaded to Pipedrive. Files attach to the corresponding Person, Organization, or Deal record. Pipedrive's file size limits apply — files exceeding the limit are flagged before migration so you can choose to skip or compress.

CASH owner records resolve to Pipedrive Users by email address match. Unmatched owners are flagged before migration — you either invite them to Pipedrive first or assign their records to a fallback user. No record lands without a Pipedrive owner assignment.