Power Systems AdvisorsGet a Power Cloud Assessment

Stay on AIX vs. move to Linux

Stay on AIX or Move to Linux: How to Decide

A workload-by-workload look at keeping applications on AIX versus porting them to Linux on Power, x86, or cloud, driven by ISV calendars rather than platform loyalty.

Get a Power Cloud AssessmentSee all comparisons

Independent guidance, not tied to IBM or to any hosting or software vendor.

Should we stay on AIX or move to Linux?

Treat it as a workload triage, not an estate-wide vote. Some workloads are being pushed off AIX by software vendors: SAP HANA runs only on Linux, and Oracle's October 2025 platform update plans to retire JD Edwards EnterpriseOne support for UNIX platforms including AIX. Others have a long, supportable runway: Oracle Database 19c carries Extended Support on AIX to December 2032 per Oracle's lifetime support policy, and IBM's published AIX roadmap extends into 2035. Most real AIX estates end up split for years, and that is a normal outcome, not a failure.

Practical decision support

Bucket workloads, then schedule moves against ISV calendars

Use this comparison to place each AIX workload into one of four buckets: forced move, strong stay, cheap win, or decide later with a review date.

  • Anchor every move to a dated forcing event (SAP maintenance windows, JDE platform retirement, Oracle Database support milestones), not to sentiment.
  • Score each workload on ISV certification, endian exposure in code and data, skills coverage, license math, HA and DR model, and remaining hardware life.
  • Model Oracle license counts for equivalent throughput on each platform rather than applying the core factor alone.

Forcing events

What is forcing the question in 2026

The pressure on AIX is not coming from IBM. IBM’s published strategy guide lays out an AIX roadmap extending into 2035, and AIX ran on Power11 from launch (announced July 8, 2025, generally available July 25, 2025). The pressure comes from the software vendors who decide where their products are certified to run, and several have now put dates on the calendar:

  • JD Edwards EnterpriseOne: Oracle’s platform support update of October 28, 2025 (My Oracle Support Doc 3108726.1) announces a plan to retire JDE EnterpriseOne support for UNIX platforms, including AIX, HP-UX, and Solaris. IBM i is not part of the retirement, and Oracle’s Applications Unlimited page commits to Premier Support for the product through at least 2037, so this is a platform decision, not a product decision. The full timeline sits behind a My Oracle Support login; pull the document and confirm dates with Oracle. Our JD Edwards on IBM i guide covers the parallel story on the platform Oracle is keeping.
  • SAP: HANA runs only on Linux (SUSE Linux Enterprise Server and Red Hat Enterprise Linux), including on IBM Power hardware; it has never been offered on AIX. SAP’s February 2020 announcement set mainstream maintenance for core Business Suite 7 applications through the end of 2027, with optional extended maintenance at a premium through the end of 2030. SAP has since added RISE-based transition options, so verify current terms with SAP. Either way, an ECC estate on AIX eventually lands its database tier on Linux.
  • Oracle Database: 19c is the current production release on AIX, with Premier Support to December 2029 and Extended Support to December 2032 per Oracle’s lifetime support policy. The next-generation database (26ai, formerly 23ai) had not shipped on AIX as of this writing; IBM-side commentary has pointed to calendar year 2026, but that is IBM talking about Oracle’s deliverable, so verify with Oracle.
  • The shrinking field: HP-UX reached end of support in December 2025, per trade coverage, leaving AIX as the last major commercial UNIX with an actively developed hardware line. That feeds the other pressure practitioners commonly report, a thinning pool of AIX administrators. We have not seen a rigorous survey to cite, so treat hiring difficulty as real but anecdotal.

The stay case

The case for staying on AIX

IBM is still investing. The company’s AIX executive strategy guide (an IBM ID is required to download it) shows a roadmap into 2035, and Power11 shipped in July 2025 with AIX supported from day one. IBM claims 99.9999% uptime for the platform, zero planned downtime for system maintenance, and under one minute of ransomware threat detection with Power Cyber Vault; those are IBM’s numbers, but they signal a vendor planning for the long haul, not managing a decline.

The support runway is real. Oracle Database 19c on AIX is supportable to December 2032 with Extended Support, which is a longer horizon than most migration programs need. And the economics of a working estate matter: an AIX system that runs well today carries near-zero change risk, while every migration carries testing, cutover, and downtime costs that never appear in a license comparison. PowerVM consolidation and strong per-core performance often mean fewer cores doing the same work. Our AIX hubtracks the platform’s support dates and options in one place.

One honest caveat: AIX-specific fine print is creeping into Oracle’s own policy. The current lifetime support document states that from May 2027, support for 19c excludes Java 8 related third-party software, an exclusion Oracle says primarily impacts the 19c ports, including AIX. Small today, but it shows which direction the wind blows.

The move case

The case for Linux is really two cases

