Migrate from etEngine to Epicor Prophet 21

etEngine account codes, names, and types map to Epicor GL Account records within the Chart of Accounts. Currency assignments and department segments map to Epicor account segments or custom fields depending on the customer's Chart of Accounts structure. We flag any account codes that exceed Epicor's segment length limits during scoping and propose truncation or prefix strategies before migration. Multi-company Epicor deployments require the account code prefix to be scoped per company entity.

etEngine customer records with contact details, billing addresses, and payment terms map to Epicor Customer records. The customer's payment terms map to Epicor Term records; ship-to addresses map to Customer Ship Tos. We flag any custom fields on the etEngine customer record during scoping and map them to Epicor User Defined Fields (UDFs) or UD Codes on the Customer table. Customer credit limits require a corresponding Epicor Credit Check configuration before the records activate.

etEngine vendor master records with contact and payment information map to Epicor Supplier records. Payment terms, bank details, and W-9 or tax registration fields migrate to corresponding Supplier fields. Historical purchase transactions are sequenced separately from the vendor master and import after Supplier records are active. We flag any etEngine vendor records with zero PO history as candidates for inactive status to avoid cluttering the Epicor supplier list.

etEngine Item masters with SKUs, descriptions, pricing, and cost records map to Epicor Part records. Epicor Parts carry additional structural fields (Type, Class, IUM, PUM, TypeCode, Method) that may require default values during migration if etEngine did not track them. If etEngine Items contain BOM or routing data, we migrate these as separate Epicor Bill of Materials and Job Router records after the Part master is established. Stock and cost records map to PartBin and PartCost respectively. Custom attributes on etEngine items map to UD Fields on the Part table.

Outstanding AP invoices from etEngine migrate to Epicor AP Invoice records with original invoice dates, amounts, and vendor references. We resolve each invoice's vendor reference to the migrated Supplier record before inserting. Payment terms, hold status, and approval workflow assignments carry forward as fields on the Epicor invoice. Fully reconciled etEngine AP records that are paid and closed are flagged during scoping and excluded from migration to avoid reopening closed periods.

Outstanding AR invoices from etEngine migrate to Epicor AR Invoice records with original invoice dates, amounts, and customer references. We resolve each invoice's customer reference to the migrated Customer record. Credit memos and pre-payments map to Epicor AR Credit Memo and Deposit records respectively. Invoice aging at cutover is preserved as the Epicor invoice due date minus the original invoice date. AR records in dispute or with partial payments retain the partial payment history within Epicor's invoice-level payment application.

Past journal entries and transaction history from etEngine migrate to Epicor GL Journal Entry records chunked by fiscal period. We sequence them in chronological order and assign them to the correct Epicor fiscal period and fiscal year. Entries that span multiple periods in etEngine are split into separate Epicor journal entries per period to maintain fiscal boundary integrity. We flag any journal entries that reference deleted or inactive accounts and present them to the customer for resolution before import.

etEngine user accounts map to Epicor Kinetic User records with role assignments based on the customer's role matrix. We extract role and permission data from etEngine during scoping and map it to Epicor Kinetic menu-level security groups. Active versus inactive status is preserved and validated post-migration. Any etEngine user without a clear Epicor role mapping goes to a reconciliation queue for the customer admin to assign before the user records import.

etEngine-attached files and linked documents are exported to a structured file store (network share, SharePoint, or S3-compatible storage) with a manifest mapping each file to its source record ID and entity type. After migration, we re-link documents to their corresponding Epicor records using a file-path reference field added to the relevant record (Customer, Supplier, Part, Order, etc.). We do not store documents inside Epicor's database; the external store keeps Epicor's blob storage within licensed limits.

If etEngine Items contain BOM data, we split each multi-level BOM into Epicor multi-level BOM records. The top-level part maps to the Part master; sub-components map to their respective Part records before BOM lines are created. BOM quantities per assemble, scrap percentages, and BOM approved dates migrate to Epicor BillOpr. We validate that all sub-component Part records exist in Epicor before BOM insert to avoid orphan-line failures.

Open purchase orders from etEngine migrate to Epicor PO Header records with vendor reference resolved to the migrated Supplier. PO lines migrate with part number resolved to Part records, quantity confirmed against PartBin, and unit cost validated against PartCost. Release-based POs in etEngine map to Epicor PO Release records under the parent PO Header. Closed or received POs are excluded from migration scope.

Open sales orders from etEngine migrate to Epicor OrderHed (header) and OrderDtl (detail) records. Customer reference resolves to the migrated Customer record; part numbers resolve to Part records. OrderHed ship date, terms, and carrier assignments carry forward. Line pricing and discounts are mapped to Epicor OrderDtl price fields. Historical closed orders are scoped separately and migrated as OrderHed records with a Closed status flag if reporting continuity is required.