Migrate from HashMicro ERP to Dolibarr ERP

HashMicro's Finance module stores a multi-level COA with codes, names, account types, currency settings, and entity associations. Dolibarr uses Bank Accounts (for cash and credit accounts) and Categories (for income and expense classification) rather than a traditional GL hierarchy. We split each HashMicro COA entry by type: balance sheet accounts map to Bank Accounts in Dolibarr; income and expense accounts map to Categories with a category tree structure. Multi-entity COAs require separate Bank Account and Category sets per entity, which we set up before loading. Currency settings are preserved in the Bank Account's currency field.

HashMicro Customer and Vendor master records (addresses, contact details, payment terms, tax IDs, open AR/AP balances) map to Dolibarr Third Parties. We use the Type field (Customer / Supplier / Both) to set Dolibarr's nature of third-party classification. Linked open AR/AP balances at cut-off migrate as separate Bank line entries under the corresponding Third Party record. Multi-entity configurations require Third Party records to be scoped per entity if HashMicro stores separate Customer records per entity.

HashMicro Items (SKU, description, unit of measure, cost, pricing tiers, reorder points, BOM links) map to Dolibarr Products. We set the type to Product (for inventory-bearing items) or Service based on HashMicro's item type. Pricing tiers from HashMicro become Dolibarr Customer Specific Prices linked to the relevant Third Party. Inventory quantities and reorder points migrate to Dolibarr's stock module if the Stock module is activated. BOM links for manufactured items require the Dolibarr BOM module (a community or third-party module) to be installed before migration.

HashMicro Sales Orders (status, line items, owner assignments, linked Customer and Item records) map to Dolibarr Customer Orders. We preserve order status by mapping HashMicro's status codes to Dolibarr's draft / validated / approved / closed / cancelled / billed state model. Line items reference the migrated Product records via the Products/Service link. Historical closed orders migrate with their full line item detail; open orders are flagged for downstream order-to-invoice processing in Dolibarr after cutover.

HashMicro Purchase Orders and Goods Receipt records map to Dolibarr Supplier Orders. We preserve PO-to-GR linkages by creating Dolibarr Supplier Order records with received quantity tracking aligned to HashMicro's receipt status. Partially received orders are flagged at cut-off for reconciliation by the customer's procurement team after go-live.

Outstanding HashMicro AR and AP invoices, credit memos, and payment schedules are mapped to Dolibarr Customer Invoices (unpaid) and Supplier Invoices (unpaid) respectively. We map due dates, outstanding amounts, and currency codes explicitly, and set Dolibarr's payment status to unpaid at cut-over. Any partial payment records are preserved as Payment entries linked to the invoice. Multi-currency AR/AP requires the corresponding Bank Account currency in Dolibarr to be set before migration.

Ledger journals and posted transactions from HashMicro migrate to Dolibarr as Bank Movement lines under the corresponding Bank Account or as general journal entries. Schema varies by HashMicro company configuration and fiscal year setup, so we handle date-range filtering and revalidation of posting dates against the destination fiscal year. Only summarised or opening-balance transactions migrate; full historical journal replay is documented as a separate engagement scope if the customer requires complete fiscal-year history.

HashMicro Projects (tasks, assignees, time entries, cost tracking, project-to-item linkages) map to Dolibarr Projects if the Project module is activated. We create the Project record first, then migrate tasks as Tasks under the Project, time entries as Task time records, and consumed materials as Product line items linked to the Project. Dolibarr's native project billing requires the Contracts module; we flag this and map the customer's project billing preference during scoping.

HashMicro Employee profiles (roles, departments, compensation history, attendance records) map to Dolibarr User records for system access and to HR module records (if the HR module is activated) for employment details. Effective-dated compensation changes are preserved as historical HR entries in Dolibarr's HR module. Attendance and timesheet data migrates as Project time entries under a dedicated internal project if Dolibarr's HR module is not activated.

HashMicro Asset registers (acquisition cost, depreciation schedule, location, custodian) map to Dolibarr Asset records. Depreciation method and accumulated depreciation at cut-off are critical fields that we validate against HashMicro's depreciation schedule before import. Dolibarr's standard Asset module handles straight-line and declining-balance depreciation; we recalculate any custom depreciation methods in HashMicro against Dolibarr's standard methods and flag discrepancies for the customer's accountant to review.

HashMicro BOMs and routing data (stored per Item) map to Dolibarr BOM records if the BOM module is installed. Multi-level BOMs require recursive explosion during export to preserve the full component hierarchy in Dolibarr. Dolibarr's BOM module is a community contribution; we confirm its activation status with the customer before migration and flag it as a prerequisite.

Regional tax configurations from HashMicro (GST for Singapore and Malaysia, VAT equivalents, local tax per entity) map to Dolibarr's Taxes and Charges Templates. We map each HashMicro tax code to the corresponding Dolibarr tax rate, account, and jurisdiction setting. Multi-entity tax configurations require separate Tax Templates per entity if HashMicro maintains per-entity tax jurisdictions.