Pillar · Oracle EBS · 2034 sunset

Oracle EBS to Oracle Cloud ERP: a roadmap for mid-market companies.

Premier Support for Oracle EBS 12.2 ends in 2034. The procurement, design, and migration timeline for mid-market companies is 18–30 months. Trevera builds the roadmap.

Tier 1
Oracle Platinum Partner
15+ yrs
NetSuite Alliance Partner
5×
Spotlight Award winner
$50M–$1B
Mid-market focus
Sunset calendar

Premier Support ends December 2034.

Working backward from sunset: 18–30 months of execution, plus 6–12 months of procurement and executive alignment. The practical decision window is 2027–2030.

2024
Premier Support
2025
Premier Support
2026
Premier Support
2027
Decision window
2028
Decision window
2029
Decision window
2030
Decision window
2031
Late
2032
Late
2033
Late
2034
Premier ends
2035+
Sustaining only
Premier on Decision window Late Premier ends Sustaining only
The deadline

Why 2034 means decide now.

Oracle EBS 12.2 Premier Support runs through December 2034. After that, Sustaining Support continues indefinitely — but excludes new patches, regulatory updates, and 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.

Working backward from 2034: a typical mid-market multi-pillar migration is 18–30 months from kickoff to go-live. Add 6–12 months for procurement, business case, and executive alignment. That puts the practical decision window at 2027–2030 for most companies — and if you are not already planning, you are already behind schedule.

The 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. Plan now, execute carefully.

Migration paths

Four ways to leave EBS.

We scope all four during Assessment. The right answer depends on your customization volume, operational risk tolerance, and how much of the next 30 months you want spent in transition.

Path Best forWhat it isTimelineRange
1. Lift & shift to OCI Buying 2–4 yrsSame EBS, cloud-hosted3–5 mo$150K–$350K
2. Re-implementation (clean slate) Most commonNew design, modern process12–18 mo$500K–$1.5M
3. Hybrid (Cloud + EBS) Niche modules retainedCloud for core, EBS for specialty9–14 mo$400K–$1.2M
4. Phased pillar migration De-risk by sequencingFinancials → Procurement → SCM → HCM15–24 mo$700K–$2M
Mid-market multi-pillar references. Single-pillar runs roughly 50% of these durations and 60% of cost.
Roadmap

Five phases. Real durations.

Phase DurationKey outputs
1. Assessment 4–6 weeksCustomization + integration inventory; business case; sign-off
2. Design 3–5 monthsTO-BE process; config decisions; customization scope
3. Build 5–9 monthsConfiguration; customization; integration; data migration
4. Test + UAT 2–3 monthsReal-data testing; defect resolution; readiness sign-off
5. Cutover + Hypercare 3 monthsCutover weekend; day-one validation; 60-day hypercare
Typical durations for a mid-market multi-pillar EBS-to-Cloud migration.
Customization disposition

Most EBS customizations don't migrate.

The single biggest source of EBS migration scope creep is "we have to bring all our customizations forward." Most EBS install bases have customizations in three categories:

  • Native in Cloud ERP now. EBS could not do something natively 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 decision 8 years ago and no one remembers why. Drop after stakeholder sign-off.

Trevera does the customization inventory and disposition during the Assessment phase — before you commit budget — so you have a realistic picture of what actually needs to move.

What "disposition" looks like in practice

Each customization gets logged with: original business need, current usage, native Cloud ERP equivalent (if any), recommended disposition (drop, replace with config, replace with extension, retain via integration), estimated rebuild effort, and stakeholder owner.

Disposition is a decision document, not an inventory. It moves through finance, ops, and IT for sign-off so the call is explicit and the budget reflects reality.

Data migration

How much history actually needs to move?

Less than people think. Most "we have to bring all the history" requirements collapse under scrutiny. Open transactions, balances, and master data are non-negotiable. Recent transactional history is selective. Full archive lives read-only in EBS for 3–7 years.

Data class Move forward?Notes
Open transactions AlwaysMigrate forward
Trial-balance / period balances AlwaysValidated against legacy
Customer + vendor masters AlwaysCleaned + deduplicated
Item master + BOMs AlwaysRationalized before migration
Recent transactional history 12–24 months typicalSelective by criticality
Full transactional history RarelyRead-only EBS retained 3–7 yrs
Custom tables / schema SelectivePer disposition outcome
Hybrid

