Migrate from Impact ERP to Epicor Prophet 21

Impact ERP uses a hierarchical Indonesian COA with fixed account codes and IDR-only functional currency. We map each Impact account code to an Epicor Kinetic GLAccount record with the correct AccountType (Asset, Liability, Equity, Revenue, Expense), SegmentValue per configured segment types, and IsActive flag. We flag any IDR-denominated historical balances and map them to Epicor's functional currency. Indonesian account groups (aktiva, passiva, pendapatan, beban) map to Epicor's natural account segment types, and we validate the resulting trial balance totals after migration.

Impact ERP customer master records include billing and shipping addresses, NPWP tax ID, payment terms, and credit limits. We map these to Epicor Kinetic Customer records with ErpPkg—Customer__c or native Customer table fields. NPWP is preserved as TaxPayerID or a custom UD field since Epicor's default global tax configuration does not include Indonesian fiscal fields. We extract effective-dated payment term changes as CustomerPaymentTerm records and flag any custom customer fields for UD field creation in Epicor.

Vendor masters in Impact ERP mirror customer structure with NPWP tax ID, bank account details for payment runs, and lead-time fields. We map these to Epicor Kinetic Vendor records, preserving the NPWP as TaxPayerID and Indonesian bank account details in VendorBankAcct or equivalent fields. Lead-time and procurement settings map to Epicor's vendor-related planning fields (LeadTimePull, UrgentLeadTime). Any custom fields added during Impact implementation require UD field creation in Epicor.

Impact ERP item masters include SKU, description, unit of measure, cost, and inventory valuation method. We map these to Epicor Kinetic Part records with PartNum, PartDescription,IUM, UnitCost, and CostMethod set to match Impact's valuation method (Standard, Average, FIFO). Impact's inventory site or warehouse assignments map to Epicor's WhsePlant or Warehse records. We flag any custom item fields for Epicor UD field creation before migration.

Impact ERP stores BOMs as item-level attachments rather than separate table records. We extract BOMs as a distinct migration object from Impact exports, then create Epicor Kinetic PartMtl records linked to the parent Part. Each line maps PartNum, MtlPartNum, QtyPer, andBomDetailType. BOM accuracy is critical before go-live because Epicor's production scheduling and work order costing depend on correct material quantities. We recommend a BOM validation step with the customer's engineering and planning team.

Routings in Impact ERP are attached to item records. We extract them as a separate migration object and create Epicor Kinetic PartOpr records linked to the parent Part. Each operation maps to the correct PartOpr with OperationCode, ResourceGrpID, ProdStandard, EstSetHours, EstWaitHours, and OpCode description. Work center codes in Epicor must be provisioned before routing migration, and we flag any operations referencing resources that do not yet exist in Epicor's Resource or ResourceGroup tables.

Open payables in Impact ERP carry invoice number, vendor reference, due date, amount, and IDR currency. We map these to Epicor Kinetic APTran line records linked to an APHead header, preserving the vendor invoice number, invoice date, due date, and amount in IDR. We set Epicor's functional currency to match the IDR source and flag any multi-currency invoices that require exchange rate lookup at time of migration. Fully-paid records are flagged for optional historical carry-forward depending on customer scope.

Open receivables carry invoice number, customer reference, due date, and IDR amount. We map these to Epicor Kinetic ARTran line records linked to an ARHead header. The original invoice number, invoice date, due date, and amount in IDR are preserved in Epicor's ARTran. Customer reference and currency are resolved via the Customer mapping, and open invoice status is validated against Impact ERP's current balances before posting.

Past invoices, purchase orders, receipts, and payment records from Impact ERP are extracted in date-range chunks and mapped to Epicor Kinetic transactional tables (APTran, ARTran, InvoiceHed, PurOrdHed, ReceiptHed). Each record is linked to its corresponding GLJournal entry, preserving journal batch number and posting date. We recommend limiting historical migration to the most recent 2-3 fiscal years unless audit requirements mandate full history, to manage Epicor database size and performance.

Impact ERP generates GL journal entries from transactions. We split each Impact journal entry into Epicor Kinetic GLJrnHed (header) and GLJrnDtl (line) records. The header preserves entry date, source module, batch number, and memo; each line maps to the correct GLAccount, debit or credit amount, and department or project code. Header-level and line-item memo fields are preserved in Epicor's Description and LineRef fields.

Impact ERP's custom fields and user-defined objects have no standardized schema. We identify custom field definitions via exported metadata and map them to Epicor Kinetic UD fields (UD01-UD20) or custom UD tables. We flag any custom fields with no semantic equivalent in Epicor's standard object model and document them in the migration handoff notes for the customer's admin to evaluate post-migration.

Impact ERP user accounts include role assignments and department assignments. We map active Impact users to Epicor Kinetic User records by email match, resolving inactive status as appropriate. Role assignments from Impact map to Epicor Kinetic security roles (Production, Engineering, Finance, etc.), and department assignments map to Epicor's department codes. Passwords are not migratable; we provision new accounts at the destination and flag missing users for the customer's admin to create before record migration begins.