Migrate from ECOUNT ERP to Epicor Prophet 21

ECOUNT Items (inventory) map to Epicor Part records. ECOUNT item code maps to Part.PartNum, description to Part.PartDescription, unit of measure to Part.IUM, standard cost to Part.StandardCost, and sales price to Part.MarketUnitCost or a PriceLbr record depending on the customer's pricing model. We also map the ECOUNT item type (finished goods, raw material, subassembly, service) to Part.TypeCode (M for manufactured, P for phantom, K for kit, S for sales). Multiple ECOUNT items cannot share one Part in Epicor without creating a PartPlant row per warehouse.

ECOUNT Bills of Materials with multiple BOMs per product and process-level inventory adjustments map to Epicor PartMtl rows. We explode the multi-level BOM structure from ECOUNT's flat Excel export into parent-material rows with PartMtl.ParentPart = ECOUNT parent item, PartMtl.MtlPartNum = component item, PartMtl.QtyPer = quantity per, and PartMtl.BOMSequence = step number. Sub-assemblies require multiple passes to resolve the full indented structure. Process-level adjustments from ECOUNT map to PartOpr (operation routing) records in Epicor if the destination includes the Manufacturing module.

ECOUNT Customer records map to Epicor Customer by Company and CustID. ECOUNT customer code becomes Customer.CustID, name becomes Customer.Name, payment terms map to Customer.TermsCode, and credit limit maps to Customer.CreditLimit. The ECOUNT auto-retrieved outstanding balance field is not written to Epicor as a static field; instead, we import open AR invoices from ECOUNT Sales Slips as Epicor InvcHead records so the running balance is computed from transactions rather than stored as a stale number.

ECOUNT Vendor records map to Epicor Supplier. Vendor code maps to Supplier.VendorID, vendor name to Supplier.Name, and payment terms to Supplier.TermsCode. ECOUNT's vendor-specific fields for bank details and W-9 or tax registration migrate as Supplier-level UD fields. If the ECOUNT vendor holds open purchase orders, those map to Epicor PODetail after the Supplier record is created.

ECOUNT Sales Slips map to Epicor OrderHed (order header) and OrderDtl (order line). ECOUNT slip number becomes OrderHed.OrderNum, customer PO number maps to OrderHed.PONum, ship date maps to OrderHed.RequestDate, and sales amount maps to OrderHed.OrderAmt. Each Sales Slip line item becomes an OrderDtl row with PartNum, selling quantity, and unit price. We import open and closed Sales Slips depending on whether the customer wants historical orders in Epicor; closed orders affect AR aging but do not consume Epicor's ATP reservation engine.

ECOUNT Purchase Slips map to Epicor POHeader and PODetail. The ECOUNT slip number becomes POHeader.PONum, vendor code links to the Supplier record, and each slip line item becomes a PODetail row. Incidental cost allocations (freight, duty, handling) from ECOUNT purchase slips migrate to PODetail.DocInActiveCost. Closed purchase slips with received inventory post to Epicor's PartTran as positive quantity movements if the customer enables the receiving module.

ECOUNT accounts, departments, and cost centers map to Epicor's GL Account structure with segment components. We request the customer's ECOUNT account template during scoping, identify the segment count and format, and configure Epicor's COA segment rules (GLAccount, Division, Department, Cost Center) to match. Custom department-level restrictions from ECOUNT become Epicor Department or Division assignments on User-authorized records. The mapping is created during configuration before any financial record migration begins.

ECOUNT Employee records map to Epicor Employee with EmployeeNum, Name, Title, and department assignment. Effective-dated compensation changes from ECOUNT migrate as Epicor PayClass and PayRate records tied to the Employee. Attendance records migrate as Epicor TimePhas mobile or Labor records depending on whether the customer licenses the MES module. We flag any ECOUNT HR data that has no Epicor equivalent (e.g., custom HR screens) as UD fields on Employee for the admin to populate or deprecate post-migration.

ECOUNT invoices generated from Sales Slips map to Epicor InvcHead (accounts receivable invoice) and InvcDtl rows. The ECOUNT invoice number becomes InvcHead.InvoiceNum, customer maps via InvcHead.CustNum, and shipped date becomes InvcHead.InvoiceDate. Packing lists from ECOUNT map to Epicor PackSlip and ShipDtl if the destination includes shipping and warehouse management. We extract complete invoice history and regenerate header and line records in Epicor AR so that open invoices appear in aging reports immediately after cutover.

Ecount allows companies to add, rename, or delete fields on any input screen with calculation formulas. These custom fields exist in the screen configuration rather than a standard metadata API. We request the customer's ECOUNT upload templates during scoping, identify all active custom columns, and map each to an Epicor User-Defined (UD) field on the equivalent table (PartX_c, OrderHedX_c, CustomerX_c, etc.). We pre-create the UD field schema in Epicor before any data migration begins. Calculation formulas from ECOUNT are documented but not reimplemented; Epicor admin rebuilds them as BPMs or calculated fields post-migration.

File attachments linked to ECOUNT slips and records are extracted from the ECOUNT document store and re-associated in Epicor. We extract attachment references with their source record ID during the discovery phase, then link each file to the migrated Epicor record by looking up the new Epicor ID via the migration mapping table. Epicor stores attachments as DocumentRev records with FileName and URL or as Linked/Attachable records depending on the destination module configuration.

Ecount's bank statement data (available through the free bank statement service) maps to Epicor CashHead and BankRec records for reconciliation. We extract the full bank transaction history including dates, amounts, and descriptions, and load them as unmatched BankRec lines so the customer's accounting team can match them against Epicor GL transactions during the reconciliation phase. We do not auto-match ECOUNT slip references to Epicor GL entries unless the customer provides a cross-reference table.