Migrate from Iptor ERP to Infor CloudSuite Corporate

Iptor Business Partner records with BP type flag set to Customer map to Infor CloudSuite Customer Party. We split the unified BP entity during transformation using the BP type attribute, creating separate Customer and Vendor records. Customer address, contact details, payment terms, and credit limits transfer to the CloudSuite party record. Any custom fields on the BP migrate as custom properties against the party record for manual review and classification by the customer's Infor consultant.

Iptor Business Partner records with BP type flag set to Vendor map to Infor CloudSuite Vendor Party. Vendor-specific fields including bank details, W-9 status, and EDI trading partner IDs transfer. EDI configuration does not migrate as a live connection; we document the EDI endpoint and format settings so the customer's Infor consultant re-establishes connectivity post-migration.

Iptor's configurable segment-based account structure maps to Infor CloudSuite's chart of accounts. We extract the full segment layout, identify account assignments per segment, and map to the destination account codes. Accounts with non-standard segment assignments (from custom modifications) are flagged for manual review before import. The customer approves the account mapping before we commit the data.

Iptor Items map to Infor CloudSuite Item Master records. We preserve item classification hierarchies as parent-child classification path attributes rather than flattening to a single category, since Infor supports hierarchical categorization. Configurable attributes, unit-of-measure settings, lot/serial tracking, and warehouse assignments transfer. Items are migrated before any transactional records to satisfy the foreign key dependency.

Iptor's multi-level Item Classification tree does not map 1:1 to a flat category field in Infor CloudSuite. We extract the full classification hierarchy with parent-child relationships, preserve the full path as a delimited attribute (e.g., Food/Beverage/Dairy/Milk), and assign the leaf-level classification as the primary category. The customer chooses between hierarchical tag attributes or a flat category assignment during scoping.

Open payables are migrated as explicit vendor invoice records at go-live to establish accurate aged trial balance in CloudSuite. Invoice number, vendor assignment, invoice date, due date, amount, and tax jurisdiction transfer. We flag any open AP items that reference a vendor not yet migrated so the customer can sequence provisioning before cutover.

Open receivables are migrated as explicit customer invoice records at go-live to establish accurate aged trial balance in CloudSuite. Invoice number, customer assignment, invoice date, due date, amount, and tax jurisdiction transfer. Closed AR items migrate as historical records for reporting continuity but are excluded from the open aging report.

Sales Order headers and lines migrate in a single pass with order number, dates, customer assignment, pricing, and status preserved. Open orders transfer with their current status so the Infor consultant can configure the appropriate workflow for order fulfillment. Fulfilled orders transfer as historical records. We link order headers to customer and item records that were migrated in earlier phases.

Purchase Order headers and lines export from Iptor with vendor assignment, line quantities, and expected delivery dates. Partially received POs transfer with received quantities flagged so the destination reflects the current receipt state. We link POs to vendor records migrated in the Business Partner phase.

Iptor AR invoices map to Infor CloudSuite AR invoice records with invoice number, date, customer assignment, amounts, tax codes, and payment terms preserved. We differentiate between open invoices (migrated to the live AR ledger) and closed invoices (migrated as historical records for reporting). The invoice-to-customer linkage is resolved through the Customer Party mapping.

Iptor AP invoices map to Infor CloudSuite AP invoice records with invoice number, date, vendor assignment, amounts, and tax codes preserved. Open AP invoices appear in the aged payables report at go-live. Closed AP invoices transfer as historical records. Vendor linkage is resolved through the Vendor Party mapping.

Delivery Notes map to Infor CloudSuite shipment records with header and line details including quantities shipped versus ordered. We preserve the linkage back to the originating Sales Order for audit continuity. Warehouse assignment resolves through the warehouse code mapping established during inventory migration.