Migrate from Unit4 ERP to Odoo ERP

Unit4 Customer records map to Odoo Contact with the Company flag set to True, which creates the corresponding Company record automatically. We map billing address to Odoo's partner address fields, payment terms to Odoo's property_payment_term_id, and credit limit to credit_limit on the partner. Tax registration numbers map to Odoo's vat field for VAT reporting. Any custom Unit4 Customer fields require an Odoo custom field or a Python pre-import hook to resolve.

Unit4 Supplier records map to Odoo Contact with supplier_rank set to 1 (and customer_rank to 0), creating a Supplier-type Company in Odoo. W-9/W-8 status and bank details map to Odoo's res.partner.bank records attached to the partner. Multi-address support migrates as additional partner address records with sequence ordering preserved. Purchase-specific fields like supplier taxes and lead times map to Odoo's property_supplierinfo records.

Unit4's multidimensional account structure with cost centres, departments, and projects as natural axes requires flattening before Odoo import. We extract account codes and descriptions, then create Odoo account.account records. The customer's cost-centre hierarchy becomes a set of Odoo account.analytic.account records (analytic dimensions) that the customer configures as one, two, or three analytic tags per the Odoo analytic plan. We discuss whether to preserve the Unit4 natural-account hierarchy in full or collapse it to a simplified Odoo chart during scoping.

General Ledger account codes, account types (asset, liability, equity, income, expense), and posting controls migrate directly to Odoo account.account. Currency settings and consolidation flags require mapping to Odoo's account.account properties. Any Unit4 account that is a posting-control account for automatic tax or rounding requires a manual review to ensure the equivalent configuration exists in Odoo's tax settings.

Unit4 Item records map to Odoo product.product with type set to product (stockable), consumable, or service based on Unit4's stock-control flags. GL mapping for COGS and inventory accounts becomes Odoo's property_account_income_id and property_account_expense_id on the product. Pricing matrices in Unit4 require either a product.pricelist item or a product.template attribute line in Odoo, depending on complexity. We discuss whether to migrate full pricing history or just the current active price list during scoping.

Outstanding Unit4 AP and AR documents migrate as Odoo account.move records with move_type set to out_invoice (AR) or in_invoice (AP). Document headers (invoice number, date, due date, currency, amount) map directly; line items require product or account resolution against the migrated product and account data. Open amounts and payment states preserve so that Odoo's reconciliation process can match payments post-go-live. We do not re-print or re-email these documents; they are imported in a state that allows Odoo to reconcile them against new payments.

Unit4 journal history migrates as Odoo account.move records with move_type set to entry. We scope the date range during discovery (full history vs a configurable window) because bulk import of hundreds of thousands of historical lines requires Odoo's direct PostgreSQL insertion or a chunked CSV approach to avoid timeouts. Locked journal entries from Unit4 become posted moves in Odoo. We preserve posting dates, source references, and user stamps as Odoo move line name fields and move metadata. Account and analytic line structure must be resolved against the migrated chart of accounts and analytic plan.

Posted Unit4 journal entries migrate as Odoo account.move with move_type entry. The Unit4 journal code maps to Odoo's journal_id; account code maps to account_id; amount, debit, and credit map to balance. Multi-line entries with tax lines require tax code resolution against the migrated tax matrix. We flag any Unit4 journal entries that reference accounts or tax codes not yet migrated; those records are held in a reconciliation queue until the prerequisite data is loaded.

Unit4 country-specific tax matrices with rates, jurisdictions, and posting rules map to Odoo account.tax records. Unit4's tax type (VAT, sales tax, withholding) maps to Odoo's tax_scope; the tax rate maps to amount. Complex compound taxes and reverse-charge mechanisms require manual Odoo configuration review. Jurisdiction combinations that do not have an Odoo standard tax template are flagged for the customer's admin to configure post-migration. Country-specific Odoo tax templates (l10n modules) are pre-installed in the destination Odoo instance before migration begins.

Unit4 asset master records with depreciation schedules, cost centres, and insurance values map to Odoo account.asset records. Depreciation method (straight-line, declining balance, sum-of-years) requires alignment with Odoo's asset profile settings. Depreciation board entries (already-posted depreciation lines) migrate as Odoo posted account.move records linked to the asset. We align on a per-asset-category conversion approach during scoping because Unit4 and Odoo may use different depreciation conventions. Insurance value and cost-centre assignments become custom fields on the Odoo asset record.

Unit4 bank account masters with currency, account type, and reconciliation settings migrate as Odoo account.journal records of type bank or cash. Opening balances reconcile as a first Odoo bank statement or a manual opening entry. Bank reconciliation settings map to Odoo's journal's allow_date_setting and to account.journal's receivable/payable account references.

Unit4 HCM employee records with employment history, compensation, job titles, and department assignments migrate to Odoo hr.employee. Effective-dated employment changes (multiple assignments or role changes) require careful sequencing: we import the most recent active assignment as the primary Odoo record and hold prior assignments as a historical note in a custom field or an Odoo hr.contract record. Department and cost-centre assignments resolve against the migrated analytic account plan. We flag any Unit4 payroll-specific fields that do not have an Odoo equivalent; these require review by the customer's HR admin post-migration.