Migrate from Floww.ai to Odoo CRM

Floww.ai Contact records map directly to Odoo CRM Lead. Standard fields (name, email, phone, company name, address) migrate with Odoo field equivalents (partner_name, email_from, phone, contact_name). We apply an email deduplication step because Floww.ai Contacts may share email addresses across multiple records; the first record wins and subsequent duplicates are flagged for admin review. Floww.ai contact custom properties migrate as Odoo custom fields on crm.lead.

Floww.ai Lead records (distinct from Contacts in Floww.ai's data model) map to Odoo CRM Lead. The Lead record, its categorization features, activity history, and pipeline assignment migrate as a single Lead record in Odoo. Floww.ai Lead custom properties migrate as Odoo custom fields on crm.lead. We preserve the Floww.ai lead owner as an Odoo user reference resolved by email match.

Floww.ai Deals map to Odoo CRM Opportunity (crm.lead with type='opportunity'). The Deal value, expected close date, owner assignment, and linked Contact or Lead reference migrate. We resolve the Contact reference by email match against the migrated Lead records. The Floww.ai pipeline assignment maps to an Odoo CRM stage within the configured pipeline, and the Deal stage history (if exported) migrates as Odoo log notes with timestamps preserving the original progression order.

Each Floww.ai Pipeline becomes an Odoo CRM Pipeline (crm.team) with its own stage set. We create Odoo CRM stages that mirror the Floww.ai stage names and sequence order. Stage probability percentages from Floww.ai migrate to Odoo stage probability values. Teams that had 4-stage pipelines in Floww.ai get 4 Odoo stages; teams with 12-stage pipelines get 12 Odoo stages. The mapping is stored in the migration configuration file for reconciliation at cutover.

Floww.ai stage names and per-stage filter definitions are extracted during scoping. We configure Odoo CRM stages with the same sequence order as Floww.ai. Stage-level filters from Floww.ai cannot be exported programmatically and do not carry over; we document which filters were active per stage so the customer's admin can rebuild them in Odoo using domain filters on the Pipeline or Team model.

Floww.ai call activities map to Odoo CRM phonecall records (crm.activity with activity_type_id set to Phone Call). Call duration, disposition, owner, and timestamp migrate to Odoo activity fields. The linked Contact or Deal reference resolves to the migrated Odoo Lead or Opportunity via email match and record ID lookup. Activity ordering is preserved by setting the Odoo activity date to the original Floww.ai timestamp.

Floww.ai email activities map to Odoo CRM email records (crm.activity with activity_type_id set to Email). Subject, body, direction (inbound/outbound), and timestamp migrate. The linked Contact or Deal reference resolves to the migrated Odoo Lead or Opportunity. Email attachments migrate as Odoo ir.attachment records linked to the activity.

Floww.ai meeting activities map to Odoo CRM meeting records (calendar.event). Start datetime, duration, location, and meeting subject migrate. Attendee information from Floww.ai migrates as Odoo calendar.event attendee records linked to the Odoo user or contact equivalent. Meeting notes and description migrate to the Odoo event description field.

Floww.ai task activities map to Odoo CRM activity records with the default activity type. Task title, description, due date, owner, and completion status migrate. The linked Contact or Deal reference resolves to the migrated Odoo Lead or Opportunity. Completed status maps to Odoo's 'Done' activity state.

Floww.ai Custom Objects with one-to-many and many-to-many relationships require Odoo custom model creation via Odoo Studio or Python module definition. We request the Floww.ai schema map from the customer during scoping, then define equivalent Odoo models with matching field names and types before data insert. Many-to-many relationship tables from Floww.ai become Odoo relational fields (many2many) on the appropriate custom model. This step requires an Odoo developer or advanced admin to register the new model in the Odoo database before migration write begins.

Floww.ai tags applied to Contacts, Leads, and Deals migrate as Odoo CRM tags (crm.tag). Tag names are preserved exactly and applied to the corresponding Lead or Opportunity records in Odoo. If Floww.ai used tags for segmentation logic beyond simple labeling, we document the segmentation strategy separately for admin review during Odoo CRM tag-group rebuild.

Floww.ai user accounts map to Odoo User records. We match Floww.ai user email addresses to existing Odoo User records by email. Any Floww.ai Owner without a matching Odoo User goes to a reconciliation queue for the customer's Odoo admin to provision before the final write pass. Owner assignment on Lead and Opportunity records resolves to the Odoo User id.