Migrate from Floww.ai to Twenty CRM

Floww.ai Contact records map directly to Twenty CRM Person objects. Standard fields (name, email, phone, company association) migrate 1:1. Custom Contact properties require field-by-field mapping to Twenty's custom field types during schema design. The Contact's linked Pipeline and Stage assignments migrate as a custom field on the Person record since Twenty does not attach Persons directly to Pipelines at the Contact level.

Floww.ai Lead records are distinct from Contacts in Floww.ai's data model. We assess each Lead's status and stage to determine whether it migrates as a Twenty Person record or as an Opportunity with the Person pre-linked. Leads with no deal value and no pipeline assignment migrate as Person records; Leads with active pipeline stages and deal values migrate as Opportunities with the linked Person pre-created.

Floww.ai Deals map to Twenty CRM Opportunity records. The Deal value, owner assignment, expected close date, and stage history timeline transfer. The Deal's linked Pipeline and Stage are mapped to Twenty's Opportunity pipeline and stage. We preserve the stage history as a custom field log or note on the Opportunity since Twenty's standard stage history is platform-generated.

Floww.ai Pipelines map to Twenty CRM Pipelines. Each Floww.ai pipeline definition (name, stage count, stage names, stage order) is extracted and mapped to a corresponding Twenty Pipeline. Pipeline-level configuration (filter logic per stage) is documented separately for admin rebuild in Twenty because the filter logic cannot be exported directly from Floww.ai.

Floww.ai stage names and counts vary per pipeline. We extract the live stage definitions and map them to Twenty's stage schema. Any stages in Floww.ai that have no direct equivalent in Twenty are flagged for reconciliation during scoping. Stage probability and stage type (open, won, lost) migrate as stage metadata where supported.

Floww.ai Activities (calls, emails, meetings, tasks) linked to Contacts and Deals migrate to Twenty Task and Event records. We preserve activity type, timestamp, owner assignment, and the linked record reference. Bulk activity exports from Floww.ai require coordinated manual runs; we batch activity records and write to Twenty in chronological order to preserve timeline fidelity.

Floww.ai Custom Objects with custom properties and cross-object relationships migrate to Twenty CRM Custom Objects. We require a schema map from the customer covering all Custom Object definitions before migration. One-to-many relationships migrate as standard lookup fields on the child object; many-to-many relationships migrate as junction objects in Twenty or as custom link fields depending on Twenty's current schema support for the relationship cardinality.

Floww.ai's non-standard one-to-many and many-to-many relationship cardinalities require pre-migration schema design in Twenty. We request a full schema map from the customer, then pre-create junction objects or custom link fields in Twenty before any Custom Object data is written. Relationship tables are migrated as junction objects where Twenty supports them, or flattened into a custom field on the primary object in simpler destination configurations.

Floww.ai tags used for segmentation migrate as Tag records in Twenty or as a multi-select custom field on the Person or Opportunity depending on the customer's preference and Twenty's current tagging support. We discuss the tagging strategy during scoping and apply the chosen approach across all tagged records.

Floww.ai User accounts map to Twenty CRM WorkspaceMember records. We resolve Floww.ai user email addresses to destination WorkspaceMember records. Any unmapped users are flagged for admin review before the final write pass. Owner assignments on Deals and Activities are updated to reference the resolved WorkspaceMember.