Migrate from ManEx to Acumatica

ManEx vendor master (name, address, payment terms, tax ID) maps directly to Acumatica's Vendor table (VendorID, VendorName). We use VendorID as the Acumatica key and preserve the original vendor code as VendorRefNbr for reconciliation. Vendors without tax IDs get a default tax zone applied from the Acumatica tax configuration.

ManEx customer records map to Acumatica Customer by name and contact details. The Acumatica customer class (Price Class ID) is set based on the revenue tier from ManEx's customer record. Multi-contact customers are handled via the Contact screen with the CustomerID relationship; we create the primary contact as the billing contact.

ManEx inventory items map to Acumatica's InventoryItem table keyed by ItemID (InventoryCD). The UOM, UOM class, and valuation method are derived from ManEx's unit of measure and cost layer. Lot/serial tracking settings are enabled in Acumatica if ManEx tracks them. Item class is used to set the default posting class for GL account defaults.

ManEx UOMs (each, foot, reel, etc.) map to Acumatica UOM records within a UOM Class. We create the UOM Class first in Acumatica with the base UOM, then populate all ManEx UOMs as conversion rows. Stock item UOMs vs. sales item UOMs are separated into distinct UOM Class instances.

ManEx BOMs use a header row with component lines and operation sequence. In Acumatica, each BOM becomes a BOMRevision record with a RevisionID, effective dates, and a MaterialMstxn component table. The operation sequence from ManEx maps to the OperationID sequence in Acumatica's production routing. We preserve the BOM revision number as the Acumatica RevisionID for traceability.

ManEx work orders map to Acumatica Production Orders (ProductionOrderNbr). The production status in ManEx (Pending, In-Process, Complete) maps to Acumatica's Production Order status field (Pending, In Process, Completed, Closed). The component issue and labor recording are preserved as MaterialMstxn and LaborMstxn lines linked to the Production Order.

Open ManEx purchase orders become Acumatica Purchase Orders with status reflecting the current approval and fulfillment stage. Line items map to POLine with InventoryCD lookup, UOM, quantity, and basecury amount. The PO type (Standard, Drop-ship, Blanket) is set based on the ManEx PO type code. Completed ManEx POs migrate as historical records attached to the receiving transaction.

ManEx AP invoices map to Acumatica APInvoice (AP301000 screen). Reference numbers, vendor IDs, invoice dates, due dates, and amounts transfer directly. The GL batch number from ManEx is stored as a custom reference field on the Acumatica invoice. Hold status in ManEx becomes Hold = True in Acumatica until approved through the AP Approval Matrix.

ManEx GL accounts map to Acumatica Account records using a value-by-value account code mapping table. Where ManEx uses segment-based account codes (e.g., 4100-01), we create Acumatica accounts with the equivalent account code and map the cost center to the Acumatica Subaccount dimension. This ensures the trial balance from ManEx posts to the correct Account + Subaccount combinations in Acumatica.

ManEx approval workflow definitions (conditional routing by document type, dollar threshold, and role) have no direct Acumatica equivalent. We extract the workflow rules as a structured document and surface them in the migration plan as a rebuild reference for Acumatica's Approval Matrix screen under Configuration. Document-level approval chains (AP Invoice, PO) require manual configuration in Acumatica's system by the admin.

Any ManEx custom fields on vendors, customers, or inventory items are preserved as Acumatica custom fields with a Usr prefix (e.g., UsrCustomerGroup, UsrOriginalSystemID). We document each custom field's data type and create the corresponding field in Acumatica's Customization Project before data loads. Value pick-list fields use Acumatica's predefined list with the original ManEx values restored.

ManEx fiscal periods map to Acumatica Financial Period records. We ensure all ManEx periods (open and closed) exist as periods in Acumatica so historical AP invoices and work orders post to the correct period. Closed ManEx periods are set to Closed = True in Acumatica to prevent accidental posting back to them.

ManEx lot numbers and serial numbers map to Acumatica's LotSerialNbr field on InventoryReceipt and InventoryIssue transactions. If ManEx tracks lot expiration dates, those migrate as Lot/Serial class attributes in Acumatica. The lot number is preserved as the primary key for traceability linking back to the ManEx record.