Migrate from ERPAG to Acumatica

ERPAG customer maps to Acumatica BAccount with Type='Customer'. ERPAG's embedded address fields become a Location record attached to the BAccount. If ERPAG stores multiple ship-to addresses, each becomes a separate Location under the same BAccount.

ERPAG supplier maps to Acumatica BAccount with Type='Vendor'. The supplier's primary address and contact information migrate as the default Location and Contact records attached to the vendor BAccount.

ERPAG items flagged as inventory-tracked become Acumatica StockItem records with ValMethod (valuation method), POItemMax and OTQTY (order quantities), and warehouse-specific quantities as LocationDetails. StockItem.ItemStatus controls whether the item is active or discontinued.

ERPAG items without on-hand tracking become Acumatica NonStockItem records — they appear on purchase and sales documents but do not carry quantity-on-hand. Useful for services, miscellaneous charges, and special-order parts.

ERPAG sales orders map line-by-line to Acumatica SalesOrder SOLine records. Each line references the StockItem or NonStockItem, quantity, unit cost, and discount. Original ERPAG order number stored as a custom field for traceability.

ERPAG purchase orders migrate to Acumatica PurchaseOrder POLine records. Vendor BAccount link established by email match. Lines carry item ID, vendor SKU (if stored in ERPAG), quantity, and cost — all mapped to POOrderNbr sequence.

ERPAG invoices become Acumatica ARInvoice documents. Customer BAccount link resolved before invoice creation. Original invoice number and date preserved as custom fields since Acumatica's RefNbr is the system identifier.

ERPAG vendor invoices migrate to Acumatica APInvoice documents. Vendor BAccount resolved by email match. Line items carry the vendor's item reference from ERPAG where present.

ERPAG quotations require Acumatica's Quotation extension (SMQuote). We map the header and lines to SMQuote and SMQuoteDetail respectively. If the Quotation module is not licensed, quotations migrate as SalesOrder with a 'Quotation' status for reference.

ERPAG work orders map to Acumatica ProductionOrder with ProductionOrderMaint. Material issues and labor entries from ERPAG become ProductionOrderMaterial and ProductionOrderLaborDetail records in Acumatica — preserving original BOM components and production steps.

ERPAG custom fields migrate as Acumatica custom fields with the Usr prefix (UsrCustomField__c). Each requires a Customization Project in Acumatica to define the DB column, DAC field, and form control. Field type mapping: text→PXDBString, number→PXDBDecimal, date→PXDBDate.

ERPAG user and owner IDs resolve to Acumatica Contacts and Users by email match. If an ERPAG owner has no matching Acumatica user, their transactional records attach to a fallback 'Migration User' until a human assigns ownership in Acumatica.