Migrate from HashMicro ERP to Infor CloudSuite Corporate

HashMicro's Finance module stores the COA as a structured multi-level hierarchy with account codes, names, types, and currency settings. We export the full account tree including parent-child relationships and map to Infor GLAcct with AccountType, SubAcctType, and CostCentre assignments. Each HashMicro entity's COA is extracted separately and loaded into the corresponding Infor company code. Currency assignments on HashMicro accounts map to Infor's fiscal setup currency fields.

HashMicro Customer master records include addresses, contact details, payment terms, and tax IDs. We preserve linked open AR balances and invoice histories at migration cut-off. Multi-entity configurations mean customers may be assigned to different HashMicro entities; we extract per entity and map to the corresponding Infor company. Tax IDs map to Infor's tax registration fields, and payment terms map to Infor's AR terms codes.

HashMicro Vendor master records mirror the Customer structure with addresses, contact details, payment terms, and tax IDs. We preserve linked open AP balances and purchase history at cut-off. Multi-entity extraction applies to vendors as it does to customers. Tax jurisdiction assignments from HashMicro map to Infor's AP tax codes, and payment terms map to Infor's AP terms codes.

HashMicro Items are catalogued with SKU, description, unit of measure, cost, and pricing tiers. Inventory quantities and reorder points extract from the stock module. We map HashMicro item types (finished goods, raw materials, subassemblies, services) to Infor mitmstr ItemType and ItemGroup codes. Standard cost and current cost migrate to Infor's cost fields, and UOM codes map to Infor's UOM set.

HashMicro BOMs and routing data are stored per Item. Multi-level BOMs require recursive explosion during export to preserve the full component hierarchy. We extract the complete BOM tree starting from top-level finished goods down through all subassemblies and raw materials, then load into Infor prdmcfg. Routing operations migrate to prdrout with work centre assignments. This phase runs after Items are loaded because BOM components reference Item numbers that must already exist in Infor.

Outstanding invoices, credit memos, and payment schedules require careful open-item sequencing at cut-off. We map due dates, outstanding amounts, and currency codes explicitly. Any partial payments are flagged as split-line entries in Infor's ardist distribution table. Open AR migration runs after Customer and GLAcct are loaded because invoice records require Customer and account references.

Outstanding vendor invoices and credit memos require the same open-item sequencing treatment as AR. We map due dates, outstanding amounts, and currency codes from HashMicro's AP module to Infor's apinvh header and apinvd distribution tables. Partial payments become split-line entries. Open AP migration runs after Supplier and GLAcct are loaded.

HashMicro Sales Orders include header status, line items with quantities and pricing, and owner assignments. We export all open and partially-shipped orders for migration into Infor socomoc. Orders with pending allocations are flagged for the customer to resolve manually after load. Order-to-invoice linkages from HashMicro are preserved via custom reference fields in Infor.

HashMicro Purchase Orders and Goods Receipt records are tied to Vendor and Item masters. We preserve PO-to-GR linkages and flag any partially-received orders at cut-off for downstream inventory reconciliation. POLine pricing, terms, and delivery schedules map to Infor popomh header and popomd line tables. Open PO migration runs after Suppliers and Items are loaded.

HashMicro employee profiles include roles, departments, compensation history, and attendance records. Effective-dated compensation changes require row-level sequencing to maintain history in the destination HRM. We map HashMicro department codes to Infor hrlemp CostCentre assignments and job titles to position codes. Compensation history loads as effective-dated rows in Infor's hrlemp salary tables. HRM migration is sequenced after GLAcct because cost distribution entries require account references.

HashMicro Projects carry tasks, assignees, time entries, and cost tracking. Project-to-item linkages (consumed materials, labour) require cross-object joins handled via staged extraction. We load project headers to Infor cdeptsk, then load project tasks, time entries, and cost transactions as related records. Projects referencing non-existent Items or Employees at load time are held in a reconciliation queue.

HashMicro asset registers include acquisition cost, depreciation schedules, location, and assigned custodian. Depreciation method and accumulated depreciation at cut-off are critical fields. We validate these against Infor's faasset table requirements including asset class, serial number, and location codes. Depreciation schedules from HashMicro map to Infor faasset depreciation method and life settings, and accumulated depreciation is loaded as a separate asset history record.