Migrate from Triumph to Odoo ERP

The Triumph chart of accounts migrates directly to Odoo account.account records. Each account.code maps to the Odoo code field, account.name maps to name, and account_type maps to Odoo's account_type (receivable, payable, other, liquidity, etc.). We extract the full account hierarchy including parent relationships if defined. This phase runs first because all other modules (debtors, creditors, inventory) reference GL accounts as default receivable, payable, or expense/revenue accounts. Historical balance amounts for each account are posted as opening journal entries during the final migration window. Tax codes in the Triumph GL become Odoo account.tax records linked to the relevant accounts.

Triumph debtor records map to Odoo res.partner with customer_rank set to a positive value and the appropriate receivable account assigned as the property_account_receivable_id. Debtor name, address, contact details, ABN, and payment terms migrate as partner fields. Open debtor invoice balances (unpaid sales invoices in Triumph) migrate as Odoo account.move records of type out_invoice linked to the partner. Reconciliation happens by matching invoice reference and amount against the outstanding balance in Triumph's debtor ledger.

Triumph creditor records map to Odoo res.partner with vendor_rank set to a positive value and the appropriate payable account assigned as the property_account_payable_id. Creditor name, address, contact details, ABN, and payment terms migrate as partner fields. Open creditor invoice balances (unpaid purchase bills in Triumph) migrate as Odoo account.move records of type in_invoice linked to the partner. Supplier statements from Triumph reconcile against Odoo's vendor bill balance to verify the payable ledger matches post-migration.

Triumph bank account records map to Odoo account.journal records of type bank or cash, with the corresponding GL bank account assigned as the default_account. Bank reconciliation transactions from Triumph (matched and unmatched items) migrate as Odoo account.bank_statement.line records within the associated journal. Note that Odoo does not have a native automated bank statement import from file for all Australian bank formats; we document the required Odoo bank statement import format so the customer's admin can configure the daily import routine post-migration.

Triumph Electronic Funds Payments (EFT batches, payment runs) map to Odoo account.payment records with the payment_method_line matching the bank journal. Payment status (approved, sent, cleared) from Triumph carries into Odoo's payment state field. Outstanding EFT transactions that have not yet cleared the bank become Odoo payments in a draft or posted state depending on the Triumph payment run status at migration cutover.

Triumph inventory items migrate to Odoo product.product records with product_type = product and the inventory valuation method (FIFO or Standard from Triumph) set on the associated product.category as property_valuation = automated and property_cost_method = fifo or standard. Opening stock quantities migrate as Odoo stock.quant records against the appropriate warehouse location. If Triumph tracks minimum stock levels or reorder rules, these migrate to Odoo stock.reordering_rule records on the product.

Triumph Inventory module assembly records and bill-of-materials entries map to Odoo mrp.bom records as a separate migration pass after product and component stock quants are loaded. The BOM product (assembled item) references the Odoo product.product created in the inventory phase. Component quantities and bom_line records are created from the Triumph assembly component list. BOM routing and workcenter definitions require manual configuration in Odoo Studio post-migration because Triumph does not expose workcenter-equivalent data in its standard export. This phase is deferred until all product and component records have stable Odoo IDs.

Triumph add-on modules introduce custom fields on debtor and creditor records (for example, ABN validation fields, custom credit limit fields, or industry classification codes). We audit the Triumph module configuration to identify all custom fields on debtor and creditor records before migration, pre-create each as an Odoo ir.model.field on res.partner with the appropriate field type (char, selection, float, boolean), then migrate the values during the partner import phase. Without pre-creation, Odoo's strict schema enforcement causes import errors on any record containing a custom field value.

Triumph payment term codes (Net 30, Net 60, Cash, etc.) attached to debtor and creditor records migrate to Odoo account.payment.term records with the corresponding line values (number of days, percentage of total). Payment term assignments on debtor and creditor records map to the Odoo property_payment_term_id and property_supplier_payment_term_id fields on res.partner.

Triumph add-on modules that extend the Inventory module introduce custom fields on item records such as warehouse-specific codes, bin location fields, or supplier product codes. We audit these before migration, pre-create them as Odoo ir.model.field records on product.product, then load values during the product import phase. Custom fields introduced by Triumph's optional modules are a common source of silent data loss in ERP migrations when they are not identified and pre-created in the destination schema.

Triumph's closed fiscal periods require coordination with the customer's finance team to set an Odoo accounting lock date before migration begins. Historical journal entries from closed Triumph periods migrate as Odoo account.move records with the move_type set to opening_balance (for the earliest open period) or regular for subsequent periods. The lock date prevents back-dating entries beyond the agreed migration cutover period. We post all historical entries in a single batch and then set the lock date immediately after validation to prevent accidental back-posting.

Triumph user accounts referenced on debtor records (credit controller assignments), creditor records (buyer assignments), and inventory records (stock controller) are resolved against Odoo res.users by matching the username or email. Any Triumph owner without a matching Odoo user is placed in a reconciliation queue. The customer's Odoo admin provisions missing users before record import resumes because OwnerId references on account.move and stock.quant records require a valid res.users ID at insert time.