Migrate from Sales Flow Technologies to Odoo CRM

Sales Flow Contacts map to Odoo CRM Lead for unqualified prospects and Contact (attached to a Company/Partner) for qualified contacts. We use the Sales Flow Contact's Prospect List membership and any sequence enrollment status to determine qualification: Contacts enrolled in at least one Sequence map to Odoo Lead for re-qualification in the new system; Contacts with confirmed meeting or reply engagements map to Odoo Contact under a Partner record. Custom fields (LinkedIn URL, role, company) migrate to custom fields on both Lead and Partner.

Sales Flow Contact company records map to Odoo res.partner records of type company. The company domain becomes the partner Website field. Parent-company and subsidiary relationships in Sales Flow export become contact hierarchy in Odoo Partner. If Sales Flow exports company revenue or employee count, those become custom fields on the res.partner record.

Sales Flow Prospect Lists are named groupings of Contacts. We export list membership as a dedicated column in the Contact CSV and recreate each list as an Odoo Tag (fleet_management.tag model used for CRM tagging). Tags attach to both Lead and Partner records, preserving the list membership context for segmentation and campaign targeting. Customers choosing Odoo Studio configure dedicated CRM Groups as an alternative to Tags.

Sales Flow Sequences define the cadence and channel steps (LinkedIn connection, follow-up email, InMail) for a group of Contacts. Sequence step ordering and timing data are exported as a structured CSV and reconstructed in Odoo as a Tag-based naming convention (e.g., 'SEQ-Email-FollowUp-Day3') plus a detailed Step Inventory document listing every step, its delay, channel, and template reference. The cadence logic itself cannot be automated in Odoo CRM without a third-party sales engagement integration; the Step Inventory documents the intended cadence for manual or third-party implementation.

Sales Flow Campaigns bundle multiple Sequences under a single objective. Campaign names and associated Sequences migrate as Odoo CRM Team records (odoo crm.team) with a descriptive tag that links back to the original Sales Flow campaign. Reporting date ranges from Sales Flow Campaign migrate as note fields on the CRM Team. Channel routing logic and A/B testing configurations do not transfer and are flagged in the Automation Inventory document.

Sales Flow Workflows define conditional branching logic for prospect responses (e.g., 'if no reply after 3 days, send template B'). The workflow builder configuration is not exposed via CSV or API. We produce a detailed Workflow Migration Summary documenting every conditional rule, step order, and timing for the customer's team to manually reconstruct using Odoo CRM Action Rules (crm.lead.create or crm.lead.assign actions) or Odoo Studio. This is the highest-impact documentation deliverable in this migration.

Sales Flow email engagement history migrates to Odoo mail.message records linked to the parent Lead or Partner. Email subject, body content, and timestamp transfer. Delivery status and open/click tracking data from Sales Flow migrate as custom fields on the mail.message record since Odoo CRM does not natively track email engagement metrics. We merge the standard CSV export with the Advanced Analytics CSV to reconstruct the complete timeline when timestamps are truncated.

LinkedIn connection requests sent through Sales Flow are documented as CRM Lead notes with a structured label (e.g., 'LinkedIn Connection Sent—[date]—[prospect name]'). Connection acceptance status from Sales Flow migrates as a custom boolean field on the Lead or Partner. LinkedIn conversation content lives in LinkedIn's infrastructure and is not accessible via Sales Flow export; we flag this gap and recommend LinkedIn Sales Navigator sync as a post-migration data enrichment step.

Sales Flow call engagement records (call disposition, duration) migrate to Odoo CRM Lead notes with structured labels and a custom call_duration_minutes field. If the Sales Flow export includes call recording URLs, those attach as URL fields on the Lead. Call history is documented as note entries rather than native Odoo call records because Odoo CRM does not have a standalone call log object without Service Cloud or a third-party telephony integration.

Sales Flow meeting engagements (calendar invite, attendee, location) map to Odoo calendar.event records linked to the parent Lead or Partner via event.partner_ids (EventRelation). Meeting outcome notes from Sales Flow migrate as a note on the calendar event. Recurring meeting series in Sales Flow are documented as a separate Meeting Series Inventory with the recurrence pattern for manual rebuild in Odoo Calendar or a third-party scheduling integration.

LinkedIn InMail sent through Sales Flow sequences migrates as Lead notes with a structured label (e.g., 'LinkedIn InMail Sent—[date]'). InMail template reference migrates as a custom field. Response rate data from Sales Flow Analytics migrates as a custom field on the Lead. InMail content is not stored in Sales Flow's infrastructure in a retrievable format beyond the sequence enrollment record.

Sales Flow per-sequence and per-step open rates, reply rates, and connection acceptance rates are exported from the Analytics CSV and migrated as custom fields on the Odoo Lead model (e.g., sf_sequence_open_rate__c, sf_connection_accept_rate__c). These are informational fields—the customer's team uses them for reference but cannot trigger Odoo automations from them without custom development. Odoo's native CRM reporting (Pipeline Analysis, win/loss reporting) does not have equivalents to these outreach-specific metrics.

Sales Flow User accounts (Admin, Standard roles) map to Odoo res.users. We match by email address. Any Sales Flow Owner without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role labels (Admin, Standard) map to Odoo access rights groups (CRM / Sales / Administrator) in Odoo Access Controls.