Migrate from Flavor CRM to Odoo CRM

Flavor CRM Leads map directly to Odoo CRM Leads (crm.lead model). We export all Lead fields including source, status, and custom properties, then map them to Odoo lead fields (name, contact_name, email_from, phone, description, priority, tag_ids). Flavor CRM's custom lead properties map to Odoo custom fields on the crm.lead model, which we create via the Odoo interface (Settings > Technical > Custom Fields) before migration. Unconverted Leads migrate as crm.lead records; any Leads already converted to Students are handled in the Student mapping step.

Flavor CRM Students map to Odoo Contacts (res.partner with type='contact'). The Flavor CRM student_id becomes a custom field flavor_student_id__c on the res.partner record to preserve the original identifier for reporting and audit. We extract enrollment history, enrollment dates, and program affiliation from Flavor CRM and map them to custom Contact fields or tags in Odoo. If the Student has a linked Parent record, we create a related Contact in Odoo and link it via the Odoo Contact's Parent field (parent_id on res.partner). Student ownership (assigned staff member) maps to Odoo's user_id on the record if using Odoo's CRM team assignments.

Flavor CRM Parent records are separate objects linked to Students. We export Parent records and map each to an Odoo Contact with parent_id set to the related Student contact (the Child link on res.partner). Odoo's Contact model natively supports Parent-Child relationships for individuals. Parent contact information (name, email, phone, address) maps to the standard res.partner fields. If a Parent in Flavor CRM is linked to multiple Students, we create a single Contact in Odoo and attach it as a parent link to each related Student contact record.

Flavor CRM Class records have no direct Odoo equivalent. We map Classes to Odoo Project (project.project) as a configuration mapping, with custom fields added to capture enrollment capacity, class schedule (days and times), location, instructor (linked via res.partner), and program. The project.project model supports tasks (project.task) which we use to represent Class Sessions or enrollment slots. If Odoo Project is not licensed, we create a custom ir.model object named x_class with the equivalent fields. The customer confirms the preferred approach during scoping.

Flavor CRM enrollment records (which Student is enrolled in which Class, with enrollment date and status) map to Odoo Project Tasks under the corresponding Class project. The task name references the Student (linked via res.partner), and custom fields capture enrollment status, enrollment date, completion date, and grade or outcome. Task stage in Odoo maps to enrollment status in Flavor CRM (active, completed, dropped, waitlisted).

Flavor CRM Opportunities map to Odoo CRM Leads in the Won stage. The opportunity name, amount, stage, expected close date, owner, and create date migrate directly. Odoo's CRM pipeline uses crm.lead records with stage_id controlling the pipeline position; lost opportunities are recorded with a Lost stage. We map Flavor CRM pipeline stages to Odoo stage names during schema configuration. Note that Odoo does not have a separate Opportunity object separate from crm.lead; the same model serves both inbound leads and opportunities.

Flavor CRM Contracts (enrollment agreements, service contracts) map to Odoo Sale Orders (sale.order) if the customer licenses Odoo Sales or Subscription apps. Contract terms, dates, and related Student or Parent links migrate to sale.order fields. The contract PDF and any signed documents migrate as Odoo Attachments linked to the sale.order. If Odoo Sales is not licensed, we create a custom object to hold the contract record with its terms and linked contact.

Flavor CRM Invoices are financial documents that require a decision about destination. If Odoo Accounting (account.account) is licensed, we migrate Invoice records as Odoo Account Moves (account.move with type='out_invoice') linked to the related Contact (Student or Parent). Invoice line items, amounts, payment status, and due dates migrate to the corresponding account.move fields. If Odoo Accounting is not licensed, we flag Invoice records for mapping to a separate accounting system via integration (QuickBooks, Xero, or the customer's preferred tool) and deliver them as tagged Custom Objects with the full invoice data in a JSON blob for later import.

Flavor CRM Activities (calls, emails, meetings, tasks, notes) map to Odoo's mail.activity and mail.message records. Call activities map to mail.activity with activity_type_id set to the Call activity type; meeting activities map with the Calendar event activity type. Notes in Flavor CRM map to mail.message records of type='comment' linked to the parent Contact or Lead. Odoo stores email history in the mail.message table linked to the relevant partner (contact). Activity dates, subjects, and descriptions migrate directly; activity owners map to Odoo Users by email resolution.

Flavor CRM Staff records map to Odoo User accounts (res.users). We export Staff records including name, email, role, and permissions level. During migration, we match Staff email addresses to existing Odoo Users in the destination instance. If a Staff record has no matching User, we add it to a reconciliation queue for the customer's Odoo admin to provision the User account before Contact ownership is assigned. Staff without active user access in Odoo may be migrated as Contacts instead, with a staff designation tag.

Flavor CRM's Lead-to-Student conversion creates a permanent reference link that is not preserved in standard exports. We extract the conversion timestamp, original lead_id, and converted student_id from Flavor CRM and write them as custom fields on the resulting Odoo Contact (flavor_lead_id__c, flavor_conversion_date__c, flavor_converted_from_lead__c boolean). This preserves the enrollment funnel historical record that schools use for conversion rate reporting. This mapping requires explicit scoping because it affects how the customer rebuilds pipeline analytics in Odoo.

Flavor CRM does not expose a documented bulk export endpoint for binary files. Media transaction reports export as CSV or Excel, but actual file attachments (enrollment documents, contracts, images) require individual manual downloads or a scripted browser-based extraction. We flag this as a limitation and deliver a written inventory of every attachment record (file name, record type, URL if available) so the customer's team can manually download or use a custom script to extract them for Odoo ir.attachment import.