Migrate from Infor M3 to Dolibarr ERP

Infor M3 Items (the product/material master) map directly to Dolibarr Products. We export Item Number, Description, Type (Stocked/Non-stocked/Service), Unit of Measure, and any costing data. M3's costing model (Standard, Average, FIFO) is preserved in a Dolibarr custom field; the costing itself is not calculated in Dolibarr since Dolibarr does not compute weighted average or FIFO cost internally. If the M3 Item has multiple UOMs, we map the primary purchasing UOM and primary sales UOM as separate Dolibarr UOM entries. Discontinued Items in M3 map to Dolibarr Products with the archived status flag.

M3 Customer Orders map to Dolibarr Customer Orders. Header fields (order number, order date, customer reference) map directly. Order lines map to Dolibarr Order lines with Product reference, quantity, unit price, and discount. M3 order status (Pending, Released, Invoiced, Cancelled) maps to Dolibarr status values (Draft, Validated, Closed). Open orders migrate with status preserved so the customer's sales team can continue fulfillment in Dolibarr. Historical closed orders migrate with status set to Closed and are available for reporting.

M3 Supplier Orders (Purchase Orders) map to Dolibarr Supplier Proposals that are validated to create Supplier Orders. Supplier order number, date, and terms map directly. Line items map with supplier product reference, quantity, and cost. M3 approval status maps to Dolibarr Draft/Validated status. Open purchase orders with goods pending receipt migrate with lines open for receipt against the supplier order in Dolibarr.

M3 Bills of Material with multi-level structures, operations, resources, and by-products do not have a direct Dolibarr equivalent. Dolibarr Products support a flat BOM (list of components with quantities) but not routing-based manufacturing with work centers, operations, or labor time. We flatten multi-level M3 BOMs into single-level Dolibarr Product BOMs by recursively exploding the hierarchy. Any M3 BOM with operations or work order routing is flagged in the handoff document as requiring manual re-creation in Dolibarr's BOM module or an external MES. Configured and attribute-controlled products in M3 require a separate re-design session because Dolibarr does not support attribute-based configuration.

M3 Work Orders with status, operations, and time entries are split across Dolibarr. The Work Order header (number, item, quantity, start date, due date) migrates as a Dolibarr Project. Each Work Order operation that consumed time or materials generates a Project Task line in Dolibarr. The actual production output is not modeled in Dolibarr since there is no MES; the Project serves as a manufacturing summary record. Work Orders with a status of Released or In-Process that are not yet complete are flagged in the handoff for the customer's team to close or continue manually.

M3 Inventory quantities, warehouse locations, and bin assignments map to Dolibarr Stock (Warehouse > Stock). We export warehouse code, bin location, quantity on hand, and unit of measure per Item-Warehouse-Bin combination. M3's multi-warehouse configuration maps to separate Dolibarr warehouses. If M3 uses lot or serial number tracking, these migrate as Dolibarr Lot/Serial entries linked to the Stock movements. Current stock values are informational in Dolibarr since Dolibarr does not compute weighted average cost; the M3 costing data is preserved in custom fields for reference.

M3 General Ledger accounts map to Dolibarr Accounts (plan comptable). We export the account number, description, account type (Asset, Liability, Equity, Income, Expense), and company association for multi-company configurations. Open AR and AP balances migrate as Dolibarr third-party accounts with aged outstanding amounts. M3's inter-company journals require manual mapping because Dolibarr is single-company per instance; inter-company entries are reconciled and posted to a clearing account with a note in the handoff document. M3 cost center and department associations map to Dolibarr Projects or Categories for segmentation.

M3's multi-company chart of accounts structure is extracted and mapped to a single Dolibarr chart of accounts. For multi-company M3 deployments, each company's account ranges are preserved as a named cost center or project prefix within the single Dolibarr chart. The customer reviews and approves the account mapping before we load. M3's financial dimensions (departments, cost centers, projects) map to Dolibarr Categories and Projects for reporting segmentation.

M3 Fixed Asset records including asset classification, acquisition date, cost, accumulated depreciation, and depreciation method map to Dolibarr Assets. Open depreciation periods with remaining book value migrate with the current depreciation schedule. Depreciation history migrates as asset accounting entries. M3 assets fully depreciated or disposed of migrate with their final values as historical records.

M3 Distribution Orders managing inter-site or inter-company transfers map to Dolibarr Stock Movements with a Project reference for tracking. The origin warehouse, destination warehouse, item, and quantity transfer as a multi-warehouse movement in Dolibarr. Status (Pending, Shipped, Received) maps to movement status. Distribution orders that are part of a closed cycle migrate as completed movements; open transfers migrate with lines pending receipt.

M3 Business Partners (Customers and Suppliers) map to Dolibarr Third Parties with type distinction (Customer, Supplier, or Both). M3's Address, Contact Person, Payment Terms, and Price List assignments map directly. M3's multi-company business partner assignments are preserved as Third Party Categories for reporting segmentation. Customer and Supplier accounts are separate Third Party records in Dolibarr rather than a unified partner record as in M3.

M3 custom fields attached to Items, Orders, and other objects are extracted and mapped to Dolibarr Extra Fields (Extrafields). We preserve the field label, data type, and current values. Fields that are not exposed in the M3 API (display-only custom fields) are noted in the manifest for manual re-creation in Dolibarr. Dolibarr's Extra Field system supports text, integer, float, date, select, checkbox, and link-to-dictionary types, which cover most M3 custom field scenarios.