Migrate from Oracle Financials Cloud to Odoo ERP

Oracle Ledgers define currency, accounting calendar, and COA assignment. Each Oracle Ledger maps to an Odoo Company record with the corresponding currency and accounting period configuration. For organizations with multiple ledgers that should share a single Odoo Company (e.g., multiple currencies under one entity), we map multiple Oracle Ledgers to one Odoo Company and configure Odoo's multi-currency per journal. We flag any Oracle Ledger with a non-standard accounting calendar for Odoo fiscal year configuration before migration begins.

Oracle Business Units own AP, AR, and Assets subledger data and define legal-entity segmentation. They map to Odoo Company records in the multi-company configuration. Odoo Company records must exist in the destination before any subledger records (invoices, payments, assets) can be assigned to them. We create all Odoo Company records as a pre-migration step and hold subledger records in a pending state until the Odoo multi-company structure is validated by the customer's Finance team.

Oracle's multi-segment COA (typically Company, Division, Department, Account, Product, Project) is the most complex schema transformation in this migration. We detect all active flexfield segments during discovery and apply one of three strategies: concatenation (join segments into a single Odoo account code), segment dropping (preserve the Account segment and store others as Odoo Analytic Accounts), or hybrid (concatenate primary segments and overlay analytic distributions). The customer's Finance team selects the strategy during scoping, and we preserve a segment-value reference table in Odoo to prevent reporting gaps after cutover.

Oracle Supplier records include address, tax registration, payment terms, and bank account assignments. They map to Odoo Contact records with supplier=True. Oracle Supplier Sites map to Odoo Contact child addresses. We preserve supplier-level purchase history references and payment terms as Odoo vendor payment terms linked to the Contact. Tax IDs migrate to Odoo's fiscal_position matching logic for multi-country configurations.

Oracle Customer records span AR subledger with billing profiles, credit limits, and dunning assignments. They map to Odoo Contact records with customer=True. Oracle Bill-To and Ship-To sites map to Odoo Contact child addresses. Credit limits migrate to Odoo's internal credit management fields, and dunning schedules map to Odoo collection follow-up plans.

Oracle AP invoices carry ledger-specific distributions, accrual flags, and validation status. We migrate open (unpaid) and recent historical AP invoices as Odoo Vendor Bills with invoice lines mapped to Odoo account codes from the COA transformation. Oracle invoice distributions by line and account map to Odoo bill lines. We flag invoices in Oracle draft or unvalidated status for manual review before import; validated invoices migrate as Open in Odoo.

Oracle AR invoices include Revenue lines, tax lines, and receivables distributions tied to the subledger BU. We map AR transactions to Odoo Customer Invoices with customer, amount, and accounting date preserved. Tax lines migrate to Odoo's tax computation based on the mapped tax code. We flag inter-company AR invoices that involve two Oracle BUs and flag these for Odoo inter-company journal configuration post-migration.

Oracle Payments are linked to AP or AR invoices via payment schedules. We migrate payment records to Odoo Payments with settlement discounts and withholding tax details preserved. The Odoo payment must be reconciled against the corresponding Vendor Bill or Customer Invoice after both records exist in Odoo. We resolve the destination invoice reference using Oracle's payment schedule link before writing the Odoo payment record.

Oracle Assets carry depreciation books, asset categories, assignment records, and financial depreciation histories. We map asset registers and depreciation schedules to Odoo Asset records. For Oracle assets with multiple depreciation books (different methods or rates), we create one Odoo Asset and attach the primary depreciation schedule; secondary books with alternate methods are documented for Odoo asset revaluation post-migration. Depreciation histories migrate as Odoo asset value adjustment entries.

Oracle Bank Accounts are linked to Payment Process Profiles and Cash Management bank account balances. We map bank account details including branch, account number, currency, and the associated Payment Process Profile to Odoo Bank Account records. Odoo's bank reconciliation feature links to these accounts for cash management post-migration.

Oracle Financials maintains tax registries per tax authority with rates, recovery accounts, and applicability rules. We map tax codes to Odoo Tax configurations, creating Odoo Tax records with the corresponding rate, tax scope (sale/purchase/refund), and account assignment. We flag compound tax structures (multi-step VAT) and cascading tax configurations that require multiple Odoo tax records with sequence dependencies.

Oracle journal entries are posted to ledgers with journal categories, sources, and approval statuses. We migrate approved, posted journals within a configurable date scope to Odoo General Journal entries. Unposted journals and draft batches are excluded from migration scope. The Oracle journal batch name maps to the Odoo journal reference, and we preserve the posting date for Odoo period assignment. Oracle journal lines with multi-segment account codes use the COA mapping strategy selected during discovery.