Migrate from PayTraq to Odoo ERP

PayTraq GL account codes and types (Asset, Liability, Equity, Revenue, Expense) map directly to Odoo Account records. We establish the Odoo Chart of Accounts as the first migration phase so that all subsequent GL references are satisfied. Account groups in PayTraq map to Odoo account group or row configuration. Cost-center tagging, if used in PayTraq, requires manual Odoo analytic account setup post-migration.

PayTraq Clients import via CSV template (matched by name or client code) and map to Odoo Partner records with Partner Type set to Customer. PayTraq fields including currency, payment terms, and tax ID map to Odoo Partner fields (property_payment_term_id, property_supplier_payment_term_id, vat, country_id). Multi-currency client assignments are preserved.

PayTraq Suppliers import via the same CSV template as Clients and map to Odoo Partner records with Partner Type set to Vendor. Purchase terms and currency assignments migrate to Odoo's vendor-specific payment term and currency fields. We maintain Supplier object identity from PayTraq for audit trail purposes.

PayTraq Products map to Odoo Product variants. Per the Odoo Apps Store PayTraq migration module guidance, we configure the Costing Method (AVCO or FIFO) in Odoo before fetching product data. Unit of measure, product category, and standard cost from PayTraq map to Odoo fields. PayTraq product codes become Odoo default_code for dedupe.

PayTraq Services import via a separate CSV template and merge into the Odoo Product table as service-type products. Service price lists from PayTraq map to Odoo seller IDs and pricelist entries. The distinction between storable and service products in Odoo determines inventory tracking behavior, which we configure at migration time.

PayTraq Sales Invoices map to Odoo Account Move records with move_type=out_invoice. Invoice headers and line items migrate together with tax rates, discount amounts, and currency preserved. Multi-currency invoices require currency_id and exchange rate mapping. Invoice status (draft, posted, cancelled) maps to Odoo state.

PayTraq Purchase Invoices map to Odoo Account Move with move_type=in_invoice. Supplier references, invoice amounts, and line items transfer with currency and tax mapping. Partially received POs that generated invoices are flagged for reconciliation against Odoo's vendor bill and receipt logic.

PayTraq Purchase Orders map to Odoo Purchase Order records. PO headers, supplier references, and line items migrate with product and quantity. Odoo's partial receipt handling differs from PayTraq's model, so we flag any partially-received POs for admin review of the receipt-to-bill matching workflow post-migration.

PayTraq Journal Entries are double-entry records with debit/credit lines mapped to GL accounts. We migrate these after the Chart of Accounts is established. Prepaid expense journal entries reference the Prepaid Expenses GL account group and are flagged for manual reconstruction since PayTraq's API does not expose the allocation schedule timeline.

PayTraq lacks a bulk export path for warehouse inventory, so we read current on-hand quantities per product-warehouse combination via individual API calls (throttled to PayTraq's 1 req/sec limit) and write to Odoo's quant table under the corresponding warehouse location. Each PayTraq warehouse maps to an Odoo warehouse with stock_location hierarchy. This approach is slower than CSV but preserves all on-hand quantities and warehouse assignments.

PayTraq price list rows for Products and Services map to Odoo Pricelist or Pricelist Item records. Currency and effective-date ranges migrate. Multiple PayTraq price tiers (wholesale, retail, etc.) become separate Odoo Pricelist records linked to the product.

PayTraq Employee records import via CSV and map to Odoo Employee objects with compensation fields and effective dates. Payroll history preservation depends on whether the destination Odoo instance includes the Payroll app; we flag this for scoping.