Migrate from iXERP Standard to Infor CloudSuite Corporate

iXERP Customer records (name, contact fields, addresses, financial balances, payment terms) map to Infor Cloudsuite Customer or Party records. iXERP stores contact persons within the Customer record; Infor typically separates contact persons as Contact records linked to the Party. We extract embedded contact persons during the transform phase and create Infor Contact records with PartyId lookups. Outstanding invoice amounts and credit limits map to Infor's AR-specific fields.

iXERP Vendor master records (supplier details, payment terms, accounts payable balances) map to Infor Cloudsuite Supplier records. Currency and payment term fields require transformation if iXERP uses custom term codes. We run a vendor name dedupe check during pre-flight because duplicate supplier names are a known issue in iXERP source data.

iXERP Items (stock SKUs, non-stock items, services) map to Infor Cloudsuite Item records with item codes, cost prices, selling prices, and stock-on-hand quantities. Serial and batch tracking fields carry across where configured. Infor's item master uses a more complex structure with BOM (Bill of Materials) associations; we map item type codes to Infor Item Type and flag any iXERP items that require BOM creation in the destination as a separate configuration step.

Open iXERP Purchase Orders map to Infor Cloudsuite Purchase Order headers with line items, quantities, and received-to-date values. Status mapping is direct (iXERP Issued maps to Infor Released, iXERP Received maps to Infor Received). Closed and historical POs migrate as read-only records if the customer scopes historical data; open POs are the primary migration target to preserve buy-side commitments. We resolve vendor references using the Supplier mapping before PO import.

iXERP Sales Orders (customer commitments with line items, pricing, fulfilment status) map to Infor Cloudsuite Sales Order records. Fulfilment progress, shipping status, and related invoice references carry across. The CustomerId lookup resolves to the Infor Party or Customer record created during the master data phase. We map iXERP order statuses (Open, Invoiced, Cancelled) to Infor equivalents (Infor Open, Infor Closed, Infor Cancelled).

iXERP Issues Invoices (accounts receivable) and Receipts Invoices (accounts payable) map to separate Infor AR Invoice and AP Voucher objects. Mappings between iXERP invoice types and Infor invoice types must be agreed upfront because naming conventions differ between modules. Historical invoices migrate as open items with payment status preserved; paid invoices may be scoped out to reduce migration volume. Tax codes and multi-line detail transfer with validation against Infor's tax code table.

iXERP Projects (with associated tasks, time entries, budgets, and milestone dates) map to Infor Cloudsuite Project records. Custom project fields migrate as extended fields on the Project object. Resource assignments and budget data transfer with validation against Infor's project cost structure requirements. We preserve the task-to-project parent relationship during migration to maintain hierarchy integrity.

iXERP Tasks (assigned to projects, with status, hours logged, and assignees) map to Infor Cloudsuite Task records linked to the parent Project. Assignee resolution uses email-based matching against Infor User records. Time entries associated with tasks carry across as task detail or separate time recording entries depending on the Infor edition configured.

iXERP HR Employees (personal details, job roles, departments, compensation) map to Infor Cloudsuite Human Capital Management Employee or Worker records. Effective-dated fields are preserved during transformation. Multi-address records require flattening or multi-address handling based on the Infor HCM configuration. We map department and job role codes to Infor org structure equivalents during the schema mapping phase.

iXERP document attachments are stored as URL or hyperlink references to external cloud storage rather than as binary blobs. We migrate the URL references but not the files themselves. Before migration, we validate that all document URLs remain accessible and document the storage dependency. If the customer changes cloud storage providers or revokes access, document links in Infor Cloudsuite will break. We flag this as a precondition in the pre-flight report.

iXERP custom fields across CRM and HR modules are detected during profiling and mapped to Infor extended fields with __c naming conventions or Infor's user-defined field framework. Picklist values are converted to Infor picklist domains. Multi-select custom fields in iXERP require transformation to Infor's multi-select format. Custom field mapping is validated in the test migration phase before production load.