Migrate from Standard ERP to Epicor Prophet 21

Standard ERP's structured GL chart with parent-child hierarchy, account type, currency, and cost-center assignments maps to Epicor GL Account with a matching segment structure. We preserve account numbers, descriptions, account type, and the hierarchy parent reference. Cost-center assignments from Standard ERP map to Epicor GL Account Allocation Code or Reporting Category depending on the destination company's reporting structure. Active/inactive status transfers as-is.

Standard ERP customer records including billing/shipping addresses, payment terms, credit limits, and contact associations map directly to Epicor Customer. Customer-specific pricing tiers transfer as Price List assignments in Epicor. ShipTo addresses migrate as Customer ShipTo records linked by CustNum. Payment terms and credit hold status map to Epicor Customer tables with the same effect at go-live.

Standard ERP vendor master records including bank details, 1099 flags, W-9 status, and purchase terms map to Epicor Supplier. Vendor address formats are validated against Epicor's country-specific requirements during import. Remit-To addresses migrate as Supplier RemitTo records. PO approval limits transfer as Supplier PPBuyer authorization levels.

Standard ERP items (inventory, non-inventory, service) map to Epicor Part records with type preservation (Stock, Non-Stock, Service). The Standard ERP item number becomes Epicor PartNumber. Unit of measure, weight, dimension, and lot/serial settings transfer as Part UOM, PartWhse, and PartClass assignments. Item image references map to Epicor's attached document model if the Standard ERP export includes file paths.

Standard ERP BOM structures with multi-level component linkages map to Epicor PartRev records with revision control. Each BOM level becomes a PartRev revision; component quantities and scrap percentages transfer as PartMtl records linked to the parent revision. Phantom BOM logic from Standard ERP maps to Epicor's Phantom BOM flag on PartRev. We preserve the BOM effective date and any alternate BOM routing assignments.

Standard ERP production orders with BOM linkages, routing, work-center assignments, and actual versus estimated costs map to Epicor Job records. The production order header becomes JobHead; lines and material requirements become JobMtl; operations and routing become JobOper. Estimated costs transfer as JobHead.EstLaborHrs and JobMtl.EstQty; any actual costs incurred at time of migration transfer to preserve job cost history. Open production orders migrate with status preserved so manufacturing can resume without re-entry.

Standard ERP work centers with capacity, efficiency, and calendar assignments map to Epicor Resource Group. Resource Group shifts, calendars, and queue and overlap settings transfer. Labor rates assigned to Standard ERP work centers map to Resource Group default rates. Work Center Group assignments from Standard ERP become Resource Group parent hierarchies.

Standard ERP job costing linking labor, materials, and overhead to specific projects maps to Epicor Project (for quote-to-cash project tracking) or Job (for discrete production costing). Phase-level breakdowns transfer as Project Phases with WBS coding. If Standard ERP uses a separate project ledger for job costing, we map it to Epicor Project Cost Categories for earned-value tracking. The customer's Epicor edition determines whether Project module is in scope.

Outstanding invoices, credit memos, and payments are extracted from Standard ERP with full aging detail and linked to corresponding GL entries for reconciliation. Open AP documents map to Epicor APTran and APHead records; open AR documents map to Epicor ARInvoice and ARC发了 records. Payment terms, due dates, and aging buckets transfer so that cash forecasting and collections workflows remain intact. We validate that the AP/AR net balances reconcile to the GL after migration.

Standard ERP closed-period journal entries map to Epicor GL JrnHdr and GL JrnLine records. Locked fiscal periods on Standard ERP require coordination with the customer's IT team for temporary reactivation or migration as current-period adjustments. Exchange rate effective dates transfer so that historical rate reconstruction is auditable. We flag any journal entries that cannot balance due to source system cleanup as exceptions for manual posting.

Open vendor invoices with line items, GL distributions, and tax allocations map to Epicor AP Invoice. Prepayments and retainage amounts transfer as separate invoice lines. Invoice images stored in Standard ERP's document vault migrate as attached documents linked to the corresponding AP Invoice record via filename-to-record-ID mapping.

Standard ERP document vault attachments use a proprietary internal format requiring HAL-scripted extraction or direct database query. We export vault packages as file packages and associate them with the corresponding migrated records in Epicor using a filename-to-record-ID cross-reference table built during discovery. Large attachment volumes require staged transfer with retry logic. Epicor stores attachments in Kinetic Content or DocStar ECM.

Standard ERP user accounts, roles, and permission sets map to Epicor User records. We create a role-mapping matrix that maps Standard ERP role names to Epicor Security Role assignments. Any permissions without a direct Epicor equivalent go to a reconciliation list for the customer's admin to configure post-migration. The migration user performing the data load must have sufficient Epicor role grants to write to all target tables.