Migrate from IS Packaging to Epicor Prophet 21

IS Packaging Items map to Epicor Part as the primary product master, with PartPlant records created per site for plant-level data like safety stock, reorder point, and costing layers. The IS Packaging Item Number becomes Part.PartNum, Description becomes Part.Description, and the uom class maps to Part.IUM and Part.PUM. Costing layers (standard, average, last) migrate to the corresponding Epicor costing method on Part. We extract all standard and custom Item properties during discovery and map them to Part UD fields or related Part tables.

IS Packaging BOMs with revision codes map to Epicor PartRev (revision header) and PartMtl (component lines). We build a revision cross-reference table during discovery that maps each IS Packaging revision code and effective date to the Epicor PartRev.RevisionNum, PartRev.EffectiveDate, and PartRev.ApprovedDate. Phantom assembly flags, scrap percentages, and operation-specific material issues from IS Packaging routing steps map to PartMtl and JobOper records in Epicor. This mapping is the most critical artifact of the migration because incorrect BOM revision mapping causes wrong material assignments on open Production Orders.

IS Packaging Production Orders map to Epicor Job records. JobHead holds the order header (quantity, start date, due date, site), JobMtl holds material lines with the PartMtl.MtlSeq referencing the PartRev BOM components, and JobOper holds operation steps. We map IS Packaging order status to Epicor JobHead.JobReleased, JobHead.JobComplete, or JobHead.JobClose using a status matrix built during discovery. Any open IS Packaging orders that cannot resolve to a valid Epicor PartRev revision are held in a reconciliation queue for manual resolution before import.

IS Packaging Work Orders linked to Production Orders map to Epicor JobOper records. JobOper.OpCode, LaborHrs, MachineHrs, and WorkCenterId come from the IS Packaging work center and labor posting data. Status flags vary between IS Packaging plants, so we apply the destination-status mapping matrix during import. Work Orders without a parent Production Order are imported as standalone JobOper records with an informational flag for the customer's review.

IS Packaging Finished Goods Locations tied to Items map to Epicor PartBin records. On-hand quantity, lot number, and serial number from the source location transfer to PartBin.LotNum, PartBin.BinOnHandQty, and PartBin.SerialNo. We resolve the IS Packaging Location ID to an Epicor Warehouse and Bin combination during import using a location cross-reference table built during discovery.

IS Packaging transaction history (receipts, issues, adjustments, WIP moves) maps to Epicor PartTran records. We preserve transaction type, date, quantity, cost, warehouse, lot, and reference fields. High-volume transaction sets require chunked extraction and chronological sequencing to maintain integrity. Historical PartTran records older than 24 months may be flagged for archive rather than live migration to protect Epicor performance post-go-live.

IS Packaging Customer Orders map to Epicor OrderHed (order header) and OrderDtl (order lines). OrderDtl maps to the target Part number and links to the corresponding Epicor PartRev for configured items. Pricing exceptions from IS Packaging custom pricing rules are flagged as OrderDtl.DiscountPercent overrides and flagged for manual pricing review before import.

IS Packaging Vendor masters map to Epicor Vendor and VendorPP (purchase point) records. Vendor Name, address, terms, and item-supplier cross-references migrate to Vendor and VendorPP with the supplier PartNum preserved on VendorPP.SupplierPartNum. We reassociate any IS Packaging Item-to-Vendor links as VendorPP records for the purchasing module.

IS Packaging custom fields on standard objects require field-level mapping to Epicor UD columns or Part UD tables. We inventory all custom field names, data types, and values during discovery and pre-create the corresponding Epicor Part UD columns (PartUD01 through PartUD10 and related tables) before import. Custom fields that have no Epicor equivalent are flagged for the customer's admin to review for manual re-entry or alternative placement.

The IS Packaging Chart of Accounts maps to Epicor GLAccount with segment alignment. We build an account cross-reference table during discovery, mapping IS Packaging account codes to Epicor segment values and COA codes. Any inactive, intercompany, or suspense accounts are flagged for reactivation review in Epicor before import. Multi-entity IS Packaging implementations may require separate COA mapping per legal entity in Epicor.

IS Packaging lot numbers across multiple plants use different conventions that we normalize into a unified Epicor PartLot.LotNum format. We build a lot-normalization rule during discovery that maps source lot prefixes, date codes, and sequence formats to the target Epicor convention. PartLot records are created before inventory transactions import, ensuring that PartBin and PartTran records reference valid lots.

IS Packaging plants map to Epicor Sites. We create Site records for each source plant, map plant-specific parameters (site code, description, address, calendar) to Epicor Site fields, and associate PartPlant records to the corresponding Site during Part import. Multi-plant consolidation scenarios require site code standardization to prevent duplicate sites in Epicor.