Migrate from Pronto Xi to Infor CloudSuite Corporate

Pronto Xi GL accounts use a hierarchical code system stored in IBM Informix with parent-child relationships and account attributes. We extract account codes, descriptions, account types, and parent references via direct Informix DB queries, preserving the full hierarchy for import into Infor CloudSuite's GL Account structure. Any accounts with non-standard segment structures require custom field mapping during extraction.

Pronto Xi customer records include address books, contact details, payment terms, credit limits, and tax codes stored as structured Informix records. We map these to Infor CloudSuite Customer with handling for multi-address scenarios, ship-to and bill-to splits, and the customer's tax jurisdiction assignment. Credit limit and payment term overrides at the customer level migrate as custom fields if the destination schema does not support them natively.

Pronto Xi supplier records mirror the customer structure with address books, contact details, payment terms, and tax codes. We map these to Infor CloudSuite Supplier, preserving the same multi-address handling and payment term assignments. Supplier-specific fields like WHS vendor codes and Erichson compliance flags migrate as custom fields with documentation for the customer's admin to configure.

Pronto Xi inventory items include item masters with BOMs, cost layers, reorder points, and multi-warehouse location assignments stored in Informix. We extract item headers, cost records per site, and current stock quantities per location, maintaining the inventory valuation method (FIFO, average, standard) during migration. Inactive items flagged in Pronto Xi for write-off or discontinuation are migrated with their status and held for admin review at destination.

Pronto Xi multi-location inventory assignments require extraction of warehouse codes, addresses, and bin location hierarchies per item. We map these to Infor CloudSuite Warehouse and Location structures, preserving any custom location naming conventions used in picking and receiving workflows. Multi-site configurations where the same item carries different stock quantities per warehouse migrate with full balance detail.

Pronto Xi BOMs store component items, quantities per assembly, and revision versions tied to manufacturing processes in Informix. We extract BOM headers and component lines, mapping to Infor CloudSuite's BOM structure with revision control preserved. Any BOMs referencing discontinued items or components with no Infor equivalent are flagged for the customer's engineering team to resolve before production data moves.

Pronto Xi work orders carry routing steps, labor allocations, and component consumption records tied to specific BOM versions. We map these to Infor CloudSuite Job with work order status, routing operation sequences, and component allocations preserved. Jobs in progress at migration time are flagged with their completion percentage so that Infor job costing picks up from the correct point without double-counting material or labor.

Outstanding receivables require extraction with aging buckets, invoice numbers, due dates, and payment reference history. We sequence open AR extraction before the final period close at source, then apply matching payments or credit allocations at the destination in the correct chronological order. Any invoices with partial payments carry both the remaining balance and the payment history so that aging reports remain accurate post-migration.

Outstanding payables migrate with the same sequencing discipline as AR: extraction before final period close, then allocation of matching payments or credit notes at the destination in chronological order. Vouchers with hold status or dispute flags are mapped to equivalent Infor statuses with a custom field carrying the original Pronto Xi hold reason for audit trail.

Open sales orders include headers with pricing and discounting and line items with delivery scheduling. We extract order headers and lines with pricing, discounting, and fulfillment progress flags. Status at migration time determines whether orders land as Infor Sales Orders in open, confirmed, or picking status to avoid inadvertent re-processing of completed lines.

Open purchase orders carry supplier references, line items with pricing, and delivery scheduling. We extract PO headers and lines, mapping supplier codes to the Infor Supplier records created earlier in the migration. Purchase orders with partial receipts carry receipt history so that Infor's receiving module resumes from the correct balance.

Pronto Xi environments frequently contain bespoke modules built on the SDK or RAD framework alongside User Defined Fields on standard tables. We identify each custom element during scoping, map its data structure to either an Infor CloudSuite custom object or extension field, and flag any that have no equivalent in the destination schema for the customer's admin to decide between replacement or retirement.