Migrate from Infor LN to Infor CloudSuite Corporate

LN maintains Business Partners as a single entity type with a Role field distinguishing customers from suppliers. Address, contact, and financial limit child records attach to the parent. We extract from crmsupplier and tcustpadhdr tables with join to LN Tools text tables for description fields, preserving payment terms, credit limits, and tax categories. Multicompany BP assignments require Financial Company lookup before BP import.

LN Items carry BOM structures, routing steps, and costing information as related child records. We extract tdinv001 (item master), tdinv002 (warehouse stock), and tdinv010 (costing) with attribute joins. Item surcharges and cost adders are stored in tdpcg0610m000 and must export alongside pricing data to preserve the valuation chain.

LN Financial Companies each maintain separate chart of accounts, fiscal calendar, and tax configuration. We extract all financial company records before any transactional data, because multicompany invoicing creates intercompany settlements that must reference valid company codes. Missing Financial Company records at migration time orphan settlement records and create unbalanced intercompany positions.

LN Sites represent physical or logical locations with inventory policies, location definitions, and receiving rules. Multisite Control module governs cross-site stock transfers. We extract wmswarehouse and wmslocat tables, preserving location codes, stock policies, and site-specific reorder points before any inventory transaction migration.

LN BOMs support multiple nesting levels, phantom assemblies, option classes, and lead-time offsets. Engineering Change Orders attach as revision-controlled overlays. We extract tdintf1460 (BOM header), tdintf1461 (BOM lines), and tdintf9020 (ECO attachments), preserving the revision chain and engineering approval status. BOM explode against the Item master ensures component items exist before BOM lines import.

LN separates purchase order headers from lines and schedule dates. Purchase contracts (blanket orders) link to release schedules that decrement funded quantities. We extract from tdpur400 (PO header), tdpur401 (PO lines), and tdpur402 (schedules), resolving supplier Business Partner IDs and site warehouse assignments from previously migrated reference data.

Sales order pricing in LN resolves through price books and matrix definitions. Multicompany sales invoicing can combine lines from Sales, Project, and Service logistic packages onto a single invoice. We extract from tdsls400 (SO header), tdsls401 (SO lines), and tdsls440 (price matrices), resolving customer Business Partner IDs, Financial Company IDs, and price matrix priority rules from metadata tables before record import.

LN Projects support ETO and MTO lifecycles with phase structures, work breakdown hierarchies, and billing milestones. We extract tdproj001 (project header), tdproj002 (phases), tdproj003 (WBS elements), and tdproj010 (billing milestones), preserving phase start dates and revenue recognition rules. Projects with linked purchase orders and sales orders require those records to migrate first.

Service contracts track entitlement, coverage periods, and SLA terms. Field service records include technician assignments, mobile dispatch data, and parts consumed. We extract from tdsfsv400 (contract header), tdsfsv401 (contract lines), and tdsfsv450 (dispatch records), resolving Business Partner entitlement flags before import.

Price matrices in LN use priority-based search rules across purchase, sales, and transfer price types with matrix attributes as dimensions. We export tdpcg0610m000 (Matrix Definition) metadata alongside each price book to preserve the priority chain. Item surcharges function as cost adders in valuation price schedules and must export as related records. Without the priority metadata, CloudSuite may resolve prices differently than LN did.

LN stores document references (pointers to file storage) rather than binary content in most transactional tables. We extract document metadata (URL paths, file names, description text from LN Tools tables) and map to CloudSuite Document Management. Binary file migration requires separate file transfer and is scoped as a supplementary task.

LN maps users to Business Partner contacts and organizational roles for approval routing. Owner assignments on orders, projects, and settlements reference the LN user table. We extract the user table with email and role assignments, then resolve Owner IDs in transactional records by matching email against the CloudSuite user directory. Any user without a CloudSuite match goes to a reconciliation queue.