Migrate from Salesflare to Pipedrive

Salesflare Account records map 1:1 to Pipedrive Organization. Standard fields (name, domain, industry, location) map directly. We use the domain field as a dedupe key during import. Organization must import before Contact to satisfy the relationship requirement that Salesflare enforces at the Account level.

Salesflare Contact maps to Pipedrive Person. Name, email, phone, title, and social links transfer directly. We preserve Salesflare's enrichment metadata (scraped company size, LinkedIn profile URL, enrichment source) as custom Person fields in Pipedrive since this data has no native equivalent and represents historical record quality at the time of migration.

The Account-Contact junction in Salesflare preserves which Persons belong to which Organization and whether a Contact is designated as primary. We migrate this as a Person-Organization association record. Pipedrive supports multiple Organization assignments per Person, which mirrors Salesflare's model but without an explicit primary-contact flag; we carry this designation in a custom field primary_contact__c on the Person record.

Salesflare Opportunity maps to Pipedrive Deal. Deal value, expected close date, and stage name transfer directly. Pipeline assignment from Salesflare maps to the corresponding Pipedrive pipeline. We remap Salesflare stage names to Pipedrive stage labels using the customer-supplied stage matrix documented during discovery.

Salesflare pipelines define the ordered set of deal stages available to Opportunities. We export pipeline definitions as metadata and recreate them as Pipedrive Pipelines with corresponding stage sets. Stage order and probability percentages transfer as Pipeline stage configuration in Pipedrive.

Salesflare Activity records (logged calls, emails, meetings, tasks) map to Pipedrive Activity records. Activity type, date, duration, outcome, and notes transfer directly. We preserve the relationship to the linked Person and Deal. The email body content migrates as an Activity note. Call disposition and duration transfer to custom Activity fields.

Salesflare tags are flat labels applied to Accounts, Contacts, and Opportunities. Tag names and object associations migrate as a many-to-many join table. No hierarchy or inheritance exists in either platform. Pipedrive's tag implementation supports the same flat-label model, so the mapping is direct.

Salesflare custom properties on Accounts, Contacts, and Opportunities map to Pipedrive custom fields. We export the full property map per object and create matching custom fields in Pipedrive before import. Field types (text, number, date, picklist, checkbox) map to Pipedrive field types. Any Salesflare formula or calculated fields are exported as their last-computed value, not as live formulas.

Salesflare Users map to Pipedrive Users. We match by email address as the reconciliation key. Any Salesflare User without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision. Role and permission sets from Salesflare map to Pipedrive permission sets, though some Salesflare-specific role names may require admin relabeling.

Salesflare file attachments stored as URLs or accessible binary blobs migrate as Pipedrive Files linked to the parent record (Person, Organization, or Deal). We preserve filename, file size, and linked object. Files that are not accessible (restricted URLs or embedded-only attachments) are flagged in the migration report for manual re-upload by the customer.