Migrate from Oracle E-Business Suite to Dolibarr ERP

Oracle GL stores multiple ledgers per legal entity with configurable segment structures (up to 30 flexfield segments). Dolibarr's accounting module uses a flat chart of accounts with a four-to-six segment account code convention. We extract the chart of accounts, period balances, and open journal batches from Oracle GL. The Oracle COA segment structure is flattened into Dolibarr's account code hierarchy (typically 6-digit numeric or alphanumeric codes) during transform. Multi-ledger structures are consolidated into a single Dolibarr ledger unless the customer requires separate entity instances, in which case we document the instance topology during discovery. GL period-open/close status migrates as Dolibarr fiscal year and period configuration.

Oracle AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL map to Dolibarr Third-Party records with the type flag set to Supplier. Oracle supplier bank accounts (IBAN, SWIFT, internal bank account numbers from CE_BANK_ACCOUNTS) migrate to Dolibarr'srib_type field and associated bank account records. Payment terms from Oracle AP_TERMS migrate to Dolibarr'scond_reglement_supplier. Address book entries flatten into Dolibarr's address and contact records linked to the Supplier Third-Party. Suppliers without sites in Oracle are created as single-site records in Dolibarr.

Oracle AR customers span RA_CUSTOMERS, RA_ADDRESSES, and HZ_PARTIES, where a single HZ_PARTY can have multiple customer account sites. Dolibarr stores a single Third-Party record with multiple address and contact records. We flatten Oracle's party hierarchy by creating one Dolibarr Third-Party per HZ_PARTY, then attach Oracle customer site addresses as Dolibarr contact or address records. Profile classes (AR_CUSTOMER_PROFILE_CLASSES) migrate as custom fields on the Third-Party. Outstanding AR balances and hold statuses from RA_CUSTOMER_BALANCES move as Dolibarr invoice headers in Open status.

Oracle AP_INVOICES_ALL invoice headers and AP_INVOICE_LINES_ALL map to Dolibarr fact Fournisseur records. We extract invoice headers with vendor, invoice number, invoice date, GL date, and payment terms; invoice lines with line amount, description, and distribution account. APPROVED and PERPAID status invoices migrate as Open or Paid in Dolibarr; CANCELLED and REJECTED invoices are excluded unless the customer requests closed-record preservation for audit. Hold statuses from Oracle AP_HOLDS_ALL map to Dolibarr's draft status with a hold flag field, requiring manual review before posting.

Oracle AR_INVOICES_ALL and RA_INTERFACE_LINES_ALL store customer invoices. We extract RA_CUSTOMER_TRX_ALL (header) and AR_PAYMENT_SCHEDULES with balance-owing amounts, due dates, and hold statuses. Oracle AR's transaction type (INV, CM, DM) maps to Dolibarr's invoice, credit note, and debit note types. Lines migrate with quantity, unit price, and account assignments. Postable status in Dolibarr is set based on the Oracle invoice status; invoices in AR's CLOSED status move as Paid with a payment record created.

Oracle PO_HEADERS_ALL and PO_LINES_ALL with schedule distributions carry authorization status. APPROVED POs migrate to Dolibarr Commande Fournisseur in Ordered or Draft status. REJECTED and CLOSED POs are excluded from active migration unless the customer requests closed-record preservation. We flag Oracle PO schedule distributions as Dolibarr order lines with delivery dates and quantities, preserving authorization status as a custom field. Draft and Incomplete POs require the customer to decide whether to migrate as draft orders or archive them.

Oracle MST_ORGANIZATIONS defines inventory org structure; MTL_SYSTEM_ITEMS_B defines item master with on-hand quantities per org. Dolibarr has no native multi-organization model. We either (a) create separate Dolibarr instances per Oracle inventory org, (b) use Dolibarr's multi-entity feature (if licensed) to separate warehouse-level data, or (c) consolidate all items into a single Dolibarr product catalog with warehouse tracked in the Stock movement records. The choice is made during discovery. On-hand quantities per subinventory become Dolibarr Stock warehouse records.

Oracle item masters carry item number, description, unit of measure (from MTL_UNITS_OF_MEASURE), template ID, and costing method. We extract primary attributes (item number, description, UOM, primary UOM) and map Oracle item types to Dolibarr product types (Item or Service). Costing method (Standard, Average, FIFO) from Oracle MTL_ITEM_COSTS migrates as Dolibarr cost price. Long descriptions and extended attributes from Oracle FND_DESCRIPTIVE_FLEXS on items are extracted as custom field notes during discovery for the customer's admin to re-enter in Dolibarr.

Oracle multi-level BOMs with explode/implode relationships between levels map to Dolibarr's BOM nomenclature feature (included in the manufacturing module). We extract BOM_STRUCTURES_B (header and lines) and BOM_ROUTINGS_B for routing sequences. The topological ordering of BOM levels is preserved so that parent and component relationships are correctly structured in Dolibarr. The manufacturing module in Dolibarr is an add-on; we verify its activation during discovery and flag it as a separate configuration step if not already licensed.

Oracle discrete and process work orders with status codes (RELEASED, COMPLETE, CLOSED, CANCELLED) migrate to Dolibarr's project module for tracking. Open and Released WIP jobs carry material allocations and routing step sequences that map to Dolibarr task structures. Oracle WIP routing step sequencing (from BOM_ROUTINGS_B) becomes Dolibarr task dependencies. Closed and Cancelled jobs are migrated as reference records but set to Completed or Cancelled status; material and labor actuals from Oracle WIP_COST_COLLECTORS migrate as project cost entries.

Oracle Projects (PA_PROJECTS_ALL) with expenditure organizations and billing organizations map to Dolibarr Project records. Resource breakdown structures and billing rates from Oracle require cross-module mapping: we extract PA_EXPENDITURE_ITEMS as Dolibarr expense line entries under the Project, and PA_BILLING_RATES as Dolibarr project pricing rules. The Projects module in Dolibarr is an add-on; we confirm its activation status during discovery. Projects without a PA (Projects) module in Oracle (i.e., only GL postings) map directly to Dolibarr Projects with financial tracking enabled.

Oracle HRMS employee records (PER_ALL_PEOPLE_F, PER_ASSIGNMENTS_F, PER_PAYMENT_METHODS) map to Dolibarr Contact records with theEmployee flag enabled, plus a corresponding Dolibarr User record if the employee has system access. Effective dates on assignments are used to determine current active status at migration time. Assignment grades, supervisors, and cost centers migrate as custom fields on the Dolibarr Contact or User. The HR module in Dolibarr is an add-on; if not activated, employees are migrated as Contacts only with employment details stored as notes. Termination dates from Oracle mark migrated records as Inactive in Dolibarr.

Oracle bank accounts with bank name, account number, currency, and SWIFT codes migrate to Dolibarr's Comptabilite bank account records. Payment format templates from Oracle (CE_PAYMENT_DOCUMENTS) do not have a direct Dolibarr equivalent; remittance layout and payment file format configurations are documented separately for the customer's admin to reconfigure in Dolibarr's accounting module payment format settings. We also extract Oracle AP payment holds and CE_BANK_BRANCHES for branch address data.

Oracle FND_ATTACHED_DOCUMENTS and FND_LOBS store files linked to entities across modules (suppliers, customers, invoices, POs, items). We extract binary blobs or file paths from FND_LOBS and map them to Dolibarr's document management linked files using the entity's Dolibarr document_id. Large binary attachments (>10 MB per file) are flagged for the customer to decide on a document storage strategy (Dolibarr database storage vs. external file storage). File names and entity linkages are preserved; the full file content is migrated where storage permits.