Migrate your HashMicro ERP data

HashMicro's Finance module stores the COA as a structured, multi-level tree. We export the full account hierarchy including codes, names, account types, and currency settings. Mappings to destination COA structures are configured during scoping.

Customer and Vendor master records include addresses, contact details, payment terms, and tax IDs. We preserve all linked open AR/AP balances and transaction histories at migration cut-off. Multi-entity setups require entity-to-entity mapping before import.

Items are catalogued with SKU, description, unit of measure, cost, and pricing tiers. Inventory quantities and reorder points are extracted from the stock module. BOM links for manufactured items are preserved as separate row-level records.

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, flagging any partial payments that span the migration date.

Ledger journals and posted transactions are extractable in batch, but schema varies by company configuration and fiscal year setup. We handle date-range filtering and revalidation of posting dates against the destination's fiscal calendar.

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 system.

Sales Orders, Quotes, and Pipeline records flow from the CRM module into Inventory and Finance automatically. We export all open and closed orders with status, line items, and owner assignments. Pipeline stage names require mapping if the destination uses a different stage schema.

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.

BOMs and routing data are stored per Item. Multi-level BOMs require recursive explosion during export to preserve the full component hierarchy in the destination manufacturing module.

Projects carry tasks, assignees, time entries, and cost tracking. Project-to-item linkages (consumed materials, labour) require cross-object joins that we handle via staged extraction before loading into the destination.

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 the destination's asset module schema.

Regional tax configurations for GST, VAT, or local equivalents are stored per entity and per item class. We map these to destination tax codes explicitly, flagging any jurisdiction mismatches.