Migrate from Infor LX to Microsoft Dynamics 365 Business Central

Infor LX GL accounts (account codes, descriptions, account-type flags, currency associations) map directly to Dynamics 365 Finance G/L Account records. We extract account codes and descriptions from the source database and map account type (Asset, Liability, Equity, Revenue, Expense) to the Dynamics 365 AccountType field. Multi-entity configurations require financial dimension mapping: Infor LX's cost-centre hierarchy maps to Dynamics 365 Financial Dimensions (typically Business Unit, Department, Division, Project), which must be configured before account import because dimensions govern posting group assignment. Period-based account activation dates migrate as the G/L Account valid-from date.

Infor LX customer master records (MMS001 address data, credit limits, payment terms, multi-currency AR settings) map to Dynamics 365 Customer records with separate party and account structure. The customer party (PartyType = Organization or Person) creates a dirPartyTable record, and the customer account creates a CustTable record linked by the party ID. Multi-currency AR from Infor LX's per-customer currency settings maps to the Dynamics 365 customer currency and the accounting currency pair. Open receivable balances carry forward as unsettled customer transactions against the migrated G/L Account.

Infor LX vendor master records (tax registration, Pay-to addresses, multi-currency AP settings) map to Dynamics 365 Vendor records with the same party-account separation as Customer. The vendor party creates a dirPartyTable record; the vendor account creates a VendTable record. Multi-currency AP settings from Infor LX map to Dynamics 365 vendor currency and the accounting currency pair. Open payable balances carry forward as unsettled vendor transactions against the migrated G/L Account.

Infor LX item master records in MMS001 (stocking parameters, unit-of-measure conversions, Phantom Item flags, item-type classifications) map to Dynamics 365 Supply Chain Management Released Products. The source item type (Stocked, Service, Phantom, Category) determines the ProductType and the item model group, which controls inventory valuation methods (Standard, Moving Average, FIFO). Unit-of-measure conversions from Infor LX's UOM table map to the Dynamics 365 Unit of Measure framework. Custom fields from CMS470 attach to the item header and migrate as custom fields on Released Product.

Infor LX PO headers and lines (approval workflows, distribution accounts, foreign-currency amounts, three-way match logic) map to Dynamics 365 Purchase Orders. We extract PO number, vendor reference, header status, line item, quantity, unit price, and delivery date. Three-way match configuration does not migrate; we document the current match tolerance settings as a configuration reference for the customer's Dynamics 365 admin to set in Procurement and Sourcing Parameters. Discounting rules and promotional pricing from Infor LX line-level adjustments carry as price adjustment records or manual line discounts.

Infor LX SO records (pricing structures, warehouse assignments, inventory commitments, header-level terms) map to Microsoft Dynamics 365 Sales Orders. We extract SO number, customer account, header terms, line items, quantities, prices, and requested delivery dates. Source-specific discounting rules and promotional pricing that exist as line-level adjustments in Infor LX carry as Dynamics 365 manual line discounts or price adjustment lines. SO status (Open, Confirmed, Shipped, Invoiced) maps to Microsoft Dynamics 365 Sales Status with the corresponding Workflow state.

Infor LX work orders tie production operations to BOMs and routing steps. We preserve work-order numbers, scheduled start and end dates, component allocations (BOM line consumption), and operation-level routing references. Operation-level dependencies and scheduling constraints that drive the APS module do not migrate; these are documented as a separate APS reconfiguration scope for the customer's production planning team. The Dynamics 365 production order carries the same item, quantity, and scheduling date as the source work order.

Physical inventory adjustments and stock movements recorded in Infor LX as transaction history map to Dynamics 365 Supply Chain Management inventory transactions. We extract current on-hand balances (item, warehouse, location, quantity, unit of measure) and recent transaction history (adjustment date, adjustment type, quantity delta, financial cost). Full transaction history spanning multiple years migrates selectively based on the customer's reporting retention policy; transactions older than the cutover date are archived rather than loaded into the live inventory ledger to maintain import performance.

Infor LX period tables define user-defined financial reporting intervals (fiscal year, period start and end dates, period status) and map directly to Dynamics 365 Finance fiscal calendars. We export the period table structure and the current year's open and closed status. Period status (Open, Closed, On Hold) migrates as the fiscal period's start and end dates, with closed periods locked against further posting in the destination. Multi-company configurations require a separate fiscal calendar per legal entity if fiscal year definitions differ across Infor LX partitions.

Infor LX CMS470 custom fields (alphanumeric, numeric, date types) attached to item headers, supplier records, and purchase agreement headers and lines map to Dynamics 365 custom fields on the equivalent standard entities. We extract field definitions and their values together during the same extraction pass. Custom field type mapping: Infor alphanumeric maps to Dynamics 365 Text, numeric maps to Decimal or Integer depending on precision, date types map to Date. The custom field schema must be deployed into Dynamics 365 before the corresponding data import to satisfy the column requirement.

Infor Document Management exports carry a 5,000-document per-run cap when SharePoint is in use, and history and old versions are excluded. We split large document libraries into numbered chunks and run sequential export sessions. Document IDs and extended properties are reassigned on import; we build a cross-reference table during export that maps source document IDs to destination IDs so that document links on migrated POs, SOs, and work orders can be updated post-import. The latest version of each document migrates as a SharePoint file attachment or Dataverse document location.

ION connector configurations that orchestrate data flow between Infor LX and connected systems (supplier portals, customer EDI, shop-floor data collection) do not migrate as integration code. We deliver a written inventory of each active ION service, its trigger (REST, queue, schedule, storage), its timeout configuration, its payload structure, and its destination endpoint. The customer's integration team or a Microsoft partner rebuilds equivalent flows in Azure Logic Apps, Dataverse connections, or Power Automate, referencing the inventory as the functional specification.