Migrate from Encompass Production Cloud to Epicor Prophet 21

Encompass Batch records are the primary production unit, linking to a Bill of Materials, production schedule, ingredient lot assignments, and finished-goods inventory. We map Batches to Epicor JobMtl and JobOper records where each Job is associated with a Part number and a Revision (revision-controlled BOM equivalent). Because Epicor is a discrete manufacturing ERP, batch quantities and production dates map to JobHead StartDate and ReqDueDate. We flag any batch that uses process-manufacturing attributes (TTB alcohol content, fermentation temperature logs) as requiring a custom field or QC record rebuild in Epicor's Quality Management module.

Encompass BOMs define recipe formulations with ingredient quantities, unit-of-measure conversions, and cost allocations. We extract all BOM versions and present the customer with a versioning strategy decision: migrate active BOM only or include historical recipe variants for reformulation audit traceability. In Epicor, BOMs become Part BOM entries linked to a Part number with a Revision code. The Epicor Revisions module tracks ECO-level changes that serve as the equivalent of Encompass BOM version history. We map Encompass ingredient items to Epicor Part records with the correct unit-of-measure class before BOM import.

Encompass Production Schedules capture planned run quantities, start/end times, and assigned resources. Epicor Job records capture the same fields via JobHead.StartDate, JobHead.DueDate, and JobHead.JobQty. Resource assignment in Epicor maps to the Labor table and optionally to the MES module if the destination has Epicor MES configured. The scheduling granularity difference (Encompass uses segment-level routing; Epicor uses work centre routing) requires a work centre mapping step during discovery.

Encompass Inventory Lots track raw materials and finished goods with quantity, location, cost, and TTB-relevant attributes. We migrate lot records with full genealogy chains to Epicor PartLot records, preserving lot number, lot effdate, and lot attributes. Finished-goods lots attach to the Part number created from the related Batch. The destination PartBin records capture the on-hand quantity and warehouse location. We validate that ingredient lots and finished-goods lots form closed genealogy circles in Epicor's lot traceability view before confirming migration completeness.

Encompass Production Variances capture planned vs. actual consumption for each batch run, including material usage, labour time, and yield discrepancies. Variance records are keyed to parent Batch ID. We map these to Epicor JobOper fields (EstSetQty vs. ActSetQty for labour) and Part transactions for material usage. Where Encompass stores a named variance value (favourable/unfavourable delta), we store it as a decimal in Epicor's JobAsmbl and JobMtl tables and reconstruct the variance report in Epicor GL or a reporting tool post-migration.

QC records in Encompass include inspection checkpoints, pass/fail results, and corrective actions tied to specific batches. The Epicor Quality Management module provides non-conformance tracking, inspection recording, and corrective action workflows. We map Encompass QC records to Epicor Quality data classes and inspection templates, but the schema for QC fields varies by Encompass tier and add-on configuration, so we assess the complete QC field set during discovery and design the Epicor QC template accordingly. Any TTB-mandated checkpoints require manual rebuild as Quality Management rules in Epicor.

Encompass Sales Orders link to inventory allocation and production demand signals. We map order headers to Epicor SalesOrder with OrderDtl line items, pricing, and fulfilment status. Orders in partial-ship status require careful status mapping to Epicor's OrderRel records. Epicor's Available-to-Promise (ATP) logic recalculates on import, so we preserve the original committed date as an OrderDtl user-defined field rather than relying on post-import ATP recalculation for historical orders.

Open and historical purchase orders in Encompass with vendor assignments, line items, expected delivery dates, and received quantities are extracted to Epicor POHeader and PODetail. We flag any PO-to-receiving linkage that may break if inventory lots were received against Encompass lots that do not map cleanly to Epicor PartLot numbers, and we surface this to the customer for a receiving reconciliation decision before import.

Encompass inventory balances migrate to Epicor PartBin (on-hand quantity per warehouse) and PartLot (lot-level detail). We reconcile total raw material value and finished-goods value to Encompass's inventory valuation report before and after import. Any lot attributes specific to beverage production (fermentation vessel ID, mash bill lot reference, barrel house location) migrate as custom PartLot attributes in Epicor. Post-import, Epicor's standard cost rollup recalculates based on BOM and routing, which may differ from Encompass's COGS calculation; we document the delta for the customer's finance team.

Encompass finance module accounts define the cost structure for COGS, labour, overhead, and revenue recognition. Account numbers and segment structures vary by company, so we map account IDs from Encompass to Epicor GL Account records and require a customer-provided account crosswalk. Epicor's Account Segment functionality supports multi-segment account strings (e.g., Division-Department-Account) that mirror the Encompass structure if configured. We do not migrate closed GL periods as posted entries; we deliver a written account map for the customer's Epicor admin to configure in the GL module before go-live.

Open payables and receivables in Encompass carry customer/vendor IDs, invoice amounts, due dates, and payment terms. These require careful reconciliation against the customer/vendor master records already migrated into Epicor. We map APOpen invoices to Epicor's vendor-based payable records and OROpen invoices to customer-based receivable records. Any Encompass-specific invoice numbering conventions are preserved as user-defined fields. Open transactions with unmatched GL accounts are held in a reconciliation queue until the customer provides a GL account mapping decision.

Encompass user accounts map to Epicor User records and security roles that control access to production, QC, and finance modules. We extract role assignments from Encompass and map them to Epicor's Plant/Organization security model. Because Encompass floor staff may enter data under shared accounts (a licensing constraint from the per-user pricing model), we flag owner attribution gaps during data audit and advise the customer to review Epicor user provisioning before migration so that each production operator has a named account for traceability.