Migrate from Sales Snap to Freshsales

Sales Snap contacts with a lifecycle stage indicating an unqualified prospect (subscriber, lead) map to Freshsales Lead. Contacts with lifecycle stage indicating qualified engagement (SQL, customer, evangelist) map directly to Freshsales Contact. We preserve the original Sales Snap lifecycle stage value in a custom field ss_original_lifecycle__c on both the Lead and Contact for audit and reporting continuity. Email is the unique identifier used for deduplication during import.

Sales Snap company records map to Freshsales Account. Because companies may duplicate across contacts in Sales Snap exports, we deduplicate on company name before import and retain the first associated contact as the primary. Account is created before Contact import so that the Account Lookup relationship is satisfied at the moment of insert.

Sales Snap sequences map to Freshsales Sales Sequences, but Freshsales sequences are a native engagement cadence tool with their own delivery engine rather than a static template export. We extract email templates, step order, step timing, and personalization tokens from Sales Snap as a written handoff document. The customer's admin rebuilds the cadence in Freshsales Sales Sequences using the extracted template content, with timing rules reconfigured to match Freshsales native controls.

Follow-up tasks generated by Sales Snap sequences export as a flat list. We map task type, due date, completion status, and linked contact email. Orphaned tasks (no linked contact record) are flagged in a separate queue with the original Sales Snap task ID for the customer's admin to manually associate post-migration.

Opens, clicks, replies, and calls logged per contact in Sales Snap are aggregated and mapped to Freshsales sales activity records. Freshsales captures emails, call logs, appointments, and tasks as native sales activities on the contact or account timeline. We map the original engagement timestamp to the Activity Date field so the timeline ordering reflects the original sequence interactions.

Sales Snap does not expose a configurable pipeline object in exports. We infer pipeline state from contact lifecycle stages and map to Freshsales deal stage values the customer configures before migration. We deliver a pipeline mapping document during discovery specifying which Sales Snap lifecycle stages correspond to which Freshsales deal stages and deal probability percentages.

Custom fields present in the Sales Snap CSV export map 1:1 to Freshsales custom fields of the equivalent type. We flag any fields requiring type conversion such as date versus datetime, free-text versus picklist, or numeric fields that require decimal versus integer precision. Freshsales Growth and above support all standard custom field types from the field picker without requiring a developer.

File attachments linked to contacts or sequence email templates are not included in the standard Sales Snap CSV export. We do not migrate attachment binaries. We inventory attachment count during discovery and include a separate attachment retrieval step in the project plan with an estimated manual effort surcharge. Post-migration, the customer can re-upload key attachments manually or use Freshsales file storage as part of the contact record.

Sales Snap owners referenced on Contact, Company, and Task records are matched by email to Freshsales User accounts. Any Sales Snap owner without a matching Freshsales User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Active/inactive status is preserved in a custom field during migration.