Migrate from Extensiv Order Manager to Dolibarr ERP

Extensiv Orders map to Dolibarr Orders (Commande client). We preserve order number, order date, customer reference, order status, line items with SKU and quantity, shipping fees, and warehouse assignment. Sales channel assignment from Extensiv (Shopify, Amazon, Walmart) is stored in a Dolibarr custom field since Dolibarr has no native channel object. We validate that Dolibarr's Order module is activated in the customer's modules configuration before migration begins.

Extensiv Customer records map to Dolibarr Third Parties (Societe) in contact mode. We map customer name, email, phone, billing address, and shipping address. Extensiv's per-customer custom fields (pre-configured under Customers > Custom Fields) migrate to Dolibarr extrafields on the Societe table if admin opt-in is confirmed. Multiple shipping addresses per customer in Extensiv map to separate Dolibarr contact addresses under the same Third Party.

Extensiv Products map to Dolibarr Products with type = Product. We preserve SKU (ref), product name, description, cost price (buy price), and sell price. The Extensiv Product module must be activated in Dolibarr and the appropriate price management modules (Customer catalog or Multi-price) enabled to handle the sell price migration. Product weight and dimensions from Extensiv map to Dolibarr weight and volume fields for stock calculations.

Extensiv Bundle and Kit products with component-level SKU tracking map to Dolibarr BOM (nomenclature). We preserve the parent SKU, all component SKUs with quantities, and the bundle pricing override if set. Note that Dolibarr BOMs support kit assembly and disassembly workflows but do not natively support pricing overrides at the bundle level the way Extensiv does; bundle-level pricing adjustments in Extensiv require a custom price rule or manual price entry in Dolibarr after migration. The BOM module in Dolibarr must be explicitly activated by the customer's admin.

Extensiv per-warehouse inventory positions require a consolidation decision at scoping. If the customer runs multiple Extensiv warehouses, we ask whether Dolibarr will represent each as a separate Warehouse object or whether inventory should be aggregated into one canonical warehouse position. Extensiv's per-SKU, per-warehouse stock quantities map to Dolibarr's Stock-Warehouse-Multiple (Stock > Warehouses) if the Multi-warehouse module is activated, or to a single stock position if simplified tracking is acceptable. FIFO cost basis is stored as a custom price field on Product since Dolibarr's standard stock valuation does not include FIFO.

Extensiv Warehouse records (in-house and 3PL) map to Dolibarr Warehouse (Entrepot) objects. We preserve warehouse name, code, and address. If the customer uses 3PL warehouses connected via Extensiv Integration Management, those warehouse entities migrate to Dolibarr as standard Entrepot records; the customer should understand that Dolibarr has no native 3PL connection management and any ongoing 3PL EDI sync will need to be rebuilt outside Dolibarr.

Extensiv Purchase Orders map to Dolibarr Supplier Orders. We preserve PO number, vendor reference, PO date, status, and line items with vendor SKU, quantity, and cost. Vendor records in Extensiv (vendors associated with POs) map to Dolibarr Third Parties in supplier mode (Societe with type = Supplier). Inbound receipt records from Extensiv map to Dolibarr Reception records if the Reception (Receptions) module is activated; otherwise they are flagged as note objects for manual reconciliation.

Extensiv cross-warehouse stock transfers map to Dolibarr Stock Movements (Mouvement de stock) between warehouses. We preserve source warehouse, destination warehouse, SKU, and quantity transferred. Single-warehouse transfers map to a stock movement with the same source and destination warehouse. Note that Dolibarr's stock movement module does not carry a Transfer object type; every cross-warehouse move is represented as an outgoing movement from the source warehouse and an incoming movement to the destination, which we reconcile as a paired set.

Extensiv Shipment records map to Dolibarr Shipments (Expedition) linked to the corresponding customer order. We preserve carrier name, tracking number, shipment date, and shipping cost. The Dolibarr Expedition module must be activated and linked to the customer order before shipment records import. Note that Dolibarr does not natively support carrier rate shopping or multi-carrier label printing; any Extensiv Integration Management carrier logic (such as live rate shopping) is not replicated in Dolibarr.

Extensiv Custom Order Info fields and pre-configured Customer custom fields require admin opt-in (Admin > Settings > Enable custom fields) before export. If confirmed, we map these to Dolibarr extrafields on the corresponding tables (llx_commande for orders, llx_societe for third parties). Ad-hoc order-level custom fields from the Custom Order Info section migrate to Dolibarr extrafields on llx_commandedet (order line) if line-level custom data exists. Custom Product Fields from Extensiv's Products > Fields tab migrate to Dolibarr extrafields on llx_product.

Extensiv FIFO cost basis, inventory value, SKU profitability, and inventory aging reports are exported as reference data. We map FIFO unit costs to Dolibarr Product buy price fields and flag inventory value reporting as a custom report requirement to be built in Dolibarr's reporting module or an external BI tool post-migration. We do not migrate the reporting configuration itself; the customer rebuilds dashboard preferences and scheduled reports in Dolibarr's built-in reporting engine.

Extensiv Sales Channels (the integration sources attached to orders) have no native Dolibarr equivalent. We store the Extensiv channel name (Shopify, Amazon, Walmart, eBay, etc.) as a custom field on each migrated Dolibarr Order record so that historical channel attribution is queryable. Channel connection credentials and ongoing sync settings are documented separately as out-of-scope because Dolibarr does not have an integration management layer equivalent to Extensiv Integration Management.