Plain-English guidance on moving Power to the cloud

Why IBM Power is moving to the cloud

For decades, AIX and IBM i ran on Power servers sitting in the corner of the data center — reliable, but tied to a hardware refresh cycle and a shrinking pool of specialist skills. Two forces are now pushing those workloads toward the cloud: aging Power8 and Power9 fleets reaching end of support, and IBM's own expansion of Power Virtual Server as a first-class cloud destination.

What changed

Power Virtual Server made it possible to run AIX, IBM i, and Linux on Power as a cloud service, billed by consumption, in IBM data centers worldwide. Partner-hosted Power clouds and Skytap on Azure followed. For the first time, leaving your own Power hardware no longer means leaving the platform — or rewriting the applications that depend on it.

What's pushing teams to act now

• Power8 and older systems past or nearing end of service support
• Capital cost and lead times of a like-for-like hardware refresh
• A retiring generation of AIX and IBM i administrators
• Data-center consolidation and exit mandates from the business
• Pressure to put DR and resilience on a modern footing

AIX, IBM i, and Linux on Power — what runs where

The three operating systems on Power have very different migration profiles. AIX and IBM i are proprietary to Power, so the realistic cloud options keep them on Power hardware. Linux on Power is more portable — it can stay on Power or be replatformed to x86. Knowing which OS you're moving is the first fork in the decision.

Destination support by operating system

The quick read

• AIX — stays on Power; lift-and-shift to cloud Power, or a high-effort replatform to Linux to exit
• IBM i — stays on Power; cloud-host as-is, optionally modernizing the front-end
• Linux on Power — the portable one; keep on Power or move to x86/cloud Linux

Power hardware end-of-life and refresh pressure

As Power servers pass end of service support, IBM stops providing hardware maintenance and firmware updates for them. Running production on unsupported Power hardware carries the same risks as any end-of-life infrastructure — and because Power systems tend to host the most critical, hardest-to-move workloads, the stakes are higher.

Generations and support status

Eras are approximate and for planning orientation — confirm the exact end-of-service date for your specific models in your assessment.

What end of service means for Power

• No IBM hardware maintenance or firmware fixes
• Spare-parts availability tightens and lead times grow
• Newer AIX / IBM i releases may not be supported on the hardware
• Compliance and cyber-insurance exposure on unsupported systems
• A single hardware failure can become a business-critical outage

Cloud Power vs. on-prem refresh: which is right?

An on-prem Power10 refresh keeps everything in your control but means fresh capital outlay and another hardware lifecycle to own. Cloud Power (PowerVS, Skytap, partner-hosted) removes the hardware burden and shifts to consumption billing, but ongoing cost discipline becomes essential. The right answer depends on your refresh timing, team, and DR strategy.

Many teams land on a hybrid: production on cloud Power, or production on-prem with cloud-Power DR. We model both against your numbers rather than defaulting to either.

What does an IBM Power migration cost?

A lift-and-shift of a modest AIX/IBM i estate to cloud Power is largely a project-services and consumption cost. A replatform off Power is dominated by application engineering and testing. As with any migration, plan by component and on a three-year total cost of ownership — not the migration project alone.

Cost components by path

Hidden costs to budget for

• Network and private-connectivity setup into the cloud Power region
• Data migration and replication transfer for large databases
• IBM i and AIX software / ISV licensing portability checks
• Backup, HA, and DR reconfiguration on the new platform
• Specialist contractor augmentation for scarce skills

What a Power migration timeline looks like

A cloud-Power lift-and-shift typically runs 3–6 months from decision to cutover. An IBM i modernization or AIX-to-Linux replatform is a longer program — 9–18 months or more — because application work, not infrastructure, sets the pace.