Migrate from Pronto Xi to Epicor Prophet 21

Pronto Xi GL accounts use hierarchical account codes stored in IBM Informix with parent-child relationships across multiple levels. We extract account codes, descriptions, and segment positions via direct Informix queries, preserving the full account hierarchy as COA segments in Epicor. The natural account dimension maps to Epicor's Natural Account field; optional division or department segments map to Epicor's statistical or financial segment fields depending on the customer's Epicor configuration.

Pronto Xi accounts include address books, contact details, payment terms, tax codes, and multi-address scenarios. We map these to Epicor Customer and Supplier tables, preserving the address hierarchy (primary, ship-to, bill-to) as Epicor Address records linked via ShipToNum. Payment terms and tax codes are mapped to Epicor equivalents during transformation.

Pronto Xi item masters include SKUs, descriptions, UOMs, cost layers, reorder points, and item type classifications. We map ItemCode to Part Number, preserve the cost layer (FIFO, Average, Standard) as Epicor's costing method, and extract current stock quantities per warehouse location into PartWhse records with the correct Site and Warehouse assignments.

Pronto Xi BOMs store component items, quantities per assembly, and revision versions tied to manufacturing processes. We extract BOM headers and component lines, ordering components by BOM revision and MtlSeq before import so that parent parts resolve before assemblies. PartRev revision records are created in Epicor with the correct revision code before PartMtl records are loaded. Migrations with 5+ BOM levels require explicit dependency sequencing to avoid orphan errors.

Pronto Xi Work Orders carry routing steps, labor allocations, and component consumption records tied to specific BOM versions. We map Work Order headers to Epicor JobHead, component lines to JobMtl, and operation steps to JobOper. JobMtl sequences must resolve after PartMtl is confirmed in Epicor, and JobOper sequences are assigned in BOM routing order. We flag any steps referencing deprecated BOM revisions for the customer's admin to resolve before import.

Outstanding receivables and payables require sequencing before the final period close at source to avoid duplicate postings or payment allocation mismatches. We extract open items with aging buckets, reference numbers, and payment terms, then apply them at Epicor in chronological order. Credit memos are applied to matching invoices before the final balance is established in the AR/AP ledger.

Open orders include line items with pricing, discounting, delivery scheduling, and fulfillment progress. We extract order headers and lines, set destination order statuses based on fulfillment progress (Backorder, Partial Ship, Open), and preserve pricing and discount records. Lines referencing obsolete inventory items are held in a reconciliation queue for the customer's admin to update before import.

Pronto Xi BOM revisions track engineering change orders across multiple revision codes. We extract the revision effective dates, the change description, and the affected BOM components. Epicor's PartRev revision codes are created for each active Pronto revision, and any ECO-driven changes are mapped to Epicor's ECORev and ECOGroup tables where the customer's Epicor edition supports engineering change management.

Pronto Xi stores multi-location inventory assignments with site-specific reorder points and transfer hierarchies. We map each Pronto site and warehouse to Epicor Site and Wareh records, preserving the location address, default bins, and any inter-site transfer rules. Stock quantities per location are imported into PartWhse against the correct Site-Warehouse combination after PartWhse schema is validated.

Pronto Xi environments frequently contain bespoke modules built on the SDK or RAD framework that reference modified core tables. We identify these during scoping, map their data structures to Epicor UD columns on the relevant tables (Part_c, OrderHed_c, JobMtl_c), and flag any that have no equivalent in Epicor's standard schema. UD Tables are used for multi-field custom objects that cannot fit into UD columns.

Payroll data in Pronto Xi is sensitive and often edition-gated. We extract employee compensation history, leave balances, and pay categories, mapping them to Epicor EmpBasic and Labor records while respecting data residency requirements. Timesheet and labor posting data are mapped to Epicor Labor tables against the relevant JobNum and OperNum.

Pronto Xi service module records include asset links, job scheduling, technician assignments, and contract details. We map these to Epicor's FieldService or Asset Management tables depending on the customer's Epicor edition, preserving service history linked to the asset record and maintaining the job scheduling sequence against the correct technician or work center.

Linked documents stored in Pronto Xi's document management system are extracted via file references or direct DB blob access. We handle file naming conventions, map document types to Epicor's document control schema (DocumentRev, XgPln-frxDocument), and preserve document associations to Part, Job, or Order records. PDF and image attachments are stored as Epicor attachments linked to the relevant record.

Pronto Xi tax codes carry jurisdiction assignments, rates, and tax type classifications. We map these to Epicor TaxRegion records and configure TaxConnect for ongoing tax calculation if the customer licenses that module. GST and VAT rates from the Australian Pronto Xi environment are mapped to the corresponding Epicor tax jurisdiction records.