Migrate from Sales Snap to Pipedrive

Sales Snap Contact records map directly to Pipedrive Person (name, email, phone, company name, lifecycle stage). We map lifecycle stage to a Pipedrive custom field lifecyclestage__c because Pipedrive Person does not have a native equivalent. Email addresses serve as the dedupe key during import. Phone number formats are normalized to E.164 where possible; invalid formats are flagged for manual correction before import rather than loaded with bad data.

Sales Snap exports company data per-contact, which produces duplicate Organization records when multiple Contacts share the same company. We deduplicate on normalized company name during the pre-import transform phase and create a single Pipedrive Organization per unique company. The Organization-Address and Organization-Person links are resolved in a second pass after Person records are loaded.

Sales Snap Deals inferred from contact lifecycle stage and any visible deal-related fields in exports map to Pipedrive Deals. The destination pipeline and stage configuration is designed during scoping: Pipedrive pipeline stages are created to match the customer's current lifecycle stage distribution as closely as practical, with probability weights assigned per stage. We flag any Deal fields that cannot be mapped because Sales Snap does not expose a dedicated deal object in exports.

Sales Snap Tasks generated by sequence follow-ups map to Pipedrive Activity records (type: Task) with due date, completion status, and linked Person preserved. Activity is linked via Pipedrive's Person ID resolved from the email match done during Person import. Completed flag maps to Pipedrive Activity's done field.

Sales Snap Sequences represent outbound cadence logic (email templates, step order, timing rules). Pipedrive's Workflow Automation does not replicate this model natively; sequences are a sales engagement feature outside Pipedrive's core automation scope. We deliver a written inventory of every Sales Snap sequence with its step order, personalization tokens, and timing configuration. Rebuild in Pipedrive requires the Growth plan or above ($39/seat/mo annual) and is documented as a separate post-migration step.

Sales Snap engagement logs (opens, clicks, replies, calls) attached to contacts map to Pipedrive Activity records. Because there is no bulk export endpoint, engagement data availability depends entirely on what is visible in the CSV export UI. We inventory engagement record counts during scoping and flag any gaps as data exclusions. Email-type activities link to the Person; call-type activities link to the Person with a custom activity_subtype field.

Sales Snap custom fields visible in the UI export appear in the CSV. We map field names 1:1 to Pipedrive custom fields on the Person or Organization object depending on the field's assignment. Fields requiring type conversion (date vs. datetime, multi-select text vs. Pipedrive picklist) are flagged with the required conversion documented. Hidden or programmatically gated fields that do not appear in exports are inventoried as data exclusions.

Sales Snap Owner references on contacts, companies, and tasks are resolved by email match against the destination Pipedrive User table. Owners without a matching Pipedrive User go to a reconciliation queue; the customer's admin provisions missing Users before record import resumes. We cannot automate User provisioning because Pipedrive User creation requires admin-level authentication.

File attachments linked to contacts or email templates are not included in the standard Sales Snap CSV export. This is a documented data gap, not a migration failure. We inventory the estimated attachment count during scoping and provide a separate attachment retrieval guide with step-by-step manual retrieval instructions from the Sales Snap UI, along with an estimated effort range. Pipedrive file attachments are loaded post-migration in a separate step.

Sales Snap does not expose a configurable pipeline object in exports. We infer pipeline state from contact lifecycle stage values in the CSV and map them to Pipedrive pipeline stage names designed during scoping. The customer reviews the proposed stage mapping before production migration begins. Any lifecycle stage value not represented in the destination pipeline is assigned to a catch-all stage with a custom field flag for post-migration re-segmentation.