Linux on Power (ppc64le) is the smaller move. PowerVM runs RHEL, SLES, and Ubuntu LPARs beside AIX on the same machine, so you keep the hardware, the virtualization layer, the RAS characteristics, and often the support contract. It is the only path that gets SAP HANA while staying on Power. Two caveats: current Linux distributions on Power are little-endian and AIX is big-endian, so even a same-machine move is a real port, and Oracle Database has no Linux on Power port, per Oracle’s support statement for IBM Systems as of this writing (confirm against Oracle’s certification matrix). For Oracle Database, the realistic destinations are staying on AIX, x86 Linux, or a cloud service.

Linux on x86 or in the cloud is the bigger move with the bigger ecosystem: the widest ISV certification lists, container and Kubernetes-native tooling, and the broadest hiring pool. The license math also shifts. Oracle’s core factor table (updated January 28, 2026) rates x86 at 0.5 per core against 1.0 for POWER8 through POWER10, so one processor license covers two x86 cores but only one Power core (Power11 is not yet named in the table; the catch-all row is 1.0). The honest comparison is licenses needed for equivalent throughput, not the factor alone, because fewer, faster Power cores can offset the higher factor.

Side-by-side view

How the three paths compare

Staying on AIX compared with the two Linux destinations across five decision factors.
OptionISV directionMigration effortOracle Database fitLicense mathSkills pool
Stay on AIXIBM roadmap into 2035 per IBM's guide; some ISVs retiring UNIX certificationsNone today; plan hardware refresh and support milestones instead19c supported, Extended Support to December 2032 per OracleOracle core factor 1.0; fewer, faster cores per workloadDeep but thinning; hiring difficulty commonly reported
Linux on Power (ppc64le)Only SAP HANA path that keeps Power hardwareReal port: endian audit, recompile, retest; same machine possibleNot available as of this writing; no Linux on Power portDepends on ISV; Oracle Database does not apply hereLinux skills transfer; Power-specific operations remain
Linux on x86 or cloudLargest ISV and tooling ecosystemFull replatform: port plus new infrastructure and operationsFully supported; cross-endian data migration requiredCore factor 0.5; model licenses for equivalent throughputBroadest hiring pool

Migration reality

What an AIX to Linux migration actually involves

Endianness comes first. AIX is big-endian; every current Linux distribution on Power is little-endian (ppc64le), a switch IBM made in the POWER8 era to align Linux on Power with the x86 software ecosystem. Moving to x86 crosses the same boundary. Either way, binary data files, network code that assumes byte order, and shared memory layouts in C and C++ all need an audit, which is why even a move to a Linux LPAR on the same physical machine is a port, not a copy.

Then the toolchain: code built with IBM XL compilers gets rebuilt with gcc or clang, and every build dependency and runtime library needs an inventory on the target. Java, scripting languages, and most middleware move easily. Decades-old C and C++ with endian and compiler assumptions is the expensive tail, and it is usually where estimates go wrong.

Databases are their own project. Oracle documents cross-endian moves via transportable tablespaces with RMAN CONVERT, Data Pump, and GoldenGate replication for minimal-downtime cutovers. The path is tooled but not trivial: budget for conversion runs, validation, and rollback rehearsal. Finally, the operations layer re-platforms too: NIM, mksysb, smitty, and PowerHA workflows map to different Linux tooling, and every third-party product in the stack needs an ISV certification check on the target. Our AIX cloud migration checklist covers the inventory work, and if the real question is whether to change the application rather than the platform, start with migrate vs. modernize.

Decision framework

Triage workload by workload

Do not put the estate to a vote. Score each workload on ISV certification, endian exposure, skills coverage, license math, HA and DR model, and remaining hardware life, then place it in one of four buckets. An independent assessmentis the fastest way to get that map built without a vendor’s thumb on the scale.

Four buckets

Where each workload lands

Bucket 1: Forced moves on a calendar

SAP ECC heading to S/4HANA (HANA is Linux-only) and JD Edwards EnterpriseOne on AIX. Pick the landing zone and sequence these first; the dates are not yours to move.

Bucket 2: Strong stay candidates

Oracle Database inside the 19c support window, stable homegrown COBOL and C estates with no ISV pressure, and PowerHA-clustered core systems that would carry high migration risk.

Bucket 3: Cheap wins to move

Java and WebSphere-style application tiers, and anything already containerizable. Low endian exposure, short test cycles, early proof that the program works.

Bucket 4: Decide later, with a review date

Everything else. Tie the review date to real events: Oracle 26ai availability on AIX (verify with Oracle) and IBM's next AIX roadmap update.

Dates that matter

Timelines to put on your wall

