Migrate from Snovio to Salesforce Sales Cloud

Snov.io Prospects with no associated Deal or pipeline stage map to Salesforce Lead. Prospects with an active pipeline Deal and a defined stage map to Salesforce Contact attached to an Account. We preserve the original Snov.io lifecycle status in a custom field snov_lifecycle_stage__c on both Lead and Contact for audit and reporting continuity. Custom fields on Prospect profiles migrate to Salesforce custom fields with type mapping (text to Text, number to Number, date to Date).

Snov.io Company records map directly to Salesforce Account. The company domain and website URL migrate to the Account Website field and serve as the dedupe key during import. Account must be created before any Contact import so that the AccountId Lookup relationship is satisfied at Contact insert time. Owner assignment resolves by email match against Salesforce Users.

Snov.io Deal records map to Salesforce Opportunity. The Snov.io deal stage name maps to a Salesforce StageName value within a Record Type that we configure during schema setup. Deal amount, close date, owner, and associated contact references all migrate directly. Closed-Lost and Closed-Won reasons from Snov.io become custom fields on Opportunity for loss/win analysis.

Snov.io Campaign structure (sequence steps, timing rules, channel settings, and step order) is exported as structured JSON and delivered as a written campaign inventory document. This document is not a migratable object because Salesforce Sales Cloud has no native drip-sequence builder. The inventory lists each campaign's trigger, steps, delays, and channel, with a recommended rebuild path in Salesforce Flow or a Sales Engagement add-on.

Snov.io Recipients (unique leads who received at least one email) map to Salesforce Contact records. We export the full recipient list including status, engagement metrics (opens, clicks, replies, bounces), and the campaign reference. Engagement history migrates as Task and Event records linked to the Contact via the WhoId field. Snov.io-specific recipient IDs are preserved in a custom field snov_recipient_id__c for reconciliation.

Snov.io campaign-level KPIs (delivered, bounced, opened, clicked, replied counts) are exported via CSV from premium plans and stored as a reference report alongside the migrated Campaign record. These metrics are not Salesforce-native Campaign metrics but serve as the baseline for reporting until Salesforce's own tracking captures fresh data post-migration. We deliver the full stats export as a supplementary CSV file.

Snov.io connected email accounts and warm-up settings are exported as a metadata list (mailbox address, warm-up volume, rotation settings). The actual SMTP credentials and OAuth tokens cannot be extracted from Snov.io and do not migrate. We deliver the warm-up configuration as a written reference document so the customer's admin can recreate warm-up settings in a dedicated warm-up tool (Lemwarm, Lemlist, or similar) post-migration.

Snov.io Unibox reply metadata (sender, timestamp, thread reference) migrates to Salesforce Task records with the original timestamp preserved for timeline ordering. The full email body content does not migrate because Snov.io threading access has content limitations and the actual emails live in the connected mailbox, not the Snov.io platform. We flag the Unibox metadata export scope during discovery so the customer understands the threading boundary.

LinkedIn message sequences and connection request records from the $69/month LinkedIn add-on are exported as structured data and delivered in the campaign inventory document alongside email campaigns. The actual LinkedIn tokens and message content cannot be extracted. Teams rebuilding LinkedIn sequences in a dedicated LinkedIn Sales Navigator or Sales Engagement tool use the exported configuration as the rebuild reference.

Snov.io user-defined custom fields on Prospects and Deals are exported with their full schema (field name, type, picklist values where applicable). Each custom field receives an equivalent Salesforce custom field with the __c suffix and a matching field type. We create the Salesforce custom field schema in a Sandbox before production migration so that validation rules and required-field constraints are tested against the migrated data first.

Snov.io tags stored as multi-checkbox properties on Prospect profiles migrate to Salesforce multi-select picklist fields on the Contact object. The tag vocabulary is extracted during discovery and the picklist values are created in Salesforce before the Contact import. Tags with more than 500 distinct values are split across multiple picklists or stored as Salesforce Topics with TopicAssignment records.

Snov.io email engagement records (opens, clicks, replies) migrate to Salesforce Task records with ActivityDate set to the original Snov.io timestamp for timeline continuity. The email content itself does not migrate because it lives in the connected mailbox. We flag the engagement metric migration scope during discovery and recommend that the customer treat post-migration engagement tracking as the new source of truth, given the known accuracy issues with Snov.io's pixel-based data.