Migrate from Infor LX to Odoo ERP

Infor LX GL accounts with defined account types, currency associations, and cost-centre groupings map to Odoo Account records with Account Type, Account Tag, and internal_group. We extract account codes, descriptions, and account-group mappings from the database export and map them to Odoo's accounting.chart template for the relevant country, adding any Infor-specific cost-centre accounts as Odoo analytic account records. Multi-currency account flags from Infor Enterprise Financials map to Odoo Foreign Currency Gain/Loss accounts on the Fiscal Position.

Infor LX customer master records include credit limits, payment terms, address data, and multi-currency AR settings. We map customer records to Odoo res.partner with type=contact, customer_rank set for deduplication, and payment terms from Infor's payment terms code. Multi-currency AR from Infor translates to a Fiscal Position in Odoo that assigns the correct currency and exchange rate account per customer. Open receivable balances migrate as Odoo Account Move lines against the customer partner.

Infor LX vendor master records include tax registration, Pay-to addresses, and multi-currency AP settings. We map vendors to Odoo res.partner with type=supplier and vendor_rank set. Infor's Pay-to location concept maps to Odoo's multi-address capability on the vendor partner record. Multi-currency AP settings map to a vendor-specific Fiscal Position in Odoo that controls the correct currency and gain/loss account on foreign-currency AP.

Infor LX MMS001 item records carry stocking parameters, unit-of-measure conversions, Phantom Item flags, and item-type classifications. We map standard items to Odoo Product Template with the product type (stockable, consumable, service) derived from the Infor item type. Unit-of-measure conversions in Infor map to Odoo's UoM categories and conversion factors in the uom.uom model. Phantom Items in Infor (used as assembly explode components) map to Odoo BoM lines with type=phantom. CMS470 custom fields attach to item headers and map to Odoo ir.model.field custom fields created on product.template.

Infor LX PO headers with approval workflows, distribution accounts, and foreign-currency amounts map to Odoo purchase.order records. PO status (open, closed, cancelled) maps to Odoo's state field (draft, sent, purchase, done, cancel). Line-level distribution accounts in Infor translate to Odoo's analytic account on PO lines for cost allocation. We preserve PO dates, payment terms, and line quantities; Infor-specific discounting rules and promotional pricing that rely on Infor pricing engines are noted as requiring manual review or Odoo pricelist configuration post-migration.

Infor LX SO records include pricing structures, warehouse assignments, and inventory commitments. We map SO headers and line-level quantities to Odoo sale.order and sale.order.line. Warehouse commitment from Infor maps to Odoo's picking policy and delivery reservation logic. Infor's pricing and promotional rules that are source-specific are not carried forward; Odoo pricelist configuration replaces these post-migration. Customer-specific credit limits from Infor AR migrate as Odoo partner credit limits on the res.partner record.

Infor LX work orders tie production operations to BOMs and routing steps. We map work order numbers, scheduled dates, and component allocations to Odoo mrp.production records with associated mrp.workorder lines. Infor BOM components map to Odoo mrp.bom lines; Infor routing steps map to Odoo work centre operations. Operation-level dependencies and scheduling constraints that rely on Infor's finite capacity scheduling engine are flagged as requiring Odoo planning configuration review post-migration. Component allocations (issuance quantities) migrate as Odoo mrp.workorder qty values.

Infor LX physical inventory adjustments and stock movements are recorded as transaction history against warehouse locations and items. We extract current on-hand balances by warehouse location from the database export and create Odoo stock.quant records for the initial inventory snapshot. Full historical transaction logs migrate as Odoo stock.move records if the scope includes inventory history; otherwise, the current on-hand balances serve as the opening inventory for Odoo's stock valuation.

Infor LX period tables define financial reporting intervals with start and end dates, organised by year and calendar name. We export the period table structure and the current year's open/closed status and map them to Odoo account.fiscal.year records. Infor's period-based accounting (where transactions are bound to a specific period) requires Odoo's lock date and fiscal year lock configuration to replicate the same access control. Inter-company or multi-subsidiary period calendars map to separate Odoo fiscal year configurations per company.

CMS470 custom fields in Infor LX attach to items, suppliers, and purchase agreement headers and lines. They support alphanumeric, numeric, and date types. We extract field definitions and their values together, create the equivalent Odoo ir.model.field definitions (custom fields on the relevant model), and populate the values during the corresponding record import. Alphanumeric multi-select CMS470 fields map to Odoo selection fields or many2many tags depending on the cardinality of values.

Infor Document Management exports carry a 5,000-document cap per run, strip historical versions, and reassign IDs on import. We split large document libraries into numbered chunked export sessions, build a cross-reference table mapping source document IDs to destination attachment IDs, and re-link attachments to their associated transactional records (POs, SOs, work orders) after import by matching document filenames or metadata keys against the migrated record identifiers.