Migrate from Industry Software to Epicor Prophet 21

Industry Software Chart of Accounts map directly to Epicor GL Account records with Account Type, Currency, and Division assigned during import. We extract the account structure (segment count, separator character, natural account versus statistical) from Industry Software's configuration and create the equivalent Epicor GL Account segments before any transactional data loads. Division or department codes from Industry Software become Epicor Book or Division references.

Industry Software Customer records map to Epicor Customer with ShipTo and BillTo split handled by creating separate Customer records with the IsShipTo or IsBillTo flag. Credit limits, payment terms, and tax codes migrate to Epicor Customer credit, terms, and tax entity fields. Email and phone contacts migrate to the CustomerContact table with primary-flag sequencing.

Industry Software Vendor records map to Epicor Vendor with the same contact structure (VendorBTG, VendorContact) as Customer. 1099 flag, payment terms, and bank account details for ACH transfer migrate to Epicor VendorPPM fields. We resolve any Industry Software vendor codes to Epicor's VendorNum assignment during the import phase.

Industry Software Inventory Part records map to Epicor Part with the Class, Type (stock, non-stock, special), UOM, and cost layer preserved. For multi-site installations, the Industry Software warehouse code becomes an Epicor Warehouse record, and on-hand quantities migrate to PartWhse. We flag any Industry Software parts with negative on-hand or obsolete status for reconciliation before Epicor PartBin insertion.

Industry Software BOM records map to Epicor PartBOM with multi-level explosion handled by parent-Part resolution during import. Revision and ECO tracking migrate to PartRev. We apply the Epicor DMT BOM template, and any Industry Software BOM with materials not yet created as Epicor Parts go to a pre-creation queue before the BOM import phase runs.

Industry Software routing operations map to Epicor JobOper records attached to JobHead. Work centers and labor rates become Epicor ResourceGroup and Resource. Machine hours and labor hours per operation migrate to the Epicor ResourceTimeVec and JobOper start and end timestamps. We flag any routing step referencing a non-existent Industry Software machine or labor code for operator review.

Open Industry Software AP invoices migrate to Epicor APInvoiceHed with VendorNum resolved from the Vendor mapping. Memo and unposted invoice types map to APMemo (or APTran without invoice header depending on Industry Software's posting state). Historical paid invoices do not migrate to the live Epicor AP module; they are archived separately for audit access.

Open Industry Software AR invoices migrate to Epicor ARInvoiceHed with CustomerNum resolved from the Customer mapping. Memo type invoices migrate to ARMemo for open credits or pre-payments. We preserve invoice date, due date, and aging bucket as Epicor TranGLC records for reporting continuity. Historical closed AR records are archived separately.

Open and recent Industry Software Purchase Orders map to Epicor POHeader and POLine with VendorNum, ShipTo, and PartNum resolved. Line items referencing non-existent Part records in Epicor are held in a pre-creation queue. PO statuses (open, released, closed) migrate as Epicor POHeader approval statuses. Historical POs beyond the retention window are not migrated to live Epicor PO tables.

Open Industry Software Sales Orders map to Epicor OrderHed and OrderDtl with CustomerNum resolved, ship date and promise date preserved, and line status mapped to Epicor OrderLine.Status. Order-held and credit-hold flags migrate as Epicor credit check flags. Completed or invoiced orders are not migrated to live Epicor Order tables; historical order data is archived separately for financial reporting continuity.

Open Industry Software Work Orders map to Epicor JobHead with JobMtl (materials from BOM) and JobOper (operations from routing) populated. We resolve the JobMtl PartNum reference and JobOper ResourceGroup reference at migration time. WIP quantities and job status migrate to JobHead.JobClosed and JobHead.JobComplete flags. Historical closed jobs are not migrated to live Epicor Job tables; they are archived separately.

Industry Software industry-specific or custom modules (field service, distribution add-ons, vertical-specific tables) do not have a direct Epicor ERP equivalent without configuration. We catalog every active Industry Software module during scoping, map its data fields to a written configuration plan for Epicor's equivalent module (Service Connect, Distribution, Prophet 21, BisTrack depending on vertical), and deliver the module inventory as a configuration roadmap for the customer's Epicor administrator. No custom Industry Software module data migrates into Epicor without a documented target schema.