Migrate from Infor LX to Dolibarr ERP

Infor LX GL account codes, descriptions, and account-group mappings map to Dolibarr's double-entry accounting chart of accounts. We extract account codes, account types, and currency associations from the IBM i database and map them to Dolibarr's compta_account_misc table and the Plan Comptable structure. Account type (asset, liability, equity, income, expense) translates to Dolibarr'saccount_type field. Multi-currency account flags in Infor LX require activation of Dolibarr's multi-currency accounting extension module during configuration.

Infor LX customer master records — including credit limits, payment terms, address data, and multi-currency AR settings — map to Dolibarr's Third-party object in Customer mode. Customer-to-account assignments for AR link to the corresponding GL account in Dolibarr's accounting configuration. Open-receivable balances migrate as initial accounting entries against the appropriate receivable account. We preserve the Infor LX customer code as a reference field and use it as the dedupe key during import.

Infor LX vendor master records — including tax registration, Pay-to addresses, and multi-currency AP settings — map to Dolibarr's Third-party object in Supplier mode. Vendor codes and pay-to locations translate to Dolibarr's siret/siren fields and address structure. Open-payable balances migrate as initial accounting entries against the appropriate AP account. We preserve the Infor LX supplier code as a reference field.

Infor LX MMS001 item master records — stocking parameters, unit-of-measure conversions, item-type flags including Phantom Items — map to Dolibarr's Product object. We extract the item number, description, UoM, and stock parameters. If Dolibarr's MRP module is active, BOM and component associations also map. Phantom item flags from Infor LX translate to Dolibarr's Type of Product (assembly vs stockable vs service) and may require admin-level review for manufacturing accuracy.

Infor LX PO headers and lines map to Dolibarr's Supplier Order object. PO approval workflows and distribution accounts do not migrate as automation; they are documented for admin-level rebuild in Dolibarr. Foreign-currency amounts from Infor LX PO lines require the multi-currency accounting extension to be active in Dolibarr, as the base accounting module handles single-currency only. Three-way match logic does not migrate; it is noted in the automation inventory for the customer's admin to configure post-migration.

Infor LX SO records — pricing structures, warehouse assignments, and commitment quantities — map to Dolibarr's Customer Order object. Source-specific discounting rules and promotional pricing tiers are noted in the pricing-rule inventory document; Dolibarr's price list system can replicate simple tiered pricing but not complex promotional logic without customisation. We preserve order status (open, closed, cancelled) as Dolibarr's statuts_orders table values.

Infor LX work orders tied to BOMs and routing steps map to Dolibarr's Production Order object if the MRP module is active. We preserve work-order numbers, scheduled dates, and component allocations. Operation-level dependencies and scheduling constraints from Infor LX's routing steps do not map directly; Dolibarr's production module does not support multi-level routing with time constraints. These are documented in the scope notes for the customer's admin to evaluate whether Dolibarr's simpler production order model meets their post-migration scheduling needs.

Infor LX physical inventory adjustments and stock movements map to Dolibarr's Stock Movement records. We extract current on-hand balances and recent transaction history. Full transaction history exceeding 12 months is scoped selectively based on the customer's reporting needs; bulk historical movement records beyond 100,000 rows are reviewed for relevance before inclusion. Dolibarr's stock module supports multi-warehouse tracking with warehouse codes mapped from Infor LX warehouse locations.

Infor LX period tables defining financial reporting intervals migrate to Dolibarr's Financial Year and accounting period structure. We export the period table name, start and end dates, and open/closed status for the current and prior year. Dolibarr supports a single open period per year; multi-period configurations within a single year require configuration by the customer's admin post-migration.

Infor LX CMS470 custom fields on items, suppliers, and purchase agreement headers/lines (alphanumeric, numeric, or date type) map to Dolibarr's extrafields system attached to the corresponding object. We extract field definitions and values together and create equivalent Dolibarr extrafield definitions with matching types before importing the data. Numeric fields with decimal places map to Dolibarr's numeric input type. Custom field groups from CMS471 translate to labelled extrafield sections on the Dolibarr object form.

Infor LX IDM documents attached to POs, SOs, work orders, and item masters migrate as files linked to the corresponding Dolibarr object. The 5,000-document IDM cap per export run requires sequential numbered export sessions for large libraries. Version history and old document versions are not included in IDM exports and are noted as a gap in the migration report. Original document IDs are reassigned on import; we build a cross-reference table mapping source document IDs to destination IDs so that any application-level references can be re-linked post-migration.

Infor LX users referenced on PO, SO, work order, and customer records map to Dolibarr User accounts. We resolve by username or email match. Users without a matching Dolibarr account go to a reconciliation queue for the customer's admin to provision before production migration begins. Dolibarr's permission groups (commercial, accountant, admin) require configuration to match Infor LX's role-based access model.