Migrate from inoERP to Epicor Prophet 21

inoERP GL account codes, types, and currency assignments map to Epicor ERP GL Account codes. inoERP account type (Asset, Liability, Equity, Revenue, Expense) maps to Epicor GL Account Type. Account balances are imported as opening balances in Epicor GL through the Account Balance import template rather than as live transactions. We validate that inoERP account codes use characters compatible with Epicor's GL segment structure before import.

Posted journal entries in inoERP carry header data (journal name, date, description, reference) and line data (account, debit, credit, description). We import journal entries into Epicor ERP GL through the Journal Entry import template. Entries with non-standard currency or complex intercompany dimensions are flagged as requiring Epicor admin review before import. We recommend importing only open-period entries; closed historical periods are imported as opening balance adjustments rather than re-posted journal entries.

Open AR invoices in inoERP (invoice headers with line items, customer references, amounts, due dates) map to Epicor ERP AR Invoice. inoERP party structures map to Epicor ERP Customer records. Open invoices are imported as posted AR transactions; closed invoices are imported as historical records or excluded based on customer preference. Epicor DMT AR template supports header-level and line-level import.

Open AP invoices in inoERP map to Epicor ERP AP Invoice. inoERP supplier records map to Epicor ERP Vendor. We preserve invoice number, vendor reference, terms, and line-item amounts. Prepayments and credit memos migrate as separate AP transaction types. Historical closed AP invoices migrate as reference records if the customer chooses full history scope.

inoERP item definitions with UOM, cost layers, category hierarchy, and on-hand quantities across locations map to Epicor ERP Part and PartWhse records. Lot and serial number traces migrate if inoERP tracks them. On-hand balances per warehouse map to Epicor PartWhse OnHandQty. Stock locations in inoERP map to Epicor Warehse and Bin records. We flag any inoERP item with negative on-hand as a data anomaly for cleansing before import.

Open sales orders in inoERP (header fields including order number, dates, customer reference, terms, and line items with item, quantity, price, warehouse) map to Epicor ERP Sales Order. Closed orders can be migrated as historical records or excluded based on date-range filtering agreed during scoping. We resolve inoERP customer references to Epicor Customer IDs before import so that OrderHed.Company and OrderHed.CustNum are populated correctly. Order-level discounts and freight charges migrate as OrderMsc records.

Open purchase orders in inoERP map to Epicor ERP PO Header with PO Release lines. inoERP supplier references resolve to Epicor ERP Vendor records. Line items (item, quantity, price, due date) migrate as PORel records. Closed POs migrate as reference records if historical scope is agreed. We flag inoERP POs with mismatched line quantities and prices that may indicate data-quality issues.

inoERP work orders with routing steps, material issues, resource transactions, and completion records map to Epicor ERP JobHead, JobMtl, and JobOper tables. The WIP ledger aggregate cost per work order in inoERP does not map directly to Epicor job costing because Epicor calculates WIP from JobMtl and JobOper actuals at runtime. We import JobMtl and JobOper from inoERP's material and operation records, but Epicor recomputes WIP on the first transaction post-migration. Open work orders migrate fully; closed work orders migrate as job history for audit trail purposes.

inoERP BOMs and routings with multi-level structures and super BOMs map to Epicor ERP Engineering Control Center (ECC) BOM and Job BOM records. We export the full BOM hierarchy and routing sequence. Phantom BOMs in inoERP map to Epicor ECC Phase records with the Phantom flag. Co-products and by-products require manual mapping review because the co-product cost allocation model differs between platforms. We recommend validating BOM costs in Epicor after import because inoERP cost calculations may use different labour and overhead rates.

inoERP employee profiles, job definitions, positions, and compensation records map to Epicor ERP Employee. Compensation history is sensitive data that requires explicit customer consent during scoping and is imported as EmployeePay records. Leave balances migrate as leave transaction records. Approval hierarchies in inoERP do not map to Epicor's workflow system and are documented separately for rebuild. We flag compensation records with non-standard pay components (piece rates, shift premiums) that require Epicor HR admin review before import.

inoERP payroll registers and compensation history map to Epicor ERP payroll data structures, but electronic bank file formats are customisable via JavaScript REST APIs in inoERP and have no direct Epicor equivalent. We export payroll registers, leave balances, and compensation history as reference data. Direct deposit bank file generation should be reconfigured in Epicor ERP post-migration by the customer's Epicor HR partner rather than imported from inoERP's custom file formats.

inoERP asset registers with acquisition details, depreciation schedules, and asset categories map to Epicor ERP Asset Register. Book values and accumulated depreciation import as opening asset balances. Depreciation methods (straight-line, declining balance, units of production) migrate to Epicor Asset Book records. Assets under construction in inoERP require review for appropriate Epicor capitalisation treatment. Asset locations map to Epicor Warehse and site records.

inoERP's flexible schema allows organisations to add custom fields and tables without formal schema management. These map to Epicor Kinetic User-Defined Fields (UDCs) on standard tables or UD Tables for standalone custom records. We pre-create the Epicor UDF schema before production migration so that custom inoERP data has a landing destination. Custom PHP/Go code that computes field values in inoERP does not migrate; these calculations are documented for Epicor BPM rebuild.