Migrate from FowCRM to Odoo CRM

FowCRM Accounts map to Odoo res.partner records with partner_rank set to indicate a company entity and type set to 'company'. The FowCRM account_name becomes the partner's name field; industry and employee_count map to industry_id and employee_nbr on res.partner. Account is imported before any Contact records so that the parent relationship is satisfied at the moment of Contact insert via parent_id on res.partner.

FowCRM Contacts map to Odoo res.partner records with type set to 'contact' and parent_id referencing the FowCRM Account's corresponding partner record. Lifecycle stages and contact-specific custom fields migrate to partner fields or custom columns on res.partner. The email and phone from FowCRM become email and phone on res.partner. We resolve the parent_id relationship during a second-pass import after all Accounts are committed.

FowCRM Deals map directly to Odoo crm.lead records. The FowCRM dealstage maps to crm.stage_id via a stage-name lookup within the destination crm.team. Closed-Lost and Closed-Won states from FowCRM map to Odoo's lost and won stage flags. Deal amount becomes planned_revenue on crm.lead; deal name becomes name.

Each FowCRM Pipeline becomes an Odoo crm.team (sales unit) with its own crm.stage sequence. Stage names, ordering, and probability percentages migrate from FowCRM to the Odoo stage definitions. FowCRM's pipeline-to-stage mapping is preserved as a crm.team configuration so that each sales team in Odoo sees only its relevant pipeline stages.

FowCRM Deal stages map to Odoo crm.stage records within the appropriate crm.team. Stage probability percentages migrate to stage sequence order; stage name becomes name. The is_won and is_unclosed flags on Odoo stages are set based on the FowCRM stage being closed-won or closed-lost.

FowCRM Cases (available on Professional and Enterprise plans only) map to Odoo helpdesk.ticket if the helpdesk module is installed, or to crm_case if using the legacy case management within CRM. Case priority and status map to ticket priority and stage_id. Custom case-type fields become custom columns on the destination ticket model. We check the source plan tier during discovery and skip Case export gracefully if the Standard plan is detected, returning a zero-count report rather than a 403 error.

FowCRM custom fields require the two-step Model-then-Field discovery process. We enumerate all Models first, then fetch Field definitions for each, building a complete schema index before attempting any custom field data export. On the Odoo side, custom fields are defined via Odoo Studio or XML data files in the target module. We pre-create the ir.model.fields definitions in a staging database before importing any records with custom field values, ensuring the destination schema is ready before data arrives.

FowCRM call engagements map to Odoo mail.activity records with activity_type_id set to 'call'. Duration, disposition, and call recording URL migrate to custom activity fields. The activity date and deadline are set from the FowCRM call timestamp. Res_user_id is resolved via the Owner mapping to the destination Odoo User.

FowCRM email engagements map to Odoo mail.message records. The email body, subject, and timestamp migrate to mail.message body, subject, and date fields. The message is linked to the destination res.partner (Contact or Account) via res_id and model='res.partner'. Email attachments migrate as ir.attachment records linked to the message.

FowCRM meeting engagements map to Odoo calendar.event records. Start and end datetime, location, and meeting title migrate directly. Attendee mapping links to calendar.attendee records pointing at the res.partner records for the contacts who attended. The linked crm.lead (if the meeting was attached to a Deal) is preserved via the calendar.event's res_id and model='crm.lead'.

FowCRM note engagements map to Odoo note.note records. The note body and creation timestamp migrate to the note content and date. Notes are linked to the parent res.partner or crm.lead via res_id and model references. If the destination Odoo instance uses the discuss module instead, notes migrate as mail.message with message_type='notification'.

FowCRM Owner records (sales reps assigned to Deals, Contacts, and Accounts) map to Odoo res.users by email match. We extract all distinct owner_ids referenced across the migration scope, match against the destination Odoo User list, and hold any unmatched owners in a reconciliation queue. The customer's Odoo admin provisions missing users before the Owner resolution pass runs. Active/inactive status is preserved from FowCRM.

FowCRM Survey definitions and response data are exported as structured JSON. Survey questions map to survey.question records; survey response values map to survey.user_input_line records. Because survey question types and validation rules differ between platforms, we treat survey data as a mapping exercise with a written schema translation document rather than a direct field-level copy. Survey responses reference the res.partner of the respondent when available.

FowCRM integration configurations and webhook subscriptions are not exposed via the public API. These cannot be exported programmatically and must be manually reconfigured in Odoo using Odoo Studio or via the integrations module post-migration. We provide a written inventory of detected webhook endpoints and integration names during discovery for the customer's admin to rebuild.