Migrate from Icicle ERP to Epicor Prophet 21

Icicle Products with full formulation hierarchies (ingredients, packaging BOMs, allergen declarations, nutritional data) map to Epicor Part records with PartRevision BOMs. We preserve ingredient-level traceability by creating multi-level BOMs in Epicor, mapping Icicle's allergen fields to Epicor's Part Restriction and Part Restriction Type records. Unit-of-measure conventions (weight, volume, case-pack configurations) map to Epicor's UOM class structure.

Icicle Production Orders link to Formulations, scheduled batches, and resource allocations. We migrate production order history, quantities run, and the resulting finished-goods lot numbers into Epicor Job records. The Icicle batch identifier becomes the JobHead.JobNum, and the linked formulation BOM version is preserved as a PartRev revision code. Open production orders migrate as active Jobs; closed orders migrate as historical records.

Lot traceability in Icicle is a first-class linked graph connecting raw-material lots to in-process lots to finished-goods lots. We map this to Epicor's PartLot table with LotNum and LotDescription, and we preserve forward and backward genealogy via LotTran (lot transactions) records. The full traceability graph is validated before production migration to confirm Epicor can represent the same lot relationships without breaking food-safety compliance chains.

Icicle inventory at the lot level (locations, expiry dates, QC hold statuses) maps to Epicor PartLot records with PartBin location assignments. Lots under active quality holds are flagged in Epicor with a QC Hold flag and remain excluded from stock transactions until released by a quality manager. We verify expiry date handling in Epicor's lot aging reports before cutover.

Quality checks in Icicle are tied to specific lots and production orders with pass/fail criteria and inspector assignments. Epicor's QC Engineering module supports Inspection Plans and Characteristics. We map Icicle inspection records to Epicor Inspection Result records linked to the corresponding PartLot, preserving pass/fail status, inspector name, and the inspection date. Epicor's standard QC module may require configuration to match Icicle's inspection criteria model.

Supplier records in Icicle include food-safety rating fields, certifications (organic, kosher, halal), and approval statuses. We migrate all supplier fields and map food-safety ratings to Epicor Vendor PPAP and Supplier Rating fields or UD fields if the certifications exceed Epicor's standard supplier fields. Approval workflow state is preserved at migration time.

Customer records in Icicle include standard billing and shipping fields. We map these to Epicor Customer records, carrying forward customer-specific pricing tiers as UD fields or Price List assignments. Customer contacts migrate as Person records linked to the Customer.

Sales Orders reference Products, Customers, and Delivery schedules. We map open orders by status to Epicor OrderHed and OrderDtl records, preserving order date, requested dates, quantities, and pricing. Orders tied to lots that are pending QC hold are flagged for the customer's review before release.

Accounts payable records in Icicle are extracted and matched to migrated vendor records. Open invoice amounts, due dates, and payment terms are mapped to Epicor AP Invoice and APTran records. We migrate only open items; closed historical invoices are mapped as read-only records in a migration archive file for audit purposes.

AR records reference customer accounts and open sales orders. We extract outstanding invoice balances and remap them to Epicor AR Invoice and ARTran, preserving payment terms and ageing buckets. Customer-level credit limits migrate as Epicor Customer Credit data.

Icicle's GL structure includes food-industry-specific accounts (COGS by product category, facility-level cost splits). We map these to Epicor GL Accounts and flag accounts that require Epicor book or cost element configuration. Epicor's COGS posting groups are set up to match Icicle's product category structure.

Icicle's co-packer mode adds customer-specific contract fields (formula versioning, NDA flags, customer-specific spec documents) that do not map to a standard Epicor object. We split these into three destinations: the co-packer customer record, Part UD fields for formula-specific extensions, and Document records for spec documents and NDAs. We document each co-packer extension and its target during scoping so the Epicor admin can configure UD fields before migration.