Migrate from Acumatica to Epicor Prophet 21

Acumatica Business Accounts with Customer marked as primary map to Epicor Customer. The Acumatica CustomerClass and CreditTerms map to Epicor CustomerType and PaymentTerms. Address records in Acumatica (Location table) map to Epicor CustomerPriceHdr/CustomerShipTo addresses. We preserve the primary contact name and email as Customer.AllowShipTo changes to no flag. Multi-entity Acumatica customers with separate CompanyIDs may map to separate Epicor companies or to divisions within one Epicor company depending on the customer's chosen organizational structure.

Acumatica Vendors map to Epicor Supplier. AP settings, payment terms, and tax registration IDs transfer to Epicor Supplier rows. Vendor addresses map to Epicor SupplierPriceHdr/ShipVia addresses. If the Acumatica Business Account serves as both Customer and Vendor, we create separate Customer and Supplier records in Epicor linked by the same name.

Acumatica Inventory Items map to Epicor Part records. Stock items carry warehouse-specific AvailabilityQty data that maps to PartWhse OnHandQty by Site and Warehouse. Non-stock items map to Part with TypeCode = Non-Stock. Units of Measure from Acumatica map to Epicor's UOMClass and UOM conversions. The Acumatica ItemClass determines the Epicor Part Class group. AvailabilityQty is derived at migration time by aggregating warehouse-level stock records.

Acumatica BOMs defined on Inventory Items map to Epicor JobMtl and PartMtl (depending on whether the customer uses make-to-stock or make-to-order). We extract the BOM structure with line quantities, scrap factors, and bill sequence, then create Epicor PartMtl records linked to the parent Part. If Acumatica maintains multiple BOM revisions, we migrate the most recent active revision and flag revision history for manual handoff.

Acumatica production routings map to Epicor PartOpSeq (for standard routing definitions) and JobOper (for job-specific operations). Work centers from Acumatica map to Epicor Workstations and ResourceGroups. If Acumatica uses Project-based production with tasks, those map to Epicor JobHead with project-linked job numbering.

Acumatica GL Accounts map to Epicor GLAccount with account class, type, subaccount mask, and active/inactive status preserved. Subaccount segmentation from Acumatica maps to Epicor's segment structure if the customer uses multi-segment account codes. We preserve the account hierarchy and map the AccountClass to Epicor's Category field for reporting grouping.

Acumatica Projects map to Epicor Project with budgets, tasks, and change orders preserved. Project attributes and user-defined fields migrate to Epicor Project-level UD fields. If the Acumatica project uses Project-based billing or revenue recognition, we map those settings to Epicor Project and ProjectPhase billing rules. Project hierarchies with sub-projects map to Epicor ProjectPhase records.

Acumatica Sales Orders map to Epicor OrderHed (header) and OrderDtl (lines). Document status (on hold, pending fulfillment, completed) preserves to allow reactivation in Epicor. Line items carry item, quantity, warehouse assignment, and tax category. Tax calculation settings on customer and inventory item combine to produce the Epicor tax liability on import. Open versus closed status governs whether we import the full history or only open documents.

Acumatica Purchase Orders map to Epicor POHeader and PODetail. Vendor, line items, receipts, and amendments are extracted as related records. Receipts and amendments in Acumatica use separate schemas and migrate as separate linked records in Epicor with appropriate PO line references. Closed PO history migrates if the customer requires it; otherwise we migrate open POs only.

Open AR invoices from Acumatica carry payment schedules, terms, and aging data. We map customer invoices to Epicor AR Invoice with the aging bucket assignments preserved. Historical invoices referencing balance tables require careful sequencing to maintain GL impact. Closed AR history can be migrated as a reference record without posting impact if the customer requires an audit trail.

Open AP invoices from Acumatica map to Epicor AP Invoice with vendor, invoice number, date, and amount. Terms and payment schedules transfer. GL batch references from Acumatica map to Epicor GL Journal entries for reconciliation. We flag any prepayment or credit memo records that require separate handling in Epicor's prepayment workflow.

Acumatica Employee records include compensation history, department assignments, and timecard data. Employment status, job titles, and earning codes preserve. Effective-dated rows (such as compensation changes) migrate as separate records with the effective date carried forward. We map the Acumatica Department to Epicor Class for labor reporting.

Acumatica Warehouse records with bin structures map to Epicor Plant (Site) and Warehouse. Each Acumatica warehouse with bins becomes an Epicor Site with one or more Warehouses containing Bin records. Warehouse assignments on inventory items map to PartWhse records linking Part to Site and Warehouse.

Acumatica UDFs on any entity (Business Account, Vendor, Inventory Item, Project, etc.) use the extension DAC pattern and appear under a 'custom' namespace in the REST API. We discover all UDF definitions via the entity schema endpoint before building field mappings. Each UDF maps to an Epicor UD field on the equivalent entity, with Acumatica CustomStringField, CustomDateField, and CustomNumberField types mapped to Epicor string, date, and number UD field types.

Acumatica Note text and file attachments stored in the separate Note and NoteDoc tables are not first-class API entities. We extract note content, entity reference (EntityID plus EntityType), and NoteDoc binary files separately, then re-link them in Epicor using the DocReference table or embedded note fields on the target entity depending on Epicor's configuration.