Migrate from Infor XA to Epicor Prophet 21

XA Item records carry stocking codes, cost methods, warehouse assignments, lot/serial controls, and unit-of-measure conversions that map to Epicor Part and PartWhse records. We extract from the IM tables (IMITEMP, IMITEMX) and map stocking UOM, standard cost, and stocking location to Epicor Part and PartWhse. XA's stocking code (M/S/T for manufactured/stocked/transferred) translates to Epicor's TypeCode and Method of Mfg. Multi-warehouse configurations in XA generate one PartWhse record per warehouse in Epicor.

XA BOMs support multi-level, phantom, and substitute item structures with effective date windows. Migration requires recursive BOM explosion to flatten nested hierarchies into Epicor's single-level BOM format. We extract BOMM and BOMX tables, compute the full BOM tree, and map each level to Epicor PartMtl records linked to the parent Part. Phantom items (XA BOMH phantom flag) become Epicor JobMtl phantom material sequences. Effective date ranges from XA translate to Epicor's revision-effective date logic, with multiple revisions created where date-range overlaps exist.

XA Work Orders drive shop floor control with operation sequences, labor posting, and costing links. We extract WOHDDR/ WODETL tables and map WO header status, priority, type, and start/due dates to Epicor JobHead. Operation sequences map to JobOper with work center references and schedule dates. Material requirements map to JobMtl. We preserve WO-to-operation linkage and labor posting records, extracting WOLabor to post against the equivalent Epicor LaborDtl records during migration. Closed and open work orders migrate; historical WO records with status other than complete are flagged for customer review before migration.

XA PO headers carry supplier assignment, terms, and delivery schedules; line items carry quantity, price, and delivery date. We extract POHDDR/PODETL and map supplier (RMSUPP to Vendor table), PO number, terms, and line status to Epicor POHeader and POLine. Open POs (released or partially received) migrate as active records; closed or received POs migrate as historical records with receipt history. Purchase order history in XA's PO receipt records requires mapping to Epicor's PORel and RcvDtl tables with vendor invoicing matched against XA's AP invoice data.

XA GL accounts are defined in a structured chart of accounts with account codes, descriptions, and posting controls in COAFIL and COASEG tables. Standard account definitions export cleanly and map 1:1 to Epicor's GLAccount structure. We validate account code length and character set against Epicor's account segment rules and flag any XA account codes that exceed Epicor's segment length limits for manual remediation. GL fiscal periods, posting date ranges, and currency assignments migrate from XA's fiscal calendar and multi-currency setup to Epicor's GLFiscals and Currency tables.

Outstanding payables and receivables carry supplier/customer references, invoice numbers, due dates, and amounts. We extract APOPEN and AROPEN tables and map to Epicor's APInvHed (header) and ARInvoice records. We flag any AP records with hold status or discount terms that require Epicor payment terms and AP validation rule mapping. Open invoice balances must tie to the migrated GL accounts to ensure Epicor's AP/APTran posting is accurate at cutover. Period assignment is preserved from XA's fiscal period structure.

XA sales orders link to pricing, availability checking, and inventory allocation. We extract SOHDDR/SODETL and map order headers, line items, delivery addresses, and order-specific discounts or special terms to Epicor OrderHed and OrderDtl. Order status in XA (open, partially shipped, on hold) maps to Epicor OpenLine or within completion logic. Pricing and availability checking results from XA are noted but recalculated in Epicor at migration time to reflect current inventory and pricing rules.

Time entries, labor posting, and operation completions in XA's shop floor module (SFDC/SFWC tables) tie to work orders and employees. We extract labor clock-in/out records, operation completions, and scrap postings and map them to Epicor LaborDtl (linked to the migrated JobOper) and PartTran (inventory transactions for labor, scrap, and material usage). Labor cost in XA is computed using XA's labor posting rules; we migrate the hours and let Epicor recalculate cost using Epicor's labor rates and work center rates at migration time unless the customer specifies otherwise.

Routings define operation sequences, work centers, and labor or machine standards tied to production in XA. We extract the RMROUTE tables and map routing operations to Epicor JobOper, resolving work center codes to Epicor's ResourceGroup and Resource tables. Operation labor hours, machine hours, and setup/cycle times from XA map to Epicor StdFormat, EstLaborHours, and EstMachineHours. We flag any XA routing work centers that have no direct Epicor ResourceGroup equivalent for customer configuration before migration.

XA supports user-defined fields on items, suppliers, and purchase agreement headers via CMS470—these are alphanumeric, numeric, or date fields that require explicit field-level mapping to Epicor UDFs. We identify every active CMS470 field during discovery, provision matching UDFs in Epicor (with correct field type, length, and decimal places) before any data import, and map the values column-by-column. New UDFs must be created in Epicor first, which requires Epicor admin access and is sequenced before record migration begins.

XA user accounts and IBM i security profiles define access rights and default accounting entities. We extract user records and map them to Epicor's User account with role-based security. IBM i profile authority (program object restrictions, data area access) maps to Epicor's Menu Security and Company/Site restrictions. Users with multiple company assignments in XA receive multiple Epicor Company record assignments. We flag any custom security or menu restrictions that have no direct Epicor RBAC equivalent for manual configuration.

XA supplier master records carry terms, payment methods, and bank information that map to Epicor Vendor. We extract RMSUPP and map payment terms, currency, and bank details to Epicor Vendor records with Terms and BankAcct references. Supplier part numbers stored in XA's supplier item cross-reference map to Epicor's VendorPP (Vendor Part Preference). AP BACS/EFT bank details from XA map to Epicor's VendorBank table with appropriate bank routing and account number fields.