Moving from HPE or another non-IBM system?
Start with the OS and workload when the source is HP-UX, Solaris, Windows or x86 Linux. Find the application build, database conversion and recovery work before choosing a Power server.
| Starting point | Read next |
|---|---|
| HPE and other non-IBM conversion | Choose the source OS and workload. |
| Application and database conversion | Find the Oracle, SAP, database or application guide. |
| Conversion assessment and cutover | Prove the target and the recovery plan before production. |
Choose the operating system you run
Start with the platform and installed release, then choose the exact Power model. Each guide keeps OS changes separate from moving the workload.
IBM i migration by current model and release
Move the IBM i system you already run
A replacement server can skip processor generations when the release and recovery plan allow it. The current model guide identifies the hardware limit; the migration plan explains how the workload reaches an eligible destination.
| Current generation | What changes the plan | Model and release guide |
|---|---|---|
| Migration from Power 11 | The listed IBM i Power 11 models run 7.4, 7.5 and 7.6 at their required code levels. E1150 is outside the IBM i model list. L-model IBM i use is configuration-limited and must stay within its documented allocation. | Find the exact source model |
| Migration from Power 10 | Selected Power 10 models run IBM i 7.6 with the required firmware and fixes. The S1012 does not run IBM i 7.3. E1050 is outside this IBM i model list; its processor generation does not establish IBM i eligibility. | Find the exact source model |
| Migration from Power 9 | IBM i 7.5 runs on selected Power 9 models; IBM i 7.6 does not. IBM i 7.1 is a special offering on selected S922 and E980 systems, not a normal starting assumption for every Power 9 model. | Find the exact source model |
| Migration from Power 8 | IBM i 7.4 is the last release for the listed Power 8 IBM i models. IBM i 7.5 and 7.6 require later eligible hardware. The S812 starts at 7.2 and has its own native-I/O restrictions. | Find the exact source model |
| Migration from Power 7 | Power 7 and Power 7+ rack and tower models listed for IBM i stop at IBM i 7.3. BladeCenter PS and Flex compute-node exceptions stop at 7.2. IBM i 7.4 does not run on either generation. | Find the exact source model |
| Migration from Power 6 | IBM i 7.3 is not supported on Power 6 hardware. Selected Power 6 systems can run IBM i 7.2, which is a technical release ceiling rather than a statement that normal support is still available. | Find the exact source model |
| Migration from Power 5 | IBM i 7.2 does not run on Power 5 or Power 5+ hardware. A move beyond IBM i 7.1 therefore needs replacement hardware as well as a supported software migration sequence. | Find the exact source model |
The installed IBM i release decides the software work
A source on a release the new server supports may allow a common-release move. An older source can require an OS step, an intermediate system or a documented previous-release recovery procedure. Select the actual release rather than estimating it from the server age.
| Installed release | Planning focus |
|---|---|
| IBM i 7.6 | Keep fixes and application support current; check required code before a hardware move. |
| IBM i 7.5 | Compare remaining capacity on eligible hardware with a 7.6 plan that may need a replacement. |
| IBM i 7.4 | Selected Power 8 through Power 11 hardware can run it; later OS releases need eligible newer hardware. |
| IBM i 7.3 | Check a supported release step before selecting a Power 11 destination. |
| IBM i 7.2 | Separate the rack-system release ceiling from blade and Flex restrictions. |
| IBM i 7.1 | Check old program objects, installed products and any special hardware offering. |
| IBM i 6.1 / i5/OS V5R4 and earlier | Plan older release preparation and recovery media before assuming a current server can accept the save. |
Choose the IBM i migration approach
| Approach | When to consider it | Read next |
|---|---|---|
| Save and restore | A tested restore fits the permitted outage and the source/target release procedure. | Rehearse a full recovery |
| Replication-assisted migration | The final outage must be shorter than the initial data copy. | Check covered objects and synchronization |
| Live partition mobility | The exact virtual-I/O, storage, processor and software configuration qualifies. | Check mobility prerequisites |
| Staged legacy migration | The source release and destination hardware do not overlap. | Check the release sequence |
What a complete IBM i move needs
- An inventory of the current system that identifies applications and every partition.
- A sized and licensed destination with compatible storage and I/O.
- A rehearsal with business acceptance checks and measured save/restore timings.
- A cutover and rollback decision that accounts for new business transactions.
An IBM i OS upgrade on the same server is a different starting task. Compare IBM i upgrade choices if you are deciding whether to keep the hardware.
For another-platform conversion, use the HPE and non-IBM migration guides to assess the current OS, application and database.
Sources and compatibility checks
Technical guidance checked October 21, 2026. A hardware release mapping describes which releases can run; support coverage and software entitlement are separate checks.