Migrate from Oracle Financials Cloud to Epicor Prophet 21

Oracle Financials Ledgers define currency, accounting calendar, and Chart of Accounts assignment at the top level. We map each Ledger to an Epicor Company record by Ledger name and ID. Where Oracle uses multiple Ledgers for different currencies or fiscal calendars, we create corresponding Epicor Companies and flag the inter-company elimination entries as journal batches requiring post-migration reconciliation. Epicor supports multiple Companies within a single database tenant, but the customer must confirm their Epicor licensing tier covers the Company count before migration begins.

Oracle Financials Business Units are legal-entity containers that own AP, AR, and Assets subledger data. Epicor uses a Part/Company structure where Sites represent physical or logical locations within a Company. We map each Oracle BU to an Epicor Company or, where the customer licenses multi-site Epicor, to a Site under the parent Company. All Oracle BU-specific subledger records (invoices, payments, asset assignments) are held in a pending state until the destination BU/Site is confirmed live, preventing orphaned records at migration time.

Oracle Financials COA typically uses 4-6 flexfield segments (Company, Division, Department, Account, Product, Project). Epicor ERP uses flat account codes or a hierarchical cost-center structure that typically supports fewer segments. We design a concatenation strategy during discovery: Oracle segments are concatenated into a single Epicor account code (e.g., DIV-DEPT-ACCT-PROD) with a delimiter preserved in a reference table. The customer chooses the delimiter and segment order during scoping. We flag any Oracle segment values that exceed Epicor's account code length limits and propose truncation or reformatting rules before migration begins.

Oracle Financials Suppliers with address, tax registration, payment terms, and bank account assignments map to Epicor Vendors. Supplier sites (ship-from locations) map to Epicor VendorShipTos. We preserve the Supplier number, name, TIN/EIN, payment terms, and bank account details. Oracle's multi-site Supplier architecture (Supplier as parent, sites as children) is flattened into Epicor's Vendor record with ship-to addresses stored as child records.

Oracle Financials Customers with billing profiles, credit limits, and dunning assignments map to Epicor Customers. Bill-To and Ship-To site assignments migrate as Customer ShipTos. We preserve the customer number, name, credit limit, payment terms, and dunning schedule. Where Oracle stores revenue acceptance criteria or customer-specific tax exemptions, we map these to Epicor Customer Tax Exemption records or custom fields.

Oracle Financials AP invoices carry ledger-specific distributions, accrual flags, and validation status. We map invoice headers with supplier reference, invoice number, invoice date, and due date. Invoice distributions (debit account, amount, description) map to Epicor GL Account distributions with the concatenated account code resolved from the Oracle COA mapping table. We flag unvalidated Oracle invoices (Hold status) as Epicor pre-approved vouchers requiring AP team review before posting.

Oracle Financials AR transactions include Revenue lines, tax lines, and receivables distributions tied to the subledger. We map AR invoice headers with customer reference, invoice number, invoice date, and due date. Revenue and tax line distributions map to Epicor GL distributions. We flag inter-company AR invoices requiring Epicor inter-company journal entry creation post-migration, as Epicor's inter-company model differs from Oracle's native mechanism.

Oracle Financials Payments are linked to AP or AR invoices via payment schedules. We map payment records with settlement discounts, withholding tax details, and links to source invoices. Epicor AP payments and AR receipts are resolved against their respective invoice records using invoice number and supplier/customer references as dedupe keys. Where Oracle stores payment batches, Epicor payments are processed individually or as EFT batches depending on the customer's AP/AR workflow.

Oracle Financials Fixed Assets carry depreciation books, asset categories, assignment records, and financial depreciation histories. We map asset registers including asset number, description, acquisition date, cost, supplier, and location. Depreciation schedules (straight-line, declining balance, units of production) migrate to Epicor Fixed Assets with the current book value and accumulated depreciation computed from Oracle's depreciation history. Books with different depreciation methods across Oracle book assignments are created as separate Epicor Asset Book records.

Oracle Financials Bank Accounts linked to Payment Process Profiles and Cash Management balances map to Epicor Bank Accounts. We preserve bank branch, account number, currency, and the associated Payment Process Profile assignment. Cash Management bank balances migrate as Epicor Cash Head records. Oracle's multiple bank account per BU model is preserved in Epicor where each BU maps to a Company, and bank accounts are assigned at the Company level or at the Site level depending on Epicor's configuration.

Oracle Financials maintains tax registries per tax authority with rates, recovery accounts, and applicability rules. We map tax codes to Epicor Tax Code configuration entries, preserving tax rate, description, and the applicable GL account for tax liability. Compound tax structures (VAT + withholding) are mapped to Epicor Tax Groups with component tax codes listed. We flag any Oracle tax exceptions or customer-specific tax exemptions for manual review and re-entry in Epicor's Tax Exemption maintenance screen.

Oracle Financials Journal Entries are posted to Ledgers with journal categories, sources, and approval statuses. We migrate approved posted journals within a configurable date scope (typically last 12-24 months of open or recent history). Unposted journals are flagged as requiring re-entry in Epicor. Journal batch names and descriptions map to Epicor Journal Entry batch headers. Each journal line's account distribution maps to the concatenated Epicor GL Account using the COA mapping table, and the journal line description and reference map to Epicor's Journal Entry line memo fields.

Oracle Financials expense report transactions migrate as Epicor Expense Report headers with line items, cost center assignments, and project code assignments. Oracle's mileage reimbursement rates and per-diem policy calculations are stored as configuration rather than transaction data; we export the source rates as a reference CSV and flag that Epicor's expense policy rules must be re-configured post-migration rather than carried as calculated amounts that would be stale.

Oracle Financials Cost Centers exist as independent flexfield segments or as part of the HRMS organization hierarchy depending on implementation. We identify the source (COA segment vs. HRMS assignment) during discovery and map cost center assignments to Epicor Departments. Where Oracle cost centers are stored as a separate flexfield, they are concatenated into the Epicor account code per the COA mapping strategy. Department-level reporting in Epicor uses the GL Account's cost center segment or a separate Department reference table.