Legacy evidence

Power 5 Legacy Decision Record

Identify what still exists, separate a short maintenance bridge from a recovery gamble, and document the evidence needed for a Power 5 migration decision.

Is this a bridge, a recovery project, or a migration?

Power 5 is no longer a normal hardware buying decision. The useful work is identifying the box, proving recoverability, and deciding how much temporary risk the business is accepting.

How the result is produced: Hardware identity, backup restoration evidence, parts coverage, and application constraints drive the result. A missing recovery test outweighs a preference to keep the system unchanged.
Limit: This tool cannot establish application compatibility or a supported upgrade sequence without the exact IBM i release, licensed programs, database dependencies, device inventory, and target system.

What successful and failed upgrades teach

A successful legacy migration is not just a target model and a completed cutover. The reusable evidence is what was installed, which dependencies were missed, what failed in rehearsal, what changed, how rollback worked, and whether the restored workload behaved correctly.

This page is intentionally a decision record. It does not convert incomplete evidence into false certainty.