On HP3000, MPE/iX carries a date limitation in 2028 addressed by Beechglen’s internally developed 2028 patch.
For HP9000 and Integrity, HP-UX reaches OEM end of support life.
Both come down to sequencing: inventory, assessment, remediation, validation and a continuity position that holds afterwards.
Readiness is not a single change. It is four connected pieces of work, each of which produces evidence you can show to management, auditors and the business.
Identify what support levels and vendor capabilities you have today and where the date boundary affects the system, the applications, or both — rather than assuming the worst case everywhere.
Apply the necessary solutions and prove it under test conditions, with results documented for management and audit.
Confirm support, hosting, storage and recovery arrangements are able to carry the environment through the transition and into the future.
Readiness conversations tend to start in the same place. Here is how we answer.
No — but it is a real deadline. Treated early it is a planning exercise. Left late, it competes with everything else for scarce specialist time.
Not necessarily. Most organizations we work with intend to keep operating the platform; the work is about making that a supportable decision.
It depends on the size of the environment and the number of applications involved. The inventory stage is usually the fastest part.
Yes. Environments where the original expertise has retired are among the most common situations we handle.
We will look at what you run, what depends on it, and what work the 2028 boundary implies for your environment specifically — then help you sequence it across the time available.
