Migrate your Infor LN data

LN maintains Business Partners as a single entity type with a Role field distinguishing customers from suppliers. Address, contact, and financial limits are stored as related child records. We map these child structures to the target system's equivalent Contact/Company/Account split during migration.

Items in LN carry rich attribute data including BOM structures, routing steps, and costing information. The Item is the anchor object for pricing matrices, purchase orders, and sales orders. We preserve the full item hierarchy and costing version during export.

LN supports multiple financial companies within a single logical instance. Each financial company maintains its own chart of accounts, fiscal calendar, and tax configuration. We extract all financial company definitions before any transactional data to preserve account linkage.

Sites in LN represent physical or logical locations with their own inventory policies, location definitions, and receiving rules. Multisite Control module data governs cross-site stock transfers and replication. We extract site parameters and inventory positions as a sequenced block.

LN BOMs support multiple levels of nesting, phantom assemblies, option classes, and lead-time offsets. Engineering Change Orders (ECOs) attach to BOMs as revision-controlled overlays. We preserve BOM structure and the active revision link during migration.

LN separates purchase order headers from lines and schedule dates. Purchase contracts (blanket orders) link to release schedules that decrement funded quantities. We map header/line/schedule relationships and handle the contract funding balance at import time.

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 document. We preserve the pricing source and multicompany linkage flags.

LN Projects support ETO (engineer-to-order) and MTO (make-to-order) lifecycles with phase structures, work breakdown hierarchies, and billing milestones. We map project phases and linked revenue recognition schedules to the target system.

Service contracts in LN track entitlement, coverage periods, and SLA terms. Field service records include technician assignments, mobile dispatch data, and parts consumed. We extract contract terms and field service history as separate linked objects.

LN custom fields are defined in the Extensions package with a Domain property specifying data type. Custom field values are stored in dedicated extension tables that join to the base object tables. We map each active custom field as a named column in the export, inferring the Domain type to validate against the target schema.

Price matrices in LN use priority-based search rules across purchase, sales, and transfer price types with matrix attributes as dimensions. Item surcharges function as cost adders in valuation price structures. We export both the matrix definition metadata and the effective price records to ensure the target system reconstructs the same pricing logic.

LN stores document references (pointers to file storage) rather than binary content in most transactional tables. We extract the document metadata and URL paths and map them to the target system's attachment model, flagging any orphaned references that lack a valid target file.

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 before migration. We flag settlement records that lack a matched counterpart in the export scope.

LN maps users to Business Partner contacts and to organizational roles for approval routing. Owner assignments on transactional records (orders, projects) reference the LN user table. We map user IDs to the target system's user or employee object, preserving role-based routing where applicable.