Migrate from Dolibarr ERP to Odoo ERP

Dolibarr's llx_societe and llx_socpeople tables hold Third Parties, Contacts, Customers, and Suppliers as variants of the same entity distinguished by the client/prospect/fournisseur type flags. We map these to Odoo res.partner records with the is_company flag set true for company records and false for individual contacts. Supplier flag maps to Odoo's supplier flag on res.partner. The customer's address fields (street, zip, city, country) map directly to Odoo's address fields; country maps via the res.country lookup by ISO code.

Dolibarr products (type=0) and services (type=1) map to Odoo product.product variants under a product.template. The Dolibarr sell price, buy price, and VAT rate map to Odoo's list_price, standard_price, and taxes respectively. Product code (ref) maps to Odoo's default_code for SKU matching. Stock quantities in llx_product_stock map to Odoo quants on the product's default warehouse location.

Dolibarr Proposals map to Odoo sale.order records with the state field transformed: draft to draft, validated to sent, signed to sale, refused to cancel. The proposal date maps to Odoo's date_order, and the validUntil date maps to Odoo's validity_date. Proposal lines referencing llx_proposaldet map to sale.order.line with product_id resolved from the product mapping and discount preserved.

Dolibarr Customer Orders map to Odoo sale.order with state mapping: draft to draft, validated to sent, approved to sale, cancelled to cancel. Order lines (llx_commandedet) map to sale.order.line with product, quantity, unit price, and discount preserved. If the Dolibarr instance uses custom order references containing filesystem-unsafe characters, we sanitize these to Odoo's compatible naming convention before import.

Dolibarr Invoices map to Odoo account.move with type=out_invoice. State mapping: draft to draft, validated to posted, cancelled to cancel. Invoice lines (llx_facturedet) map to account.move.line with product_id, quantity, price_unit, and discount preserved. Payment records in llx_paiement and llx_paiement_facture map to Odoo account.payment linked to the account.move via reconcile. We preserve partial payment states for invoices with multiple payments.

Dolibarr Projects map to Odoo project.project with the project name, description, and status preserved. Tasks in llx_projet_task map to Odoo project.task records linked to the parent project. Task assignees from llx_projet_task_time map as Odoo timesheet entries if the Odoo Timesheets app is installed, or as task description notes if not. We flag any task dependencies stored in Dolibarr's task table for manual Odoo planning configuration.

Dolibarr bank accounts (llx_bank) and their transaction rows map to Odoo account.journal with type=bank and the linked account.account for the bank balance. Each transaction in llx_bank maps to account.bank.statement.line. Dolibarr's reconciliation flags (reconciled column) map to Odoo's statement line reconciled state. We note that Dolibarr's payment-to-invoice links (llx_paiement_facture) are already resolved in the Invoice mapping above.

Dolibarr stock movements map to Odoo stock.move records within the stock.picking context. Warehouse locations from llx_entrepot map to Odoo stock.location records. Current stock levels in llx_product_stock map to stock.quant records. Movement types (source vs destination) map to Odoo's stock.location type classification (internal, transit, supplier, customer). We preserve movement dates for audit traceability.

Dolibarr user accounts map to Odoo res.users by email match. We extract user metadata including name, email, and active status. Password hashes (bcrypt-salted) do not transfer; we flag all migrated users for password reset at Odoo destination. Active status maps directly to Odoo's active flag. The Odoo administrator provisions the migration user's access rights separately before migration begins.

Dolibarr's extrafields system stores custom field definitions and values as JSON in the extraoptions column on the parent table. We deserialize each object's extraoptions JSON during the transform phase, extract named key-value pairs, and create corresponding custom fields on the Odoo destination model using ir.model.fields before writing values. Field-type mismatches (e.g., file paths stored as text in Dolibarr extraoptions) are flagged for the customer's Odoo administrator to resolve as attachments or links post-migration. This step requires the most manual review of any mapping object.