Migrate from Aqilla to Odoo ERP

Aqilla hierarchical account codes map to Odoo Account records with Account Type assigned (Receivable, Payable, Liquidity, Revenue, Expense, Contra). The parent-child hierarchy from Aqilla is preserved via Odoo's account groups or analytic account tags. Where Aqilla uses a flat code structure, we create Odoo accounts with codes matching the source; where the destination requires a different chart design, we produce a remap table with the customer choosing between code preservation and structural redesign.

Posted journal entries migrate to Odoo Account Move records. The journal reference is resolved to an Odoo journal (Sale, Purchase, General, Bank, Cash) before migration. Line-level debit and credit amounts map directly, with Odoo's account_id, debit, and credit fields populated. Effective dates are preserved as the Account Move date; the source reference number is stored in Odoo's ref field for audit trail.

Open journals in Aqilla that are not yet locked require a period-status checkpoint before migration. We carry them as Odoo draft Account Moves for the customer to review and post after confirming the period is open in both systems. Any journals in locked periods in Aqilla but open periods in Odoo are flagged as a reconciliation risk requiring explicit resolution before the cutover window.

Aqilla's up to 20 Analysis Codes per transaction do not map directly to a single Odoo field. We configure Odoo Analytic Accounts (for project-level or department-level analysis) and Analytic Tags (for flexible dimension tagging) to replicate the source structure. During scoping we identify which Analysis Codes carry recurring dimension values (e.g., Cost Centre, Region, Department) and configure those as Analytic Accounts, with one-time or categorical codes as Analytic Tags. The full Analysis Code inventory is documented with recommended Odoo equivalents.

Aqilla's inter-company journals post across two or more entities in a single transaction. Odoo Community Edition does not natively support inter-company posting; each entity receives its own database in Community. We decompose inter-company journals into individual entity-level Account Moves and create an elimination entry (typically a clearing account posting) that nets the inter-company balances in the destination. The inter-company elimination table is documented separately for the customer's consolidation team to review.

Aqilla customer records map to Odoo res.partner with the Customer checkbox enabled. Fields preserved include name, email, phone, website, credit limit, currency settings, and tax registration number. Open AR items (invoices, credit notes, payments) are migrated as related Account Moves linked to the partner. The customer flag distinguishes AR from AP in Odoo's payable ledger.

Aqilla vendor records map to Odoo res.partner with the Supplier checkbox enabled. Multi-currency settings, payment terms, and tax codes are preserved. Purchase invoices and credit notes migrate as Account Moves linked to the vendor partner, with open items surfaced as Odoo Vendor Bills and Credit Notes.

Aqilla purchase invoices with their container-header and subordinate-lines structure map to Odoo Vendor Bills. Each line transfers with account_id, product (if applicable), quantity, unit price, and tax configuration. Analysis codes attach to each line via Analytic Account or Tag where configured. Invoice references and dates are preserved for reconciliation matching post-migration.

Aqilla sales invoices migrate to Odoo Customer Invoices as Account Move records. Line items, tax breakdown, and payment terms are preserved. For invoices with partial payments already recorded in Aqilla, the payment entries migrate as related Account Payment records linked to the invoice.

Aqilla fixed asset records (acquisition date, cost, depreciation method, and book values) map to Odoo Asset records. We migrate the acquisition entry as an Odoo Asset with its depreciation table pre-populated from the source schedule. Mid-period acquisitions or assets with partial-year depreciation are flagged for manual review against the Odoo fiscal year configuration.

Aqilla inventory item definitions (stock valuation, costing method, on-hand quantities) map to Odoo Product records with the Storable Product type enabled and the current stock position recorded in Odoo Stock Quant. Open purchase orders and sales commitments require separate purchase and sales order migration; we flag these as out-of-scope unless specifically scoped during discovery.

Aqilla bank account definitions map to Odoo Bank Account records linked to the corresponding Account (type: Liquidity). Reconciled and unreconciled positions migrate as Account Moves and Bank Statement lines respectively. Unmatched items are flagged for re-reconciliation in Odoo post-migration; the reconciliation history is preserved as Odoo Note records on the relevant moves.