Migrate from Infor LX to Infor CloudSuite Corporate

Infor LX GL account codes and descriptions export from the database as master-file records with account types and currency associations. We map account codes to CloudSuite GL Account structure, preserving account group assignments and any multi-currency flags. Period tables (open/closed status per fiscal period) export and reload into CloudSuite's financial calendar configuration. Custom fields in CMS470 that attach to GL accounts migrate as custom fields on the CloudSuite GL Account form.

Infor LX customer master records carry credit limits, payment terms, multi-currency AR settings, and address hierarchies. We map customer codes to CloudSuite Customer records, preserving AR aging balances as beginning receivables entries, multi-currency settings as currency assignment, and any CMS470 custom fields. Open AR invoices (unpaid invoices, credit memos) export separately and load as open receivable records against the migrated customer accounts.

Infor LX vendor master records carry tax registration, pay-to addresses, and multi-currency AP settings. We map vendor codes to CloudSuite Vendor records, preserving open AP vouchers and unpaid invoice balances as beginning payables. Foreign currency AP amounts carry forward with the original currency and exchange rate context so that CloudSuite's multi-currency AP module can process them through to payment.

Infor LX item master records hold stocking parameters, unit-of-measure conversions, item-type flags (including Phantom Items), and BOM associations. We map item codes to CloudSuite Item records, preserving stocking type, cost layers, and any multi-location inventory flags. Custom fields from CMS470 on item headers migrate as custom fields on the CloudSuite Item form. BOM definitions on phantom or subassembly items link to the migrated item records.

Infor LX BOMs define multi-level component structures for manufactured items. We export BOM headers and BOM lines, resolve component item references to the migrated item codes, and load into CloudSuite's BOM structure. Phantom items that represent assemblies with no inventory record of their own migrate with the Phantom flag preserved. Routing steps associated with work orders migrate separately as operations.

Infor LX work orders carry scheduled dates, component allocations (BOM-to-order pegging), and operation routing steps. We migrate work order headers with status, scheduled start and due dates, and the BOM and routing assignments. Component allocations migrate as material requirements against the work order. We do not migrate operation-level scheduling dependencies or constraint-based scheduling flags; these are flagged for manual review and re-entry in CloudSuite Planning.

Infor LX PO headers and lines carry approval workflows, distribution accounts, and foreign-currency amounts. We map open PO status and line details, including three-way match logic (PO-to-receipt-to-invoice relationships). POs with partial receipts migrate with receipt history carried forward as receipt records against the PO. POs without any receipts migrate as open POs ready for CloudSuite receiving processing.

Infor LX sales orders include pricing structures, warehouse assignments, and inventory commitment records. We extract header-level terms and line-level quantities, pricing, and delivery schedules. Source-specific discounting rules and promotional pricing that exist as configuration in LX do not migrate; these are documented for the customer's admin to reconfigure in CloudSuite's pricing engine.

Infor LX inventory transactions (physical adjustments, stock movements) exist as historical records against warehouse locations and items. We extract current on-hand balances as the beginning inventory position in CloudSuite. Recent transaction history (last open period plus one closed period) migrates as stock movement records. Full transaction history beyond that is not migrated through the standard export path due to volume and the lack of a migration utility step for full historical ledger; we flag the scope for manual entry or a separate analytics-only data load.

Custom fields in CMS470 attach to items, suppliers, and purchase agreement headers and lines with alphanumeric, numeric, or date types. We extract field definitions and values together and map them to CloudSuite custom field equivalents on the matching forms. The field type mapping preserves data type integrity (date fields migrate as dates, numeric fields as numbers) to avoid validation errors at import.