Migrate from Info.Net to Epicor Prophet 21

Info.Net Items (finished goods, raw materials, components) map 1:1 to Epicor Part records. The source SKU becomes Part.PartNum, description maps to Part.LineDesc, unit of measure maps to Part.IUM, and cost fields map to Part.StdCost or Part.AvgBurdenCost depending on the cost type. We extract PartClass and PartGroup assignments from Info.Net and create corresponding Epicor PartClass records before Part import so that classification lookups resolve at load time.

Info.Net Production Orders track manufacturing jobs with status, quantity, scheduled dates, and work center assignments. These map to Epicor Job records with JobHead and JobOper structure. We preserve job status (released, complete, closed), quantity, start and due dates, and map the Info.Net work center reference to the Epicor ResourceGroup. Closed production orders preserve their history as completed Jobs for audit trail purposes.

Info.Net BOMs define component hierarchies for manufactured Items. We map multi-level BOM structures to Epicor's PartRev revision, BOMHead header, and BOMMtl component lines. Revision versions from Info.Net map to PartRev.RevisionSeq and RevDescription. Alternate production methods become additional PartRev records with different primary methods flagged. We resolve the parent Part reference before BOM import to satisfy the foreign key constraint.

Info.Net Work Orders assign production tasks to employees or work centers with start/end dates and labor estimates. These map to Epicor LaborDtl records linked to the parent Job. The work order lifecycle (status transitions) maps to LaborDtl.ActiveTrans and Payroll related flags. Actual labor consumption from Info.Net migrates as historical LaborDtl entries with clock-in/clock-out timestamps preserved.

Info.Net QC logs hold inspection results, pass/fail flags, and measurement data linked to production lots. We map measurement field names from Info.Net to Epicor InspectionAttr and QtyAttr records, and pass/fail flags map to NonConf records linked to the Part Lot. Field naming conventions differ between Info.Net deployments, so we apply field-level mapping during the transform phase and flag any measurement attributes with no matching Epicor equivalent.

Info.Net Vendor master records include contact details, payment terms, and lead times. These map 1:1 to Epicor Vendor records with VendorNum, Name, Address, TermsCode, and LeadTime fields. Multi-contact handling in Info.Net may require creation of VendorContact records in Epicor. We deduplicate vendor records using vendor code as the dedupe key.

Info.Net Customer records hold billing addresses, shipping addresses, and credit limits. These map to Epicor Customer records with CustNum, Name, and address structures split into CustCnt contact records for bill-to and ship-to assignments. Multi-address customer accounts require splitting into separate CustCnt records with the appropriate ShipToNum assigned in Epicor.

Info.Net Inventory movements (receipts, issues, adjustments, transfers) carry timestamps, quantities, locations, and costs. These map to Epicor PartTran records with TranDate, TranQty, WarehsCode, and the cost layer fields (StdBurdenCost, StdMaterialCost, StdLaborCost). We preserve post dates as PartTran.TranDate for audit trail accuracy and maintain the transaction type code mapping (receipt, issue, adjustment, transfer) to Epicor PartTran.TranType values.

Info.Net inventory locations map to Epicor Warehs (warehouse) and WarehseBin (bin) records. We create the warehouse structure before any PartTran import so that location codes resolve at load time. Multi-bin warehouses require creation of WarehseBin records with the appropriate WarehsCode parent.

Open Info.Net Purchase Orders migrate as Epicor POHeader and PODetail records with vendor reference, order date, and line items. We set POHeader.Status to open values (O for open) and preserve line-level quantities and unit costs. Closed POs are archived and not imported as active records but may be referenced in PartTran history.

Open Info.Net Sales Orders migrate as Epicor OrderHed and OrderDtl records with customer reference, order date, and line items. We map OrderHed.Status and preserve OrderDtl.Quantity and OrderDtl.UnitPrice. Fulfilled lines from Info.Net are reflected in PartTran records rather than open OrderDtl lines.

Info.Net supports custom fields on Items, Customers, and Vendors. We extract custom field definitions and create corresponding Epicor UDF fields in the target table schema before data import. We flag any custom fields with no matching Epicor UDF equivalent and document them for the customer's admin to create post-migration. Custom field data types map to Epicor UDF data types (character to string, numeric to decimal, date to date).

Info.Net User accounts carry role assignments and permission sets. These map to Epicor User records with the username, email, and role assignments. Role mapping requires a manual translation table because Info.Net and Epicor use different permission models. We cannot preserve password hashes; users require password reset post-migration.

If Info.Net tracks lot numbers for manufactured or received parts, these map to Epicor PartLot records linked to the Part. Lot number, lot description, expiration date, and lot quantity migrate. PartLot is required as a parent for any QC inspection records linking to production lots.