Identify the HP-UX release and processor
Capture uname output, the installed software inventory and the server model. HP-UX 11i names alone do not tell a vendor which application binary or patch level you run. HPE distinguishes Integrity/Itanium from HP 9000/PA-RISC in its installation guidance.
| Source release | What Midland and the application vendor need |
|---|---|
| HP-UX 11i v1 | Exact release, PA-RISC model, patch inventory and working recovery media. |
| HP-UX 11i v2 | Exact B.11.23 level, processor architecture and installed application build. |
| HP-UX 11i v3 | B.11.31 update level, architecture and each application/database version. |
Older HP-UX applications need a recoverable starting point
For an older PA-RISC or Itanium installation, first establish that the business can still recover the source. Locate installation media, application source or vendor installers, database credentials and license records. A running production system is not a spare recovery copy.
If the application supplier cannot provide a maintained AIX or Power Linux build, assess a source-code port or replacement. Do that before selecting the target OS.
HP-UX 11i v3 still needs application conversion
Separate the HP-UX update level from the application release. A vendor may support the application on one AIX release and a different Linux distribution, or require an application upgrade first. Neither an Itanium binary nor a PA-RISC system image becomes a Power application by copying its disks.
Choose the HP-UX workload to move
| Workload | Required decision |
|---|---|
| Oracle Database | Qualify the Oracle target OS and choose a supported cross-platform data method. |
| SAP on HP-UX | Check the SAP application, database and target platform as one combination. |
| Custom C, C++ or UNIX applications | Locate source and build tools; replace OS-specific calls and libraries. |
| Java and middleware services | Qualify the runtime, application server, native modules and database drivers. |
Choose AIX or Linux for the application
AIX is a different UNIX environment; it is not an HP-UX compatibility mode. Power Linux is a different OS and processor build too. Let the supported application release determine the OS, then compare the eligible server models using the AIX release guide or Power Linux release guide.
Inventory Serviceguard or other cluster resources, LVM and filesystem layouts, startup scripts, backup agents, batch schedules and external interfaces. Recreate and test their required behavior on the target rather than importing the source configuration unchanged.
Prove the HP-UX replacement before cutover
Rehearse a business cycle with representative data: transaction entry, batch completion, reporting, backup and recovery. Compare the outputs and measured response times with the current HP-UX system. Include the external teams that exchange files or messages.
Plan the final transaction handover and rollback decision before setting the retirement date.
Plan the Power destination with Midland
Use the assessment to decide which workload belongs on Power before comparing hardware. Midland’s Power model catalog supplies the server identities; software eligibility and measured workload demand decide the configuration.
Prepare the conversion inventory and Bring your current OS, application and database versions to Midland.
Sources and release checks
Technical guidance checked October 21, 2026. Confirm the exact application edition, OS release and target architecture with its vendor before ordering. Older technical papers explain migration methods; they do not establish current certification.