A Washington, DC, organization contacted us about a significant infrastructure problem. They were running a 9406 520 server on V5R3. That version of IBM i predates most of the professionals currently managing these systems.

The hardware served them well, but it had been off active maintenance for years. The organization also had a tight timeline to transition to a new location.

Standard upgrade paths typically cost approximately $15,000 to complete safely. Conventional methods require stepping carefully through multiple intermediate operating system versions. Our team completed the migration seamlessly within 30 days for between $2,000 and $3,000.

When the Standard IBM System Upgrade Path Makes Sense

The standard IBM-prescribed upgrade path exists for good reason. Moving through each release incrementally reduces the risk of application errors surfacing after the jump. For organizations running Independent Software Vendor (ISV) software with complex dependencies, that measured approach is often the right call.

This Washington, DC, client was running custom RPG code. Our team had migrated environments at V5R3 before, pushing custom RPG applications directly into a V7.5 logical partition without stepping through the intermediate versions.

We knew from prior experience that this was a viable path. Our team also brought in a consultant to verify it live. For organizations with similar application profiles, the cost and timeline difference is substantial.

Executing the V5R3 Direct Jump to V7.5

Our IBM i upgrade bypassed the intermediate stepping the manufacturer prescribes through its multi-stage upgrade tooling. Rather than paying for consulting time, testing cycles, and licensing at each intermediate release, the team assessed the RPG codebase and confirmed direct portability. They then moved the environment into a right-sized Power9 logical partition.

Bob Losey has field experience spanning more than four decades of IBM i environments. That experience comes with pattern recognition that distinguishes a prescribed path from a practical one.

“We’ve migrated users at V5R3 and just pushed their applications, because they’re custom written, into a logical partition at V7.5. Normally, you’d go from V5 to V7.5 using a program IBM designed to upgrade the software every two steps, and that would cost about $15,000. We pushed them right across, had a consultant verify it worked, and the entire consulting cost was about $2,000 to $3,000. We got them cut across in 30 days.” – Bob Losey, Founder and President, Source Data Products

This is not a shortcut or a compromise you get from cutting corners. It is a more direct path to the same result made possible by extensive experience.

Evaluating Direct Transition Opportunities

This client transition was urgent, but the lesson applies to any IBM i shop running on an aging, out-of-maintenance system. The longer an organization delays an upgrade, the more the standard path appears to be the only path. But that isn’t always the case.

Whether a direct jump makes sense depends on several factors. You have to consider the nature of the application code, the ISV or custom origin of the software, and the version gap being crossed. These are not questions a generalist hosting provider can answer with confidence. They require someone who has watched that software behave across multiple OS generations and can read the risk accurately before committing to a plan.

For organizations running custom RPG on older releases, savings of $12,000 or more on an IBM i migration event are not unusual. You just need to get a transition team with the right expertise on the job. The real difference comes from asking the right question before the work begins.

Are you wondering whether this type of jump is possible for your system? Talk to the Source Data team to explore your strategic transition options.

Massive Optimization Benefits After Migration

The DC client’s old 9406 520 carried 8 gigabytes of memory and 300 gigabytes of storage, with only about 150 gigabytes in active use. We move them to a hosted Power9 Logical Partition (LPAR) with 1,300 CPW. While that’s the smallest available, it was more than sufficient for their workload.

We often see organizations carry more hardware capacity than their applications ever consume. That’s typically because IBM’s manufacturing economics push toward larger standard configurations. When a client migrates to a properly sized hosted LPAR, the new environment often performs comparably or better while costing a fraction as much. We covered this in a recent post comparing cloud hosting to on-premises hardware.

For an organization under the time pressure the DC client faced, the right-sized LPAR approach meant no capital outlay. They didn’t have to procure new hardware or wait for parts to ship. The result was a transition that took thirty days from start to finish.

Navigating IBM i Hardware Going Off Active Maintenance

Many organizations underestimate the impact of this until it’s too late. When IBM i hardware moves from active maintenance to extended maintenance, IBM outsources technical support to contractors. Those engineers lack IBM’s proprietary tools for relinking system boards to serial numbers. If a system board fails under extended maintenance, the system may be unrecoverable. The DC client was already in that window when they called.

