Migrate from Floww.ai to Pipedrive

Floww.ai Contact records map directly to Pipedrive Person. Standard fields (name, email, phone, organization association) migrate 1:1. Custom Contact properties are mapped field-by-field to Pipedrive custom fields. The Contact's primary organization in Floww.ai links to a Pipedrive Organization lookup during import. We run email dedup logic at migration time to flag duplicate Person records before insert.

Floww.ai Lead records map to Pipedrive Lead. Lead status, source, owner, and any scoring properties migrate to the corresponding Pipedrive Lead fields. If the customer's Floww.ai uses Leads primarily for unqualified prospects that flow into a pipeline later, we preserve the original Lead score in a custom field for segmentation in Pipedrive. Pipedrive Lead status values (New, Contacted, Qualified, Unqualified) are reconciled against Floww.ai's lead status definitions during scoping.

Floww.ai Deals map to Pipedrive Deals. Deal value, expected close date, owner assignment, and stage history migrate. Pipedrive's deal status model (open, won, lost) aligns with Floww.ai's deal lifecycle. We map the Floww.ai deal owner email to the Pipedrive user by email match. Lost deal reasons from Floww.ai custom fields migrate to Pipedrive's lost_reason field on Deal.

Floww.ai supports multiple concurrent pipelines, each with its own stage set. Each Floww.ai pipeline maps to a Pipedrive Pipeline. We extract the live pipeline definitions including stage names, stage order, and probability percentages, and create matching Pipedrive Pipelines before any Deal records are imported. Pipedrive allows multiple active pipelines, which mirrors Floww.ai's architecture.

Floww.ai stage definitions (names, order, probabilities) per pipeline are extracted and mapped to Pipedrive stage entries within each corresponding Pipeline. Stage count varies per pipeline in Floww.ai (4 to 12 stages), and Pipedrive's unlimited stage model accommodates any count. Stage probabilities migrate as Pipedrive's probability percentages. Any stage without a direct Pipedrive equivalent is mapped to the nearest Pipedrive stage and flagged in the configuration inventory.

Floww.ai's company association on Contact records maps to Pipedrive Organization. Organization name, domain, address, phone, and industry fields migrate 1:1. We resolve the Organization lookup reference at Contact import time. Floww.ai organizations without linked Contacts are migrated as standalone Organization records.

Floww.ai Activities (calls, emails, meetings, notes) and Tasks map to Pipedrive Activity records with the corresponding activity_type (call, email, meeting, note, task). We preserve the original timestamp, owner assignment, and linked Person/Deal reference. Activity type, duration for calls, and disposition notes transfer to custom Pipedrive activity fields. Bulk activity exports from Floww.ai require multiple filtered CSV runs and are merged before Pipedrive import.

Floww.ai Custom Objects with their custom properties and cross-object relationships migrate to Pipedrive Custom Objects (available on Essential plan and above) or are flattened into custom fields on the relevant standard object (Person, Organization, Deal) depending on the customer's Pipedrive plan tier and the relationship cardinality. Many-to-many relationships between Custom Objects are migrated as label-based relationship fields on the primary object or as a junction custom object in Pipedrive. We request a schema map from the customer before migration and pre-create the destination schema.

Floww.ai user accounts map to Pipedrive users by email address match. We extract every distinct owner referenced on Contact, Lead, Deal, and Activity records and match by email against the Pipedrive destination. Unmatched owners are flagged for the customer's admin to provision in Pipedrive before the record migration phase begins. Inactive Floww.ai users are mapped to inactive Pipedrive users to preserve assignment history.

Floww.ai tags used for segmentation migrate as Pipedrive Labels on the relevant record type (Person, Organization, or Deal). Tag names are preserved verbatim. If the customer uses tags across multiple record types, we apply them to the equivalent record types in Pipedrive and document the cross-type usage in the configuration inventory.

Floww.ai Flows (workflow automation engine) are tightly coupled to the platform's runtime triggers and are not exportable as data. We do not migrate Flows. We document every active Flow by name, trigger type, conditions, and actions, and map each to a recommended Pipedrive Automation equivalent. The customer's admin rebuilds Flows in Pipedrive's Automation rules builder post-migration.