Migrate from Sales Snap to Twenty CRM

Sales Snap Contact records map to Twenty CRM Person records. We extract name fields (firstName, lastName), email, phone, company name, lifecycle stage, and any visible custom fields from the CSV export. Email address serves as the dedupe key. The Sales Snap lifecycle stage property maps to a custom field on the Twenty Person record so that original stage history is preserved for audit. Lifecycle stage is not a native Twenty Person field in v1.x, so we create a custom field (lifecycle_stage__c) during schema setup.

Sales Snap Company records (exported per-contact or as standalone rows) map to Twenty CRM Company records. Deduplication occurs on company name during import. The Twenty Company record is created before Person import so that the Person-to-Company link is satisfied at the moment of insert. Any Sales Snap contacts without a matching company are imported as Persons without a Company link and flagged for reconciliation.

Sales Snap Deal records map to Twenty CRM Opportunity records. The deal name, amount, stage, owner, and close date migrate directly. Sales Snap pipeline stages map to Twenty Opportunity stage values that we configure during schema setup. Deals without a linked Contact in Sales Snap are flagged as orphaned and require manual contact linking in Twenty post-import.

Sales Snap does not expose a configurable pipeline object in CSV exports; pipeline state is inferred from the lifecycle stage on each Contact record. We extract unique stage values from the Sales Snap export, map them to Twenty Opportunity stage values during schema design, and create a stage probability mapping that the customer validates before migration runs. Pipeline configuration is rebuilt in Twenty's settings as a prerequisite step.

Sales Snap Sequences (email templates, step order, timing delays, personalization tokens) are core to the source platform but have no direct equivalent in Twenty CRM's v1.x workflow builder. We inventory every Sequence in the export: template subject, body copy, personalization tokens, step order, and inter-step wait durations. We deliver a written Sequence Rebuild Document that maps each Sales Snap step to a Twenty Workflow step or recommends an external sales engagement tool (Lavender, Apollo, Instantly) if cadence-style sequencing is required. We do not build the workflow in Twenty as part of migration scope.

Sales Snap Tasks (follow-up tasks generated by sequences or created manually) map directly to Twenty CRM Task records. Task type, due date, completion status, and linked Contact name migrate. Orphaned tasks (no linked Contact) are flagged in a separate reconciliation report. Owner assignment migrates by resolving the Sales Snap owner name to a Twenty User record created during workspace provisioning.

Sales Snap engagement metrics (opens, clicks, replies, calls) are logged per Contact but stored as aggregate properties in CSV exports rather than discrete activity records. We aggregate these into a single Comment on the Twenty Person record labeled 'Engagement History Summary' with the full set of engagement counts and dates. The raw engagement data is preserved in structured text format; it does not become discrete Activity records in Twenty because the source export format does not preserve individual event timestamps for each interaction.

Sales Snap custom fields visible in the CSV export map to custom fields on the corresponding Twenty CRM object (Person, Company, or Opportunity). We create the destination custom fields during schema setup with the closest matching Twenty field type. Date fields, text fields, and numeric fields migrate directly. Multi-select or checkbox fields require type conversion to Twenty's supported custom field types. Any custom field that does not appear in the CSV export (gated behind the UI or programmatically accessible) is flagged as a discovery gap and addressed separately.

File attachments linked to Sales Snap Contacts or email templates are not included in the standard CSV export. We do not migrate attachment binaries. We inventory the count and types of attachments referenced in the Sales Snap export and deliver this as a separate Attachment Gap Report so the customer can assess reconstruction needs. Attachments stored in a linked cloud storage service (if configured) may be retrievable separately; this requires a dedicated discovery step with the customer.

Sales Snap Owners referenced on Contact, Company, and Deal records map to Twenty CRM User records provisioned during workspace setup. Owner resolution uses the owner name from the Sales Snap export matched to a User record created in Twenty by the customer's admin. Any Sales Snap Owner without a matching Twenty User is placed in a reconciliation queue. User provisioning is a manual prerequisite step; we cannot create Twenty User records without admin credentials and SSO configuration.