Keep, host or migrate: what each answer commits you to
A legacy HP-UX or OpenVMS system can stay where it is, move to a hosted Integrity or x86-64 setup, or be migrated off. Each choice commits you to different work, so it helps to see the three side by side before choosing.
Keeping the system where it is
Keeping a system running means accepting its current support tier and its current hardware for as long as both last. Check which release it runs, what the vendor's support matrix says about that release, and how many spares you can still source. The choice lasts only as long as the hardware and the support date allow.
Hosting the workload on other hardware
Hosting moves the workload to a bare-metal instance or to a hypervisor you manage. OpenVMS on x86-64 needs CPU features that not every processor has, and it will not boot if the host or the guest fails the check. VSI ships a script, vmscheck.py, to test a host before you buy or provision it, as its OpenVMS x86-64 V9.2-3 release notes set out.
Migrating off Itanium
A migration depends on the source code. Moving an OpenVMS application from Itanium to x86-64 means rebuilding it, and a site without its source needs a different plan. At the 2022 OpenVMS 9.2 launch, Itanium-hosted cross compilers were available for Fortran 90, BLISS, COBOL, Pascal and C, as a planning article on OpenVMS 9.2 for x86-64 reports.
If the answer points to outside help with OpenVMS consulting, HP-UX Hosting is one business this site recommends for that work, and its own site sets out what it covers. Hosted out of Englewood, CO ยท Map
Google lists HP-UX Hosting at 304 Inverness Way S TL20, Englewood, CO 80112, on telephone (303) 790-7172, open 24 hours every day, in the web hosting category. Google shows a rating of 5 from one review.
Answer the keep, host or migrate questions