Migrate from Infor XA to Acumatica

XA customer records map to Acumatica's Customer table. XA's country codes and address structure map to Acumatica's Address / Contact fields — multiple ship-to addresses in XA become separate Location records under one Customer in Acumatica. Each location retains its own address lines, contact phone, and email, and the original XA location code is stored in a UsrOriginalShipTo custom field for audit traceability.

XA vendor records map to Acumatica's Vendor table. XA's 1099 flag maps to Acumatica's Tax ID type and reporting settings. Remit-to addresses become separate Vendor Locations in Acumatica. Each vendor location can store its own contact name, phone, email, and payment terms; the original XA vendor location code is preserved in a UsrOriginalVendorLoc custom field to support reconciliation and audit trails.

XA item records split into Acumatica's Stock Item (for inventoried parts) and Non-Stock Item (for services and non-inventoried parts). XA's unit of measure conversions map to Acumatica's UOM class and UOM records. If the item carries lot or serial tracking, the lot/serial number assignments and expiration dates are transferred to Acumatica's Lot/Serial master and linked to the stock item's inventory ID, ensuring traceability from receipt to usage.

XA multi-level BOMs map to Acumatica's BOM structure. XA's phantom BOMs (type P) become Acumatica non-stock kit items. BOM rollup costs recalculated in Acumatica's Cost Management module post-migration. Component quantities, scrap factors, and operation step references are also transferred, preserving the original BOM routing so that production scheduling in Acumatica reflects the same material flow and labor assumptions as the XA system.

XA open sales orders map to Acumatica SO Orders with original order dates preserved. XA's order type codes map to Acumatica's Order Type configuration. Lines map with warehouse and inventory ID resolution. Shipping address, freight terms, and any line-level discounts are carried forward; the original XA sales order number is retained in the ExtRefNbr field for cross-reference and audit purposes.

XA open purchase orders migrate to Acumatica PO Orders with the vendor and line structure intact. XA's approval workflow status carries as a custom field if the approval state does not match Acumatica's workflow states. All line items retain the original unit cost, promised date, and UOM; the original PO number is stored in ExtRefNbr for traceability, and any notes or attachments are exported as file links in the Acumatica PO record.

XA work orders map to Acumatica Production Orders. XA operation sequences (labor and machine steps) become Acumatica operations linked to the production order. XA's material allocations map to Material Issues in Acumatica. Each operation captures the work center code, scheduled start and end times, and the labor hours, while material issues record the inventory lot, quantity issued, and the warehouse location, preserving the original XA work order number in the ProductionNbr field for reference.

XA open AR and AP invoices map to Acumatica's AR Invoice and AP Bill records with original posting dates. Closed historical invoices migrate as journal entries in Acumatica's GL if open-item reporting is required. Each invoice line includes the account code, amount, tax amount, and description; the original invoice number is stored in ExtRefNbr for cross-referencing, and any payment terms or due dates are transferred to the Acumatica document's financial tab.

XA GL detail lines map to Acumatica GL Transactions. XA's chart of accounts structure (division/department segments) must be mapped to Acumatica's account segments or subaccount dimension. Multi-segment XA accounts split into Acumatica's Main Account + Subaccount. Every transaction retains the original posting date, source module, and batch reference, and the original XA journal entry number is stored in the ExtRefNbr field for audit traceability and reconciliation against the legacy trial balance.

XA lot and serial number master records map to Acumatica's Lot/Serial tracking at the inventory-item level. XA lot expiration dates carry forward. Active lots link to on-hand quantity records in Acumatica's warehouse. Each lot record stores the original XA lot code in a custom field, and the warehouse location, bin, and receipt date are preserved to support FIFO or LIFO costing layers in Acumatica's inventory valuation.

XA custom fields on any Business Object are exported and re-created as Acumatica Usr-prefixed DAC fields in a Customization Project. FlitStack delivers the field list and data population mapping as part of the migration package. Each custom field is added to the appropriate DAC with a data type matching the original XA definition, and the existing values are imported using the Acumatica REST endpoint with batch inserts, ensuring no loss of historical information.

XA closed sales orders and invoices become historical records in Acumatica. Original transaction dates and amounts are preserved for reporting continuity. History records post to GL as posted batches. Each historical document retains its original document number in the ExtRefNbr field, and any associated line-level tax, discount, or freight amounts are mapped to the corresponding Acumatica financial columns, maintaining audit trail integrity.