Oracle EBS Sunset Dates: EBS Support and NetSuite Migration Guide

Oracle confirmed that EBS 12.1.3 moved to Sustaining Support on January 1, 2022. Oracle had previously announced that Extended Support for EBS 12.0 ended January 31, 2015, while Premier Support for EBS 11i ended in November 2010.

Therefore, organizations using EBS 12.1 or earlier are already operating on releases that no longer receive the benefits associated with Premier Support.

What Does Sustaining Support Mean for Oracle EBS Customers?

Sustaining Support allows customers to continue accessing certain existing support resources for as long as they maintain eligible Oracle support agreements. However, it is not equivalent to Premier Support.

In practical terms, an older EBS release in Sustaining Support may not receive:

• New product updates, fixes or security patches

• New tax, legal and regulatory updates

• Certifications with newly released Oracle or third-party products

• New upgrade tools

• Fixes for newly discovered issues that were not previously addressed

• Support for newer operating systems, browsers, databases and infrastructure components

This distinction is especially important for businesses in regulated industries or organizations with strict cybersecurity, audit and compliance requirements.

An application may continue to operate after entering Sustaining Support, but the risk profile can change substantially. Over time, it may become harder to protect, integrate and maintain the environment while supporting modern business requirements.

Oracle EBS 12.2 Is Supported, but It Still Requires Active Management

Oracle EBS 12.2 is not currently at end of life. Oracle’s March 2026 announcement extends Premier Support through at least 2037, and the latest release update pack listed by Oracle is EBS 12.2.15, released in October 2025.

Oracle’s Continuous Innovation model enables customers to apply ongoing EBS 12.2 updates without undergoing another major application-version upgrade. However, Continuous Innovation does not remove the need to maintain the broader EBS technology stack.

Companies must still evaluate and manage areas such as:

• EBS release update packs and application patches

• Oracle Database versions

• Operating-system certifications

• Middleware and identity-management components

• Security updates

• Browser compatibility

• Customizations and extensions

• Integrations with third-party systems

• Infrastructure capacity and performance

• Disaster recovery and business continuity

• Specialized Oracle technical resources

For example, Oracle has continued to certify EBS 12.2 with newer technology components, including Oracle AI Database 26ai for qualifying on-premises Linux environments. These certifications can extend the life of EBS, but adopting them may require planning, testing and technical upgrades.Workflows and customization should accelerate and streamline processes. Yet many NetSuite environments accumulate outdated SuiteScripts, undocumented customization, and manual workarounds that slow operations and frustrate users.

Why Companies Are Considering a Move Away From EBS

A support extension provides additional time. It does not necessarily resolve the operational reasons companies consider replacing EBS.

Many organizations originally implemented Oracle E-Business Suite when an on-premises enterprise application was the standard approach. Since then, business expectations have shifted toward cloud delivery, mobile access, real-time reporting, simplified integrations, automatic updates and lower infrastructure overhead.

Common reasons businesses evaluate a transition from Oracle EBS to Oracle NetSuite include:

Aging or unsupported EBS versions:
Companies running EBS 12.1 or earlier must decide whether to undertake a significant technical upgrade to EBS 12.2 or move to a modern cloud ERP platform.

High infrastructure and maintenance requirements: An EBS environment can require database administrators, system administrators, developers, security specialists and functional consultants. Hardware, hosting, backup, disaster recovery and monitoring responsibilities must also be addressed.

Heavy customization: Years of custom development can make an EBS environment expensive to patch, test and upgrade. Some customizations may also reflect outdated business processes that should be redesigned rather than recreated.

Limited accessibility: Organizations increasingly expect employees to access ERP information from different locations and devices without relying on complex remote-access configurations.

Fragmented reporting: Companies may depend on separate data warehouses, spreadsheets or reporting applications to obtain consolidated business information from EBS and its surrounding systems.

Growth through acquisitions or new subsidiaries: Adding entities, currencies, countries and business units to a heavily customized legacy environment can take considerable time and technical effort.

Difficulty hiring specialized resources: Experienced EBS technical resources can be difficult and expensive to recruit and retain, particularly when an organization relies on highly customized legacy configurations.

Oracle EBS vs. Oracle NetSuite

Security and compliance are often rushed during go-live and ignored until an audit, incident, or access issue exposes gaps. A health check should confirm that your ERP environment follows current requirements for access control, audit trails, and change management.

Review user roles for access to sensitive data, financial records, and administrative functions. Permissions should follow least privilege, and inactive users should be removed to reduce security and compliance risk.

Audit logs should also be complete for critical records and transactions. NetSuite system notes should show who changed what, when, and where, so teams can investigate issues and support audit requirements.

Change management is the final control layer. Customizations, workflows, and integration updates should be reviewed, tested in a sandbox, approved, and documented before reaching production. This keeps the ERP environment stable, traceable, and audit-ready.

AI and Analytics Readiness: Can You Analyze Data Faster in 2026?

Oracle E-Business Suite and Oracle NetSuite are both Oracle ERP platforms, but they were designed around different deployment models and operating philosophies.

Oracle EBS is traditionally deployed and managed as an on-premises enterprise application, although it can also be hosted on cloud infrastructure. NetSuite is a multitenant software-as-a-service platform in which the application and underlying infrastructure are managed as a cloud service.

Oracle describes NetSuite ERP as an integrated, AI-powered cloud business management platform that supports financial management, order management, inventory, procurement and other core business processes.

Oracle EBS vs. NetSuite: High-Level Comparison