Migrate your Floww.ai data

Contacts are the primary record object in Floww.ai. We migrate them 1:1 with standard fields (name, email, phone, company association) preserved. Custom Contact properties are mapped field-by-field against the destination schema.

Leads are distinct from Contacts in Floww.ai's data model and support separate categorization features. We preserve the Lead record alongside its activity history and assign it to the correct pipeline stage in the destination.

Deals in Floww.ai are tied to a specific Pipeline and Stage. We extract the full deal record including deal value, owner assignment, expected close date, and the stage history timeline.

Floww.ai supports multiple concurrent pipelines with distinct stage sets. We map each pipeline to the destination CRM's pipeline object, but the stage order and naming conventions must be reconciled manually per pipeline during scoping.

Stage names and counts vary per pipeline in Floww.ai. Some teams have 4 stages, others have 12. We extract the live stage definitions and map them to the destination's stage schema, flagging any stage-level custom fields for explicit review.

Activities include calls, emails, notes, and scheduled tasks logged against Contacts and Deals. We preserve the activity type, timestamp, owner, and linked record reference. Bulk activity exports require pagination across the platform's internal query interface.

Floww.ai allows teams to define Custom Objects with custom properties and cross-object relationships. We migrate Custom Object records but require a schema map from the customer before writing to the destination, since relationship cardinalities differ across platforms.

Floww.ai's workflow automation engine (Flows) is tightly coupled to its runtime and trigger logic. We do not migrate Flows as executable objects. We document which workflows were active and provide a human-readable specification for rebuilding them in the destination.

Dashboards are rendered from live queries against the platform's data store and are not exportable as data. We do not migrate Analytics objects. The underlying data (Deals, Activities, Contacts) is migrated so reports can be rebuilt in the destination.

Attachments linked to Contacts, Deals, and Activities are exported via the platform's file export utility where available. Call recordings require a separate export workflow and may need manual retrieval if the platform's recording storage is not accessible via bulk export.

Floww.ai supports tagging records for segmentation. Tags are migrated as label or tag fields against the relevant record. We preserve tag names and apply them to the corresponding Contact or Deal in the destination.

User accounts map to Owners in the destination CRM. We match Floww.ai user email addresses to destination user records. Any unmapped users are flagged for admin review before the final write pass.