Migrate from Xledger to Odoo ERP

Xledger Entities map to Odoo Company records. Each Xledger Entity carries its own Subledger, Chart of Accounts, and bank connections; we create a corresponding Odoo Company and map the Entity's base currency to Odoo's currency settings. Multi-currency support requires enabling the Accounting app's multi-currency configuration per Company. Odoo's shared ledgers option must be configured if the customer wants cross-company reporting without separate company-level P&L exports.

Xledger's Chart of Accounts migrates to Odoo Account records. We map account type (Asset, Liability, Equity, Revenue, Expense) from Xledger's account classification to Odoo's account.account model and reconcile numbering schemes. Non-profit and fund accounting accounts require Odoo's statutory reporting configuration or a third-party localisation module. Account code length and hierarchical structure are preserved; Odoo's view accounts are used for parent-level grouping.

Xledger Subledgers map to Odoo Journal records. An AP Subledger becomes a Vendor Bill Journal; an AR Subledger becomes a Customer Invoice Journal; a Banking Subledger becomes a Bank Journal; a Project Subledger becomes a Miscellaneous Journal for project cost recording. We preserve the Subledger-to-Entity relationship as Company assignment on the Journal so that journal entries are correctly scoped to the originating entity.

Xledger open AP and AR Subledger invoice records migrate as Odoo account.move records of type out_invoice or in_invoice. We preserve invoice number, invoice date, due date, partner (Customer or Supplier), line amounts, tax codes, and payment terms. Payment terms from Xledger map to Odoo's account.payment.term model. Historical closed invoices migrate as posted account.move records against the General Ledger. This is a critical distinction from balance-only migration: Odoo stores open AP/AR as invoice records, not aged trial balance entries.

Xledger journal entries migrate to Odoo account.move records. Multi-line distributions with debit and credit columns map to move_line records with account_id, debit, credit, and analytic_account_id references. Xledger's dimension and cost-centre fields map to Odoo's analytic account model. Historical journal lines preserve the original posting date, making Odoo's lock date configuration critical to set before migration to prevent accidental reposting.

Xledger intercompany journal entries reference both the source Entity and the destination Entity Subledger. Odoo does not natively generate intercompany elimination entries; we flag every cross-Entity posting during data profiling, document the elimination pair, and provide Odoo journal entries with a memo field indicating elimination status for the customer's accountant to post in the consolidation company. This requires the customer to decide whether to include, merge, or drop intercompany postings before migration.

Xledger Customers and Suppliers map to Odoo res.partner records. Customer maps to partner with customer_rank set to 1; Supplier maps with supplier_rank set to 1. Xledger's multi-entity shared customer records are deduplicated by partner name or tax ID during migration. Payment terms, tax codes, and Subledger references migrate as partner fields. Street, city, country, and email map to Odoo's standard address fields.

Xledger fixed asset records migrate to Odoo's account.asset model. We map acquisition date, original cost, depreciation method (straight-line or declining balance), useful life in months, and accumulated depreciation. The asset category maps to an Odoo asset model that determines the depreciation journal and account. Current depreciation schedules are preserved as posted depreciation lines in Odoo; the customer must configure the depreciation board in Odoo after migration.

Xledger budget items created at the Entity level map to Odoo crossovered.budget records. Each budget version and forecast iteration becomes a separate budget in Odoo. Account and dimension assignments map to Odoo's crossovered.budget.line with the relevant account_id and analytic_account_id. Odoo's budget module must be installed; it is not part of the core accounting app by default. Budget vs actual reporting requires Odoo's accounting report configuration post-migration.

Xledger project records map to Odoo project.project linked to an account.analytic.account for financial tracking. Project billing, revenue recognition, and cost allocation migrate to Odoo's project costing and billing features. Xledger's Subledger-to-project references become Odoo's analytic account on project journal entries. The Project app must be installed in Odoo alongside Accounting. If the customer uses Xledger's fund accounting for grants, we map fund restrictions to Odoo analytic tags.

Xledger bank account records migrate to Odoo account.journal records of type bank. Routing details, account type, currency, and Entity assignment migrate as journal fields. Bank API integrations configured in Xledger (JPMorgan, Wells Fargo, Bank of America) are documented as a configuration reference for reconfiguration in Odoo via Odoo's built-in bank synchronization feature or a third-party integration. The bank account must be reconciled manually in Odoo after migration or via automatic bank statement import.

Documents and attachments stored against journal entries, vendors, customers, and assets migrate as Odoo ir.attachment records linked via res_model and res_id. We migrate document metadata and URL references. Large-volume document archives (thousands of files) require chunked migration with file validation. Any OCR-captured receipts stored in Xledger are documented as image references; the OCR data itself is preserved as text fields on the related record, but the receipt images are migrated as attachments.