Migrate from Orion ERP to Infor CloudSuite Corporate

Orion's COA maps directly to Infor CloudSuite's Chart of Accounts structure using account code, name, type, and currency settings. Multi-segment COA (common in multi-entity Orion deployments) requires we flatten or decompose each segment into Infor's account code hierarchy. We extract via the financial module report and map each account to the corresponding COSP segment in Infor before any journal entry import begins.

Orion Customer records including contact details, billing address, payment terms, and credit limits map to Infor's Customer entity. The Infor customer number becomes the primary key; we preserve the Orion customer code as a reference field. Payment terms from Orion map to Infor's payment term codes (PTDC). Multi-address customer records require we create Infor address book entries with roles.

Orion Vendor master records including tax ID, payment terms, and bank details map to Infor's Supplier entity. Tax ID format validation is applied during the transform step since Orion and Infor may use different tax ID formatting conventions by country. Bank details migrate as separate bank account records attached to the supplier via Infor's address book role structure.

Orion GL header and line-item records (date, journal number, description, account, debit, credit) migrate as Infor journal entries. We extract full GL history via the financial report export and import as journal batches with header metadata and line items. The Infor fiscal year and period must be open at migration time; we coordinate with the customer's Infor admin to confirm period status before loading.

Orion open AP records (vendor reference, invoice number, amount due, due date) cannot be imported as new AP invoices because doing so would double-post against the opening-balance position. We extract open AP as a distinct scope item, map due dates and amounts, and inject them as opening-balance journals in Infor's AP subledger with a specific opening-balance document type. Each open AP line becomes a journal entry that establishes the payable without triggering a new invoice workflow.

Orion open AR records (customer reference, invoice number, amount receivable, due date) follow the same treatment as AP: they become opening-balance journals rather than new invoice records. We extract open AR as a distinct migration scope item, map amounts to Infor's AR subledger, and inject them as opening-balance document type entries so that the customer's AR aging report reflects the correct starting position.

Orion Item master records (SKU, description, unit of measure, cost, warehouse location) map to Infor's MITMAS master file. We extract via the inventory management report. Unit of measure conversion factors from Orion's UOM settings map to Infor's UOM conversion table during import. If Orion's Manufacturing Cloud edition is in scope, BOM (bill of materials) data maps to Infor's MBOM structure.

BOM data from Orion's Manufacturing Cloud edition maps to Infor's MBOM structure. We detect BOM existence during the scoping export and add MBOM mapping as a separate configuration scope item if applicable. BOM versioning and effective dates from Orion map to Infor's BOM revision control. If the destination is Infor CloudSuite LN, EBOM may also be relevant for engineering-to-order scenarios.

Orion PO headers and lines including status, vendor assignment, and line-item quantities map to Infor's PO tables. Open versus closed PO status must be preserved to determine whether the PO imports as open or closed in Infor. We extract PO data via the procurement module report export and map line-item quantities, UOMs, and costs to the corresponding Infor PO structure. Only open POs require opening-balance treatment; closed POs migrate as historical records without triggering new workflow actions.

Orion Sales Order records including customer reference, product lines, pricing, and order status map to Infor's SO tables. We map order headers and lines separately and flag fulfilled versus pending lines to align with Infor's order fulfillment workflow. Open SOs require inventory reservation checks in Infor; we coordinate with the customer's Infor admin on whether to import open SOs as confirmed orders or as demand signals pending confirmation.

Orion Employee records including name, department, job title, compensation, and employment dates map to Infor's employee master. We extract through the HR management module report. Effective-dated compensation history requires we sequence records chronologically to preserve the compensation timeline in Infor. If the destination Infor CloudSuite edition includes a dedicated HRMS module, employees map there; otherwise, they map to the address book with HR role assignments.

Orion custom fields on master and transaction records require pre-detection during the scoping export. Custom field existence and data types vary by Orion edition and customer configuration. We detect all custom properties, map their data types to equivalent Infor extended property structures, and include them in the extraction templates. Custom field mapping is a configuration step deployed before any data load begins.