Oracle EBS Premier Support ends 2034. Here's the roadmap.

The deadline

Oracle EBS 12.2 Premier Support runs through December 2034. After that, Sustaining Support continues indefinitely — but Sustaining excludes:

  • New patches
  • Regulatory updates
  • Tax updates

For a US multi-state manufacturer or a multi-country distributor, that is the practical end of EBS as a viable production ERP. Every quarterly tax change, every state regulatory shift, every country-level statutory update becomes a custom build at the cost of senior in-house developers or expensive consultants.

Working backward from 2034

A typical mid-market multi-pillar migration is 18–30 months from kickoff to go-live:

PhaseDurationOutput
Assessment4–6 weeksCustomization + integration inventory; business case; sign-off
Design3–5 monthsTO-BE process; configuration approach; customization scope
Build5–9 monthsConfiguration; customization; integration; data migration
Test + UAT2–3 monthsReal-data testing; defect resolution; readiness sign-off
Cutover + Hypercare3 monthsCutover weekend; day-one validation; 60-day hypercare

Add 6–12 months on top of that for procurement, business case, and executive alignment. Total end-to-end: 24–42 months.

That puts the practical decision window at 2027–2030. Companies that wait until 2032 will pay a premium for accelerated implementations, rushed change management, and reduced consultant availability as the industry’s bench fills up with EBS migration work.

Four migration paths

There are four real options. We scope all of them during Assessment.

1. Lift and shift to OCI. Preserves your EBS install with cloud hosting. Buys 2–4 years. Reduces on-prem maintenance. Does not solve 2034 — postpones planning. 3–5 months, $150K–$350K.

2. Re-implementation to Cloud ERP. Clean slate, new design, drop most customizations, re-implement the genuinely unique business logic. Most common path. 12–18 months, $500K–$1.5M.

3. Hybrid (Cloud + EBS). Cloud ERP for Financials and Procurement, EBS retained for niche modules until those have native Cloud equivalents. De-risks change. 9–14 months, $400K–$1.2M. The 18–36 month hybrid window before EBS-side modules also migrate.

4. Phased pillar migration. Sequence the pillars: Financials → Procurement → SCM → HCM. Lower risk per phase, longer total timeline. 15–24 months, $700K–$2M.

Customization disposition is the real work

The single biggest source of EBS migration scope creep is “we have to bring all our customizations forward.” We have done customization inventories on EBS install bases with 200+ customizations and walked out with 30 that actually needed to migrate.

Three categories:

  • Native in Cloud ERP now. EBS could not do something in 2010, so you customized. Cloud ERP can do it natively today. Drop the customization.
  • Genuinely unique business logic. Re-implement as a Cloud ERP extension using OIC or VBCS. Usually 10–20% of customizations.
  • Historical decisions. Customizations that exist because someone made a call 8 years ago and no one remembers why. Drop after stakeholder sign-off.

We do this inventory and disposition during Assessment — before you commit budget — so the proposal range reflects what actually has to move.

Data migration: less than you think

Open transactions, balances, customer/vendor masters, item master, and selectively-defined recent history move forward. Full transactional history typically stays in EBS as a read-only system of record for 3–7 years post-migration.

We will be honest about how much history needs to come forward. Most “we must have all the history” requirements collapse under scrutiny. Audit, regulatory, and analytical needs are usually met by 12–24 months of recent transactional data plus the read-only EBS archive.

NetSuite or Cloud ERP?

Most EBS customers do not belong on NetSuite. The EBS install base biases toward larger, multi-pillar implementations that fit Oracle Cloud ERP.

But mid-market EBS customers — under $500M revenue, single-pillar Financials, modest customization — often migrate to NetSuite for cost and speed reasons. NetSuite implementations run roughly half the cost of comparable Cloud ERP implementations and ship 6–12 months faster.

We scope both paths in our Assessment. The right answer depends on operational complexity, scope, and existing Oracle investment — not on a tribal preference.

What to do now

If you are an EBS 12.2 customer and you have not started planning:

  1. Run an Assessment in the next 6 months. 4–6 weeks of focused work to inventory customizations, scope migration paths, and produce a business case. ~$50K–$120K depending on EBS footprint.
  2. Use it for executive alignment. A written assessment with realistic ranges is the document that moves a CFO + CIO + COO from “yes, eventually” to “yes, in this fiscal year’s plan.”
  3. Decide between 2027 and 2030. The decision is when, not if. Decide too late and you are buying accelerated execution at a premium.
FAQ

Frequently asked questions

01 What exactly happens at the end of 2034?
Premier Support for Oracle EBS 12.2 ends December 2034. Sustaining Support continues indefinitely after that — but Sustaining Support excludes new patches, regulatory updates, and tax updates. For US multi-state operators or multi-country businesses, that excludes the things that actually keep the system production-viable.
02 Can we just stay on EBS in Sustaining Support?
Technically yes. Practically no for most mid-market businesses. Sustaining excludes regulatory and tax updates — which means every payroll change, sales tax change, or country-level reporting change becomes a custom build. The cost of staying compounds quickly.
03 Is OCI lift-and-shift a real option?
Yes, as a stopgap. Lift-and-shift to Oracle Cloud Infrastructure preserves your EBS install with cloud hosting. It buys 2–4 years before re-implementation and reduces on-prem maintenance burden. It does not solve the 2034 problem — it postpones the planning decision, not the migration decision.
04 What's the realistic timeline for a typical mid-market migration?
Multi-pillar migrations run 18–30 months of execution: 4–6 weeks Assessment, 3–5 months Design, 5–9 months Build, 2–3 months Test/UAT, 3 months Cutover and Hypercare. Add 6–12 months on top of that for executive alignment, business case, and SI procurement. So 24–42 months end to end.
05 How do we know if we should migrate to NetSuite or Cloud ERP?
Three questions. (1) Is scope genuinely multi-pillar — Financials plus SCM, HCM, or EPM? (2) Does international statutory complexity push past NetSuite's localization library? (3) Is your customization volume and operational complexity at enterprise levels? Yes to two or three: Cloud ERP. No to all: NetSuite often wins on cost and time. We scope both paths in Assessment.
06 What about all our customizations?
Three categories. Native in Cloud now (drop), genuinely unique business logic (re-implement as OIC + VBCS extensions, usually 10–20% of customizations), and historical decisions no one remembers (drop after sign-off). Most EBS customers are surprised how few customizations actually need to migrate.
07 What's the cost?
$500K–$2M for typical EBS-to-Cloud migration. Variables: pillars, country rollouts, customization volume, integrations. Sounds large; staying on EBS through Sustaining Support sounds smaller until you price the regulatory and modernization debt.