Migrate from Freshsales to Pipedrive

Freshsales Contacts map directly to Pipedrive Persons. All standard contact fields (name, email, phone, address, job title) migrate as typed Pipedrive fields. The Freshsales lifecycle stage property is stored in a custom text field fs_original_lifecycle__c on the Person record for reporting continuity. Contact-to-Account associations are preserved as the Person's primary Organization link in Pipedrive.

Freshsales Leads merge into Pipedrive Persons with lead_flag set to true. The Freshsales Lead Status property maps to Pipedrive's label on the Person record. We run the Lead extraction first, then the Contact extraction, and use the Person's email address as the dedupe key so that any Freshsales Contact with the same email as a Lead does not create a duplicate Person in Pipedrive.

Freshsales Accounts map to Pipedrive Organizations. The Account industry, size, website, and address fields migrate as typed Organization fields. Multiple Contacts can link to a single Organization in Pipedrive, matching Freshsales' contact-account association model. We create all Organizations before Persons so that the Organization lookup is satisfied at Person insert time.

Freshsales Deals map to Pipedrive Deals 1:1. Pipeline stage mapping is configured during Pipedrive setup before migration so that the stage values from Freshsales exist in Pipedrive's stage list. Deal amount, probability, expected close date, owner, and custom fields migrate as typed fields or custom fields on the Deal entity. Pipedrive deal fields are limited per plan tier; we verify the destination plan's custom field allowance during scoping.

Each Freshsales pipeline maps to a corresponding Pipedrive Pipeline with its own stage list. We pre-create the Pipedrive pipeline and stages with names matching the source stage labels before any Deal records are imported. Probability percentages from Freshsales stage configurations migrate as stage probability values in Pipedrive.

Freshsales Product catalog entries map to Pipedrive Products with name, code (from hs_sku), unit price, and description preserved. Pipedrive Products require an active Pricebook to be associated with Deals; we pre-create the standard pricebook entries during Pipedrive setup.

Freshsales call logs migrate to Pipedrive Activities with type = Call. Call duration (in seconds), disposition, and outcome are stored in custom fields on the Activity record. Freshsales call recordings require the Pipedrive LeadBooster add-on to be accessible post-migration; we flag this before migration day so the customer can activate LeadBooster if recordings must be preserved.

Freshsales email engagements migrate to Pipedrive Activity records with type = Email. The email subject, body content, and sent timestamp migrate as custom fields on the Activity linked to the corresponding Person or Organization. Email content is stored as a note on the Activity rather than as a native email thread because Pipedrive's native email sync requires a connected inbox.

Freshsales Tasks, Meetings, and Notes map to Pipedrive Activities. Meeting entries include start and end time; tasks include due date and status; notes are stored as Activity descriptions. Activity timestamps are preserved to maintain the Person and Organization activity timeline order.

Freshsales custom objects created via the Freshworks developer platform require schema documentation before migration. If the app schema is documented, we map the custom object fields to custom fields on the appropriate Pipedrive entity (Person, Organization, Deal, or Activity). Pipedrive does not have a native custom object equivalent; custom fields on standard entities are the only path. We verify custom field count against the destination Pipedrive plan tier during scoping.

Territory assignments in Freshsales (Pro-tier) migrate to a custom multi-select picklist field on Person and Deal in Pipedrive. Pipedrive's territory management is available on higher tiers and uses a different model; we preserve the assignment data as a field value rather than attempting a schema-level territory structure migration.

Freshsales file attachments are exported from the Freshsales API and uploaded to the corresponding Person, Organization, or Deal record in Pipedrive. Pipedrive's file storage limits vary by plan; we sample attachment volumes during scoping and flag if the projected total exceeds the destination plan's storage allowance.