Migrate from Sanoflow to Odoo CRM

Sanoflow Contact records map to Odoo res.partner. The contact's name, phone, email, and custom field values migrate directly. Sanoflow does not have a separate Account/Company object — contacts store company affiliation as a text field or custom field. We create res.partner records for each company name encountered in contacts and link individual contacts as children of the parent partner record using partner_id. Owner assignment (hubspot_owner equivalent) maps to Odoo user_id on res.partner.

Sanoflow Enquiry records map to Odoo crm.lead. The enquiry body, source channel, status, and assigned agent migrate. Enquiry custom fields map to crm.lead custom fields created in Odoo Studio before migration. The Sanoflow channel source (WhatsApp, Instagram, Messenger, TikTok) is preserved as a tag on the crm.lead for reporting. Enquiry Forms submitted with no existing Contact create crm.lead records with the contact_name field populated from the form submission.

Sanoflow Pipelines map to Odoo stage sequences within crm.lead. Each Sanoflow Pipeline name becomes an Odoo Sales Team (crm.team) with its own stage sequence. Stage order and names migrate 1:1. Stage-specific automation rules (Sanoflow stage-entry triggers) are flagged in the Workflow Specification Document for manual rebuild in Odoo automated actions or Studio.

Sanoflow pipeline stages map directly to Odoo crm.stage records. Stage names, sequence order, and is_won/is_lost flags migrate. Probability percentages from Sanoflow map to Odoo stage on_change_mapping probability values. Stage-specific assignees and routing rules are documented in the Workflow Specification Document.

Sanoflow Channels (WhatsApp, Instagram, Messenger, TikTok) cannot be migrated as live channel credentials — WhatsApp Business API tokens are destination-specific and tied to the Sanoflow Meta Business account. We document each active Channel name and type as a crm.tag with tag_name prefixed by 'channel_' (e.g., channel_whatsapp, channel_instagram) so the customer can filter lead sources by channel in Odoo reporting. Channel reconnection happens post-migration in Odoo WhatsApp integration settings.

Sanoflow Custom Fields on Contacts (text, number, date, choice) at Growth tier and above migrate to Odoo custom fields on res.partner created via Odoo Studio before migration. Choice-field options map to selection fields or many2one relations depending on option count. Field labels and help text are preserved. We verify field types are compatible with Odoo's allowed field types before migration.

Sanoflow Custom Fields on Enquiries migrate to Odoo custom fields on crm.lead. Date and datetime fields are validated against Odoo's datetime format before import. Choice fields with more than 40 options are mapped to many2one relations to avoid Odoo's selection field length limits.

Sanoflow Flows have no documented export endpoint. We cannot migrate Flows as code. We extract Flow metadata during scoping — name, trigger type, step count, and action types — and document every Flow in a Workflow Specification Document. The customer rebuilds flows in Odoo Automated Actions (triggered on crm.lead write/create), Server Actions, or Odoo Studio. Flow rebuild is outside migration scope and is handled by the customer's admin or an Odoo implementation partner.

Sanoflow Teams and role assignments migrate to Odoo crm.team records. Team members map to crm.team member records linked to Odoo res.users. Sanoflow role names are preserved as tags on crm.team for reference. Permission granularity differences between Sanoflow and Odoo are documented — Sanoflow's per-Enquiry visibility rules may require simplification in Odoo based on the customer's chosen security model (record rules per team vs. global access).

Sanoflow Enquiry Forms cannot migrate as live web forms because they are tied to Sanoflow's frontend infrastructure. We document form field definitions, routing rules (which Flow a submission triggers), and field-to-Enquiry field mappings in a Form Specification Document. The customer rebuilds forms in Odoo's Website Form Builder or as custom website controllers. Form routing rules become Odoo Automated Action triggers on crm.lead creation.

WhatsApp campaign records (audience segments, message template content, send history metadata) migrate as documentation. Actual WhatsApp message template content is preserved in a text inventory for re-submission to Meta. The template approval status does not carry over — Meta requires fresh template approval in the new WhatsApp Business account. Odoo WhatsApp integration uses mail.template with wa.template model; we document the target template structure so the customer's admin creates the replacement templates post-migration.

Sanoflow Webhooks are Premium and Enterprise tier only and point to Sanoflow-specific destination URLs. Webhook endpoints cannot transfer between platforms. We document active webhook configurations (URL, event triggers, payload structure) in the Integration Specification Document. The customer recreates webhook endpoints in Odoo's Webhook module (Enterprise) or via custom ir.model.records with the out.wa webhook model.

Sanoflow Owners (agents assigned to Enquiries) map to Odoo res.users by email match. Any Sanoflow Owner without a matching Odoo User goes to a reconciliation queue. The customer's Odoo admin provisions missing users before record import begins. Owner-less Sanoflow records (unassigned Enquiries) are held in a default Odoo team for manual reassignment post-migration.