Migrate from Infor LN to Acumatica

Infor LN stores all parties (customers, vendors, prospects) in a single Business Partner table with a Type field. FlitStack splits these into separate Acumatica Customer and Vendor records based on the LN BP Type. B2B addresses attached to the BP map to Acumatica Address defaults on each entity.

LN BP address lines map directly to Acumatica's Address record attached to Customer or Vendor. The primary address flag and country code are preserved. Multiple addresses per BP become multiple Acumatica address records keyed to the same entity. Each address can be designated as billing or shipping within Acumatica's address types.

LN BP contact names, titles, phone numbers, and email addresses migrate to Acumatica Contacts attached to Customer or Vendor. The primary contact flag is preserved. Contact methods (phone, fax, email) map to Acumatica's Contact Methods table. Additional fields such as role and department can be added as custom fields if needed.

LN Item records with Stock type map to Acumatica Stock Items; Non-Stock items map to Non-Stock Items. The LN Item Class drives Acumatica's Item Class assignment. Unit of Measure definitions from LN's UOM table are translated to Acumatica's UOM setup before item import.

LN warehouses map 1:1 to Acumatica Warehouses. The warehouse code, name, and address details carry over. Each warehouse's default location-to-bin structure maps to Acumatica Location records within the Warehouse. If multiple sites share a warehouse in LN, split them into separate Acumatica warehouses to maintain site-level inventory tracking.

LN purchase order headers and lines migrate to Acumatica Purchase Orders. Vendor ID, PO number, status, date, and terms are mapped. Line-level detail (item, quantity, UOM, site, unit cost, extended cost) maps to Acumatica POLine with the appropriate inventory and land cost accounts applied.

LN sales orders migrate to Acumatica Sales Orders with header fields (order number, customer ID, date, terms, ship-to address) and line fields (inventory ID, quantity, UOM, warehouse, unit price, line total) preserved. Open orders are prioritized; closed orders migrate as historical records.

LN GL accounts use a segmented numeric code (company-6, cost center-4, subaccount-2-2 structure). Each LN account must be mapped to an Acumatica Account with matching segment structure or a consolidated code. Value-by-value mapping is required because Acumatica validates account existence before transactional import.

Infor LN's cost element hierarchy (material, labor, overhead, outside processing) has no native Acumatica equivalent. Cost element codes are preserved as a custom field on the Account (CostElement__c) or as a financial dimension depending on the Acumatica configuration chosen during schema setup.

LN work centers and their associated operation rates (labor rate, machine rate, overhead surcharges) map to Acumatica Work Centers. The work center code, description, and linked cost rate records carry over. Resource calendars and capacity definitions are preserved as part of the work center setup.

LN Bills of Material (BOMs) with multi-level structures, phantom BOMs, and BOM steps map to Acumatica Manufacturing BOMs. Each BOM version, revision, effective date, and line (component item, quantity per, operation step) migrates with step numbers preserved for production order routing.

Open and recently closed LN production orders migrate to Acumatica Production Orders with the linked BOM revision, quantity, scheduled dates, and material allocations preserved. Header status (released, completed, closed) maps to Acumatica Production Order status codes. History lines are migrated as completed production records.

LN inventory valuation records (on-hand quantity, average unit cost, last cost) migrate to Acumatica Inventory Summary records per item and warehouse. The on-hand quantity maps directly; the average cost is stored as the Last Cost on the Inventory Item for valuation purposes.

LN fixed asset records with acquisition cost, placed-in-service date, depreciation method, useful life, and accumulated depreciation migrate to Acumatica Fixed Assets. Depreciation schedules are preserved as Acumatica Fixed Asset depreciation records with the last depreciation period matching the LN cutoff date.

Infor LN extended data structures linked to standard tables via table ID and column name are exported as named-value pairs. These are created as Acumatica Usr-prefixed extension fields on the matching DAC (Customer, Vendor, InventoryItem, POOrder, SOOrder). Each custom field requires an Acumatica Customization Project to be published before data import.

LN financial period definitions (fiscal year, period start/end dates, period status) migrate as Acumatica Fiscal Years and Periods. Closed periods are flagged as locked in Acumatica to prevent post-migration postings to historical periods. We also map the period calendar to Acumatica's fiscal year setup, ensuring the year-end close process aligns with LN's existing configuration.

LN currency exchange rates with effective dates migrate to Acumatica Exchange Rates. The From Currency, To Currency, Effective Date, and Rate are mapped directly. Acumatica's multiple exchange rate sources (manual, ECB, etc.) are noted and the LN rate source is documented for post-migration rate management.

LN subaccount segments used for profit center reporting are mapped to Acumatica Subaccounts or Financial Dimensions depending on the Acumatica configuration. Each LN subaccount code is mapped value-by-value to ensure segment-based financial reporting continuity after migration. This mapping supports drill-down reporting and helps maintain consistent cost allocation across the new system.