Migrate from Odoo Enterprise to Dolibarr ERP

Odoo's res.partner holds both individuals and organizations in a single table with the partner_type (contact/company/invoice/delivery) and is_company flags. We split each res.partner into a Dolibarr llx_societe record (when is_company=true) and a linked llx_contact record (always). For Odoo partners where is_company=false, we create only an llx_contact linked to a parent llx_societe. Address fields (street, city, zip, country) migrate to llx_societe_address or llx_contact with address type preserved via llx_coder_compose. The Dolibarr s.rowid maps to Odoo res.partner.id.

Odoo res.company records represent the operating units (branches, subsidiaries) and map to Dolibarr llx_societe records with the company=true flag. Company logo migrates to Dolibarr's /documents/logos/ directory and the logo filename is stored in llx_const.name='MAIN_INFO_SOCIETE_LOGO'. Fiscal address, VAT numbers, and SIREN/SIRET fields migrate to llx_societe and llx_societe_extrafields where the Dolibarr module is activated. Multi-company Odoo setups with separate legal entities produce one llx_societe per Odoo company record.

Odoo product.template holds the product definition (name, description, list_price) and product.product holds variants (size, color, dimension combinations). We flatten these into a single llx_product per product.product variant, with the template name stored in llx_product.description and the variant label in llx_product.label. Product categories from product.category map to llx_categorie with type='product'. For Odoo BoM components (mrp.bom), we create llx_product as type=1 (stockable) and note the bill of materials relationship for Dolibarr's manufacturing module activation or manual rebuild. Units of measure from product_uom migrate to Dolibarr's unit conversion table.

Odoo sale.order records map to Dolibarr llx_commande with state mapped from Odoo state (draft/quotation->DRAFT, sale_order->VALIDATED, done->SHIPPED, cancel->CANCELED). Odoo order lines migrate to llx_commandedet with product reference, quantity, unit price, and tax rate preserved. The Odoo partner_id lookup resolves to the target llx_societe.rowid; the sale_order_id and client_order_ref map to Dolibarr ref_client and ref. Historical sale orders (state=sale_order, picking_ids, invoice_ids) migrate with their lines; Odoo's on-change pricing rules are resolved at migration time and stored as static prices in llx_commandedet.

Odoo purchase.order records map to Dolibarr llx_commande_fournisseur with state mapped from Odoo state (draft/purchase_order->DRAFT, purchase_order->VALIDATED, done->RECEIVED, cancel->CANCELED). Supplier_id resolves to the target llx_societe.rowid by matching Odoo's partner_id with a supplier flag. Order lines migrate to llx_commandedet with product reference, quantity, buy_price (cost price), and tax rate. Receipt matching from stock.picking migrates to Dolibarr's supplier order receipt workflow; incoming shipments with no linked purchase order become Dolibarr supplier orders in CLOSED state.

Odoo account.move records with type in (out_invoice, out_refund) map to Dolibarr llx_facture with type in (invoice, credit_note). Posted invoices migrate with their full line items to llx_facturedet; draft invoices migrate separately with state=DRAFT. Odoo's invoice.line_ids carrying tax_ids resolve to Dolibarr's localtax mechanism (localtax1 or localtax2 depending on the country) which must be pre-configured in Dolibarr before invoice migration. Odoo's account.move.name (invoice number sequence) maps to llx_facture.ref and ref_int. Payment records (account.payment) migrate as Dolibarr llx_paiement linked to the invoice via llx_paiement_facture.

Odoo account.move records with type in (in_invoice, in_refund) map to Dolibarr llx_facture_fournisseur. Supplier_id resolves to the target llx_societe.rowid by matching Odoo's partner_id with a supplier flag. Line items with product_id and purchase_price migrate to llx_facturedet. Vendor bill states (posted, draft) map directly. Odoo's vendor bill number (bill_number) maps to llx_facture_fournisseur.ref and ref_supplier. Bills in Odoo reconciled with account.move.line records via full reconciliation are flagged in Dolibarr's payment matching table for the customer to re-reconcile in Dolibarr's bank reconciliation interface.

Odoo project.project maps to Dolibarr llx_projet with name, description, date_start, and date_end preserved. project.task maps to llx_projet_task with parent_id resolved to the target Dolibarr task rowid for sub-task hierarchies. Odoo stage_id (Kanban pipeline stages) migrates as Dolibarr task status values (TODO, IN PROGRESS, DONE, CANCELLED) that the customer configures in Dolibarr's project module settings before migration. Odoo's project.task.timesheet_ids (hr_timesheet.line) do not have a native Dolibarr equivalent; we export them as read-only records in a separate timesheet migration table for the customer to manually enter or configure a Dolibarr timesheet module. Odoo automated stage actions (ir.actions.server) are not migrated and are listed separately for admin rebuild.

Odoo hr.employee records migrate to Dolibarr llx_societe with type='contact' and a linked llx_adherent record if the Dolibarr member/adhesion module is activated. Employee fields (job_title, work_email, work_phone, department_id) map to the corresponding llx_contact columns. Employment contract dates (contract_id.date_start, date_end) migrate as Dolibarr llx_adherent.date adhesion membership records for HR visibility. Historical payslip data (hr.payslip) does not have a standard Dolibarr equivalent and migrates as a read-only archive file or custom table for the customer's HR team to reference outside the ERP. Odoo's hr.contract model requires Dolibarr's RH/HR module activation or a custom PHP module.

Odoo stock.quant (on-hand inventory by warehouse and location) maps to Dolibarr llx_product_stock with warehouse_id resolved to the target Dolibarr entrepot.rowid. Odoo stock.move records (inventory adjustment, internal transfer, receipt, delivery) migrate to Dolibarr llx_stock_mouvement with product reference, qty (positive for incoming, negative for outgoing), type (INTERNAL, IN, OUT, ADJUST), and warehouse resolved. Lot/serial number traceability from stock.lot migrates to Dolibarr's llx_lot with the product and expiry date. Quant snapshots migrate as the current Dolibarr stock level; full move history migrates as individual llx_stock_mouvement rows for inventory audit trails.

Odoo's Chart of Accounts (account.account) does not migrate directly because Dolibarr ships with a pre-configured country-specific Chart of Accounts that must be activated in Dolibarr before any accounting data moves. We extract Odoo's account.account records and produce a mapping spreadsheet that aligns each Odoo account code and name to the nearest Dolibarr account from the target country's localization. Fiscal positions (account.fiscal.position) mapping taxes and accounts by partner country/VAT migrate to Dolibarr llx_accounting_fiscal_position with the account/src/dest pairs remapped to the Dolibarr Chart of Accounts codes. This step requires the customer's country and tax regime to be confirmed before any accounting migration begins.

Odoo stores file attachments in two locations: the PostgreSQL ir_attachment table (db_datas column for small files) and the /filestore/ directory for large files and PDFs. We extract both, reconstruct the filestore directory tree under Dolibarr's /documents/ structure, and create llx_ecm_files records that link the attachment to the target object (llx_societe for company docs, llx_facture for invoices, llx_project_task for task attachments). The original Odoo attachment res_model and res_id are preserved in Dolibarr's ref and ref_id fields so the attachment can be relinked during post-migration cleanup. Binary file content that exceeds Dolibarr's default size limit triggers a separate migration of the /filestore/ directory as a standalone document archive.