Migrate from Pipedrive to Freshsales

Pipedrive Persons map 1:1 to Freshsales Contacts. We map name, email, phone, and address fields by field label match. The Pipedrive Person-Organization link migrates by resolving the source org_name against Freshsales Account records created in the preceding phase. Custom fields on Persons transfer to Freshsales Contact custom fields created with matching names before migration. Owner assignment maps by email match to Freshsales User records.

Pipedrive Organizations map directly to Freshsales Accounts. We map address, domain, and custom field values by label match. The organization_phone and other org-level contact fields map to Account phone. Account is created before Person import so the Contact-Account relationship resolves at insert time without deferred linking.

Pipedrive Deals map to Freshsales Deals with deal title, value, currency, stage name, expected close date, loss reason, and probability preserved. The source Person link maps to the migrated Freshsales Contact; the source Organization link maps to the migrated Freshsales Account. Custom fields on Deals transfer to Freshsales Deal custom fields created with matching names. We preserve stage order and stage probability percentages from Pipedrive into Freshsales pipeline stages.

Pipedrive Leads inherit all Deal custom fields and live in a separate pool from Deals in Pipedrive's newer UX. We map Leads 1:1 to Freshsales Leads, preserving all standard and custom field values. Where the destination account plans to merge Pipedrive Leads into Contacts instead, we document the merge strategy during scoping and apply it as a pre-transform before migration. The customer chooses the approach based on whether they use Freshsales's separate Lead object or route all prospects through Contacts.

Pipedrive Activities include Tasks, Calls, Meetings, and Notes, each with a type, due date, assigned user, and optional deal/person link. We migrate Tasks and Appointments as structured Freshsales Activity records. Call metadata (duration, disposition, recording URL) maps to Freshsales call-specific activity fields. Meeting records map to Appointments with start/end time and location. Note content maps to Freshsales Notes with the parent record link reattached to the migrated Contact, Account, or Deal. Freshsales's native Pipedrive wizard does not migrate emails from Activities; we handle email content migration via API where full engagement history is required.

Pipedrive Products with name, SKU, pricing, and unit information map to Freshsales Products. We create the product records before Deal-Product associations are migrated so that the product reference resolves at import time. Product pricing, currency, and tax information migrate as fields on the Product record.

Pipedrive Deal-Product attachment records (quantity and pricing per product per deal) map to Freshsales Deal-Product associations. We resolve both the parent Deal and the Product reference at migration time, creating the association record only after both parent records exist in the destination.

Pipedrive Pipelines (containers for Deal stages) map to Freshsales Pipelines. Freshsales's native import wizard caps at 10 Pipelines; Pipedrive accounts with more than 10 Pipelines require the additional Pipelines to be merged into the default Pipeline's first stage during migration. We surface this constraint in the pre-flight report and advise the customer on consolidation strategy before migration begins.

Pipedrive Pipeline Stages map to Freshsales Pipeline Stages within the corresponding Pipeline. Stage name, position order, and probability percentage migrate. Closed-Loss and Closed-Won stage names map to Freshsales Deal stage values with the status preserved.

Pipedrive Users referenced as Deal owners, Activity assignees, or Person owners map to Freshsales Users by email address. Users cannot be imported via CSV; Freshsales requires manual user provisioning. We extract all distinct owner email addresses from the source data, produce a user-provisioning checklist with names and emails, and hold records with unresolvable owner references in a reconciliation queue until the customer's admin provisions matching Freshsales Users.

Pipedrive Tags are string labels applied to Persons, Organizations, Deals, and Products. We migrate tags as string arrays and apply them to the corresponding records in Freshsales by name match. Tags that do not already exist in Freshsales are created at migration time.

Pipedrive Custom Fields exist on Persons, Organizations, Deals, Leads, and Products. Each Pipedrive custom field has a 40-character hash key unique to the source account. We read the hash-to-label mapping from Pipedrive's API, resolve the human-readable field name, and create matching custom fields in Freshsales with identical names and compatible field types (text, number, date, picklist, checkbox, etc.) before data import. Freshsales's native import wizard requires exact name match; any discrepancy between the Pipedrive field label and the Freshsales field name results in the field being skipped or mapped to the wrong column. We verify field existence and type compatibility during pre-flight before any data moves.