Migrate from HashMicro ERP to Microsoft Dynamics 365 Business Central

HashMicro's Finance module stores the COA as a structured multi-level tree with account codes, names, types, and currency assignments. We export the full hierarchy and load it into Dynamics 365's G/L Account table (AccountMaster in F&O) maintaining the same account number structure as the primary key. Account types (Asset, Liability, Equity, Revenue, Expense) map directly. If HashMicro uses a non-calendar fiscal year (common in Asia Pacific), we align the fiscal year setup in Dynamics 365 before any ledger data is posted to prevent period-validation errors.

HashMicro Customer records include addresses, contact details, payment terms, and tax IDs. We preserve all Customer-to-open AR linkages at migration cut-off. Dynamics 365 Customer requires a corresponding Number (the dedupe key) which we map from HashMicro's customer_code. For multi-entity HashMicro deployments, each entity's customers map to the appropriate Legal Entity in the destination. Post-migration, open AR document numbers are matched to Customer Ledger Entries to prevent orphaned posting.

HashMicro Vendor records include addresses, payment terms, bank details, and tax registration. We map vendor_code as the Dynamics 365 Vendor Number. Open AP document numbers are matched to Vendor Ledger Entries at migration cut-off to preserve payment history and outstanding balances. Multi-entity vendor records are resolved by entity before insertion to prevent cross-entity AP contamination.

HashMicro Items carry SKU (product number), description, unit of measure, cost, and pricing tiers. We map item_code to the Dynamics 365 Item Number. For items with BOM links, we defer final inventory-quantity migration until BOM import completes, because manufactured items require the BOM structure to be in place before inventory transactions reference them. Stock module quantities and reorder points migrate from the Inventory module as warehouse tracking entries in Dynamics 365.

Outstanding invoices, credit memos, and payment schedules require open-item sequencing at cut-off. We map due date, outstanding amount, and currency code explicitly. Partial payments are flagged with remaining-open amounts. HashMicro may carry AR in multiple currencies per entity; we remap currency codes to Dynamics 365's currency table before inserting ledger entries. Any partially-paid invoices are flagged as open items for the customer's AR team to reconcile post-go-live.

Outstanding vendor invoices and credit memos migrate as open Vendor Ledger Entries with document number, posting date, due date, and remaining amount preserved. Currency codes are remapped to Dynamics 365's currency configuration. Any partially-received purchase orders that have associated GRNs (Goods Receipt Notes) in HashMicro require the GRN to be posted in Dynamics 365 before the PO invoice can be matched, and we flag this sequencing dependency in the migration plan.

Ledger journals and posted transactions are extractable in batch from HashMicro, but schema varies by company configuration and fiscal year. We handle date-range filtering and revalidate posting dates against the Dynamics 365 fiscal calendar to avoid period-closed errors. For multi-entity deployments, we split ledger history by entity and map each entity to a separate Legal Entity or Company in Dynamics 365 before loading.

HashMicro employee profiles include roles, departments, compensation history, and attendance records. Effective-dated compensation changes require row-level sequencing to preserve history in the destination HRM module. We map employment status, department, job title, and manager hierarchy. Salary and compensation history migrates as effective-dated HRM entries with the original effective-from dates preserved. Attendance records are migrated as HRM absence registrations or time entries depending on the destination HRM configuration.

HashMicro Sales Orders and Quotes carry header fields (order number, customer, dates, status) and line items (item, quantity, unit price, discount). Open orders migrate as unposted Sales Orders with status preserved so the sales team can continue processing in Dynamics 365. Closed orders migrate as historical posted invoices if the customer requests full history, or as archived documents if the scope excludes historical orders. We map order number as the Dynamics 365 External Document Number.

HashMicro Purchase Orders map to Dynamics 365 Purchase Orders with vendor, order number, lines, and delivery addresses preserved. Partially-received orders are flagged with the outstanding quantity remaining because the GRN (Goods Receipt Note) linkage must be re-established in Dynamics 365 by posting the remaining receipt against the migrated PO. PO-to-Vendor linkage is preserved by resolving the vendor_number to the Dynamics 365 Vendor Number at migration time.

HashMicro BOMs and routing data are stored per Item. Multi-level BOMs require recursive explosion during export to preserve the full component hierarchy before loading into Dynamics 365's BOM structure. Each BOM level is assigned a Version in Dynamics 365 with the correct item-unit-of-measure conversion. Routing data (work centres, operation sequences, times) maps to the Production Route entity. We flag any HashMicro BOM with more than three levels for explicit recursive explosion before the first record is inserted.

HashMicro Projects carry tasks, assignees, time entries, cost tracking, and linked consumptions (materials, labour). We map Project as a Jobs or WBS (Work Breakdown Structure) entity in Business Central, or as a Project with Work Breakdown Structure in F&O. Project-to-item linkages require cross-object joins that we handle via staged extraction: project data loads first without line details, then linked item consumption rows load with the Project ID already resolved to avoid foreign-key errors.

Asset registers include acquisition cost, acquisition date, depreciation method, accumulated depreciation at cut-off, location, and assigned custodian. Depreciation method and accumulated depreciation at cut-off are the most critical fields because Dynamics 365 posts depreciation independently after go-live and must continue from the correct accumulated-depreciation balance. We validate the depreciation method in HashMicro against the closest Dynamics 365 depreciation profile and flag any mismatches for the customer's accountant before final migration.

Regional tax configurations for GST, VAT, or local equivalents are stored per HashMicro entity and per item class. HashMicro's Singapore, Philippines, Malaysia, and Indonesia compliance features include jurisdiction-specific tax codes that we map explicitly to Dynamics 365 Tax Groups and Tax Posting Setup. Jurisdiction mismatches are flagged in the migration inventory, and the customer confirms the destination tax configuration with their tax adviser before final data load.