Migrate from Sales Snap to Salesforce Sales Cloud

Sales Snap Contacts with lifecycle stage of subscriber, lead, or prospect map to Salesforce Lead. Contacts with lifecycle stage of customer, evangelist, or sales-qualified map to Salesforce Contact tied to an Account. We compute the split using Sales Snap's lifecycle stage field from the CSV export and preserve the original value in a custom field ss_original_lifecycle__c on both Lead and Contact for audit continuity.

Sales Snap Company records map to Salesforce Account. The company name field from CSV becomes the Account Name. If the same company appears across multiple Contact rows in the CSV (common in Sales Snap exports), we deduplicate on company name before import to avoid duplicate Account records. Account is created before Contact import so that the AccountId Lookup is satisfied at Contact insert.

Sales Snap Sequences are the core workflow object in the platform. We export sequence name, step count, step order, timing rules (days between steps), and email template body text into a structured CSV. In Salesforce, these become EmailTemplate records (classic) or ContentBuilder assets, and we deliver a sequence-step inventory document so the customer's admin can rebuild the cadence cadence in Salesforce Sales Engagement (High Velocity Sales) or a third-party sales engagement tool. The cadence automation logic does not migrate as executable code.

Sales Snap follow-up tasks generated by sequences export as a flat task list. We map task type, due date, completion status, and linked contact. Orphaned tasks (task records with no linked contact in the CSV) are flagged separately in a reconciliation report for the customer's admin to resolve before production import.

Sales Snap engagement logs recording email opens migrate as Salesforce Task records with a custom TaskSubtype field set to EmailOpen and the ActivityDate set to the original Sales Snap timestamp. The WhoId points to the migrated Lead or Contact. Email open counts per contact aggregate into a custom field ss_email_open_count__c on the Contact or Lead.

Email click engagements migrate as Salesforce Task with TaskSubtype = EmailClick and the clicked URL stored in a custom field ss_clicked_url__c. The WhoId resolves to the migrated Lead or Contact.

Sales Snap call logs migrate as Salesforce Task with TaskSubtype = Call. Call duration, disposition, and recording URL (if available in the CSV) map to custom Task fields. ActivityDate preserves the original timestamp for timeline ordering.

Meeting scheduled and email reply engagements migrate as Salesforce Task records with the original timestamp and engagement type preserved in custom fields ss_engagement_type__c and ss_original_timestamp__c.

Individual sequence steps from the Sales Snap CSV (step number, step type, email subject, email body, delay days) map to Salesforce EmailTemplate body content and we generate Campaign Member records for each Contact in the sequence. The cadence rebuild in Salesforce Sales Engagement uses these as the reference data.

Sales Snap Owner (sales rep) references in the CSV export map to Salesforce User records by email match. We reconcile the owner list during discovery and hold any Owner without a matching Salesforce User in a provisioning queue. The customer admin provisions missing Users before production import resumes because OwnerId is required on most standard Salesforce objects.

Sales Snap custom fields visible in the CSV export map 1:1 to Salesforce custom fields. We flag any field requiring type conversion (Sales Snap date stored as text vs Salesforce date field, or picklist values that require value set creation in Salesforce). Fields not visible in the CSV export (hidden or programmatically gated) are flagged as data gaps during scoping.

Sales Snap does not expose a configurable pipeline object in CSV exports. We infer pipeline state from contact lifecycle stage values and map to Salesforce Opportunity Stage names. Each inferred stage gets a Salesforce Sales Process entry, and we recommend that the customer admin configures Record Types and stage probability percentages post-migration. This is a configuration step, not a data migration step.