A Power11 hardware refresh almost always touches IBM i licensing in some way. Understanding what can change, and what to verify before you commit to a configuration, avoids surprises after the quote is signed.
Software tier and processor group
IBM i licensing is tied to a software tier and processor group, both of which can change with a new Power11 configuration. Moving to a different core count or system class can shift your licensing tier, which affects both hardware and ongoing software cost. Confirm this early, not after a configuration is finalized.
OS version compatibility
Before migrating, confirm that your current IBM i version is supported on Power11 hardware, and that any third-party applications or ISV software you depend on are certified for your target IBM i release. A hardware refresh is the natural point to also plan an IBM i version upgrade if you are running an older release.
Third-party and custom application review
RPG, COBOL, CL, and DB2-based applications generally carry forward cleanly across IBM i versions, but any third-party software, custom modifications, or older APIs should be checked against your target OS version before cutover. This is one of the most commonly underestimated steps in an IBM i migration.
AIX and Linux licensing
If your Power11 system will also run AIX or Linux partitions alongside IBM i, review entitlements and subscription terms for each OS separately, since licensing models differ by operating system.