Migrate from Flectra to Dolibarr ERP

Flectra res.partner records with is_company=True map to Dolibarr llx_societe (third-party/company). We extract name, email, phone, website, vat, and address fields (street, street2, zip, town, fk_state, fk_country) and write them to the llx_societe table. The supplier and customer flags (supplier, client) map from Flectra's supplier and customer boolean fields. Parent-company relationships in Flectra (parent_id pointing to another is_company partner) map to Dolibarr's fk_societe_parent field.

Flectra res.partner records with is_company=False are individual contacts and map to Dolibarr llx_socpeople entries. Each contact is linked to its parent company (llx_societe) via fk_soc. We extract firstname, lastname, email, phone, mobile, function (job title), and address fields. Flectra's child_ids relation (multiple contacts under one company) becomes individual llx_socpeople rows in Dolibarr, each pointing to the same llx_societe.

Flectra sale.order maps to Dolibarr llx_commande (customer order). We transfer ref (order reference), date_creation (order date), date_valid (validation date), fk_soc (customer link), fk_user_author (salesperson), and the total amounts (total_ht, total_tva, total_ttc). Order status (state field: draft, sent, sale, done, cancel) maps to Dolibarr's fk_statut and statut fields with the appropriate integer code mapping.

Flectra sale.order.line records map to Dolibarr llx_commandedet order lines. We resolve the product reference to Dolibarr fk_product, copy qty and UnitPrice, and calculate the total (total_ht, total_tva) for each line. If Flectra uses a free-text line without a linked product, we write a Dolibarr desc (description) line with no fk_product link.

Flectra's two-level product model (product.template as the master, product.product as variants) requires expansion into Dolibarr's flatter product structure. Each Flectra product.template with active variants becomes a Dolibarr product with attribute rows created for each variant dimension (size, color, etc.). Variant-level pricing in Flectra (product.product UnitPrice overrides) becomes Dolibarr extra prices on the product record. Templates with no variants migrate as a single product record.

Flectra product.product records with a non-zero qty_available or non-default UnitPrice map to Dolibarr price_extra rows linked to the parent product. The variant's attribute_value_ids become Dolibarr product_attribute_value links. Stock levels from Flectra's stock.quant table map to Dolibarr's llx_product_stock entries per warehouse (fk_entrepot).

Flectra account.move with move_type='out_invoice' maps to Dolibarr llx_facture. We transfer move_id (external reference), ref (invoice number), invoice_date, date_valid, fk_soc (customer), fk_user_author, and financial amounts (total_ht, total_tva, total_ttc). The payment state (paid, unpaid, partial) maps to Dolibarr's fk_paiement and paye (0=unpaid, 1=paid) fields. Historical payment records from account.payment migrate as llx_paiement with line links to the invoice.

Flectra invoice line items map to Dolibarr llx_facturedet. We resolve fk_product (or write a free-text description line), copy qty and UnitPrice, and compute line totals (total_ht, tva_tx for VAT rate). Tax codes from Flectra's account.tax map to Dolibarr's fk_tva rate lookup. Flectra analytic account tags (analytic_distribution) map to Dolibarr llx_facture_fourn_det where applicable.

Flectra purchase.order maps to Dolibarr llx_commande_fournisseur (supplier order). We transfer the order reference, date, supplier link (fk_soc), salesperson, and amounts (total_ht, total_tva, total_ttc). Order status maps to Dolibarr's fk_statut. Flectra's picking_ids relation for receipt tracking maps to Dolibarr's llx_reception if the receiving warehouse module is active.

Flectra purchase.order.line records map to Dolibarr llx_commande_fournisseurdet supplier order lines. We resolve the supplier product reference to Dolibarr fk_product, copy qty and UnitPrice, and calculate line totals. Discounts (% discount field) migrate to Dolibarr's remise_percent field.

Flectra project.project maps to Dolibarr llx_projet. We transfer ref (project code), title (project name), description, date_start, date_end, fk_user_resp (project manager), and the fk_soc link if the project is associated with a customer. Project status (state: open, pending, close) maps to Dolibarr's fk_statut.

Flectra project.task records map to Dolibarr llx_projet_task. We transfer ref, title, description, planned_hours, effective_hours, date_start, date_end, user_id (assignee), stage_id (task stage), and fk_projet (parent project). Flectra's child_ids sub-task hierarchy becomes a flat task list in Dolibarr with fk_task_parent links for nesting. Task priority (1-5) maps to Dolibarr's priority field.

Flectra hr.employee records map to Dolibarr llx_societe entries with type='contact' plus llx_resource records for resource management. Employee name, work_email, mobile, department_id (fk_department), and job_id map to the contact record. Dolibarr's llx_resource table holds the resource definition (resource_type, fk_user) for project allocation and attendance tracking if the HR module is active. Note that Flectra payroll and salary history resides in external payroll modules and is not part of the standard migration scope.

Flectra ir.attachment binary files export as base64-encoded content and are written to Dolibarr's documents directory using the object's module path convention (e.g., commercant/projet/task_123.pdf). We preserve the original filename and create a Dolibarr llx_extrafields record with a reference back to the owning object (fk_object and object_type). The res_model and res_id from Flectra determine the Dolibarr object type and ID for the attachment link.

Flectra custom fields (x_ prefixed fields defined in ir.model.fields with state='manual') are enumerated during discovery and mapped to Dolibarr llx_extrafields table rows for the corresponding object. We create the extrafield definition (column name, label, type, and SQL column addition) before data load. The custom field value data migrates as part of the parent object write. If a custom field references another Flectra record via a many2one relation, we resolve the target ID through the migration's ID cross-reference map before writing.