Migrate from Open-Prod to Epicor Prophet 21

Open-Prod customer records map to Epicor Customer (company-level) with one or more ShipTo address records (location-level). The Open-Prod customer's primary contact details, payment terms, and credit limits map to Customer fields; shipping addresses become Epicor ShipTo records linked by CustNum. Customer-specific pricing tiers in Open-Prod map to Part/Customer cross-reference records in Epicor if the customer uses customer-specific pricing.

Open-Prod item records (product details, pricing, inventory quantities) map to Epicor Part. The Open-Prod ItemCode maps to Part.PartNum; description maps to Part.PartDescription; UOM from Open-Prod becomes the Part's stocking UOM. Any Open-Prod variant structures (size, color, finish) that use variant matrices map to Epicor PartRev revisions rather than separate Part records, or to a configurable Part where Epicor's Advanced Product Configurator is enabled. Stocking type (make, buy, phantom) requires a decision against Epicor's TypeCode during scoping.

Open-Prod bills of material (multi-level BOM and operating ranges) map to Epicor PartMtl (material lines) and PartOpr (operation sequences). Each BOM level in Open-Prod becomes a PartMtl entry with the material PartNum, qty-per, and bom-sequence, with PartOpr entries capturing operation number, work center, and estimated cycle time. Phantom BOMs in Open-Prod map to Epicor Part.PhantomBOM = true. Material scrap and operation scrap percentages transfer as-is if the customer's Epicor configuration supports those fields.

Open-Prod warehouse-level stock positions map to Epicor PartBin (on-hand quantity per part per warehouse and bin). We extract current inventory snapshots per Open-Prod warehouse location and write them to Epicor Warehse and PartBin records. Open purchase orders and pending shipments in Open-Prod require sequencing after PartBin records are populated to avoid stock discontinuity; we hold these in a pending queue until PartBin stabilization is confirmed.

Open-Prod sales orders and invoices map to Epicor OrderHed (header) and OrderDtl (line). OrderHed captures customer, order date, terms, and ship date; OrderDtl captures part number, quantity, price, and warehouse assignment. Open-Prod invoice records with payment status map to Epicor InvoiceHed and InvoiceDtl. We preserve order lineage (original order number from Open-Prod) as a custom field on OrderHed. Post-migration invoice numbering requires coordination with the customer's Epicor admin to set the correct starting sequence.

Open-Prod purchase orders map to Epicor POHeader and PODetail. Vendor, order date, terms, and expected receipt date transfer to POHeader; line items (part, quantity, cost) transfer to PODetail. Open-Prod supplier price-change tracking in the SRM module maps to VendorPart records in Epicor for part-number cross-referencing at the vendor level.

Open-Prod project records with associated tasks and milestones map to Epicor Project, ProjectPhase, and ProjectTask. Phase billing types (T&M, Fixed Fee, Rate Based) require mapping to Epicor's Project.UseTM, Project.UseFFT, and Project.UseRT fields during scoping. Open-Prod project-linked financial entries map to ProjectCost records in Epicor if the customer uses project costing. We flag any Open-Prod task dependencies as requiring manual review in Epicor's WBS after migration because dependency tracking differs between the platforms.

Open-Prod after-sales service tickets map to Epicor FSM (Field Service Management) records: FSServiceCall for the service ticket header and FSJobStage for task progression. Open-Prod status and priority values map to Epicor FSSched frozen status codes and FSM priority levels. If the destination Epicor instance does not include the FSM module, service records map to Case records in Epicor's standard service layer instead, with a note in the migration scope about module availability.

Open-Prod production orders and job records map to Epicor JobHead (job header), JobOper (operations), and JobMtl (materials allocated). The Open-Prod planned start and due dates map to JobHead.StartDate and JobHead.DueDate; operation scheduling from Open-Prod's planning module maps to JobOper entries with work-center assignments. We migrate open and in-process jobs; completed jobs are candidates for archival rather than full migration given Epicor's performance sensitivity to large job history tables.

Open-Prod resource definitions and work-center configurations map to Epicor WorkCenter and Resource. Labor rates from Open-Prod transfer to WorkCenter.HourlyBurdenCost and WorkCenter.HourlyRate. Shift calendars and capacity settings require manual configuration review post-migration against Epicor's scheduling parameters.

Open-Prod custom fields are not publicly documented in the schema, which prevents automated mapping. During discovery we request direct access to the customer's Open-Prod configuration to enumerate custom field names and data types. Each Open-Prod custom field identified maps to an Epicor UD column (e.g., Character01, Number01) on the equivalent Epicor table. Epicor requires BPM logic to populate UD fields on standard transactions; we document the required BPMs in the migration handoff and the customer's Epicor VAR implements them.

Open-Prod attachment export mechanism is not confirmed in available documentation. We cannot guarantee automated migration of file attachments stored within Open-Prod records. We flag this as out-of-scope until we can validate export capability with the customer's Open-Prod instance. If a confirmed export path exists (direct database query or API export), we can assess file migration into Epicor's EDMS (Electronic Document Management System) as a supplementary engagement.