Migrate from ERPAG to Epicor Prophet 21

ERPAG Items map to Epicor Part records with PartNumber derived from the ERPAG SKU, Description from the Item name, and UnitCost from the current standard cost. ERPAG's cost and price fields translate to Part.StandardBurdenCost, Part.StandardLaborCost, and Part.StandardMaterialCost on the manufacturing cost roll. Stock levels per warehouse migrate to PartWhse records, one per ERPAG warehouse, with OnHandQty and BinCode resolved. We handle any phantom negative quantities from ERPAG's concurrent-write glitch by applying the Repairs and Maintenance fix before extracting stock data.

ERPAG Customer records map to Epicor Customer with CustID derived from the ERPAG customer code, Name from the company name, and Address fields mapped to the primary billing address. ERPAG's financial overview fields (credit limit, payment terms) migrate to Customer fields. ShipTo addresses migrate as CustomerShipTo records linked to the parent Customer. We resolve any B2B portal assignments from ERPAG as notes for the customer's admin to configure in Epicor Customer Connect or a portal equivalent.

ERPAG Suppliers map to Epicor Supplier with SupplierID derived from the ERPAG supplier code. ERPAG's double-SKU fields, which store the supplier's own SKU alongside ERPAG's internal SKU, migrate to Epicor's Supplier Part Cross Reference table (PartXRefRef) as part of the same migration pass. Purchasing terms and payment terms map to the Supplier record's standard fields. We preserve the cross-SKU mapping so that future purchase orders in Epicor can reference supplier part numbers directly.

ERPAG Sales Orders map to Epicor OrderHed (header) and OrderDtl (line) records. The ERPAG payment_status column is preserved as an OrderHed field. Line items map with Quantity, UnitPrice, and the ERPAG Item SKU resolved to an Epicor PartNum. We migrate open and recently closed sales orders; fully historical orders beyond the reporting window are flagged for archival rather than live migration to avoid performance load in Epicor.

ERPAG Invoices map to Epicor InvoiceHed and InvoiceDtl with InvoiceNum as the reference, Customer mapped to CustNum, and invoice totals mapped to open or closed status fields. Tax amounts and currency from ERPAG's localization settings are preserved as-is, noting that ERPAG's currency and tax code settings are frozen at company initialization and do not retroactively rewrite historical documents.

ERPAG Purchase Orders map to Epicor POHeader and PODetail. The double-SKU entry (ERPAG SKU + supplier SKU) is resolved using the PartXRefRef table created during the Supplier migration pass. Goods-received state from ERPAG maps to PODetail.ReceivedQty. We flag any ERPAG Purchase Orders in pending or draft state for the customer's Epicor admin to review before finalizing.

ERPAG Quotations map to Epicor QuoteHed and QuoteDtl with validity dates, pricing, and custom fields preserved. Quotation line items resolve Item SKUs to Epicor PartNums. ERPAG's quotation-to-sales-order conversion history is noted as a data point for Epicor's quote-to-order workflow rebuild.

ERPAG Work Orders map to Epicor JobHead, with estimated materials sourced from ERPAG's BOM references, estimated labor from ERPAG's cost fields, and actuals preserved for job costing. ERPAG's production status maps to JobHead.JobClosed, JobHead.JobComplete, or JobHead.JobEngineered. Estimated vs. actual cost fields migrate as JobMtl and JobOper cost fields. For work orders without BOM references in ERPAG, we flag for manual routing assignment in Epicor before migration closes.

ERPAG BOMs map to Epicor PartMtl records. Single-level BOMs from ERPAG map directly to one PartMtl parent per BOM. Multi-level nested BOMs in ERPAG (if present in Advanced-plan accounts) are expanded and reconstructed as a hierarchy of PartMtl records with the correct ParentPartNum and MtlPartNum references. ERPAG BOM revision tracking maps to Epicor's revision control on Part. If ERPAG BOMs use sub-assemblies not present as standalone parts in Epicor, we flag them for BOM-level review before import.

ERPAG Warehouses map to Epicor Site (the facility or plant level) and Warehse (the physical warehouse within a site). ERPAG's per-warehouse tax settings, currency, and price list settings are documented as configuration notes for the customer's Epicor admin to apply at the Site or Company configuration level, since these are company-initialized settings in Epicor that do not retroactively rewrite imported data.

ERPAG Custom Fields (up to 15 per document type) map to Epicor User Defined Fields (UDFs) or Extended User Defined Fields depending on the ERPAG custom field type (Free text, List, Amount, Price, Date, Date and time). Custom Tables defined via ERPAG's Custom Table feature (introduced 2025) require schema review to determine whether they map to Epicor UD Codes, a custom table, or a related entity. Custom fields are Advanced-plan exclusives; we verify plan tier during scoping and flag any Advanced-gated objects that appear in the data inventory.

ERPAG Users map to Epicor Users with username, email, and active/inactive status preserved. Role-based permissions from ERPAG document restrictions and general restrictions are exported as scope notes for the customer's Epicor admin to rebuild using Epicor's Security Manager and Role configuration. Active vs. inactive status determines whether the user is provisioned as active in Epicor or held in a provisioning queue.

ERPAG's per-warehouse stock levels (OnHandQty, reserved quantity, available quantity) for each Item map to Epicor PartWhse records, one per warehouse-site combination. Bin locations from ERPAG map to PartBin records if Epicor's warehouse management configuration is active. We detect and repair any phantom negative quantities during the export phase before PartWhse records are created in Epicor.

ERPAG supplier-specific pricing guidelines (per-item price breaks by quantity tier) map to Epicor Supplier Price List records linked to the Supplier and Part. ERPAG's multi-warehouse pricelists require separate scoping if the customer uses Epicor's per-site price list configuration.