Migrate from Relic ERP to Infor CloudSuite Corporate

Relic ERP vendor and customer records map to Infor CloudSuite Business Partner records with the BP Type field set to Supplier or Customer. Address books, contact information, and tax registration numbers migrate as Infor BP Address and Contact records. We resolve the BP code as the dedupe key. If Relic ERP maintains separate Vendor and Customer tables, we split them into separate Infor BP records with the appropriate type flags.

Relic ERP customer and account master records map to Infor CloudSuite Business Partner records with BP Type = Customer. Credit limits, payment terms, and price lists migrate to Infor BP financial and pricing fields. Customer-specific discounts and override pricing rules are documented for manual configuration in Infor CloudSuite's pricing module.

Relic ERP item and product master records map to Infor CloudSuite Item master with Unit of Measure, stocking dimensions, and costing method preserved. Relic ERP item codes map to Infor Item codes; SKU or part number migrates to the Infor Item Cross-Reference table if the customer maintains supplier SKUs. Item-specific warehouses and stocking locations require a separate location mapping phase.

Relic ERP warehouse and location records map to Infor CloudSuite Warehouse records with address, bin structure, and picking strategy preserved where applicable. Multi-bin warehouse structures in Relic ERP require mapping to Infor's warehouse location hierarchy (Site, Warehouse, Bin). We flag any warehouse-specific inventory valuation methods for manual Infor configuration.

Relic ERP general ledger chart of accounts maps to Infor CloudSuite GL Account structure. Account codes, descriptions, account types (Asset, Liability, Equity, Revenue, Expense), and fiscal year setup migrate to Infor Financial Management. Any Relic ERP cost center or department dimension maps to an Infor Business Unit or Dimension field depending on the Infor CloudSuite edition's dimensional accounting configuration.

Open and historical Purchase Orders from Relic ERP map to Infor CloudSuite Purchase Orders with header and line structure preserved. PO status (open, closed, canceled) migrates to Infor PO status fields. We resolve the Supplier BP reference and the Item references at migration time using the BP and Item mapping tables created in earlier phases. Closed POs with outstanding receipts require coordination with the customer on whether to complete receipt processing in Relic ERP before migration or handle as a manual post-migration adjustment.

Open and historical Sales Orders from Relic ERP map to Infor CloudSuite Sales Orders with customer BP reference, order lines, pricing, and delivery dates preserved. Relic ERP order status maps to Infor SO status (Open, Confirmed, Shipped, Invoiced). We resolve Customer BP, Item, and Warehouse references at migration time. Quotes linked to open Sales Orders migrate as related Infor Quote records.

Relic ERP inventory movement records (receipts, issues, transfers, adjustments) map to Infor CloudSuite Inventory Transaction records. We migrate the transaction date, quantity, cost, warehouse, and item reference. Inventory balances are validated against Relic ERP current stock reports before migration and reconciled post-migration in Infor CloudSuite. Discrepancies are flagged in the Data Assessment Report for customer resolution before final commit.

Relic ERP financial journal entries, invoices, and payment records map to Infor CloudSuite GL Vouchers and Journal Entries. We migrate the entry date, account code (mapped via the Chart of Accounts mapping), debit/credit amounts, and description. Infor CloudSuite requires all journal entries to balance before commit; we flag any unbalanced Relic ERP entries in the Data Assessment Report. Customers typically elect to migrate only open or current-year transactions and archive historical ledgers to reduce migration scope.

Relic ERP document attachments (PDFs, images, office files) linked to master or transactional records map to Infor Document Management (IDM). We extract file attachments from Relic ERP records, associate them with the corresponding migrated Infor record using the record key mapping, and load them into IDM. File naming conventions from Relic ERP are preserved in the IDM file metadata for traceability.

Relic ERP custom fields and user-defined tables require a manual mapping spreadsheet produced during discovery. We document the Relic ERP table name, column name, data type, and current values, then map to Infor CloudSuite custom field equivalents. Infor CloudSuite supports custom fields on standard objects via Infor Configuration. Any Relic ERP custom tables that have no Infor CloudSuite standard equivalent are documented as candidates for Infor OS Data Fabric or a separate data store, not migrated into the core ERP schema.