Migrate from INNERGY ERP to Epicor Prophet 21

INNERGY Estimates cover material takeoffs, labor assumptions, and margin calculation for custom millwork jobs. They map to Epicor Kinetic Quote or Sales Order records depending on whether the Estimate has been converted to a sold job. Line items from the Estimate become QuoteLine or OrderDtl records. We preserve margin calculation logic as a custom field on the Quote since Epicor's standard margin fields operate differently from INNERGY's markup model.

INNERGY Jobs represent the core project record tracking from award through installation. They map to Epicor Kinetic Job records via JobHead with all project metadata, status history, assigned staff, and division cost pool references. INNERGY's division-specific Job numbering conventions map to Epicor's JobNum with a prefix convention we define during scoping to prevent collisions in multi-site Epicor deployments.

INNERGY BOMs auto-generated from CAD geometry include material specs, quantities, operations routing, and subassembly relationships. CAD-generated BOMs decompose into Epicor Kinetic multi-level BOM structures with PartMtl records for materials and JobOper records for operations. We preserve the source CAD file reference as a URL field on the Epicor Part record for traceability. Multi-level subassemblies create separate Job records or phantom BOM entries depending on whether the subassembly is stocked or consumed directly into the parent job.

Manually constructed INNERGY BOMs without CAD origin map to Epicor Engineering BOM records (EBOM) which can then be rolled into a Job. We map Part, PartMtl, and PartOpr records directly and preserve the BOM revision history from INNERGY.

INNERGY Work Orders drive shop-floor execution linked to Jobs and BOMs. They map to Epicor Kinetic JobOper records representing individual operations, with actual labor captured via LaborDtl entries. We export Work Order sequencing, assigned operations, and completion status to Epicor's operation scheduling and labor tracking modules.

INNERGY Change Orders modify active Job scope and track lineage across revisions. We do not collapse change orders into Job records. Instead, we create an Epicor ChangeLog or JobRev linked table that preserves the full change order sequence: original Job number, approval dates, revised quantities, and scope delta. This structure keeps audit fidelity intact and allows project managers and auditors to reconstruct any historical project state from the migration data.

INNERGY tracks material and component inventory with units of measure, reorder points, and warehouse locations. We map inventory balances, average costs, and stock statuses to Epicor Kinetic Part records with PartWhse warehouse assignments. INNERGY units of measure map to Epicor's UOM class structure; any non-standard UOMs are flagged for manual verification before import.

INNERGY Customer records include contact details, billing and shipping addresses, and associated Jobs list. They map to Epicor Kinetic Customer records with ship-to and bill-to address roles. The customer's Jobs list links via Erp.Tableset.Job tables referenced by CustNum. We preserve the full contact hierarchy including primary, secondary, and site-specific contacts.

INNERGY Vendor records hold supplier information, lead times, and preferred items. We map vendor data to Epicor Kinetic Vendor records preserving associated purchase history where INNERGY exposes it through the API. Preferred item relationships migrate as VendorPart records in Epicor.

INNERGY supports custom fields on key objects, and Feature Release 115 added custom fields for Shipments. Post-implementation custom fields may lack formal schema documentation. We query INNERGY's field definitions via API during discovery, cross-reference against the current export to catch orphaned or mislabeled custom properties, and then map them to Epicor Kinetic User-Defined (UD) fields or custom extension tables in the destination schema.

INNERGY integrates accounting data through its ERP module with account structures configured per division. We export the full account list and map it to Epicor Kinetic GLAccount records. INNERGY division-specific cost pools map to Epicor Company or Site codes with independent chart-of-account assignments per entity. The customer reconciles any account code changes before we proceed with financial record migration.

Outstanding invoices and credit memos represent live financial data that must be reconciled before migration. We extract open AP and AR records from INNERGY via API, map them to Epicor Kinetic APOpen and AROpen records, and preserve the original invoice numbers and aging buckets. The customer closes or reverses any disputed items before we write financial open items to Epicor.

INNERGY stores documents and drawings associated with Jobs, Work Orders, and Estimates — including PDFs, images, and CAD files. We export attachments in their native format and link them to the corresponding Epicor records via the document management system. CAD file references are preserved as URL fields pointing to the document store for shop-floor access through Epicor's production tools.

INNERGY divisions carry their own cost pools, naming conventions, and user access scopes. Epicor Kinetic represents divisions as Company records (for legal-entity separation) or Site records (for operational-unit separation within a single Company). We determine the appropriate Epicor structure during scoping based on whether the customer runs multi-entity financials or single-entity multi-site operations.