When hybrid is the right call.

Hybrid is right when one of these holds:

  • You run an EBS module that has no Cloud equivalent yet — niche manufacturing or industry-vertical functionality Oracle has not finished migrating.
  • The risk of replacing a critical operational system in lockstep with financials is unacceptable to the business.
  • Budget reality forces sequencing, and Financials + Procurement is the first wave that pays for itself.

The pattern: Cloud ERP for Financials, Procurement, EPM, and Reporting; EBS retained for niche modules; OIC bridges the two; data lake aggregates for reporting. The hybrid window is typically 18–36 months before the EBS-side modules also migrate.

FAQ

EBS migration questions.

01 When does Oracle EBS Premier Support actually end?
EBS 12.2 has Premier Support through December 2034. After that, Sustaining Support continues indefinitely but excludes new patches, regulatory updates, and tax updates — which is the practical end of EBS as a viable production ERP for most companies. The procurement, design, and migration timeline for a mid-market company is 18–30 months. If you have not started planning, you are already behind schedule.
02 Should we go to NetSuite or Oracle Cloud ERP?
Most EBS customers do not belong on NetSuite — the EBS install base is biased 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. We scope both paths in our roadmap.
03 What does the migration roadmap actually look like?
Phase 1 — Assessment (4–6 weeks): customization inventory, integration inventory, customization disposition (keep/replace/drop), business case, executive sign-off. Phase 2 — Design (3–5 months): TO-BE process, configuration, customization scope. Phase 3 — Build (5–9 months). Phase 4 — Test + UAT (2–3 months). Phase 5 — Cutover + hypercare. Total: 18–30 months for typical mid-market multi-pillar.
04 How do we handle EBS customizations?
Three categories. (1) Customizations that exist because EBS could not natively do something — most of these are now native in Cloud ERP and get dropped. (2) Customizations that genuinely encode unique business rules — re-implemented as Cloud ERP extensions. (3) Customizations that exist because of historical decisions no one remembers — dropped after sign-off. Most EBS customers are surprised how few customizations actually need to migrate.
05 What does it cost?
$500K–$2M for a typical EBS-to-Cloud migration depending on pillars in scope, country rollouts, customization volume, and integration count. The number sounds large; staying on EBS through Sustaining Support sounds smaller until you price the regulatory risk and modernization debt.
06 Can we go hybrid — keep some EBS modules and migrate others?
Yes, and many mid-market EBS customers do. Common pattern: migrate Financials and Procurement to Cloud, retain EBS for niche manufacturing or industry modules until those are also available natively in Cloud. The hybrid approach extends timeline but de-risks change.
07 How is data migration handled?
Open transactions, balances, customer/vendor masters, item master, and selectively-defined historical data 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 actually needs to come forward — most "must have all the history" requirements collapse under scrutiny.
08 What about lift-and-shift to OCI as a stopgap?
Lift-and-shift to Oracle Cloud Infrastructure preserves your EBS install with new 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. We recommend it only when re-implementation cannot start in the current fiscal year and OCI cost models work for your shape.
09 How does Trevera staff a multi-year EBS engagement differently from a Big SI?
Big SIs staff an A-team for the SOW, then rotate associates in once execution starts. Trevera assigns named senior consultants for the duration. Pillar leads, technical leads, and integration leads do not rotate. The economics work because we are sized for mid-market multi-pillar — we do not carry global enterprise overhead.
10 What about customizations Oracle never gave us a Cloud equivalent for?
Three options. (1) Re-implement using OIC + VBCS — the supported extension stack. (2) Push the requirement to a third-party SaaS integrated to Cloud ERP. (3) Drop it after sign-off if the original need has eroded. We document each customization with disposition during Assessment so the call is explicit, not implicit.
Next step

Have a NetSuite or Oracle Cloud project on the table?

We'll tell you what's realistic, what it'll cost, and where it could go wrong — before you sign anything.

Get a written assessment Read our insights
90 minutes · No deck · No SDR