Migrate from Prowess ERP to Acumatica

Prowess customer records map directly to Acumatica Customer (AR303000 screen). The Acumatica Customer record holds billing address, credit terms, and tax zone. CustomerClassID maps from Prowess customer type. Active/inactive status is preserved. Primary contact details migrate to the Customer's default Contact record.

Prowess vendor master maps to Acumatica Vendor (AP303000 screen). Tax zone, payment terms, and remit-to address are preserved. VendorClassID derives from Prowess vendor category. Remit-to addresses that differ from main address are stored as separate Location records on the Acumatica Vendor.

Prowess inventory items split into Acumatica StockItem (tracked) and Non-StockItem (non-tracked) based on the source's inventory tracking flag. ItemType, class code, and warehouse assignments determine which Acumatica object receives each record. Legacy item codes are stored as a custom field for reporting continuity.

Prowess sales order header maps to Acumatica SOOrder; line items map to SOLine with InventoryID resolved to the Acumatica StockItem/Non-StockItem. Each SOLine carries a COGSAcctID and SalesAcctID resolved from the Prowess item-level account assignments. Order dates, terms, and branch ID are preserved.

Prowess purchase order maps to Acumatica POOrder with line items resolved to POLine. VendorID links to the Acumatica Vendor record created during vendor migration. POLine accounts (ExpenseAcctID) are resolved from Prowess account codes or item-level COGS settings. Approval status from Prowess becomes a custom field since Acumatica handles approvals via workflows.

Prowess BOM structures migrate as Acumatica BOM records with component lines in BOMLine. Where Prowess uses multiple BOM versions per item, each version becomes a separate Acumatica BOM revision identified by revision ID. Phantom BOMs in Prowess translate to the IsPhantom flag on Acumatica BOMLine.

Prowess work orders become Acumatica ProductionOrder records. Prowess's BOM reference maps to the ProductionOrder's BOMID. Production order status (pending, in-progress, completed) migrates as-is; cancelled Prowess work orders default to Cancelled in Acumatica. Labor cost from Prowess is stored as a custom field since Acumatica production orders track labor separately via production labor clock.

Prowess chart of accounts maps to Acumatica Account records. AccountCD is the primary key — must match exactly for COGSAcctID and SalesAcctID lookups on items to resolve. Account Type maps via value list. Parent account references create ParentAccountID lookups; circular references are flagged before migration.

Prowess contact records attached to customers or vendors map to Acumatica Contact records linked via CustomerID or VendorID. Primary flag determines whether the contact is the default Contact on the parent entity. DisplayName, Email, Phone1, and Title migrate directly. Prowess contact notes attach as Acumatica NoteDoc records.

Prowess usr-prefixed custom fields map 1:1 to Acumatica Usr-prefixed custom fields on matching objects. Both platforms use the same prefix convention, so the mapping is name-for-name. Custom field data type, length, and pick-list values are preserved. FlitStack deploys these via Acumatica's Customization Project Editor schema export.

Prowess file attachments linked to orders, items, or customers are downloaded and re-uploaded as Acumatica Files attached to the matching record. File size limits (Acumatica default 25MB per file) are enforced during ingestion. Inline images in Prowess notes are extracted and stored as separate files.

Prowess cost centres split into Acumatica Branches (for operational locations) and Sub-accounts (for cost allocation on GL transactions). The split depends on whether the Prowess cost centre represents a legal entity/warehouse or an expense allocation dimension. Acumatica sub-accounts attach to GL transactions via the SubID field on journal lines.