Migrate from Fat Free CRM to Odoo CRM

Fat Free CRM contacts map to Odoo res.partner records where company_type = 'person'. The email, phone, job title, address, and website fields translate directly. The contact's primary company (account_id) becomes the parent partner_id in Odoo. If a contact has no company in Fat Free CRM, we create a stub partner record and flag it for Odoo admin review.

Fat Free CRM accounts map to Odoo res.partner where company_type = 'company'. The name, website, phone, industry, employee count, and annual revenue fields map to Odoo partner fields. Revenue and employee count have no native Odoo partner fields — we create x_annual_revenue and x_number_of_employees as ir.model.fields before import.

Fat Free CRM opportunities map directly to Odoo crm.lead records. The opportunity name becomes the lead subject (name field), amount maps to planned_revenue, and the close date maps to date_deadline. The assigned user resolves by email match to Odoo internal users. Stage mapping requires value-by-value translation from Fat Free stage strings to Odoo crm.stage record IDs.

Fat Free CRM pipelines have no direct Odoo equivalent. In Odoo, each sales team (crm.team) owns a set of crm.stage records. We create a crm.team for each Fat Free CRM pipeline and configure stage records with sequence order and fold/name matching the source stage strings. Probability values map per stage name.

Stage name strings from Fat Free CRM map to Odoo crm.stage name values. Each stage requires probability and sequence number configuration in Odoo. Stages with the same name across multiple Fat Free pipelines collapse to a single Odoo stage name per team unless you request separate pipelines per team in Odoo.

Fat Free CRM tasks map to Odoo mail.activity records attached to the parent res.partner or crm.lead. The task name becomes the activity summary, due date maps to date_deadline, and priority (low/medium/high) maps to Odoo's activity_type + priority fields. The assigned user resolves by email match.

Fat Free CRM notes map to Odoo mail.message records with message_type = 'comment' and subtype = 'note.mt_note'. The note body populates the message body field. We preserve the original created date as write_date on the Odoo message record. Messages attach to the parent res.partner or crm.lead using the res_id + model references.

Fat Free CRM campaigns map to Odoo crm.team records, since Odoo does not have a standalone campaign entity in the CRM module. Team name and description carry over. If the campaign tracks UTM data, those fields migrate as custom fields on the crm.lead.

Fat Free CRM groups map to Odoo res.groups. We preserve the group name and transfer user membership by matching user emails. Group descriptions are migrated as the res.groups description field when present. If your Fat Free groups are used for record-level access control, Odoo record rules will need manual tuning post-migration. In Odoo, the default group 'User' is created automatically; custom groups from Fat Free are added alongside it.

Fat Free CRM tags on contacts and accounts map to Odoo res.partner.category (contact category/tag). Tag names map directly, preserving spelling and capitalization. If a tag already exists in Odoo, we reuse the existing category instead of creating a duplicate. Multi-tag membership on a contact creates multiple category entries on the res.partner record. Any tag color data is stored as a custom char field if needed.

Fat Free CRM custom fields on contacts require Odoo ir.model.fields entries on res.partner. Field type translation: string fields map to char, number fields to float or integer, date fields to date, multi-select to char (comma-separated string). We create the custom field in Odoo first, then populate it during the partner import.

Fat Free CRM custom fields on opportunities migrate as Odoo ir.model.fields on crm.lead. Same type-translation logic applies. Odoo reserves field names starting with x_; we prefix all migrated custom field names with x_fcfm_ to avoid conflicts with reserved internal names.