Migrate from Agility ERP to Epicor Prophet 21

Agility ERP Customer records map directly to Epicor ERP Customer (or to Epicor Customer and ShipTo depending on whether the customer has multiple ship-to addresses). We extract the customer name, address, remit-to address, payment terms, tax ID, and contact information. Email format validation runs against the migrated set, and any duplicates based on customer name or tax ID are flagged before Epicor insert. Epicor Customer requires a CustNum assigned by the system at insert time; we track the Agility ERP customer ID to CustNum mapping for use as a lookup reference on Order and Invoice records.

Agility ERP Vendor records map to Epicor ERP Vendor with remit-to address, tax ID, and payment terms transferred as standard fields. We check for duplicate vendor names across the import set to prevent double-creation. Epicor Vendor also requires a VendNum assigned at insert; we maintain the Agility ERP vendor ID to VendNum mapping as a lookup reference for Purchase Order imports.

Agility ERP open sales orders transfer to Epicor ERP Sales Order with line items, quantity remaining, order date, and pricing preserved. The Agility ERP order status vocabulary (Open, Released, Backordered, and any customer-specific labels) must be translated to Epicor's order status codes during a discovery-phase lookup table we build specifically for each migration. Order header and line-level discounts, freight terms, and shipping instructions transfer to the corresponding Epicor order fields.

Open Agility ERP purchase orders migrate to Epicor ERP Purchase Order using the same status translation logic as sales orders. Line-level supplier reference fields, lead times, and receiving instructions transfer to the Epicor PO for audit trail continuity. The Agility ERP supplier reference on each PO line maps to Epicor's POLine.PurPoint or supplier part number fields.

Agility ERP inventory items map to Epicor ERP Part records with stock on hand, reorder point, and cost layer data (average, FIFO, or lot cost) carried across. Agility ERP uses its own costing method per item; Epicor Kinetic supports Average, FIFO, and Standard costing, and we evaluate whether the source costing method maps cleanly to the destination method or requires a cost revaluation entry post-migration. Lot and serial number traceability migrates where present in the source data.

Agility ERP BOMs map to Epicor Kinetic Bill records with parent-part, component, quantity-per, operation sequence, and work center references resolved. Epicor Kinetic supports multi-level BOMs and configure-to-order; we validate that every Agility ERP BOM parent has a corresponding Epicor Part record before inserting, and we flag any BOM that references a component not yet migrated. Routing records (work centers, labor and machine rates, setup and run times) map to Epicor JobMOps records linked to the parent Job or Bill. This is one of the highest-risk object mappings because BOM hierarchies with 10+ levels require careful parent-child ordering and component resolution before any Epicor insert runs.

Agility ERP GL account codes, descriptions, and classification (asset, liability, expense, revenue) migrate to Epicor ERP GL Account records. Any Agility ERP account code that exceeds Epicor's character limit is flagged during scoping, renumbered against a mapping table we create during discovery, and validated against Epicor's account segment structure. The mapping table is delivered alongside the chart of accounts import so the customer's finance team can audit and update it post-migration.

Historical Agility ERP journal entries transfer to Epicor ERP GL Journal as memo-line records. Entries that contain embedded account IDs from the legacy chart of accounts must be remapped to the new Epicor GL structure before loading. We run the remapping transform against the full journal history and flag any entry where the original account code cannot be resolved to an Epicor GL Account number.

Agility ERP does not expose fixed asset records through its standard export layer or API. Customers with active depreciation schedules must request a direct database extract from Agility ERP support before migration begins, which may require a separate professional services engagement with DMSI. We flag any customer with a non-zero fixed-asset balance during scoping and coordinate the custom extract timing so the data arrives before the migration window. The extracted asset records are then mapped to Epicor Fixed Asset records including depreciation schedules, asset class, and book values.

Agility ERP stores custom fields in a non-standard extension table that requires field-by-field review to determine which fields map to Epicor UD (User-Defined) fields on the corresponding Epicor table and which require a separate custom table. Epicor Kinetic supports UD01-UD19 fields and custom Z-Table fields, but post-import population of UD fields often requires a BPM (Business Process Management) rule because the data cannot always be loaded directly through the standard import tools. We document every custom field, its Agility ERP data type, and the recommended Epicor target, and we advise on whether a BPM is needed for post-import population.

Agility ERP sites or warehouse locations map to Epicor ERP Site records. If Agility ERP has multiple facilities managed as separate inventory locations, each maps to a corresponding Epicor Site with its own warehouse, bin location structure, and transit time settings. Epicor Kinetic's multi-site architecture requires site assignment before inventory records can be imported.

Agility ERP work orders with outstanding quantities transfer to Epicor ERP Job records. JobNum, part number, quantity to build, job date, and assembly sequence map across. Epicor Job records carry the production routing, work center assignments, and labor estimates; if the Agility ERP work order references a BOM and routing, those records must be migrated first so that the Job can reference them. Outstanding jobs with partially completed operations transfer with the completed operation history preserved.