Migrate from SalesCaptain to Pipedrive

SalesCaptain Contact records map directly to Pipedrive Person. Standard fields (name, email, phone, address) transfer 1:1. The SalesCaptain contact ID is preserved in a custom field sc_original_id__c for deduplication and cross-reference. Owner assignment resolves by email match against Pipedrive User records; unresolved owners are held in a reconciliation queue for admin provisioning before Person import completes.

SalesCaptain Company records map to Pipedrive Organization. Company-level fields (name, domain, address, industry) transfer directly. The Organization is created before Person import so that the Organization ID is available to satisfy Person.organization_id during bulk insert. Multi-location companies in SalesCaptain map to a single Organization with the location data stored in a custom field sc_location__c on the Organization record.

SalesCaptain Lead records (distinct from Contact) map to Pipedrive Lead. Lead status and source properties migrate to Pipedrive's lead_status and custom source fields. Pipedrive's Lead object uses the same custom field schema as Deals, so any SalesCaptain Lead-specific custom fields map to the Pipedrive Lead field group without schema changes.

SalesCaptain Deals map to Pipedrive Deals with stage mapping resolved against the destination pipeline. If SalesCaptain uses multiple deal pipelines, each becomes a separate Pipedrive pipeline with its own stage set. Deal value, expected close date, and owner transfer directly. Custom properties on SalesCaptain Deals migrate as Pipedrive custom fields on the Deal object.

Each SalesCaptain pipeline and its stage values are mapped to a Pipedrive pipeline with corresponding stage values. Stage order and probability percentages transfer to Pipedrive's stage configuration. We configure the pipeline in Pipedrive before Deal migration begins so that stage references are valid at import time.

SalesCaptain Conversation threads (SMS, calls, messages) are decomposed into individual Activity records in Pipedrive. Each message within a thread becomes a separate Note or Task with an Activity timestamp, participant list, and content. The parent thread is preserved by linking all resulting Activities to the same SalesCaptain conversation_id stored in a custom field sc_thread_id__c. If the SalesCaptain thread references a specific Deal, the Activity also links to the corresponding Pipedrive Deal via WhatId.

SalesCaptain Communication Channel Profiles (phone numbers, messaging accounts) export as metadata. These transfer to Pipedrive as custom fields on the Person record (phone_1__c, phone_2__c, sms_number__c) or as Notes attached to the Person for richer context. Channel-specific routing rules (e.g., auto-assignment by phone number) have no Pipedrive equivalent and are documented in the Workflow Inventory for manual rebuild.

SalesCaptain custom field definitions export as JSON schemas. We create matching Pipedrive custom fields on the Person object before migration, applying type coercion where SalesCaptain field types (date-only, multi-select) may not map directly to Pipedrive equivalents. Multi-select picklist values are normalized to Pipedrive's comma-delimited format. Date-only fields are stored as datetime in Pipedrive to avoid time-zone ambiguity, flagged in the mapping sheet.

Deal-level custom fields in SalesCaptain migrate to Pipedrive Deal custom fields. Pipedrive supports custom fields on Deals from the Lite tier, but pipeline-specific custom fields (visible only in certain pipeline stages) require the Premium tier. We confirm the customer's Pipedrive tier during scoping and adjust the field placement accordingly.

SalesCaptain User records (name, email, role, assignment data) map to Pipedrive Users. Owner assignment on migrated records uses email-based lookup. Any SalesCaptain user without a matching Pipedrive User account is flagged in the reconciliation report for admin provisioning before record migration begins.

SalesCaptain Automation Flows (triggers, conditions, actions, delays) are not exposed via API and cannot be migrated programmatically. We document every active Automation Flow during the discovery phase using a Workflow Inventory worksheet that captures trigger conditions, action types, filter logic, and recommended Pipedrive Automation Builder equivalent. The customer's admin rebuilds these post-migration using the inventory as a reference guide.