Migrate from Oracle Financials Cloud to Dolibarr ERP

Oracle Ledgers (the top-level financial reporting container defining currency, accounting calendar, and COA assignment) have no direct Dolibarr equivalent because Dolibarr operates as a single-ledger system. We map each Oracle Ledger to a named Dolibarr Accounting Configuration entry and preserve the source Ledger name, currency, and calendar as reference metadata. If the customer requires multi-ledger reporting, we document the ledger-to-account-segment mapping in the handoff inventory for the customer's admin to implement through separate account ranges.

Oracle Business Units are legal-entity containers that own AP and AR subledger data. Dolibarr has no native BU concept. We map each Oracle BU to a Dolibarr Third-Party category (e.g., a tag or category on the Supplier/Customer record) and store BU name and BU ID as custom fields on the third-party record. BU-specific payment terms and tax registrations are re-applied at the third-party site level post-migration.

Oracle Financials COA with 4-6 flexfield segments (Company, Division, Department, Account, Product, Project) is mapped to Dolibarr flat account codes. We concatenate all active Oracle segments into a single account string using a delimiter (typically hyphen or dot) during the transform phase and preserve the full segment-value matrix in a reference table. Any segments that the customer designates as reporting-only are dropped from the account code but preserved in the reference table for reconciliation.

Oracle Supplier records map directly to Dolibarr Third-Party records with the Supplier flag enabled. Oracle Supplier sites (ship-from and pay-from addresses) map to Dolibarr contact addresses on the Third-Party. Payment terms, bank account details, and tax registration numbers migrate as third-party properties. We preserve the Oracle supplier_id as a custom external reference field for audit.

Oracle AR Customer records map to Dolibarr Third-Party records with the Customer flag enabled. Oracle Bill-To and Ship-To sites map to Dolibarr contact addresses. Credit limits, dunning assignments, and payment terms migrate as third-party properties. Customer category assignments in Oracle (e.g., domestic vs. international) map to Dolibarr categories.

Oracle AP invoices carry ledger-specific distributions, accrual flags, and validation status. We migrate open AP invoices with their distributions (line-level account assignments from the concatenated COA) into Dolibarr Supplier Invoice records. Invoice distributions are recreated as invoice lines referencing the concatenated Dolibarr account code. Unvalidated Oracle invoices are flagged for the customer's admin to approve or re-enter manually in Dolibarr before payment.

Oracle AR transactions include revenue lines, tax lines, and receivables distributions tied to the subledger. We map AR invoices to Dolibarr Customer Invoice records preserving customer, invoice amount, accounting date, and invoice number (with a prefix if Dolibarr's auto-numbering conflicts). Tax lines migrate as Dolibarr tax lines referencing the matching Dolibarr tax configuration.

Oracle Payments are linked to AP or AR invoices via payment schedules. We migrate payment records with their settlement discounts and withholding tax details, preserving links to source invoices where the destination Dolibarr invoice ID is resolved at migration time. Standalone payments without a resolved invoice destination are flagged in the reconciliation report for admin review.

Oracle Fixed Assets carry multiple depreciation books per asset with potentially different depreciation methods per book. Dolibarr Asset module supports one depreciation book per asset. We migrate the primary Oracle depreciation book to the Dolibarr Asset record; secondary Oracle books are documented in the handoff inventory as reference data. Asset categories, acquisition dates, cost, and accumulated depreciation migrate directly.

Oracle expense report headers and line items with cost center and project assignments map to Dolibarr expense report records. Oracle mileage reimbursement rates and per-diem policy calculations are stored as configuration rather than transaction data; we export source rates as a reference table and document the recommended Dolibarr expense policy configuration for the admin to re-enter post-migration.

Oracle bank accounts linked to payment process profiles and cash management balances map to Dolibarr Bank Account records. We migrate bank name, branch, account number, currency, and the associated payment process profile name as a reference property. Bank reconciliation data from Oracle Cash Management is preserved as a reference file for manual reconciliation in Dolibarr.

Oracle Financials maintains tax registries per tax authority with rates, recovery accounts, and applicability rules. Dolibarr's tax module uses flat rate percentages per product/service category without a tax authority registry. We map Oracle tax codes to Dolibarr tax configurations (rate, name, accounting account) and flag compound tax stacking scenarios that require multiple Dolibarr tax line entries per invoice line. Tax authority names and registration IDs are documented for the customer's admin to re-enter in Dolibarr's tax module.

Oracle journal entries posted to ledgers with journal categories, sources, and approval statuses migrate to Dolibarr Accounting Entry records within a configurable date scope. We migrate approved, posted journals only; unposted journals are flagged for the customer's admin to post or discard in Dolibarr. Journal line distributions are recreated using the concatenated Dolibarr account code. Oracle's journal batching structure maps to Dolibarr's accounting transaction grouping.