Migrate from Salescamp CRM to Pipedrive

Salescamp Leads map 1:1 to Pipedrive People. We use the Lead's primary email address as the dedupe key and flag duplicates arising from the same Lead appearing across multiple Collection exports. Standard fields (name, phone, source, status) map directly. Any lead status values in Salescamp map to Pipedrive Activity flags or a custom field lead_status__c. The original Collection membership is recorded as a Tag on the Person record so the customer's admin can reconstruct segmentation logic.

Salescamp Collections are organizational groupings with no direct Pipedrive equivalent. We extract Collection membership from each export CSV and apply the Collection names as Tags on the corresponding Person records in Pipedrive. A Lead that appeared in two Collections receives both Tags. If the customer used Collections for lead routing or segmentation priority, we document the weighting during scoping and the admin recreates the logic as Pipedrive List filters or custom fields post-migration.

Salescamp Company records map to Pipedrive Organizations. In Salescamp, Companies may be secondary to Leads in the data model; we merge linked Lead-Company relationships during migration by matching on domain name or company name. The Organization record is created before the linked Person records so that the Organization-ID lookup resolves at import time. If Salescamp stores only company name on the Lead without a separate Company record, we create an Organization from that field and link it automatically.

Salescamp Deal pipeline stages map to Pipedrive Pipeline stages. Each Salescamp pipeline becomes a Pipedrive Pipeline (or a single Pipeline with multiple stage rows depending on count). Deal value, close date, and stage probability migrate directly. If Salescamp uses multiple pipelines for different product lines, we create corresponding Pipedrive Pipelines and map the deal-to-pipeline relationship by matching pipeline name. Pipedrive's visual drag-and-drop pipeline is rebuilt from the exported stage names and probabilities.

Individual Salescamp Deals map to Pipedrive Deals with the Person (from the linked Lead), Organization (from the linked Company), Deal value, expected close date, and stage migrated directly. We resolve the Person and Organization references by email match and domain match respectively during the import phase. Custom fields on the Deal (product line, deal source, region) migrate as custom fields on the Pipedrive Deal object. Stage mapping is validated against the Pipeline stage configuration before import.

Salescamp activity records (Call, SMS, email sync, meeting notes) migrate to Pipedrive Activities as Tasks or Events. Call logs with disposition and duration migrate to Tasks with TaskSubtype=Call. SMS records migrate as Tasks with a custom type field. Email sync records migrate as Activity log entries linked to the Person. We note that the primary Lead CSV export may not include all engagement history columns; we request supplemental activity exports during scoping and flag any activity type that is not present in the export as a manual supplementation item for the admin.

Salescamp Goals (sales targets per user or team) are informational records without a direct Pipedrive equivalent. Goal definitions migrate as custom fields on the User record (quota_amount__c, quota_period__c) or as Deal-level custom fields tracking deal-stage contribution toward target. The target-tracking logic itself (alerts, progress, automation triggers) is not migrated; we document the goal structure during scoping for the customer's admin to rebuild in Pipedrive using workflow automation or third-party reporting tools.

Salescamp Users and Owners map to Pipedrive Users by email match. We extract every distinct owner referenced on Lead, Deal, and Activity records and match by email against the destination Pipedrive account's User list. Users that do not yet exist in Pipedrive are held in a reconciliation queue for the admin to provision before record import. The customer's admin assigns Pipedrive roles and permissions during setup, which we do not modify.

Salescamp custom fields on Lead, Company, and Deal migrate to Pipedrive custom fields on the equivalent objects. We validate field types during scoping: text fields map to Pipedrive text fields, picklists map to Pipedrive options fields, date fields map to Pipedrive date fields. Pipedrive's custom field management is per-object and accessed through Settings > Data fields. We document every custom field mapping and field type in the field mapping appendix delivered with the migration scope.

Salescamp advertises 1000+ integrations for lead collection, but the specific integration configurations (OAuth credentials, webhook endpoints, sync rules) are not exported. We migrate the resulting lead data from those integrations but not the integrations themselves. The admin rebuilds integrations in Pipedrive using Zapier, Make, or Pipedrive's native API. We provide a list of all identified integrations from the scoping audit as a rebuild reference.