Migrate from Snapforce CRM to Pipedrive

Snapforce Accounts map directly to Pipedrive Organizations. The Account Name becomes the Organization name field, and address, website, and industry fields transfer to Pipedrive's standard Organization fields. We use Organization Name as the dedupe key during import. Organization must be created before any related People import so that the People-Organization linkage is satisfied at insert time.

Snapforce Contacts map to Pipedrive People. The Contact-Account relationship maps to a People-Organization link in Pipedrive using the Account Name as the Organization reference. Email, phone, title, and address fields map to standard Pipedrive People fields. Any custom Contact fields are rebuilt in Pipedrive by label match before migration and mapped during import. We audit duplicate prevention settings in Snapforce before import to avoid silent record rejection.

Snapforce Leads map to Pipedrive Leads. Pipedrive's Lead object shares field types with Deals, so any custom Lead fields in Snapforce are created in Pipedrive's Lead field management before migration. Lead status from Snapforce maps to Pipedrive's Lead status field. We verify whether the customer has enabled the Campaigns add-on ($8/user/month) because Campaigns data affects the Lead's source attribution.

Snapforce Opportunities map to Pipedrive Deals. The Opportunity stage maps to a Pipedrive Pipeline stage. We pre-create the Pipedrive pipeline and stage structure before migration so that stage probability and names match the source. The Opportunity-Account linkage maps to Deal-Organization linkage in Pipedrive. Pipedrive's deal-centric model ties Activities directly to Deals, which requires re-associating Snapforce's separate activity records during import.

Snapforce's Activity module (tasks, call logs, meetings) maps to Pipedrive Activity records. Call logs from Snapforce's VoIP system (with duration, timestamp, disposition) transfer as Activity records with activity type set to Call. Task status and due dates map to Pipedrive's Activity done and due_date fields. In Pipedrive, Activities are deal-linked by default; we resolve the parent Deal reference by matching Snapforce's opportunity_id to the migrated Deal.

Snapforce Users map to Pipedrive Users by email match. Snapforce's per-owner CSV export requires we split by user; Pipedrive handles owner assignment differently (post-import bulk update). We extract all distinct owners from the source data, map each by email to a Pipedrive User, and flag any owners without a Pipedrive User match in a reconciliation queue for the customer's admin to provision before record import resumes.

Snapforce custom fields are scoped per-organization and use internal field IDs that do not transfer. We capture the full custom field schema (label, data type, module) during the discovery phase, then recreate each custom field in Pipedrive's field management interface before migration. Pipedrive requires Growth tier or above for certain custom field types (formula fields, required fields); we verify the destination plan tier during scoping and flag any tier-gated field types that require plan upgrade.

Snapforce Campaigns (an $8/user/month add-on above the base CRM) map to Pipedrive's Campaign object if the customer is on a Pipedrive plan that includes campaign tracking. Campaign membership records (which Leads and Contacts are in which Campaigns) migrate as Campaign Member records in Pipedrive. We verify during scoping whether Campaign data exists in the source and whether the destination Pipedrive plan supports campaign tracking before migrating.

Snapforce Documents uploaded to Deals, Contacts, and Organizations export as file attachments. We extract documents to local storage, preserve the parent record linkage by filename, and re-associate them in Pipedrive by matching the parent record to the migrated People, Organization, or Deal. Pipedrive supports file attachments on People, Organizations, Deals, and Activities.

Snapforce voicemails and call recordings are stored as audio files on the platform and are not standard exportable CSV records. We extract the voicemail metadata (timestamp, duration, contact linkage) and audio files, preserve the contact linkage by filename, then re-upload the audio files to the corresponding migrated People record in Pipedrive as file attachments. This process is manual per-file and must be explicitly scoped during discovery. The 500-voicemail per-mailbox cap in Snapforce may result in truncated audio history.