Migrate from Flectra to Odoo ERP

Flectra and Odoo share the same res.partner model for individual contacts. The name, email, phone, street, city, country_id, and parent_id fields map 1:1. The is_company boolean distinguishes companies from individuals. We resolve the parent_id lookup (linking a contact to its company) before inserting child contact records so that the Many2one constraint is satisfied at ORM insert time rather than causing a foreign-key violation.

Companies are a subtype of res.partner flagged by is_company = True. The website, vat, street, city, country_id, and email fields map directly. The child_ids relation linking individual contacts to their parent company migrates after the company records are inserted. Flectra's industry codes and category_id (tags) map to Odoo's same fields using the same ir.model.data external IDs where possible.

Flectra's sale.order and sale.order.line map directly to Odoo equivalents with identical field names for order reference, partner_id, date_order, state, and currency_id. The order line product_id, product_uom_qty, price_unit, and discount transfer directly. We sequence sale.order inserts before sale.order.line inserts so that the order_id Many2one constraint is satisfied upfront.

Flectra account.move records with move_type='out_invoice' map to Odoo account.move of the same type. Flectra's invoice_date, partner_id, invoice_line_ids, amount_total, and payment_state transfer directly. We explicitly map Flectra's payment_state values (state_posted, state_pending) to Odoo's payment_state enumeration during the transform phase. Journal ID resolution is required since Odoo journals are organisation-specific.

Both Flectra and Odoo use product.template as the product master record with name, type (service vs consumble vs stockable), list_price, standard_price, categ_id, and taxes fields. The template-level fields migrate first. We preserve the product.template-to-product.product variant relationship by extracting the variant attribute values from Flectra's product.attribute.line and creating matching product.attribute and product.attribute.value records in Odoo before variant creation.

Flectra's product.product records (stock-keeping variants) map directly to Odoo product.product. The product_tmpl_id links each variant to its template. We insert variants after template creation and before any stock valuation or BOM records are migrated, ensuring the product_tmpl_id Many2one is resolvable at insert time.

Flectra purchase.order and purchase.order.line map to Odoo equivalents with the same field names for vendor (partner_id), order date, state, and line-level product_uom_qty and price_unit. Flectra's receipt status flags are mapped to Odoo's picking_ids state values. We insert purchase orders before the related incoming pickings are created so that the picking_ids relation resolves correctly.

Flectra project.project maps directly to Odoo project.project with name, partner_id, active, and privacy_visibility fields. We insert project records before task migration so that the project_id Many2one on project.task is satisfied. Flectra's analytic_account_id maps to Odoo's analytic_distribution field on projects with analytic plans migrated in parallel.

Flectra project.task migrates to Odoo project.task with stage_id, user_id (assignee), planned_hours, effective_hours, date_deadline, and priority preserved. Sub-tasks are nested via the parent_id relation, which requires parent task insertion to precede child task insertion. We sequence parent tasks first, then child tasks, then grandchildren, to satisfy the recursive Many2one chain.

Flectra hr.employee maps to Odoo hr.employee with department_id, job_id, work_email, work_phone, and bank_account_id fields preserved. We insert departments and job positions before employees so that the Many2one foreign keys resolve at insert time. Salary and payroll history residing in Flectra's payroll module (typically Odoo Enterprise on the source) is not migrated because it requires a separate payroll configuration on the destination Odoo instance.