SAP on IBM Power: AIX, HANA, and RISE on Power Virtual Server
What are the realistic paths for SAP on IBM Power?
Two clocks are running. SAP's maintenance strategy page states mainstream maintenance for ECC 6.0 on enhancement packages 6 through 8 ends December 31, 2027, with paid extended maintenance to the end of 2030. And SAP HANA runs only on Linux, never on AIX, so every ECC estate on AIX with Db2 or Oracle faces a platform change on the way to S/4HANA. That leaves three realistic paths: run ECC on AIX to the deadline (in your data center, in PowerVS, or with a managed Power host), convert to S/4HANA on Linux on Power (including the SAP-managed RISE offering on Power Virtual Server), or replatform to an x86 hyperscaler. This guide maps all three.
Practical decision support
Plan against SAP's published dates, not the rumor mill
Use this guide to place your ECC or S/4HANA estate on the maintenance timeline, rule HANA on AIX out early, and choose between running out ECC, converting on Power, or replatforming to x86.
- Confirm your exact enhancement package level first: EHP0 through 5 left mainstream maintenance at the end of 2025, per SAP.
- Treat vendor migration timelines, IBM's 90 day claim included, as infrastructure figures rather than conversion program plans.
- Keep the database question separate from the hosting question: AIX Db2 and Oracle sources always move through SAP migration tooling.
At a glance
Key takeaways
The deadline is compound
Per SAP, ECC 6.0 on EHP6 through 8 has mainstream maintenance until December 31, 2027, extendable to 2030 for a premium. EHP0 through 5 already ended in December 2025.
HANA never runs on AIX
SAP HANA is Linux only: SLES or RHEL, on x86_64 or Power in little endian mode. AIX still runs NetWeaver app servers and ECC databases on Db2 or Oracle.
You can reach S/4HANA without leaving Power
HANA is certified on Power8 through Power11 under PowerVM per SAP Note 2188482, on premises and on Power Virtual Server as SAP-certified IaaS.
RISE on PowerVS is live
Announced January 2025, renamed SAP Cloud ERP Private in July 2025, and taking named customers as of July 2026 per SAP and IBM. Verify regions with IBM.
The Deadline, Precisely: 2025, 2027, 2030, and the 2033 Footnote
SAP's maintenance strategy page states that mainstream maintenance for SAP Business Suite 7 core applications, which includes SAP ERP 6.0 (ECC) on enhancement packages 6, 7, and 8, runs until December 31, 2027, with optional extended maintenance until December 31, 2030 at a premium of two percentage points on the maintenance basis. The fine print matters more than the headline: per SAP's published maintenance timelines, ECC 6.0 without an enhancement package and on EHP1 through 5 already left mainstream maintenance on December 31, 2025, so those systems sit in customer-specific maintenance today unless the EHP level was raised. At the other end, SAP has committed to maintaining S/4HANA until the end of 2040.
Will SAP blink? SAP has stated there will be no further extension of the 2025 and 2027 dates, and independent coverage (The Register, citing Gartner) describes SAP holding firm while speculation continues. The one concession announced so far is not an extension. In February 2025, SAP announced the SAP ERP, private edition, transition option: a cloud subscription purchasable starting 2028 and usable from 2031 through 2033 at what SAP describes as an expanded fee. Per SAP's announcement, systems must move into SAP's private edition before the end of 2030, and HANA is the only supported database. That is a managed cloud subscription with strings attached, not on-premises ECC support. Plan against the published dates and verify them with SAP as your program starts.
Get One Thing Straight: HANA Does Not Run on AIX
SAP HANA runs only on Linux. SAP Note 2235581 lists SUSE Linux Enterprise Server and Red Hat Enterprise Linux as the only supported operating systems, on x86_64 and on IBM Power in little endian mode (ppc64le). AIX is not a supported operating system for SAP HANA on any hardware. On Power, HANA means Linux LPARs under PowerVM, full stop. What AIX does run, and runs well, is the rest of the classic SAP stack: NetWeaver application servers, and ECC database servers on IBM Db2 or Oracle. IBM's Power Virtual Server documentation draws the same line for cloud, stating that PowerVS can run NetWeaver application servers on AIX or Linux, database servers with Db2 or Oracle on AIX, and HANA on Linux, with SAP Note 2855850 governing supported OS versions. Oracle publishes dedicated Database 19c installation documentation for AIX on Power, which is why so many ECC estates look exactly like this.
A short history clears up a common confusion. HANA 1.0 on Power was big endian; with HANA 2.0, SAP moved every HANA system, Power included, to little endian, and SAP KBA 2554012 documents the conversion legacy customers went through. The consequence today: a HANA 2.0 database on Power and one on x86 share the same byte order, so endianness no longer separates the platforms. The endian issue that still matters is AIX itself, which is big endian. Db2 or Oracle data on AIX never lifts directly into HANA anywhere; that move is always a heterogeneous migration through SAP tools.
RISE with SAP on Power Virtual Server, Now Called SAP Cloud ERP Private
On January 7, 2025, IBM and SAP announced RISE with SAP on IBM Power Virtual Server: an SAP-managed S/4HANA private cloud subscription running on PowerVS infrastructure, positioned as a hyperscaler option alongside AWS, Azure, and Google Cloud. IBM's announcement claims that like-for-like Power to Power migration can cut the S/4HANA Cloud infrastructure move to about 90 days, and pairs the offering with an IBM investment program, the IBM Transformation Suite for SAP Applications (assessment, data migration, automated testing), and a buyback program for eligible on-premises Power servers. Treat the 90 day figure as a vendor claim about infrastructure relocation, not a conversion timeline. IBM also says it moved its own quote-to-cash and record-to-report processes onto the offering, serving more than 150,000 users across 175 countries, completed within 18 months with a claimed 30 percent reduction in infrastructure and operational costs. That is IBM's own account of its own project.
Two reality checks. First, naming: in July 2025 SAP rebranded RISE with SAP S/4HANA Cloud, private edition as SAP Cloud ERP Private, so contracts and coverage now mix both names for the same thing. Second, availability: the offering is live and taking customers. On July 2, 2026, SAP and IBM named JYSK, GBM, DIFARE Group, and Plastilene Group as enterprises that selected SAP Cloud ERP Private on Power Virtual Server. The January 2025 announcement said planned availability in Q2 2025, and we did not find a release marking the exact general availability date, so verify current availability, supported regions, and eligibility terms directly with IBM before building a plan around it.
The Three Realistic Paths for an SAP on Power Estate
Path A: run ECC where it is, on your terms. If you are on EHP6 through 8, mainstream maintenance carries you to the end of 2027 and extended maintenance to 2030, which buys time to build the S/4HANA business case properly. If the data center lease, not SAP, is your forcing function, you can lift the AIX ECC landscape to PowerVS or to a managed Power hosting provider without replatforming, since NetWeaver on AIX with Db2 or Oracle remains supported there per IBM's documentation and SAP Note 2855850. Our AIX cloud migration checklist covers that move step by step.
Path B: S/4HANA on Linux on Power. This keeps your PowerVM operational skills, your consolidation economics, and your IBM relationship while changing the database and application layer. It runs on premises on Power10 or Power11, on PowerVS as SAP-certified infrastructure, or as the SAP-managed Cloud ERP Private subscription described above, which is simply the managed flavor of this path.
Path C: replatform to an x86 hyperscaler on SAP-certified IaaS. This is a full heterogeneous migration, typically via SUM DMO with System Move, and a larger organizational change: you leave Power skills, PowerVM licensing, and the existing operational model behind. Since HANA 2.0 is little endian on both architectures, endianness no longer penalizes a later HANA to HANA move in either direction, but an AIX AnyDB source still goes through DMO or SWPM no matter which target you pick.
Migration Mechanics in One Page
SAP's Software Update Manager Database Migration Option (DMO) supports DMO with System Move, which relocates the complete system to a new data center or cloud while migrating the database to HANA, optionally converting to S/4HANA in the same project. The single step DMOVE2S4 memory pipe variant, per SAP community documentation, needs latency under 20 milliseconds and bandwidth above 400 Mbps between source and target, which constrains how you pair sites. AIX sources on Db2 or Oracle are heterogeneous migrations no matter the target. For cross-platform HANA to HANA copies, verify the supported system copy method with SAP before assuming backup and restore works across architectures; SAP Note 1642148, the backup and recovery FAQ, is the place to check. And remember the brownfield versus greenfield question is a bigger decision than any of the infrastructure choices here.
Sizing and Certification Notes for HANA on Power
SAP Note 2188482 is the gatekeeper for HANA on Power hardware. It states HANA is supported on Power8, Power9, Power10, and Power11 systems with PowerVM, with workload-based sizing required from Power9 onward; recent versions of the note document per-LPAR memory up to 32 TB on high-end systems with HANA 2.0 SPS05 or later and up to 16 production HANA LPARs on a Power10 E1080. Power11 became generally available on July 25, 2025, and HANA certification for the high-end E1180 was published in late November 2025 per the hanaonpower.com blog, which is run by IBM SAP on Power specialists; model-level detail should be confirmed in the live note and the SAP Certified and Supported SAP HANA Hardware Directory, which is the authoritative list. PowerVS itself is SAP-certified IaaS for production HANA, governed by SAP Notes 2947579, 2855850, and 2923984. Whether PowerVS offers Power11 capacity in your region is worth verifying with IBM; do not assume it.
Three Paths Compared
Match each path to your enhancement package level, your Power skills, and your appetite for change.
| Option | How it works | Trade-offs to weigh |
|---|---|---|
| Path A: run out ECC on AIX | Stay on ECC to 2027 or 2030 (EHP6 to 8 only); optionally lift the AIX landscape to PowerVS or a managed Power host to exit the data center | Lowest change now, but the S/4HANA decision is deferred, not avoided, and extended maintenance carries a two point premium per SAP |
| Path B: S/4HANA on Linux on Power | Convert with DMO to HANA on Power10 or Power11 LPARs, on premises, on PowerVS, or SAP-managed as Cloud ERP Private on PowerVS | Keeps Power skills and large-LPAR consolidation; the OS changes to Linux, and the managed flavor is a subscription with SAP operating the stack |
| Path C: replatform to x86 hyperscaler | Full heterogeneous migration via SUM DMO with System Move to SAP-certified IaaS on AWS, Azure, or Google Cloud | Aligns with an all-hyperscaler strategy but abandons Power skills and licensing; the biggest testing and change management load of the three |
How to Decide, and Why the Math Says Start Now
The pattern we see: staying put fits shops on EHP6 through 8 whose S/4HANA business case is genuinely not ready; the Power path fits shops with PowerVM depth, large HANA sizings, and an IBM relationship worth keeping; the x86 path fits organizations already consolidating on a hyperscaler whose Power skills are leaving anyway. Then do the timeline math. A brownfield S/4HANA conversion typically runs 12 to 24 months including testing and change management, and IBM's own internal program took 18 months by its account. As of this writing in August 2026, a shop targeting the end of 2027 needs to have started already, and targeting 2030 extended maintenance leaves roughly one comfortable program cycle. We are an independent advisory practice, not IBM, not SAP, and not a reseller of any provider covered here, and an independent assessment of your SAP on Power estate is built to pressure-test exactly this decision before you sign anything.
Risks and Common Mistakes
Use caution
Betting the estate on SAP extending the deadline
SAP has stated there will be no further extension of the 2027 and 2030 dates, and the 2031 to 2033 transition option is a cloud subscription requiring a move into SAP's private edition before the end of 2030, not an on-premises reprieve. Plan against the published dates.
Use caution
Reading the 90 day claim as a program plan
IBM's 90 day figure for RISE on PowerVS describes a like-for-like infrastructure relocation. The S/4HANA conversion around it typically runs 12 to 24 months, and IBM's own internal migration took 18 months by its account. Budget for the program, not the lift.
Use caution
Assuming the AIX database can move as files
AIX is big endian and HANA is Linux only, so Db2 or Oracle data on AIX always moves through SAP tooling (SUM DMO or SWPM system copy), never as a database file lift. Sizing, downtime windows, and test cycles follow from that fact.
Frequently Asked Questions
When does support for SAP ECC 6.0 actually end?
SAP's maintenance strategy page states mainstream maintenance for Business Suite 7, which covers ECC 6.0 on enhancement packages 6, 7, and 8, runs until December 31, 2027, with optional extended maintenance at a two percentage point premium until December 31, 2030. ECC 6.0 on enhancement packages 0 through 5 already left mainstream maintenance on December 31, 2025. After 2030, the only SAP-supported option announced so far is the SAP ERP, private edition, transition option, a cloud subscription usable 2031 through 2033 that requires moving into SAP's private edition before the end of 2030. Verify current dates with SAP.
Can SAP HANA run on AIX?
No. SAP HANA runs only on Linux: SUSE Linux Enterprise Server or Red Hat Enterprise Linux, on x86_64 or on IBM Power in little endian mode (SAP Note 2235581). On Power, that means Linux LPARs under PowerVM. AIX remains supported for SAP NetWeaver application servers and for ECC databases on IBM Db2 or Oracle, which is exactly what most legacy SAP on Power estates run today.
What is RISE with SAP on IBM Power Virtual Server, and is it live?
It is an SAP-managed S/4HANA private cloud subscription, announced by IBM and SAP on January 7, 2025, running on IBM Power Virtual Server infrastructure and positioned alongside the x86 hyperscaler options. SAP renamed the underlying RISE offering SAP Cloud ERP Private in July 2025. It is live: in July 2026 SAP and IBM named JYSK, GBM, DIFARE Group, and Plastilene Group as customers. IBM's announcement claims like-for-like Power to Power migration can cut the infrastructure move to about 90 days; treat that as a vendor claim and verify regions and eligibility with IBM.
Do we have to leave IBM Power to get to S/4HANA?
No. S/4HANA requires HANA, and HANA is certified on Power under Linux: SAP Note 2188482 covers Power8 through Power11 with PowerVM, workload-based sizing from Power9 onward, LPARs up to 32 TB on high-end systems, and up to 16 production HANA LPARs on a Power10 E1080. You can run S/4HANA on Power on premises, on IBM Power Virtual Server (SAP-certified IaaS, Note 2947579), or as SAP Cloud ERP Private on PowerVS. What you cannot do is keep AIX as the HANA operating system.
What are the realistic options for an ECC on AIX shop in 2026?
Three paths. One: stay on ECC and AIX through 2027, or 2030 with extended maintenance, optionally lifting the AIX landscape to PowerVS or a managed Power hosting provider to exit the data center without replatforming. Two: convert to S/4HANA on Linux on Power, on premises or in PowerVS, keeping Power skills and consolidation economics. Three: replatform to an x86 hyperscaler on SAP-certified IaaS, a full heterogeneous migration and a bigger organizational change. On every path, an AIX Db2 or Oracle source goes through SAP migration tooling; database files never move directly.
Does endianness still block moving between Power and x86?
Mostly not anymore. HANA 1.0 on Power was big endian, but since HANA 2.0 every HANA system on x86 and Power is little endian, so HANA to HANA moves between the platforms no longer involve an endian conversion (SAP KBA 2554012 covers the legacy migration). The endian issue that still matters: AIX itself is big endian, so anything coming off AIX Db2 or Oracle is a heterogeneous migration through SAP tools regardless of target. Verify the supported system copy method for cross-platform HANA moves with SAP (Note 1642148 is the backup and recovery FAQ).
How much time does an S/4HANA move actually need?
Vendor claims of a 90 day migration (IBM's figure for like-for-like Power moves into RISE on PowerVS) cover the technical relocation, not the S/4HANA conversion program. Full brownfield conversions typically run 12 to 24 months including testing and change management, and IBM says its own internal migration took 18 months for more than 150,000 users; that is IBM's claim, attributed. As of this writing in August 2026, a shop targeting the end of 2027 needs to have started, and targeting 2030 extended maintenance leaves about one comfortable program cycle.
Sources
- SAP Support Portal: Maintenance strategy for SAP S/4HANA and SAP Business Suite 7 (2027/2030 dates)
- SAP Community (official): Maintenance Timelines for SAP ERP 6.0, including EHP0 to 5 end dates
- SAP News Center: SAP ERP, private edition, transition option (February 2025)
- IBM Newsroom: RISE with SAP on IBM Power Virtual Server announcement (January 7, 2025)
- SAP News Center: SAP and IBM client momentum for SAP Cloud ERP Private on PowerVS (July 2, 2026)
- SAP Learning: SAP HANA supported operating systems (Linux only, SLES and RHEL)
- SAP KBA 2554012: FAQ, SAP HANA big endian to little endian migration for IBM Power
- IBM Cloud documentation source: SAP on Power Virtual Server considerations (NetWeaver on AIX, HANA on Linux)
- SAP Support Portal: Database Migration Option (DMO) of Software Update Manager, including DMO with System Move
- IBM: SAP HANA on IBM Power product page (points to SAP Note 2188482 and the hardware directory)
- SAP Certified and Supported SAP HANA Hardware Directory
- hanaonpower.com: Power11 E1180 SAP certification for on-premises deployment published (November 2025)
Two Clocks Are Running on Your SAP Estate
Get an independent, directional read on whether running out ECC, converting on Power, or replatforming to x86 fits your landscape, before a vendor timeline decides for you.