Migrate from Odoo ERP to Dolibarr ERP

Odoo Partner records (type contact vs company) split into Dolibarr ThirdParty (soc: company record) and Dolibarr Contact (socpeople: individual contact record linked by fk_soc). We preserve partner categories as Dolibarr categories and bank details as Dolibarr bank account records. Address fields (street, city, zip, country) map to Dolibarr address fields directly.

Odoo partner categories map to Dolibarr categories with type = Customer or Supplier. Categories are resolved before partner import so that the category reference is satisfied at import time.

Odoo Products map to Dolibarr products (type product or service). Product type (stockable, consumable, service) maps to Dolibarr finished, raw material, or service. List price maps to Sell price; standard cost maps to Cost price. Product variants via attribute combinations flatten to separate Dolibarr product rows if Dolibarr variant handling is not enabled.

Odoo sale.order records map to Dolibarr orders (commande). Order state (draft, sale_order, done, cancel) maps to Dolibarr status (Draft, Validated, On Bill, Billed, Cancelled). Order lines map with product reference, quantity, unit price, and tax resolved from Odoo's fiscal position. We import orders before invoices so that order references are available for invoice linkage.

Odoo account.move records (move_type out_invoice, out_refund) map to Dolibarr invoices and credit notes. Posted invoices are imported as closed records; draft invoices are imported as draft. Odoo's invoice lines map to Dolibarr invoice lines with product, quantity, price, and tax. Fiscal positions that affect tax computation require post-migration configuration in Dolibarr's tax and third-party settings.

Odoo purchase.order records map to Dolibarr supplier orders (commande fournisseur). State mapping follows the same draft-confirm-done lifecycle. Supplier invoice linkage imports as separate Dolibarr invoice records linked to the supplier third-party.

Odoo project.project records map to Dolibarr projects. Project stages map to Dolibarr project status values. Projectued and effective dates transfer directly. Project-linked tasks import as Dolibarr tasks in a second pass using project ID lookups resolved at migration time.

Odoo project.task records map to Dolibarr tasks linked to the corresponding project. Sub-tasks (parent_id hierarchy) map as tasks with a parent task reference where Dolibarr's hierarchy model permits; otherwise sub-task notes are appended to the parent task description. Stage names transfer as-is; priority maps from Odoo's priority to Dolibarr's task priority field.

Odoo stock.location records map to Dolibarr warehouses (entrepot). Multi-level Odoo location hierarchies (view locations, internal locations, partner locations) flatten to one Dolibarr warehouse per distinct location used for stock tracking. Virtual and partner locations are excluded from the stock import phase.

Odoo stock.quant on-hand quantities per location map to Dolibarr stock product quantities at the warehouse level. Lot/serial number traceability is preserved where present but flagged for manual verification post-import because Dolibarr's lot tracking module may not be activated in all customer configurations.

Odoo account.account records (code, name, user_type) map to Dolibarr accounting accounts. Country-specific tax groups and fiscal position rules require explicit configuration in Dolibarr's accounting module setup and cannot be imported as working rules. We deliver a written account mapping table for the customer's accountant to configure the destination chart before go-live.

Odoo account.tax records (name, type_tax_use, amount, tax_group) map to Dolibarr taxes with scope (sale/purchase) and rate. Tax computation method (included in price vs excluded) transfers. Fiscal position automation does not migrate; Dolibarr's third-party country-based rules require manual configuration post-import.

Odoo custom fields defined via ir.model.fields (ttype: char, text, integer, float, boolean, selection, many2one, many2many) map to Dolibarr extrafields where Dolibarr's data model supports an equivalent field type. Selection-type custom fields migrate as Dolibarr select or varchar fields. many2many fields require manual mapping because Dolibarr handles multi-value links differently from Odoo's relational model.

Odoo ir.attachment records with a public URL store map to Dolibarr documents linked to the parent record (third-party, product, order, invoice, project) via the file URL. Large binary attachments should be provided as public URLs for Dolibarr to reference rather than uploaded as base64-encoded blobs. Dolibarr document management requires the Module1 (GED/document) module to be activated.

Odoo hr.employee records map to Dolibarr contacts with the Employee category assigned and a role property marking them as internal resources. Employee-specific fields (emergency contacts, attendance, contracts) are Odoo HR module-specific and have no Dolibarr equivalent; these are flagged in the handoff document for manual review.