Migrate from Integra ERP to Epicor Prophet 21

Integra ERP Chart of Accounts records map to Epicor Kinetic GL Account (GLAccount table). Account code, account name, account type (Asset, Liability, Income, Expense), and active flag transfer directly. We resolve cost-center segmentation from Integra by mapping to Epicor's dimension codes if the customer uses multi-segment account structures; otherwise cost centers become separate GL Account records or analytical reporting tags. Customer provides an account-mapping spreadsheet during scoping to resolve any gaps between Integra's account numbering convention and Epicor's GL Account code structure.

Integra ERP Customer records map to Epicor Customer with contact details, billing address, credit terms, and GST registration preserved. Each Customer in Epicor supports multiple ShipTo addresses, which we populate from Integra's customer-branch associations. We preserve open AR balances as opening AR entries in Epicor with a reference to the original invoice numbers where available. Customer code in Integra becomes CustID in Epicor; the mapping is 1:1 with no merging required.

Integra ERP Vendor records map to Epicor Supplier with payment terms, GST/VAT registration, address records, and vendor-specific item pricing transferred directly. Supplier codes map from Integra's vendor code to Epicor VendorID. We preserve vendor-specific pricing rows as Supplier Part UOM or Supplier Price List entries in Epicor where the source data contains them.

Integra ERP Items map to Epicor Part records with part number, description, unit of measure, and item type (stock, non-stock, misc) transferred. Integra-specific classification codes migrate to Part Number Prefix or a custom Part attribute field. BOM hierarchies stored across multiple linked tables in Integra are flattened into Epicor Part and JobAsmbl records; multi-level BOMs are reconstructed with parent-part and child-part links using a recursive extraction script. Branch-level stock quantities map to PartPlant records per Epicor site or warehouse code.

Integra ERP inventory ledgers contain branch or warehouse-specific stock quantities. We aggregate by item and map to Epicor PartBin records per site-warehouse combination. Serial and batch tracking fields are preserved where present in the source; Epicor PartBin receives the aggregated quantity as the opening on-hand balance for each warehouse. Inventory valuation (average cost, standard cost) migrates to Epicor Part and PartCost records to support correct COGS posting on future transactions.

Outstanding payable and receivable balances in Integra ERP cannot be migrated as individual invoices in most scenarios. We extract the net outstanding amount per vendor (AP) and per customer (AR) and create Epicor opening balance records using the AP/AR opening balance form or as manual journal entries against the appropriate GL Account. Each opening balance line references the source system and original party for audit trail. Historical invoice details migrate as context notes on the opening balance record.

Integra ERP Sales Orders map to Epicor Sales Order records (OrderHed as header, OrderDtl as lines). We extract header fields (order number, order date, customer reference, ship-to address) and line fields (item number, quantity ordered, quantity shipped, unit price, discount) across linked tables. Order status from Integra maps to Epicor OrderHed.OrderStatus and OrderHed.OpenOrder. Orders referencing voided customers or discontinued items are flagged in a reconciliation report before load. DMT Order Entry template handles the bulk load with batch sequencing.

Integra ERP Employee records from the employee management module map to Epicor Employee with name, department, job title, and basic employment status transferred. Compensation fields migrate to the Epicor HR module or to custom fields on Employee if the customer licenses Epicor Human Capital Management. Employee number from Integra becomes EmpID in Epicor. We preserve department assignments as Epicor Department codes.

Integra ERP BOM structures for manufacturing customers require recursive flattening because the source stores multi-level hierarchies across parent-child linked tables with optional operations. We extract each BOM level, map to Epicor JobAsmbl (assembly header) and JobMtl (material lines), and preserve the operation sequence and quantity-per-assembly. Make-to-order parts get linked to JobAsmbl.JobNum for production order traceability in Epicor Kinetic MES.

Open Purchase Orders from Integra ERP map to Epicor POHeader and PODetail records. Vendor, PO date, ship-to warehouse, line item, quantity ordered, quantity received, and unit cost transfer directly. Open PO status determines Epicor OpenRelease status on release records. Historical closed POs migrate as read-only records with the closed flag set to avoid duplicate GL posting.

Integra ERP journal entries map to Epicor GLJrnHed (header) and GLJrnDtl (detail) records. We preserve the journal entry number, entry date, description, and account-debit-amount pairs. Journal source codes map to Epicor JournalCode. Entries are loaded in date order to maintain fiscal period integrity; any entries with unmapped account codes go to a suspense account per the account-mapping spreadsheet.

Attachments, scanned documents, and PDFs stored inside Integra ERP are not exposed via a documented export mechanism. We extract any linked file paths from the source database but cannot guarantee file integrity or completeness. Customers should extract documents independently before migration and store them in a document management system. We document the source file path against the relevant transaction or master record for post-migration retrieval.

Integra ERP may contain user-defined fields on standard tables or custom objects that require mapping to Epicor UD Codes (UD01-UD12) or custom fields on the equivalent Epicor table. We map each identified Integra UDF to an Epicor custom field of matching data type (string, integer, date, decimal). Custom object data is mapped to Epicor UD tables during scoping if the customer requires preservation of Integra-specific business logic.