Migrate your Agility ERP data

Customers map directly to the destination system's Account or Customer record. Address, contact name, and payment terms transfer as standard fields. We validate email format and flag duplicate customer names during import scoping.

Vendor records including remit-to addresses, tax IDs, and payment terms move 1:1. We check for duplicate vendor names across the import set to prevent double-creation in the target ERP.

Open orders transfer as line items with quantity remaining and order date. Status mapping is required because Agility ERP uses a different status vocabulary than most destination ERPs — we align them via a status lookup table built during discovery.

Same status-mapping logic applies as for sales orders. Line-level purchase order data transfers with supplier reference fields retained for audit trail continuity.

Items carry cost layer data (average, FIFO, or lot cost) that requires explicit mapping to the destination's costing method. Stock on hand and reorder point values transfer but may require re-evaluation against the target system's valuation logic.

Account codes, descriptions, and classification (asset, liability, expense, revenue) move across. Account numbers that exceed the destination's character limit are flagged and renumbered during the scoping call.

Fixed asset records including depreciation schedules are not accessible via the Agility ERP standard export layer. Customers with significant asset bases need a custom extraction from the underlying database, which must be coordinated with the Agility ERP support team separately.

Historical journal entries transfer as memo-line records. We flag entries that contain embedded account IDs from the legacy chart of accounts and remap them to the new GL structure before loading.