Migrate from Sales Flow Technologies to Twenty CRM

Sales Flow Contacts migrate to Twenty People. The CSV export provides name, email, phone, company, LinkedIn URL, and any custom fields. We map the source email address as the primary email field, phone as the phone field, and LinkedIn URL as a custom text field since Twenty's standard People object does not include a native LinkedIn URL field out of the box. Custom fields from Sales Flow require pre-creation in Twenty's data model via Settings → Data model before import.

Sales Flow stores company name and domain on the Contact record rather than as a separate Company object. We split these into Twenty's Companies object during transformation: the domain becomes the Website field on Companies, and company name becomes the Company Name field. The Company record is created before the linked People records so that the People-to-Company lookup is satisfied at insert time.

Sales Flow Prospect Lists are named groupings of Contacts. Twenty CRM does not have a native list object, so we recreate list membership as Tags. Each Prospect List name becomes a Tag value, and we create a TagAssignment record linking each People record to its list membership. This requires creating a tagging strategy during scoping: if Contacts belong to multiple lists, they receive multiple Tag values.

Sequence step ordering and cadence timing (channel, template, delay days) migrate as structured metadata attached to a Note on the enrolled Contact record in Twenty. We document the sequence name, step number, channel (Email/LinkedIn/InMail), template reference, and inter-step delay in a machine-readable format so the admin can reconstruct it in Twenty's workflow builder. We do not create live automation from this data; the Workflow Migration Summary is the deliverable.

Sales Flow Campaigns bundle multiple Sequences under a single objective. We map Campaign name to a Twenty Workflow name and link the associated sequence Notes under the workflow record. A/B testing configurations and channel routing logic do not transfer and are documented in the Workflow Migration Summary as requiring manual rebuild.

Email engagement records from Sales Flow migrate to Twenty Task records with the channel type recorded in a custom field. The task title carries the email subject, body carries the email content, and the ActivityDate preserves the original send timestamp. If the original Sales Flow CSV export omits email body content (a known export limitation), we flag this during scoping and document it as a gap in the Workflow Migration Summary.

Call engagement records migrate to Twenty Task with a call-specific subtype field. Call duration and disposition from Sales Flow transfer to custom fields on the Task. We preserve the sequence step context (which sequence step triggered the call) in a custom field on the Task so the cadence relationship is visible in Twenty's activity timeline.

Meeting records from Sales Flow migrate to Twenty Task. The meeting title, date, and outcome transfer to the Task fields. Attendee resolution is limited by the CSV export scope; we match attendee emails against the imported People records and create Task relations where a match exists.

Notes in Sales Flow migrate to Twenty Note records linked to the associated People, Company, or Opportunity record. The Note body preserves rich text content. We resolve the parent record reference from the source data's contact association and link via Twenty's relation system.

Sales Flow User accounts (Admin, Standard roles) map to Twenty User records. We match by email address. Any Sales Flow user referenced on Contacts or engagements without a matching Twenty User is held in a reconciliation queue for the customer's admin to provision before the People import completes.

Per-sequence and per-step open rates, reply rates, and connection acceptance rates from Sales Flow export as a structured CSV report. We attach these as a Note on the relevant People record or create custom fields on the People object for key metrics (open rate, reply rate). The destination fields are advisory since Twenty's native reporting does not include equivalent outreach-performance metrics.

Sales Flow Workflow configurations (conditional branching rules like 'if no reply after 3 days, send template B') live in application state not exposed via CSV or API. We do not migrate them as executable automation. We produce a written Workflow Migration Summary documenting every workflow: trigger condition, conditional branches, step sequence, timing rules, and action types. This document serves as the blueprint for manual reconstruction in Twenty's workflow builder. This is the most common source of post-migration surprise and we flag it explicitly in the scoping phase.