# Oracle EBS 12.2: Stay on Premises or Move to Fusion Cloud? > Source: https://netray.co/tools/oracle-ebs-12-2-stay-or-move-to-fusion-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Thirteen questions that point to staying and modernising on EBS 12.2, a hybrid split, or planning a full Fusion Cloud migration. ## Category oracle ## Erp Oracle E-Business Suite ## Audience - CIO - IT director - Enterprise architect - Finance director ## Tool **Kind:** assessment **Questions:** #### Which EBS release are you on? **Help:** Higher scores favour staying on 12.2. **Options:** ##### 11i **Score:** 0 ##### 12.1.3 **Score:** 1 ##### 12.2.x below 12.2.10 **Score:** 2 ##### 12.2.10 or later **Score:** 3 #### How many custom objects (forms, reports, packages, OAF pages, workflows, interfaces)? **Options:** ##### Fewer than 50 **Score:** 0 ##### 50 to 300 **Score:** 1 ##### 300 to 1,000 **Score:** 2 ##### More than 1,000 **Score:** 3 #### Which manufacturing modules carry daily operations? **Options:** ##### None, finance and HR only **Score:** 0 ##### Inventory and purchasing **Score:** 1 ##### Discrete Manufacturing or Process Manufacturing (OPM) **Score:** 2 ##### Manufacturing plus WMS or Project Manufacturing **Score:** 3 #### Do you run a validated or tightly regulated environment (FDA GxP, defense, export control)? **Options:** ##### No **Score:** 0 ##### Some regulated reporting **Score:** 1 ##### Validated processes in some plants **Score:** 2 ##### Validated system, change requires formal revalidation **Score:** 3 #### How many integrations touch EBS? **Options:** ##### Fewer than 10 **Score:** 0 ##### 10 to 30 **Score:** 1 ##### 30 to 80 **Score:** 2 ##### More than 80 **Score:** 3 #### In-house EBS DBA and developer skills? **Options:** ##### None, fully outsourced and hard to staff **Score:** 0 ##### One person who is near retirement **Score:** 1 ##### Small team plus a partner **Score:** 2 ##### Stable team covering DBA, PL/SQL, Forms and OAF **Score:** 3 #### Hardware or data centre refresh due within 24 months? **Options:** ##### Yes, major refresh and no budget for it **Score:** 0 ##### Yes, budgeted **Score:** 1 ##### Partial refresh only **Score:** 2 ##### No, recently refreshed or already on OCI **Score:** 3 #### Appetite for quarterly SaaS updates that you cannot defer indefinitely? **Options:** ##### Welcome, we want to stop patching **Score:** 0 ##### Acceptable with a test process **Score:** 1 ##### Difficult for some processes **Score:** 2 ##### Not acceptable for core operations **Score:** 3 #### Data residency, sovereignty or air-gap requirements? **Options:** ##### None **Score:** 0 ##### Country residency only **Score:** 1 ##### Some data must stay in our own facilities **Score:** 2 ##### Parts of operations must run disconnected or air-gapped **Score:** 3 #### Pressure on licence and support spend? **Options:** ##### Strong mandate to change the cost model **Score:** 0 ##### Some pressure **Score:** 1 ##### Spend is accepted **Score:** 2 ##### Spend is low relative to a migration budget **Score:** 3 #### How much reporting depends on direct SQL against APPS tables? **Options:** ##### Very little **Score:** 0 ##### Some reports **Score:** 1 ##### Most operational reports **Score:** 2 ##### Most reports plus a data warehouse fed from APPS **Score:** 3 #### Willingness to adopt standard Fusion processes instead of current customizations? **Options:** ##### High, leadership wants standard processes **Score:** 0 ##### Moderate, for finance and HR **Score:** 1 ##### Low for manufacturing **Score:** 2 ##### Low across the business **Score:** 3 #### Is a major business change coming (merger, divestiture, new plants)? **Options:** ##### Yes, new platform needed for it **Score:** 0 ##### Yes, but EBS could absorb it **Score:** 1 ##### Minor changes only **Score:** 2 ##### No major change planned **Score:** 3 **Bands:** #### Plan a Fusion Cloud migration **Min:** 0 **Max:** 40 **Verdict:** Your situation favours moving: limited customization lock-in, appetite for SaaS and pressure on cost or skills. Start fit-gap work and a business case. **Recommendations:** - Run a module by module fit-gap against Fusion, starting with finance - Inventory integrations and reports that read APPS tables directly - Plan data migration volumes and history retention - Keep EBS patched and supported until cutover #### Hybrid: move some pillars, keep manufacturing **Min:** 41 **Max:** 65 **Verdict:** A split often fits: finance or HCM to Fusion, manufacturing and supply chain stay on EBS 12.2 where customizations and plant processes are deep. **Recommendations:** - Define the system of record for items, suppliers and customers across both - Design the integration layer before moving the first pillar - Keep EBS on a current 12.2 RUP so it stays under Premier Support - Re-run this assessment for manufacturing after the first move #### Stay and modernise on EBS 12.2 **Min:** 66 **Max:** 100 **Verdict:** Your customizations, regulatory needs, skills and data constraints favour staying on 12.2 Continuous Innovation and modernising around it. **Recommendations:** - Move to a current 12.2.x RUP and keep a quarterly CPU rhythm - Upgrade the database to 19c and consider OCI or a refreshed on-prem platform - Add modern user experiences with APEX or a private AI layer over EBS data - Track Oracle's Lifetime Support Policy each year for date changes ## Content **Intro:** This assessment helps Oracle E-Business Suite customers decide between staying on 12.2 and modernising, a hybrid with some pillars in Fusion Cloud, or a full migration. It weighs support timelines, customization depth, manufacturing fit, regulatory needs, skills and data constraints. **Sections:** #### The support facts behind the question **Body:** EBS 12.2 is not at end of life. Oracle moved 12.2 to a Continuous Innovation model, delivering new features and fixes as release update packs on 12.2 rather than a 12.3, and, as of its March 2026 announcement, committed to Premier Support through at least 2037, with an annual review of whether to add another year. Check the current Oracle Lifetime Support Policy for Applications before you quote a date in a business case. EBS 12.1.3 is past Premier and Extended Support and is in Sustaining Support, so 12.1.3 sites should treat moving to 12.2 or Fusion as urgent. **Bullets:** - 12.2: Premier Support, Continuous Innovation - 12.1.3: Sustaining Support only - Confirm dates in the Lifetime Support Policy #### How to use and read it **Body:** Answer as the whole leadership group, not as IT alone. Higher scores point toward staying: deep customization, validated processes, air-gap needs, strong in-house skills and heavy direct-SQL reporting all raise switching cost or limit SaaS fit. Lower scores point toward migration. The middle band is common for manufacturers: finance and HCM move well to Fusion, while discrete or process manufacturing with heavy customization stays on EBS for longer. The tool decides direction; the fit-gap worksheet then tests it module by module. #### Manufacturing fit is the swing factor **Body:** Fusion Cloud Manufacturing, Inventory, Maintenance and Process Manufacturing cover many EBS processes, but concepts differ: Fusion uses work definitions and work orders where EBS uses routings and discrete jobs, and setup structures change. Plants running WMS, Project Manufacturing, OPM or heavily personalized shop-floor forms should run a dedicated fit-gap before committing. Validated environments also need to plan how quarterly SaaS updates fit their revalidation process. #### Common mistakes **Body:** Deciding on an end-of-life date that is not real. Comparing EBS support cost with Fusion subscription cost without including migration, data conversion, integration rebuild and retraining. Ignoring the reports and extracts that query APPS tables directly, which all need rebuilding. And treating 'stay' as 'do nothing': staying only works if you keep current on RUPs, CPUs and the database release. **Cta:** If you stay on EBS 12.2, we can add a private AI layer over your EBS data on your own servers, so users get modern answers without a re-implementation. **Faq:** #### Is Oracle EBS 12.2 end of life? **Answer:** No. Oracle provides Premier Support for EBS 12.2 under its Continuous Innovation model and, since its March 2026 announcement, has committed to at least 2037. Oracle reviews the date annually, so confirm it in the current Lifetime Support Policy. EBS 12.1.3 and 11i are in Sustaining Support. #### Is Oracle EBS outdated? **Answer:** The architecture is older than Fusion Cloud, but 12.2 still receives release update packs with new features, security fixes and certification on current databases and operating systems. Whether it is outdated for you depends on user experience needs, skills availability and how much your business depends on customizations that SaaS cannot host. #### What is the main difference between EBS and Fusion? **Answer:** EBS is software you install, patch and customize, on premises or on IaaS such as OCI. Fusion Cloud Applications are SaaS with quarterly updates managed by Oracle, extended through configuration, Visual Builder and integrations rather than direct code changes in the application or database. #### Can we move finance to Fusion and keep manufacturing on EBS? **Answer:** Yes, a hybrid is a common pattern. It needs a clear system of record for items, suppliers, customers and the chart of accounts, plus an integration layer for journals, payables and receivables data between the two. Plan reconciliation and reporting across both before moving the first pillar. ## Search terms oracle ebs 12.2 end of life, is oracle ebs outdated, oracle ebs vs oracle fusion, oracle ebs to oracle fusion migration, oracle ebs 12.2 support end date, ebs 12.2 continuous innovation --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json