Migrate from Achiever Technology to Odoo ERP

Achiever stores account structures tailored to Hong Kong and Mainland China chart layouts, often including multi-segment accounts (company-division-account format) that Odoo's flat account.code model does not support natively. We split multi-segment account codes into separate Odoo account records and use an account.analytic.account for the cost-center segment, or we configure Odoo's account group hierarchy to preserve the original segmentation. Tax codes, depreciation accounts, and bank accounts are mapped to their corresponding Odoo account types before any journal entry import begins.

Achiever customer records carry extensive custom fields for regional compliance, trade documentation, and credit terms that Odoo's standard res.partner model handles through custom fields. We preserve all associated addresses, contact persons, credit limits, and payment terms. The customer_type field is set to 'customer'. Deduping uses company registration number or email where available. Achiever's custom address formats (Hong Kong street, Mainland China province-city-district) are mapped to Odoo's street, city, state_id, country_id structure.

Vendor records migrate to Odoo res.partner with customer_type set to 'vendor'. Achiever vendor-specific fields including tax registration numbers, import/export license codes, and bank account details for HK bank transfers are preserved as custom fields. Multi-address vendor setups (separate billing and receiving addresses) are mapped to Odoo's child contact pattern under the parent vendor partner.

Open invoices in Achiever migrate to Odoo account.move records of type 'in_invoice' or 'in_refund', with the vendor partner lookup resolved before insertion. Outstanding payment amounts are preserved as account.payment records linked to the invoice via reconcile links. We sequence the cutover to avoid duplicate postings by requesting a freeze on new AP entries in Achiever for a minimum of 48 hours before the final export is generated.

Open customer invoices migrate to Odoo account.move records of type 'out_invoice' or 'out_refund', with the customer partner lookup resolved before insertion. Aging reports must match between Achiever and Odoo after migration, so we preserve the original invoice dates, due dates, and payment terms. Any partial payments already recorded in Achiever are migrated as account.payment records with reconcile links to the corresponding invoice.

Achiever's ledger history includes customer-specific formats with accrual reversals, intercompany entries, and localized journal line conventions that require parsing before mapping to Odoo's account.move + account.line structure. We extract complete journal batches, map each line to the corresponding Odoo account, and preserve the original debit and credit amounts in the company's functional currency. If Achiever uses a secondary currency for certain entries (RMB alongside HKD), we configure Odoo's multicompany or multi-currency setup before importing.

Bank account masters and cash GL accounts migrate to Odoo account.journal records of type 'bank' or 'cash'. Opening balances are reconciled against the source trial balance extracted from Achiever before cutover. We request the trial balance at a specific cutover date from Achiever and use it to set the account.journal opening balances in Odoo before any transactions are posted.

Hong Kong and China tax codes including GST/VAT equivalents, withholding tax rates, and deferred tax configurations require mapping to Odoo's account.tax model. We preserve effective dates and tax scope (sale, purchase, none) per Odoo's tax configuration. If Achiever uses tax codes that Odoo's standard Hong Kong localization does not include, we create custom account.tax records before any invoice migration begins.

HRM records including employee profiles, compensation history, and organizational hierarchy migrate into Odoo's hr.employee model. We handle effective-dated compensation rows by creating hr.contract records with the appropriate start dates and wage amounts. Department and job title hierarchies from Achiever map to Odoo's hr.department and hr.job models. Employee bank details for payroll are preserved as hr.employee.bank.account records.

Project accounting data including budgets, work breakdown structures, and cost allocations require field-level mapping to Odoo's project.project and account.analytic.account models. Custom project statuses in Achiever are translated to Odoo's project.task.stage values. If Achiever tracks project-level P&L through a cost-center account structure, we preserve the analytic account mapping so that Odoo's project invoicing and cost analysis reports remain accurate post-migration.

Achiever product records with custom fields for trade compliance, origin certificates, or multi-unit-of-measure setups map to Odoo's product.product and uom.uom models. We preserve the original SKU, product category, cost price, and sales price. If Achiever tracks lot numbers or serial numbers for inventory valuation, we map these to Odoo's stock.production.lot model, provided the Odoo inventory app is active in the destination configuration.

Documents stored within Achiever's file management layer are exported by file path and reattached to the corresponding Odoo records (res.partner, account.move, project.project) via ir.attachment. We preserve original filenames and associate them using Odoo's attachment relation fields (res_model, res_id). Customers should confirm during discovery whether the Achiever export includes binary document files or only references.