Migrate from Ridder iQ to Epicor Prophet 21

Ridder iQ Customer and Prospect records map to Epicor Customer (Customer table) with the Party record as the underlying entity. We preserve address, payment terms, and credit limits. Prospects that have not converted to Customers are imported as inactive Customer records flagged for sales team review. Epicor enforces a CustomerGroup and TermsCode on every Customer record, which we set from Ridder iQ's customer category and payment term data. Ship-to addresses map to CustShip records linked to the Customer.

Ridder iQ Supplier master records map to Epicor Supplier (Supplier table backed by a Party record). We preserve contact information, payment terms, lead times, and any associated purchase history as line-item records in Epicor. Supplier holds a RcvryCode reference for incoming inspection routing. If Ridder iQ stores bank details for payment runs, those map to VendorPP records in Epicor.

Ridder iQ Items (raw materials, components, finished goods) map to Epicor Part records. Unit of Measure conversions, cost data (standard, average, FIFO per Ridder iQ), and supplier links migrate as PartPlant and PartWhse records. Multi-UOM items require PartUOM records for each unit; Epicor's UOMClass must be configured to match Ridder iQ's UOM definitions. Parts are marked as Buy, Make, or Phantom based on Ridder iQ's BOM component sourcing flags.

Ridder iQ multi-level BOMs map to Epicor PartMtl (material lines) and PartOpr (operation steps) records. The mapping handles phantom assemblies by setting PartMtl.ProdUOM as Phantom. We flag any item with more than one active BOM variant in Ridder iQ; each variant becomes a separate Part with its own BOM in Epicor. The primary BOM variant is flagged with IsPrimary in PartMtl. Epicor requires PartMtl.QtyPer, PartMtl.MtlBurdenCost, and PartMtl.ScrapFactor to be set; we compute these from Ridder iQ's BOM line quantity and cost data.

Ridder iQ Production Orders (BOM reference, routing, work center, scheduled dates, component allocations) map to Epicor JobHead, JobMtl, and JobOpr records. The PartNum on JobHead links to the Part BOM; JobMtl lines carry material requirements; JobOpr lines carry operation steps with ResourceGroup and ResourceId references to match Ridder iQ's work center assignments. Scheduled start and end dates migrate to JobHead.StartDate and JobHead.DueDate. Open Production Orders migrate as JobHead.JobReleased or JobHead.JobOpen; completed orders migrate as JobHead.JobComplete for historical reference.

Ridder iQ Sales Orders map to Epicor SOHeader and SOLine. Order quantities, due dates, and pricing carry across. Pre- and post-calculation margin data stored per line in Ridder iQ has no native Epicor SOLine field; we preserve margin values in UD fields on SOLine and create an Epicor BPM that recalculates margin against the current cost layer on insert. Order status (open, on-hold, closed) maps to SOHeader.OrderHeld and OrderRel records control shipment releases.

Ridder iQ Purchase Orders map to Epicor POHeader and POLine. Supplier references link via VendorNum; order quantities and due dates migrate directly. BOM-level demand-driven POs carry their demand reference in POHeader.PONum for traceability. Open POs migrate as POHeader.OpenRelease records; closed POs migrate as historical records. POHeader.TermsCode maps from Ridder iQ's payment terms.

Ridder iQ Projects map to Epicor Project records with Phases representing the R&D, engineering, purchasing, and production phases tracked in Ridder iQ. Project budgets, milestones, and cost-tracking data migrate as Phase records with WBS hierarchy. ETO-specific phase sequencing (design, proto, pilot, production) is preserved in Phase.PhaseID. Epicor's Projectha as a Project-based WBS where each phase carries its own revenue and cost pools.

Ridder iQ Invoices linked to Sales Orders map to Epicor ARInvoice records. Invoice headers, line items, and payment reconciliation migrate as ARInvoice and ARInvoiceDetail. Historical closed invoices are imported as posted records (ARInvoice.InvcType = 'Shipment') marked as read-only in Epicor. Payment status and reconciliation data map to ARPayment records linked to the invoice.

Ridder iQ document attachments with version metadata map to Epicor's Document Management records (DocType, DocClass, and file storage path). We migrate document metadata and the current revision file. Epicor stores documents against specific entities (Part, JobHead, SOHeader) via DocType links. We do not migrate full version-diff history; the most recent revision becomes the active file in Epicor. Customers specify whether documents are stored in Epicor's native DMS or in an external SharePoint or network path referenced by Epicor's external storage connector.

Ridder iQ's integrated CRM contacts map to Epicor Person and CustCnt records linked to the Customer Party. Email addresses, phone numbers, and role assignments carry across. If Ridder iQ integrates with Outlook for email and calendar, those contact records are included in the Person migration. The primary contact flag maps to CustCnt.PrimeContact.

Ridder iQ's item cost layers (standard, actual, LIFO, FIFO, multiple costing methods) map to Epicor PartCost records by Plant. Historical cost transactions map to PlantTrans for costing accuracy against current inventory. Epicor's costing engine recalculates moving average and standard costs on receipt and issue; we preserve Ridder iQ's current landed cost and burden rates in UD fields for audit verification.