Moving to a hosted LPAR eliminates that exposure. The physical infrastructure risk transfers to the hosting provider’s Tier III data center. Their new hosted infrastructure has redundant power and cooling standards that are maintained independently of any single hardware component.

For organizations in the same position, the migration decision is not just about cost or convenience. It is about whether the hardware can even survive long enough to complete an in-place upgrade.

Where to Start the IBM i Hosting Conversation

Most IBM i hosting conversations start with hardware specs. The provider asks how much CPW, how much memory, and how many terabytes. Those are reasonable questions, but they are not the right starting point.

The right place to start the conversation is with what the software actually needs. From there, you determine the fastest and most cost-efficient path to getting it running safely in a modern environment.

Organizations running older hardware with systems that have aged off active maintenance may have more options than they realize. Some of those options are considerably cheaper. Finding them requires someone who knows the software well enough to recognize when the conventional path is necessary and when it is not.

The Cloud400 disaster recovery platform provides mid-market organizations with a production-ready landing zone. It does this without forcing clients into an oversized, overpriced infrastructure decision.

Common Questions about Direct System Transitions

Can you really jump from V5R3 directly to V7.5 without stepping through every release?

In some cases, yes. When an environment runs custom RPG code rather than ISV software with complex dependencies, a direct IBM i version jump is sometimes viable. The key is verifying application compatibility before committing. A general infrastructure assessment isn’t enough. It requires a team with hands-on expertise in IBM i transitions.

Why does the standard IBM upgrade path cost so much more?

The standard prescribed process requires navigating intermediate versions using specialized tooling. Each step requires special IBM software and extensive consulting time. On occasion, there can be special ISV licensing considerations. Organizations that use custom programming often bypass these expensive transitional requirements. Selecting properly optimized transition paths routinely saves organizations significant capital.

What factors determine whether a direct IBM i version jump is safe?

The first point to consider is code type. Custom RPG applications generally carry less migration risk than ISV software with undocumented dependencies. The version gap also matters. An experienced IBM i engineer will assess both and give a clear go or no-go before any work begins. We touched on some of these issues in a recent post about how transfer fees can influence transitions.

What is a logical partition (LPAR), and why does it affect migration cost?

A Logical Partition (LPAR) is a virtualized slice of a physical Power server. In a hosted environment, the provider allocates CPW, memory, and storage to an individual client. The resources match what a workload actually consumes. For migration scenarios like the DC case, an LPAR can be provisioned and ready in days, eliminating hardware procurement delays.

How long does a typical IBM i cloud migration actually take?

The DC case took 30 days, and the job was done under real pressure. Migration timelines vary based on environment complexity, application count, and testing requirements. Straightforward custom RPG environments on older releases often move faster than organizations expect once the right approach is confirmed. Environments with unusual customizations, multiple LPARs, or ISV software dependencies may require additional assessment time.

What should I look for in an IBM i hosting provider’s data center?

Look for Tier III and SOC 2 Type II certification, and documented uptime of at least 99.999%. Tier III facilities utilize fully redundant power and cooling paths to guarantee continuous system availability and peace of mind. SOC 2 Type II means an independent auditor has reviewed the controls governing your data environment. Many providers claim these credentials but cannot produce the attestation documentation on request.

Does moving to hosted IBM i affect SOC 2 or audit obligations?

It depends on how the audit scope is structured. A reputable hosting provider with SOC 2 Type II certification can simplify your audit posture by providing pre-packaged evidence of control effectiveness for infrastructure-layer controls. The key is confirming which controls fall within the provider’s attestation scope and which remain your organization’s responsibility. Compliance and risk managers should request the attestation document and review the scope before the audit cycle begins.

Your Organization Might Have a More Direct Upgrade Path

Many organizations running older hardware have more than one path available for upgrading. Standard processes often include steps that some systems do not require. An expert assessment prevents unnecessary work and expense.

Source Data reviews application structure, version gaps, and system behavior before recommending any path. That approach reduces cost without increasing risk. Connect with the team to evaluate your upgrade options.

Bob Losey is the founder and president of Source Data Products. He has held Premier IBM Business Partner status continuously since 1992 and served as President of the Association of Service and Computer Dealers International (ASCDI).