Oracle E-Business Suite

    Retire Oracle EBS After Your Cloud Migration

    Move the data you need into Oracle Fusion. Preserve everything else in a secure historical archive. Switch off EBS.

    Oracle E-Business Suite rarely gets switched off at go-live. It stays up for prior-year ledgers, closed purchase orders, leaver records, payroll history and the attachments nobody could migrate — and keeps consuming licence, hosting, database and DBA cost while it waits to be asked a question.

    General LedgerPayablesReceivablesPurchasingFixed AssetsInventoryOrder ManagementHRPayrollAttachmentsAudit history
    UK Public SectorSyntraETL data migration, archival and legacy application retirement services are available to UK public-sector buyers through the G-Cloud 15 framework.Explore G-Cloud 15 services →

    Where this normally starts

    Oracle Fusion goes live. Open balances, active suppliers, current employees and in-flight transactions come across. Closed accounting periods, terminated assignments, historical payroll runs, completed purchase orders and every FND_ATTACHED_DOCUMENTS row stay behind, because they do not belong in the target data model.

    Twelve months later EBS is still running. The finance team pulls prior-year comparatives from it, HR retrieves leaver records from it, payroll answers queries against it, and internal audit asks for transaction-level evidence out of it. The programme closed; the cost did not.

    A Legacy Exit extracts EBS financials, procurement, HCM and attachment history into DataVault, reconciles source-to-target counts, makes the records searchable and exportable through DataLens, and then lets the EBS environment be decommissioned against a documented plan.

    Architecture

    Two flows, run by the same platform. What the new application needs is migrated. Everything else is preserved and made accessible, which is what allows the old environment to be switched off.

    Migration path

    Oracle EBSR12 or 11i, on-premise or hosted
    DataMoveExtract, map, transform, validate, load
    Oracle FusionOpen balances, active masters, current employees

    Retention path

    Oracle EBS historical dataClosed periods, leavers, attachments, audit history
    DataVaultPreserve with retention, lineage and reconciliation
    DataLensSearch, report and export under role-based access
    Oracle EBS retiredLicences, hosting and support withdrawn

    Data in scope

    Scope is agreed in discovery. On an EBS retirement it usually covers the following, along with the reference data those records resolve against.

    General Ledger

    Journals, balances, closed periods, chart of accounts and the code-combination history that historical reporting depends on.

    Payables

    Invoices, payments, holds, supplier history and the scanned invoice images attached to them.

    Receivables

    Transactions, receipts, adjustments, customer history and ageing at period close.

    Purchasing

    Requisitions, purchase orders, receipts, approvals and the approval hierarchy that authorised them.

    Fixed Assets

    Asset records, additions, retirements, depreciation history and the asset register at each year end.

    HR and Payroll

    Assignments, effective-dated employment history, elements, deductions, payroll runs and year-end records.

    Supply chain

    Inventory transactions, on-hand history, order management and shipment records.

    Attachments and documents

    FND attachments — scanned invoices, contracts and correspondence — archived against the record they belong to.

    Audit history

    Change and approval trails, without which the archived transaction loses its evidential value.

    What makes Oracle EBS different

    The parts of this platform that decide whether a retirement succeeds or stalls.

    Attachments live inside the applicationEBS attachments are held through FND_ATTACHED_DOCUMENTS against a filesystem or database store. They are the single most common reason an EBS environment stays up after go-live, and the part most migrations quietly leave out of scope.
    Multi-org and multi-ledger structuresOperating units, legal entities, ledgers and set-of-books history have to be carried into the archive, or archived transactions cannot be resolved back to the entity that owned them.
    Effective-dated HR dataOracle HRMS holds assignment history as effective-dated records. Flattening that on extract destroys the ability to answer what an employee's terms were on a given date — which is exactly what historical HR and payroll queries ask.
    Customisations and CEMLI objectsCustom tables, descriptive flexfields and bespoke modules hold data that no standard extract touches. Discovery inventories them explicitly rather than assuming a vanilla install.
    Extended support economicsThe renewal date on Oracle support or the hosting contract is usually what sets the programme deadline, because that is the date the saving becomes real.

    How completeness is proven

    Nobody signs off a decommissioning on the basis that the archive looks right. Each extract is reconciled back to Oracle EBS and the evidence is retained as part of the decommissioning pack.

    Source-to-target reconciliationReconciled
    Source records identified14,829,321
    Records archived14,829,321
    Rejected / exception records0
    Reconciled100%

    Illustrative figures shown to explain how reconciliation evidence is presented. They are not drawn from a specific customer engagement.

    Duration and commercial model

    A single-module EBS archive with modest attachment volumes is typically a matter of weeks after discovery. A full multi-module financials, procurement and HCM retirement with large attachment volumes and custom objects runs longer, and the duration is established in discovery before implementation is committed.

    Work is delivered as fixed-scope packages priced against the scope established in a Legacy Exit Discovery. Projects typically start from £25K. UK public-sector buyers can call the work off through G-Cloud 15.

    Common questions

    Can we retire EBS if we are not going to Oracle Fusion?
    Yes. The retention path does not depend on the target. Whether the replacement is Fusion, SAP, Workday, Dynamics or something else, the EBS history is archived into DataVault and accessed through DataLens the same way.
    What happens to EBS attachments?
    They are extracted with their parent record and archived against it, so an archived invoice arrives with its scanned image and approval history rather than as a bare table row.
    Do we lose the ability to run our EBS reports?
    The reports people actually run are identified in discovery and reproduced against archived data in DataLens. Reports nobody has run in years are not rebuilt, which is usually most of the catalogue.
    How much of EBS has to be archived?
    Only what has to be retained or accessed. Discovery separates records with a retention obligation or a genuine access requirement from data that can simply be disposed of with the environment.
    Is this bought through G-Cloud?
    Public-sector buyers can call it off under G-Cloud 15 through Firstcron Services UK Ltd. Commercial buyers contract directly.

    Assess Your Oracle EBS Retirement

    A Legacy Exit Assessment establishes exactly which EBS modules, which years and which attachment volumes are still in play, what the environment costs to run today, and what a scoped retirement would take.

    UK Public SectorSyntraETL data migration, archival and legacy application retirement services are available to UK public-sector buyers through the G-Cloud 15 framework.Explore G-Cloud 15 services →