Migrate from Snovio to Pipedrive

Snov.io Prospects map to Pipedrive People records. Standard fields (first name, last name, email, company name, job title, phone, website) map 1:1 to Pipedrive Person fields. Snov.io's company name on a Prospect requires an Organization lookup in Pipedrive; we either resolve against an existing Pipedrive Organization by domain or create one on-the-fly during migration. Custom fields on Prospects migrate to Pipedrive custom fields, which must be pre-created in Pipedrive before migration begins.

Snov.io custom fields are user-defined properties on Prospect profiles. We export the full field schema (name, type, values) alongside data. Pipedrive custom fields are created via Settings > Fields or during import mapping. Field types must be matched: Snov.io text fields map to Pipedrive text, multi-value fields to Pipedrive visible options, and date fields to Pipedrive date fields. We deliver a custom field creation checklist as part of the migration scope.

Snov.io Recipients are unique leads who received at least one campaign email. We export the full recipient list with status, engagement metrics (open, click, reply), and last contacted date. These map to Pipedrive People with a custom activity note appended to each record containing the Snov.io engagement summary. The Snov.io-specific recipient ID is stored in a Pipedrive custom field snovio_recipient_id__c for audit and deduplication against any future Snov.io data re-import.

Snov.io Pipeline Deals (deal name, stage, owner, associated contact reference) map to Pipedrive Deals. Stage names and order migrate as Pipedrive pipeline stages. Owner assignments migrate by resolving Snov.io owner email against Pipedrive User records; any unmatched owners are flagged in the reconciliation report for your admin to provision before Deal import begins.

Snov.io campaign structures (sequence steps, timing rules, channel assignments, A/B test configurations) are not migrated as executable code. We export campaign structure as structured JSON including step order, delay rules, channel type, and template references. Pipedrive does not have a native drip campaign builder; the campaign structure inventory is delivered as a written document for rebuilding in Pipedrive Automations or a connected sales engagement tool (such as Salesloft, Outreach, or Lavender).

Snov.io campaign-level KPIs (delivered, bounced, opened, clicked, replied counts per campaign per period) are exported as structured data. These metrics do not map to a native Pipedrive object; we append them as a formatted text block on the associated Person record's activity log, preserving the historical campaign performance data without overwriting Pipedrive's native engagement tracking.

Snov.io connected email accounts and warm-up configurations cannot be transferred because SMTP credentials and OAuth tokens are not exposed via Snov.io's API and are bound to the Snov.io platform. We export a list of connected mailbox addresses, warm-up pool size, and rotation settings as a configuration document. The destination email accounts must be reconnected directly in Pipedrive's email settings or through an SMTP add-on integration.

Unibox reply metadata (sender, timestamp, thread reference) is exported as structured data. Full email body content does not migrate because Snov.io does not expose full message content via its documented export endpoints and threading limitations apply. We append a structured summary of Unibox conversation activity to the associated Person record in Pipedrive as an activity note.

LinkedIn sequences and connection request records exist in Snov.io only if the $69/month LinkedIn add-on is active. We export the LinkedIn campaign configuration (sequence structure, recipient lists, timing rules) as a structured document separate from email campaign data. Pipedrive does not include LinkedIn automation; the inventory is delivered for rebuilding in a dedicated LinkedIn sales tool (such as Phantombuster, LinkedIn Sales Navigator, or TexAu) post-migration.

File attachments to prospect profiles or campaign emails are not exposed via Snov.io's documented export endpoints. We do not migrate attachments directly. We recommend downloading files from Snov.io separately before the migration window closes and re-uploading them to Pipedrive as ContentDocument records or storing them in a connected file management tool (Google Drive, Dropbox, SharePoint) with links recorded in Pipedrive activity notes.