Migrate from Agility ERP to Acumatica

Agility ERP maintains separate Customer and Vendor record types. Acumatica consolidates these into BusinessAccount with a ClassID field toggling Customer / Vendor status. The primary address, contact info, and payment terms migrate as BusinessAccount attributes; secondary addresses migrate as separate Address records linked by the AddressID foreign key.

Vendors from Agility ERP map to BusinessAccount records with ClassID set to 'VD' (vendor class). Vendor-specific fields like W-9 status and 1099 eligibility migrate to Acumatica's Tax settings on the BusinessAccount. If a vendor is also a customer, two BusinessAccount records are created and cross-referenced.

Contact records map directly to Acumatica's Contact DAC. The Contact2Account link (CR202010) associates each contact with a BusinessAccount. Multiple contacts per account are supported natively in Acumatica, matching Agility ERP's contact-per-customer model. Contact titles and department assignments migrate as custom fields if non-standard.

Agility ERP sales orders map to Acumatica's SOOrder screen (SO301000). The OrderNbr, OrderDate, CustomerID, and status fields migrate directly. Each line item maps to SOLine with InventoryID, WarehouseID, and UOM resolved from the inventory master. Tax calculations are recreated based on Agility's tax-code definitions mapped to Acumatica's Tax Zone configuration.

Purchase orders migrate to Acumatica's POOrder DAC (PO301000). VendorID resolves to the BusinessAccount vendor record created in step 20. Line items map to POLine with the same InventoryID and UOM resolution logic as sales orders. Prepaid and drop-ship flags map to Acumatica's shipment settings per line.

A single Agility ERP inventory record splits into an InventoryItem master (item class, description, UOM, standard cost) and separate WarehouseDetails rows per stocking location. The primary warehouse from Agility becomes the default WarehouseID on the InventoryItem. Secondary locations are inserted as additional WarehouseDetails records linked by InventoryID.

Agility ERP's flat numeric-segment chart of accounts maps to Acumatica's Account + Subaccount dimensional model. Each unique segment value in Agility creates a corresponding Subaccount record in Acumatica. The first segment typically becomes the Account number; remaining segments are combined into a Subaccount mask. This mapping is defined in the migration plan before any GL batch inserts run.

Accounts payable invoices from Agility ERP (vendor bills) map to Acumatica's APDocument with DocType='INV'. The VendorID resolves to the BusinessAccount record. Line items reference GL accounts mapped in step 70. Historical AP balances are preserved as opening-balance AP documents with DocType='PPM' (prepayment) if needed for account reconciliation.

Accounts receivable invoices from Agility ERP map to Acumatica's ARDocument with DocType='INV'. The CustomerID resolves to BusinessAccount. Payment terms, due dates, and aging buckets are recalculated based on Acumatica's terms configuration. Open AR balances migrate as opening-balance AR documents for continuity in aging reports.

Agility ERP file attachments linked to orders, inventory items, or accounts are downloaded and re-uploaded to Acumatica's NoteDoc entity. The NoteID links back to the migrated parent record (SOOrder, InventoryItem, or BusinessAccount). File size limits follow Acumatica's 25MB per file threshold; larger files are flagged for chunked upload.

Agility ERP custom properties on any entity migrate as Acumatica UDFs with the Usr prefix on the DAC field name. Each UDF must be pre-created in Acumatica's Customization Project editor before the migration run executes. FlitStack AI generates the UDF creation plan as part of the schema setup deliverable. Custom properties on non-standard entities (e.g., custom objects) map to custom DACs in Acumatica.

Agility ERP approval matrices and workflow rules (e.g., PO approval thresholds, order-hold conditions) have no direct equivalent in Acumatica's screen-based workflow system. FlitStack AI exports the rule definitions as a configuration reference document, and the Acumatica admin rebuilds them in the Workflow Editor using the exported logic as a specification.