Migrate from Oracle Financials Cloud to Acumatica

Oracle Financials Cloud ledgers carry their own chart of accounts segments, fiscal calendar, currency, and subledger accounting method. Each Oracle ledger maps to one Acumatica Company (for reporting consolidation) and one or more Branches (for legal-entity separation). The migration plan must declare the Oracle ledger-to-branch mapping before chart-of-accounts translation begins because branch IDs are referenced in every subsequent document import.

Oracle Business Units are the legal-entity container in Fusion — they hold legal-entity tax registrations, statutory reporting, and subledger configurations. Acumatica Branches serve the same role. One Oracle Business Unit maps to one Acumatica Branch in most cases. If your Oracle setup has multiple Business Units sharing a single ledger, those map to separate Acumatica Branches under the same Company for inter-branch transaction routing.

Oracle Fusion charts use up to 30 flexfield segments per ledger (e.g., Natural Account, Cost Center, Department, Project, Location). Acumatica uses a two-part GL account code (Account-SubCD) with up to 30 subaccount segments. The migration extracts every Oracle segment value, creates corresponding Acumatica subaccount records for each unique combination, and preserves the segment descriptions. Oracle segment values are not changed; they are mapped to Acumatica subaccount codes by value-to-value correspondence.

Oracle journal lines carry the ledger ID, account combination, entered debit/credit amounts, statutory currency amounts, and reference information. Acumatica GL batches hold the batch number, batch date, fin period, and hold status; each batch contains journal transactions with account ID, subaccount ID, debit, credit, and reference fields. We preserve the original Oracle journal description, source module, and period-entered date as custom fields on each Acumatica transaction for audit continuity.

Oracle AP invoices store the supplier ID, invoice number, invoice date, payment terms, invoice amount, and remaining balance. These map directly to Acumatica Vendor records (with VendorID, VendorName, VendorAcct) and AP Document records (with DocType, DocDate, RefNbr, CuryOrigDocAmt, CuryDocBal). We match Oracle Supplier Site to the Acumatica vendor's default location. Historical paid AP documents are imported as Closed/Voided records with the original payment reference preserved.

Oracle AR invoices carry the customer account, invoice number, invoice date, due date, amount, and open balance. Acumatica AR documents use the same DocType model (Invoice, Credit Memo, Payment, Void) with CuryOrigDocAmt for original amount and CuryDocBal for remaining balance. We map Oracle's aging buckets to Acumatica's age-by-date categories and preserve the original Salespersons and collector assignments as custom fields since Acumatica assigns AR clerks via user permissions rather than document-level owner fields.

Oracle Fixed Assets carry the asset category, acquisition date, acquisition cost, depreciated amount, and useful life. Acumatica's Asset Management module stores the same data in the Asset record (AssetID, ClassID, AcqDate, Cost, AccumDepr, ClassID for depreciation book). Asset depreciation methods and mid-month conventions from Oracle are mapped to Acumatica's depreciation code setup before migration — we deliver a depreciation-method lookup table as part of the migration plan.

Oracle Expense reports are header-line documents: the header holds the employee, report date, and total; lines hold the project, cost type, amount, and GL account. Acumatica stores expense receipts as EPExpenseClaim records with EPExpenseClaimDetails lines. We split Oracle expense headers into separate Acumatica expense claim records, map each expense line to a detail row, and set the GL account via the cost code plus subaccount. Oracle project-linked expense lines are linked to the corresponding Acumatica ProjectID.

Oracle Project Billing stores project headers with customer, start/end dates, budget, and status. These map to Acumatica Projects (ProjectID, Description, CustomerID, StartDate, EndDate, Status, Budget). Oracle's Workplan tasks become Acumatica Project Tasks. If Oracle Project Billing is used for revenue recognition and billing rules, we export those rules as a PDF reference document for the Acumatica Project Billing configuration team — billing rule definitions are not migratable data.

Oracle Inventory items carry the item ID, description, item class, unit of measure, cost method, and default subaccounts. Acumatica Inventory Items (InventoryID, Descr, ItemClass, BaseUnit, CostMethod, ValMethod) carry the same data. Oracle item cross-references map to Acumatica cross-reference records. If Oracle uses lot/serial tracking, Acumatica uses LotSerialInfo with matching lot numbers and expiration dates. Bin location data from Oracle Warehouse Management maps to Acumatica's Site and Warehouse structure.

Oracle Cash Management bank accounts store the bank name, branch, account number, currency, and GL account. Acumatica holds cash accounts as GL accounts with the Cash-Account flag set, plus bank details in the Cash Account screen (BankCode, BankName, BankAccount, CCY). We map Oracle bank account IDs to the corresponding Acumatica cash account ID and preserve the original bank account number as a reference field for reconciliation.

Oracle Financials Cloud allows descriptive flexfields on most entities (suppliers, customers, invoices, journal lines, projects). Acumatica calls these User-Defined Fields (UDFs). Each Oracle DFF segment becomes an Acumatica custom field on the matching entity. DFF values are preserved as the field value. The migration plan lists every active DFF, its segment number, data type, and value list — your Acumatica admin pre-creates the corresponding UDFs before data migration runs so foreign-key validation passes.