Migrate from Infor LN to Microsoft Dynamics 365 Business Central

Infor LN maintains Business Partners as a single entity type with a Role field distinguishing customers from suppliers. Address, contact, financial limits, and payment terms are stored as related child records. We map the LN Business Partner to Dynamics 365 Account (with Account Type set to Customer or Vendor) and the primary contact to Contact. Financial limit data and credit terms migrate to the Account's CreditLimit and PaymentTerms fields. Multicompany BP assignments require cross-referencing the BP's Financial Company membership before writing the Account record in the correct legal entity context.

LN Financial Companies map directly to Dynamics 365 Finance and Operations Legal Entities or Business Central Companies. Each LN Financial Company maintains its own chart of accounts, fiscal calendar, and tax configuration. We extract all financial company definitions before any transactional data and create corresponding legal entity records in Dynamics. The fiscal year configuration and accounting currency migrate to ensure that period-close reporting is consistent post-migration.

LN Items carry rich attribute data including BOM structures, costing information, and unit-of-measure definitions. The Item is the anchor object for pricing matrices, purchase orders, and sales orders. We preserve the item's unit-of-measure conversions, costing version, and planning parameters during migration. Item variants in LN (size, color, configuration dimensions) map to Dynamics 365 product dimension groups.

LN BOMs support multiple levels of nesting, phantom assemblies, option classes, and lead-time offsets. Engineering Change Orders attach to BOMs as revision-controlled overlays. We preserve the BOM by mapping the parent item to a BOM Master, each nested component to BOM Lines, and the ECO revision level to a BOM Version with the effective from and to dates. Phantom BOMs in LN map to Phantom BOM type in Dynamics. Option classes with conditional components map to BOM Lines with alternative group configuration.

Sites in LN represent physical or logical locations with their own inventory policies, location definitions, and receiving rules. Multisite Control data governs cross-site stock transfers. We map each LN Site to a Dynamics 365 Site and Warehouse, preserving location structures, picking route definitions, and inventory posting profiles. The cross-site transfer orders require warehouse assignment resolution before inventory balances migrate.

LN separates purchase order headers from lines and schedule dates. Purchase contracts (blanket orders) link to release schedules that decrement funded quantities. We map PO headers and lines with schedule information, preserving delivery dates, purchasing taxes, and the supplier reference number. Purchase agreements migrate as Purchase Contracts with line items and release schedule limits mapped to the contract's remaining quantity.

Sales order pricing in LN can resolve through price books and matrix definitions. Multicompany sales invoicing can combine lines from Sales, Project, and Service logistic packages onto a single invoice. We map the sales order header, lines, and delivery schedules, preserving pricing terms and the original customer order reference. Sales agreements migrate with remaining quantities and committed amounts.

LN Projects support ETO and MTO lifecycles with phase structures, work breakdown hierarchies, and billing milestones. We map project phases and linked revenue recognition schedules to Dynamics 365 Project Management entities. Work breakdown structure lines migrate as project tasks with effort estimates, and billing milestones map to project contract lines and invoicing schedules.

LN resolves item prices through matrix priority search rules where multiple price books and matrix definitions compete and the highest priority wins. We export the full Matrix Definition (tdpcg0610m000) metadata alongside each price record to allow Dynamics 365 to reconstruct the same priority chain through trade agreement groups, price lists, and quantity break definitions. Item surcharges migrate as cost adders in the price calculation version. Without the matrix priority metadata, Dynamics would resolve prices differently than LN did.

Service contracts in LN track entitlement, coverage periods, and SLA terms. Field service records include technician assignments and parts consumed. We map entitlement and coverage data to Dynamics 365 Field Service Agreement entities, and the service history to the service journal. Note that A&D-grade depot-level MRO tracking in LN may require supplemental configuration in Dynamics Field Service beyond the base agreement migration.

LN's multicompany invoicing generates internal financial settlements between entities using self-billing. These settlement records create intercompany journal entries that must be reconciled across all financial companies. We stage all intercompany settlement records and their counterpart journal entries in a reconciliation table, then write matching intercompany journal entries in Dynamics 365 Finance and Operations. Any settlement that lacks a matched debit or credit in the export scope is flagged for the customer's finance team before write-back.

LN custom fields are defined in the Extensions package with a Domain property specifying the data type. Two custom fields with the same logical name can have incompatible domains depending on how they were created. We read the Domain definition before mapping custom field columns to the Dynamics 365 schema, rejecting any column where the domain type cannot be coerced to the target field type. Custom field values are stored in dedicated extension tables that join to the base object tables by numeric ID.