Migrate your Infor LX data

GL accounts are standard master-file records with defined account types and currency associations. We extract account codes, descriptions, and account-group mappings directly from the database and map them to the destination's chart-of-accounts structure.

Customer master records include credit limits, payment terms, and address data. Multi-currency AR is supported per-customer. We preserve customer-to-account assignments and open-receivable balances as separate line items.

Vendor master records in AP carry tax registration, Pay-to addresses, and multi-currency settings. We map vendor codes and pay-to locations to the destination's vendor structure and carry forward any open-payable records.

Item master records in MMS001 hold stocking parameters, unit-of-measure conversions, and item-type flags (including Phantom Items). Custom fields defined in CMS470 attach to item headers. We extract all item attributes and their associated custom-field values together.

PO headers and lines carry approval workflows, distribution accounts, and foreign-currency amounts. Three-way match logic ties POs to receipts and invoices. We map PO status and line details, though approval routing logic may require manual reconfiguration in the destination.

SO records include pricing structures, warehouses, and commitments against inventory. We extract header-level terms and line-level quantities, but source-specific discounting rules and promotional pricing often require manual mapping at the destination.

Work orders tie production operations to BOMs and routing steps. We preserve work-order numbers, scheduled dates, and component allocations, but operation-level dependencies and scheduling constraints often need redefinition in the target system.

Physical inventory adjustments and stock movements are recorded as transaction history against warehouse locations and items. We extract current on-hand balances and recent transaction history; full open-transaction chains require careful sequencing to avoid balance discrepancies.

Period tables define user-defined 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 for each period to reconstruct the financial calendar in the destination.

Custom fields in CMS470 attach to items, suppliers, and purchase agreement headers and lines. They can be alphanumeric, numeric, or date types. We extract field definitions and their values together, but destination-side custom field creation must precede the data import.