Migrate from Sanoflow to Twenty CRM

Sanoflow Contact records (name, phone, email, custom fields, owner assignment) map to Twenty CRM Person. The Contact's primary phone number maps to the phone field; email maps to the email field. We extract all Custom Field values and recreate them as custom fields on the Person object via Settings → Data Model before import. Owner assignment maps by email match to Twenty User.

Sanoflow does not have a dedicated Company object, but a Contact may have an associated company name. If the customer uses company-name fields on Contacts, we extract them and create Company records in Twenty CRM, then back-link the Person records via the company link field. If no company data is present, we skip the Company creation phase.

Sanoflow Enquiries are a hybrid of inbound lead records and support ticket records, attached to a Contact and a Pipeline. We ask the customer to decide whether Enquiries map to Twenty CRM Opportunities (if the Enquiry represents a sales prospect) or Tasks (if it represents a support or follow-up action). Pipeline stage assignments map to Opportunity stage values or Task status. The original Sanoflow Enquiry ID is preserved in a custom field for audit traceability.

Sanoflow Pipelines are Kanban boards with ordered stages. Each Pipeline maps to a Twenty CRM Opportunity record type with a configured stage sequence. If the customer has multiple Pipelines, we create multiple Opportunity record types in Twenty and assign the appropriate record type per Enquiry during migration. Stage names and order transfer as-is; stage-specific automation rules are documented but not migrated.

Sanoflow Custom Fields on Contacts and Enquiries (text, number, date, choice) migrate as Twenty CRM custom fields on the relevant object. Choice-field option sets migrate as Select or Multi-Select options in Twenty. We create the field definition first (Settings → Data Model → Add Field), then populate values during the data load. API field names are preserved where possible; Twenty requires API names to be unique and alphanumeric.

Sanoflow Teams and Custom Roles govern which agents see and manage which Enquiries. We extract team membership and role names. Twenty CRM uses a workspace-based permission model with Roles from the Organization plan ($19/user). We document the team-to-role mapping and note where simplification is required if the destination plan is Pro ($9/user), which has fewer permission granularities.

Sanoflow Enquiry Forms are inbound entry points that create Enquiry records. We migrate form field definitions and map them to Twenty CRM's custom field structure on the target object. Form routing rules (which Flow triggers on form submission) do not migrate because Flows cannot be exported. We document routing rules in the Workflow Specification so the admin can rebuild them in Twenty's Workflow builder.

Sanoflow Channels represent connected WhatsApp, Instagram, Messenger, and TikTok accounts. Channel configurations including WhatsApp Business API credentials, phone number associations, and webhooks are destination-platform-specific and cannot be transferred to Twenty CRM. We document the active Channel list during scoping so the customer knows what to reconnect manually in Twenty's integration settings.

Sanoflow Flows are no-code automation workflows built with Triggers, Messages, and Actions. No public export endpoint exists. We extract Flow metadata (name, trigger type, step count, associated Pipeline) and deliver it as a Workflow Specification Document describing each Flow's logic in plain language so the customer's admin can manually rebuild it in Twenty's Workflow builder.

WhatsApp campaign metadata (audience segment names, message template references, send history) migrates as a documented record set. Actual WhatsApp message template approval status does not carry over because templates are tied to the Meta Business account. We flag all active templates, document their content, and note that re-submission to Meta for approval (typically 24-48 hours) is required before campaigns resume.