Migrate from Infor LN to Epicor Prophet 21

Infor LN maintains Business Partners as a single entity with a Role field distinguishing customer from supplier. Address, contact, and financial limit data live as related child records. We map to Epicor Customer and Supplier records, splitting by LN Role at migration time. Customer and Supplier are separate record types in Epicor Kinetic. The LN financial limit data maps to Customer Credit Limit and Supplier Payment Terms fields.

LN Items carry rich attribute data including BOM structures, routing steps, costing information, and stocking dimensions. We map to Epicor Kinetic Part with PartClass assignment, Stocking UOM, and Costing information preserved. LN Item Type (make, buy, or phantom) maps to Epicor Type Code. Part Number from LN becomes Part Number in Epicor; the LN Item Revision becomes Epicor Part Revision with revision-specific BOM and routing attachments.

LN Financial Companies maintain their own chart of accounts, fiscal calendar, and tax configuration. We map each LN Financial Company to an Epicor Kinetic Company record with its own fiscal calendar, accounting period definitions, and tax jurisdiction assignment. Multicompany LN configurations generate multiple Epicor Company records. We preserve the LN currency assignments and any intercompany trading relationships as a separate configuration guide for the customer's Epicor admin.

LN Sites represent physical or logical locations with inventory policies, location definitions, and receiving rules. We map to Epicor Kinetic Site (or Plant) and Warehouse records with location structure preserved. The multisite control data governing cross-site stock transfers maps to Epicor Transfer Order and inter-site warehouse assignment rules.

LN BOMs support multiple nesting levels, phantom assemblies, option classes, and lead-time offsets. Engineering Change Orders attach to BOMs as revision-controlled overlays. We preserve BOM level structure, quantity-per, operation steps, and scrap percentages in Epicor Part Revision BOM. Phantom assemblies map to Epicor Phantom BOM type. ECO-linked BOM revisions migrate as Epicor ECO and Part Revision records with effective dates.

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, and schedule as three related Epicor records: POHeader, POLine, and PORel (release schedule). The LN purchase contract funded quantity becomes Epicor PO Header with linked release lines. Open and closed status preserves from LN Document State.

LN blanket purchase orders (contracts) hold funded quantity and delivery terms. We map to Epicor POHeader with a Blanket PO type, where release schedules correspond to individual POLine release records. Funded quantity and remaining authorized amount map from LN to Epicor POHeader Total Promise and remaining commitment fields. We flag any contract with releases that span multiple LN Financial Companies for separate intercompany reconciliation.

LN sales orders can resolve pricing through price books and matrix definitions. Multicompany invoicing combines lines from Sales, Project, and Service logistic packages onto a single invoice. We map to Epicor Kinetic Sales Order with SOLine and release schedule preserved. LN pricing resolution through matrix definitions migrates as Epicor Price Code assignments and Part Price records (see price matrix mapping). Multicompany sales order lines are split at migration time by LN Financial Company and mapped to corresponding Epicor Company records.

LN Projects support ETO and MTO lifecycles with phase structures, work breakdown hierarchies, and billing milestones. We map to Epicor Kinetic Project with phase hierarchy, WBS levels, revenue recognition milestones, and project-level accounting rules preserved. Project cost categories map from LN to Epicor Project Plant Cost Codes. Revenue recognition methods (percentage of completion, completed contract, or as-incurred) migrate as Project Billing Rules.

LN service contracts track entitlement, coverage periods, and SLA terms. Field service records include technician assignments, mobile dispatch data, and parts consumed. We map to Epicor Kinetic Service Contract with coverage terms, contract lines, and SLA response-time definitions. Contract entitlement rules migrate from LN coverage matrix to Epicor Service Agreement coverage rules.

LN field service records track technician assignments, work orders, parts consumed, and dispatch data. We map to Epicor Kinetic Service Call with linked Job for any billable labor, and Parts and Labor records for material and time consumed. Technician assignments migrate as Service Call assigned-resource records with skill certifications checked against Epicor Resource Group qualifications.

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 Epicor Customer and Supplier contact records, with organizational role assignments preserved in the contact's Role field and in the Epicor Security Groups configuration guide we deliver for the customer's admin team.

LN custom fields are defined in the Extensions package with a Domain property specifying data type; values are stored in dedicated extension tables that join to base object tables. We read the Domain definition before mapping, validate type compatibility with Epicor UDF or Extended Field data types, and reject any column where the domain type cannot be coerced. UDFs in Epicor Kinetic are defined per-table in System Management before data import begins. LN extension table join IDs require two-pass extraction (text table then transactional tables) before staging.

LN price matrices 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 setups. We export the full LN Matrix Definition (tdpcg0610m000) metadata alongside each price book to preserve the priority chain. The resulting price records migrate as Epicor Part Price entries with Price Code assignments, and Customer Price Breaks migrate with break quantity and price per tier. The priority order is delivered as a written configuration guide for the Epicor admin to reconstruct in Epicor Price Code priority rules.

LN stores document references (pointers to file storage) rather than binary content in most transactional tables. We extract document metadata and URL paths and map them to Epicor Kinetic Document Management records linked to the parent Part, BOM Revision, or Order. The customer's IT team configures the document storage endpoint in Epicor Kinetic (Epicor Data Library, SharePoint, or other) before migration so that the reference links resolve post-go-live.

LN multicompany invoicing generates internal financial settlements between entities using self-billing, creating intercompany journal entries that must be reconciled across all financial companies. Epicor Kinetic does not have a native equivalent multicompany settlement engine at the same depth as LN. We extract all settlement records and their linked journal entries, flag any settlement that lacks a matched debit or credit in the same export scope, and deliver a written reconciliation spreadsheet for the customer's financial team to post manually or through an intercompany transaction process in Epicor after go-live.