Migrate from Relic ERP to Epicor Prophet 21

Relic ERP Part Master records map to Epicor Part table (Part). We preserve PartNumber as the dedupe key, with PartDescription, TypeCode (stock vs. non-stock vs. service), ClassID, and UOM defaults migrating directly. Relic ERP's commodity codes and product categories map to Epicor's ClassID and ProductGroup fields. If Relic ERP stores Revision records, these migrate to Epicor's PartRev table with approval statuses preserved.

Relic ERP BOMs map to Epicor PartRev (header: part, revision, effectivity dates) and PartMtl (lines: material part, qty per, scrap %). If Relic ERP supports BOM substitutions or multi-level BOM nesting, we flatten or preserve nesting based on the customer's engineering practice. Revision-controlled BOMs require PartRev approval status mapped from Relic ERP's revision workflow.

Relic ERP production job headers map to Epicor JobHead with JobNum as the primary key, JobEngineered and JobReleased status preserved, and Plant/warehous assignment. JobHead.JobReleased maps to a Phase or status field in Relic ERP's equivalent. We resolve the parent SalesOrder and PartNum links at migration time to maintain job-to-order traceability.

Relic ERP material allocations map to Epicor JobMtl with MtlPartNum, RequiredQty, and IssuedQty preserved. If Relic ERP tracks material backflush behavior, that maps to Epicor's Method of Mtl Control flag. Excess material returns and substitutions migrate as separate JobMtl records with adjustment quantities.

Relic ERP operation sequences and labor entries map to Epicor JobOper (operation routing steps) and LaborDtl (actual labor transactions). We preserve labor reporting dates, employee references, clock-in/clock-out duration, and any operation-level actual times against the standard times defined in JobOper. WIP posting dates migrate to Epicor's LaborDtl.GLDate for period accuracy.

Relic ERP WIP balances map to Epicor PartWip records (part, quantity, plant, warehouse, lot, jobnum, and bin). We validate WIP quantities against the final LaborDtl and JobMtl totals to ensure that the WIP layer reflects the closed Job state. Post-migration, Epicor's costing engine recalculates WIP value from labor and material detail if the customer enables that option.

Relic ERP Sales Order headers map to Epicor OrderHed with OrderNum as the key, CustomerNum linked to the customer mapping, and order dates, terms, and freight terms preserved. Relic ERP's order types map to Epicor OrderHed.OrderUM and a configured OrderRel dropdown. Open vs. closed status migrates as OrderHed.OpenOrder.

Relic ERP shipment schedules or order lines with delivery dates map to Epicor OrderRel. We resolve the Release fields including DueDate, Warehouse, bin, lot, and the relsutd-quantity against the open quantity remaining. If Relic ERP tracks multi-address fulfillment, each release captures the ship-to address with the OrderRel record.

Relic ERP customer records map to Epicor Customer with CustID as the dedupe key. Address, payment terms, credit limit, sales territory, and shipping method fields migrate directly. If Relic ERP maintains a separate ship-to address table, these map to Epicor CustCnt or a separate Address table with the Customer link preserved.

Relic ERP vendor records map to Epicor Vendor with VendorID as the dedupe key. Address, payment terms, 1099 flag, WIP warehouse assignment, and default AP account migrate directly. Purchase ordering preferences from Relic ERP (FOB point, shipping method, tax code) map to Epicor's VendorPP table for per-vendor PO defaults.

Relic ERP PO headers and lines map to Epicor POHeader and POLine. We preserve PO status (open, released, closed), line status, PromiseDate, and quantities. If Relic ERP has landed cost tracking or multi-vendor POs, we align to Epicor's PORel granularity for partial receipt tracking.

Relic ERP inventory movements (receipts, issues, adjustments, transfers) map to Epicor PartTran. We preserve the transaction date, quantity, from/to warehouse and bin, lot number, unit cost, and GL posting reference. Multi-site inventory requires plant-level PartTran records with Plant and WarehseCode fields populated from the Relic ERP location hierarchy.

Relic ERP GL entries map to Epicor GLJrnLine with FiscalYear, FiscalPeriod, JournalNum, JournalLine, AccountNum, DebitAmt, CreditAmt, and TranDesc preserved. We validate that Epicor's fiscal period calendar aligns with Relic ERP's fiscal structure before migration. If Relic ERP uses segment codes in its account string, we map these to Epicor's Chart of Accounts dimension structure.

Relic ERP AP invoices map to Epicor APInvHed and APInvDtl with vendor reference, invoice date, due date, and line amounts preserved. Prepayments and credit memos migrate as separate APInvHed records with negative amounts. If Relic ERP tracks 2-way or 3-way PO matching, we configure Epicor's AP matching settings post-migration.

Relic ERP AR invoices map to Epicor InvcHead and InvcDtl with customer reference, invoice date, due date, and line amounts preserved. Open invoice vs. paid status migrates as InvcHead.OpenInvoice. If Relic ERP tracks customer payments and cash receipts separately, we map these to Epicor's CashHead and ARPayDT tables with payment applied to the correct invoice.

Relic ERP custom UD fields and extended tables require systematic discovery during scoping before extraction design begins. Most Relic ERP instances have undocumented UD columns on standard tables that hold business-critical data (freight cost, regional codes, custom dates). We use SQL catalog scans and BAQ inspection to enumerate all UD fields and custom tables, then map each to Epicor's UD table equivalents (UD01-UD10) or extended property fields with matching data types and length constraints.