As of this writing, these are the published milestones shaping AIX platform decisions. Verify each with the vendor before committing budget to it:

  • May 2027: Oracle 19c support begins excluding Java 8 related third-party software, primarily impacting the 19c ports including AIX (per Oracle’s lifetime support policy).
  • End of 2027: SAP mainstream maintenance ends for core Business Suite 7 applications (per SAP’s announcement; RISE-based options may change individual timelines).
  • December 2029: Oracle Database 19c Premier Support ends.
  • End of 2030: SAP’s optional extended maintenance for Business Suite 7 ends.
  • December 2032: Oracle Database 19c Extended Support ends.
  • 2035: the horizon of IBM’s published AIX roadmap.
  • JD Edwards UNIX platform retirement: dates sit behind My Oracle Support Doc 3108726.1; pull the document and confirm with Oracle.

Common mistakes

Where these decisions go wrong

Use caution

Reading the core factor as a 50% discount

Oracle's 0.5 factor on x86 versus 1.0 on Power halves the per-core license cost, not the bill. License need is factor times cores required for equivalent throughput, and Power's per-core performance often narrows the gap. Model it before promising savings.

Use caution

Assuming Oracle Database can follow you to Linux on Power

Oracle Database has no ppc64le port as of this writing, so 'move to Linux on the same box' does not work for that workload. Its realistic destinations are staying on AIX, x86 Linux, or a cloud service. Confirm current certifications with Oracle.

Use caution

Treating a same-hardware move as a lift-and-shift

AIX is big-endian and Linux on Power is little-endian, so binary data, network code, and shared memory assumptions all need an audit even when the physical machine does not change. Budget for a port, not a copy.

Stay on AIX vs. move to Linux: frequently asked questions

Is IBM discontinuing AIX?

No. IBM's published AIX strategy guide shows a roadmap extending into 2035, and AIX was supported on Power11 from its July 2025 general availability. As of this writing, the pressure on AIX comes from the ISV side, not from IBM: vendors like Oracle's JD Edwards team are retiring UNIX platform certifications even while IBM keeps investing in the operating system and the hardware underneath it.

Does SAP HANA run on AIX?

No, and it never has. SAP HANA is supported only on Linux (SUSE Linux Enterprise Server and Red Hat Enterprise Linux), including when it runs on IBM Power hardware. An SAP ECC estate on AIX facing the end-2027 mainstream maintenance date (extended maintenance to end 2030, per SAP's announcement) has to land its database tier on Linux, though it can stay on Power via Linux LPARs.

Is Oracle dropping AIX?

Distinguish product lines. JD Edwards EnterpriseOne: Oracle's October 2025 platform update plans UNIX platform retirement including AIX, while IBM i is unaffected. Oracle Database: no announced exit. Per Oracle's lifetime support policy, 19c on AIX has Premier Support to December 2029 and Extended Support to December 2032, but the next-generation database (26ai, formerly 23ai) had not shipped on AIX as of this writing, so verify current availability with Oracle.

Can I move from AIX to Linux without leaving Power hardware?

Yes, with two caveats. PowerVM runs AIX and Linux LPARs side by side, so Linux on Power (RHEL, SLES, Ubuntu) keeps the hardware, the virtualization layer, and often the support contract. Caveat one: Linux on Power is little-endian and AIX is big-endian, so this is a port, not a copy. Caveat two: Oracle Database has no Linux on Power port as of this writing, so Oracle Database workloads cannot take this path.

Will moving Oracle Database from AIX to x86 cut my license bill in half?

Not automatically. Oracle's core factor table (updated January 28, 2026) rates IBM POWER8 through POWER10 at 1.0 and x86 at 0.5 per core, so each processor license covers two x86 cores versus one Power core. But license need is the factor times the cores required for the workload, and per-core throughput differs between platforms. Model licenses for equivalent throughput, and remember a migration also carries testing, downtime, and cross-endian data conversion costs.

What makes an AIX to Linux migration hard technically?

Three things dominate. Endianness: big-endian AIX to little-endian Linux breaks binary data files, network byte-order code, and shared memory assumptions in C and C++. Toolchain: IBM XL compiler behavior versus gcc or clang, plus every runtime dependency in the build. Operations: NIM, mksysb, smitty, and PowerHA workflows all map to different Linux tooling. Java and scripted workloads usually move easily; decades-old C with endian assumptions is the expensive tail.

Should we migrate the whole estate at once?

Almost never. Triage workload by workload: some have calendar deadlines (SAP ECC, JD Edwards on AIX), some are strong stay candidates (Oracle Database inside the 19c support window, stable clustered core systems), and some are cheap early wins (app tiers that are already portable). Most real estates end up split for years, and that is a normal outcome, not a failure. An independent assessment maps which bucket each workload lands in.

Sources

Support dates, platform certifications, and license terms above are attributed to the vendors named and were current as of this writing. Verify each with IBM, Oracle, SAP, or your ISV before committing to a migration or renewal decision.

Not Sure Which Bucket Each Workload Lands In?

Get an independent, workload-by-workload triage of your AIX estate: what has a deadline, what should stay, and what moves first.

Get a Power Cloud AssessmentCompare all options

Related pages