Migrate from HashMicro ERP to Odoo ERP

HashMicro's Finance module stores the COA as a structured multi-level tree with account codes, names, types, and currency assignments per entity. We map each HashMicro account to an Odoo account.account record, preserving the code structure as name_search key, setting account_type (asset, liability, equity, income, expense, off_balance), and assigning the appropriate reconcile flag. Multi-currency accounts receive the currency_id reference. Odoo's property fields for default debit/credit accounts are configured per company after import.

HashMicro Customer and Vendor master records are distinct objects; Odoo uses a single res.partner model where customer_rank and supplier_rank flags determine role. We import each unique partner once, setting both flags when both roles exist in HashMicro, and creating separate partner records when a customer/vendor split existed. Address, tax ID, payment terms, and bank details map to the corresponding Odoo res.partner fields. open AR/AP balances are carried as separate invoice records after partners are loaded.

HashMicro Items with SKU, description, unit of measure, cost, and pricing tiers map to Odoo product.template (shared attributes) and product.product (variant records). When HashMicro Items have attribute-based variants, we split them into template plus variant records. Cost maps to standard_price on product.product. Reorder points and stock quantities from the HashMicro Inventory module become Odoo reordering_rule records against the stock.location model. The product_category from HashMicro maps to product.product categ_id.

HashMicro BOMs and routing data are stored per Item with component lines and operation steps. Multi-level BOMs require recursive explosion during export so that sub-assembly components are created as separate mrp.bom records and linked correctly. We map HashMicro operation steps to mrp.bom.line and mrp.routing.workcenter records. Odoo mrp.bom.type is set to normal for standard BOMs and kit for non-stocked assemblies. Component quantities and unit of measure conversions are applied during the transform phase.

HashMicro Sales Orders with line items, pricing, owner, and status map to Odoo sale.order and sale.order.line. The HashMicro order status (draft, confirmed, done, cancelled) maps to Odoo state (draft, sent, sale_order, done, cancel). Pricing from HashMicro order lines migrates as Odoo price_unit with the product_uom_qty and discount fields. sale.order.line tax_id is resolved against the Odoo account.tax records created from the Tax Codes mapping.

HashMicro Purchase Orders and Goods Receipt linkage map to Odoo purchase.order with GRN tracking via stock.picking linked through purchase.order_line. We preserve the PO-to-GR linkage by mapping Goods Receipt records to Odoo stock.picking records of type incoming, linked to the purchase.order. Partially received orders are flagged at cut-off with a note in the migration report so the customer's Odoo admin can reconcile open quantities manually after go-live.

Outstanding HashMicro invoices, credit memos, and payment schedules map to Odoo account.move records of type out_invoice, out_refund, in_invoice, in_refund. Due dates, outstanding amounts, and currency codes are mapped explicitly. Partial payments are modelled as Odoo account.payment records linked to the original account.move via the reconcile model. We validate total outstanding AR and total outstanding AP against Odoo's account.move reconciled totals after import.

HashMicro employee profiles with department, role, compensation history, and attendance map to Odoo hr.employee, hr.department, and hr.contract. Effective-dated compensation changes are stored as hr.contract records with start_date and wage fields so that history is preserved in Odoo. Department hierarchy from HashMicro maps to hr.department and parent_id references. hr.employee is scoped to the appropriate Odoo company_id for multi-entity migrations.

HashMicro Projects carry tasks, assignees, time entries, and cost tracking with project-to-item linkages for consumed materials and labour. We map each HashMicro project to an Odoo project.project record and each task to project.task, preserving the project.task assignees via user_id and planning fields. Project-to-item cost tracking requires custom fields or Odoo Timesheet product configuration; we flag this for post-migration Odoo Studio setup.

HashMicro asset registers include acquisition cost, depreciation schedule, depreciation method, location, and custodian. We map these to Odoo account.asset and account.depreciation.line records, computing the depreciation schedule from the original method and period so that accumulated depreciation at cut-off is preserved accurately. Asset category from HashMicro maps to account.asset.category for default depreciation parameters in the destination.

Regional tax configurations from HashMicro for GST, VAT, and local equivalents map to Odoo account.tax records with the correct amount, amount_type, and tax_scope per country. For multi-jurisdiction setups, we configure account.fiscal.position records that map HashMicro tax codes to the destination Odoo tax jurisdiction, applying automatically when vendor or customer addresses match the fiscal position country rules.