Migrate from HashMicro ERP to Epicor Prophet 21

HashMicro's Finance module stores the COA as a multi-level tree with account codes, names, types, and currency settings. We export the full hierarchy and load into Epicor's GL Account table with AccountType, PostingEdit, and the correct segment structure (company-level or site-level posting depending on the Epicor chart configuration). Active/inactive status, tax related flags, and intercompany flags transfer explicitly. Multi-currency accounts require currency code mapping to Epicor's Reporting Currency configuration before GL balances load.

HashMicro Customer and Vendor master records (addresses, contact details, payment terms, tax IDs, open AR/AP balances) map to Epicor Customer and Supplier tables. Each HashMicro entity requires a separate Epicor Company record or shared Company with site-level segmentation. We flag any customer with multiple ShipTo addresses at extraction so they can be configured as CustomerShp records under a single CustomerID in Epicor before records load.

HashMicro Items (SKU, description, UOM, cost, pricing tiers, reorder points) map to Epicor Part master. We explode any BOM linkages at extraction so the full component list is available during Part and PartBin loading. Stock quantities from HashMicro's Inventory module load into Epicor PartBin by site. Epicor's revision-controlled PartRev records require a baseline revision to be created before any job or PO can reference the Part.

HashMicro BOMs and routing data are stored per Item. Multi-level BOMs require recursive explosion during extraction to preserve the full component hierarchy. We load the exploded structure into Epicor PartRev (revision header) and PartMtl (material lines) with quantity-per and scrap-percent fields. Each revision of a manufactured Part requires a corresponding PartRev record; we map the HashMicro effective date to the revision effective date in Epicor.

HashMicro Employee profiles (roles, departments, compensation history, attendance records) map to Epicor Employee. Effective-dated compensation changes require row-level sequencing to maintain history; we load the current active record as the primary Employee and archive prior compensation rows as custom LabourRate history records. Department and cost centre mapping from HashMicro feeds Epicor's EmpBasic cost class configuration.

Open HashMicro Sales Orders (header status, line items, owner assignments, pricing) load into Epicor OrderHed and OrderDtl. We map HashMicro order status to Epicor OrderRel release status and flag any orders with partial shipments at cut-off as partially released OrderRel records. Customer and Product references resolve via the Customer and Part lookups created during master data migration.

HashMicro Purchase Orders and Goods Receipt linkages transfer to Epicor POHeader and PODetail with release-level granularity (PORelease). We preserve PO-to-GR linkages by loading GR receipts as Epicor ReceiptDtl records linked to the corresponding PORel. Partially received PORel records at cut-off are flagged for manual reconciliation against Epicor's receiving workflow.

Outstanding invoices, credit memos, and payment schedules require open-item sequencing at cut-off. We map due dates, outstanding amounts, and currency codes explicitly from HashMicro's open AR/AP module into Epicor InvcHead (for AR) and APInvHed (for AP). Partial payments against invoices require the remaining open amount and payment terms to be represented correctly as either a credit hold or open debit note in Epicor.

Ledger journals and posted transactions extract from HashMicro in batch but schema varies by company configuration and fiscal year. We normalise posting dates against Epicor's fiscal period calendar, map account codes via the COA mapping table, and load GLJrnLine records in date-range batches. Period closes in Epicor must be validated against the HashMicro balance totals before the migration is signed off.

HashMicro Projects carry tasks, assignees, time entries, and cost tracking. Project-to-item linkages (consumed materials, labour) require cross-object joins at extraction. We load Epicor Project as the header and ProjectPhase as the task level, with labour and material actuals mapped to ProjectCharge and JobMtl respectively. We flag any Project with incomplete billing milestones for manual reconciliation against Epicor's Project Billing module.

HashMicro asset registers (acquisition cost, depreciation schedule, location, custodian, accumulated depreciation at cut-off) load into Epicor Asset and AssetReg. Depreciation method, useful life, and accumulated depreciation are critical fields; we validate these against Epicor's FaDepMethod and FaBook configuration before loading. Asset-to-location mapping uses the Site structure established during master data migration.

HashMicro regional tax configurations for GST, VAT, or local equivalents are stored per entity and item class. We map these explicitly to Epicor TaxConnect jurisdiction codes and TaxCategory assignments, flagging any jurisdiction mismatch between HashMicro and Epicor's tax engine for manual configuration review before go-live.