Migrate from Infor LN to Dolibarr ERP

LN Business Partners map to Dolibarr Third Parties (societe) with a Role field distinguishing customer from supplier. LN stores address and contact data as separate child records; we reconstruct these by joining to LN's address and contact tables during extraction and writing them as Dolibarr address lines and contact records (llx_socpeople). Financial limit data from LN maps to Dolibarr's customer rating and payment term fields.

LN Items (finished goods, raw materials, semi-finished) map to Dolibarr Products. Item type (stockable, service, assembly) maps to Dolibarr's product type field. Selling and buying prices migrate as Dolibarr customer and supplier product price records. LN item costing data (standard cost, average cost) maps to Dolibarr's cost price fields if the PM (stock) module is enabled.

LN multi-level BOMs with phantom assemblies, option classes, and lead-time offsets do not have a direct Dolibarr equivalent. Dolibarr's product model is flat: it supports sub-product relationships for basic kit definitions but not recursive nesting. We flatten multi-level BOMs to finished product definitions, writing first-level component relationships as Dolibarr kit/sub-product lines. Phantom assemblies and option classes require manual reconfiguration post-migration; we document the full LN BOM tree as written inventory for the customer's admin.

LN Sites representing physical or logical inventory locations map to Dolibarr Warehouses. Site-level inventory policies, location codes, and receiving rules map to Dolibarr warehouse properties. We extract multisite control data for cross-site transfer awareness and write it as warehouse notes for post-migration reference.

LN Sales Order headers and lines map to Dolibarr Customer Order. Order status, dates, payment terms, and line items (product reference, quantity, unit price) migrate directly. LN's price matrix resolution on orders maps to the migrated price records in Dolibarr. Multicompany sales orders that span LN financial entities do not migrate as structured records; the customer must re-enter or restructure these post-migration.

LN Purchase Order headers, lines, and schedule dates map to Dolibarr Supplier Order. Purchase contract (blanket order) release schedules that decrement funded quantities migrate as standard purchase order lines with reference to the original contract number. We preserve the funded-quantity decrement context in the order notes field.

LN Projects supporting ETO and MTO lifecycles with phase structures and billing milestones map to Dolibarr Projects. We migrate project name, description, phase structures, and dates. Revenue recognition milestone data migrates as Dolibarr task-level notes for the customer's finance team to rebuild in the project billing workflow. LN project cost tracking does not replicate in Dolibarr's project module.

LN Financial Companies with separate charts of accounts and fiscal calendars require post-migration configuration in Dolibarr. We extract the LN chart of accounts and fiscal calendar structure and deliver it as a written accounting plan that the customer's accountant configures in Dolibarr's accounting module. Organizations using LN's multicompany consolidation features will need to re-architect their reporting structure.

LN price matrix priority rules (matrix definition tdpcg0610m000 with priority search order) have no equivalent in Dolibarr's flat price model. We migrate the resulting active price records to Dolibarr customer and supplier product prices, and we deliver the full matrix definition and priority chain as written documentation for the customer's admin to manually configure equivalent price books in Dolibarr.

LN custom fields defined in the Extensions package with Domain-typed data migrate to Dolibarr extrafields. We read the Domain property (alphanumeric, numeric, date, etc.) from the LN Extensions metadata to confirm type compatibility before writing to Dolibarr's extrafields table. Any column where the domain type cannot be coerced to a Dolibarr-supported extrafield type is flagged in the reconciliation report for manual resolution.

LN stores document references (URL pointers to file storage) rather than binary content. We extract document metadata and URL paths and write them as Dolibarr ECM entries pointing to the migrated file storage location. The actual binary files must be transferred separately via the customer's file transfer process; Dolibarr does not replicate LN's document storage system.

LN users mapped to Business Partner contacts and organizational approval roles map to Dolibarr Users by email match. We extract user IDs, names, and email addresses from LN and match against Dolibarr User records. LN-specific role assignments for approval routing do not replicate in Dolibarr; we document these as written role inventory for the customer's admin to rebuild using Dolibarr's permission system.