Migrate from Infor LX to Acumatica

Infor LX customer records map directly to Acumatica Customer entities. The Infor Customer ID (CONO + CUSNO) concatenates into an external reference field while the Acumatica CustomerID auto-increments. We preserve the Infor customer number in UsrSourceCustomerCD for order cross-referencing. This mapping ensures that sales orders and invoices retain the original customer identifiers for smooth lookup.

Vendor master records from Infor LX CRS605 map to Acumatica Vendor. The 15-character Infor vendor code is stored as UsrSourceVendorCD on the Acumatica Vendor record. Terms mapping converts Infor payment terms codes to Acumatica Terms entity lookups. Additionally, vendor address details, primary contact information, and payment hold status are transferred to maintain continuity of purchasing operations.

Infor LX items are split based on the Stocking Type field: stocked items route to Acumatica StockItem with warehouse assignments from MMS002, while non-stocked items (M-type) route to Non-StockItem. Costing method from MMS001 (Standard, Average, Last) maps to the Acumatica item's Cost Method field.

Infor LX warehouses defined in MMS002 map 1:1 to Acumatica Warehouse entities. The warehouse address, bin structure, and default stocking location transfer as Warehouse settings. Multi-bin configuration in Infor LX converts to Acumatica's multi-location model. Each warehouse’s site code is stored in UsrSourceWarehouseCD to preserve references in purchase orders and inventory transactions.

Open Infor LX sales orders (OMS001) with status codes 'Open', 'Partial', or 'Acknowledged' migrate to Acumatica SalesOrder with their original order date, customer reference, and salesperson assignment. Status transformation applies — Infor's hold and credit-hold codes map to Acumatica's Credit Hold and Pending Approval flags.

Each sales order line from OMS010 becomes a SalesOrderDetails line in Acumatica. Line-specific fields — quantity ordered, quantity shipped, unit price, discount percent, and tax category — map directly. Back-ordered quantities in Infor LX appear as unshipped lines in Acumatica with the same line number for continuity.

Infor LX multi-level BOMs require flattening for Acumatica. We extract the full BOM explosion from BMT100, map each component to the Acumatica BOMBill record, and store the Infor routing steps as manufacturing notes. Phantom BOMs in Infor map to Acumatica's BOM Type = 'Phantom'.

Open and released work orders from WOT100 migrate to Acumatica ProductionOrder. The work order number becomes the production order reference, the BOM link is re-established against the migrated BOMBill, and operation step data from WOT200 transfers to production order details. Completed and closed work orders are migrated as historical records.

Infor LX user-defined fields defined in CMS470 translate to Acumatica custom fields with a Usr prefix (e.g., UsrColorCode). We create each custom field in the Acumatica Customization Project before migration, preserving the Infor field data type (alphanumeric, numeric, date) as the Acumatica field type. Custom fields on items, customers, and vendors are migrated in their respective passes.

Infor LX's segmented GL account codes map to Acumatica's Account + Subaccount structure. The first segment typically becomes the main Account number; remaining segments concatenate into a Subaccount value. We deliver a GL mapping spreadsheet before migration so your accountant can review the segment-to-dimension assignment.

Open purchase orders from POE500 migrate to Acumatica PurchaseOrder. Line items, quantities received, and vendor references transfer. Infor's receipt and invoice matching status (3-way match flags) maps to Acumatica's PO Line receipt settings. The original PO number is retained in UsrSourcePONbr for cross-referencing, and any held or pending approval status is logged in the migration report.

Infor LX lot and serial number master records from INV103 map to Acumatica's LotSerialNbr on the StockItem. Lot attributes — expiration date, supplier lot code, and certification status — transfer to Acumatica's LotAttributes fields. If a lot contains special characters or exceeds the 25-character limit, our transformation routine sanitizes the lot code and flags the record for review before final import.

Infor LX user IDs are resolved against Acumatica Employee records by email address match. Records assigned to Infor users without an Acumatica email are flagged for manual owner assignment before the migration commits. Historical Infor user names are preserved as text in an audit note field on migrated records.