Home » Articles

IBM i/AS400 Services After 7.4 End of Support: Renew the Status Quo or Decide?

Last updated : October 05, 2026

A regional distributor runs its order management, warehouse, and financial systems on IBM i 7.4 on a Power9 server. Its IT team has four people, two of whom plan to retire within three years. In September 2026, the managed services provider sends a renewal proposal: another year of support at a higher price, plus a Service Extension fee for IBM i 7.4. The proposal says nothing about upgrading. The CIO signs it because it is the easiest path. A year later, the same proposal arrives, with a higher Service Extension fee, an older server, and fewer people who know the system.

This is how a support deadline turns into a slow drift. IBM i 7.4's move to Service Extension is not an emergency. Systems keep running, and support remains available for a price. But the extension fee buys time, not progress. IBM i/AS400 services that simply renew the status quo leave organizations paying more each year to postpone a decision that gets harder with every delay. The better approach is to use the extension as a bridge to a dated upgrade plan.

What Happens After IBM i 7.4 End of Support?  

IBM announced in September 2025 that IBM i 7.4 would move from standard support to Service Extension. According to IBM's withdrawal and service change announcement, marketing of IBM i 7.4 was withdrawn on April 30, 2026, and the change in service level takes effect on September 30, 2026. Service Extension for 7.4 is available until September 30, 2029.

Service Extension is a paid offering. It typically costs significantly more than standard software maintenance and provides a narrower scope of support, focused on defect support and known fixes rather than new function. Organizations on 7.4 can keep running and keep receiving help, but at a rising cost and with diminishing investment from IBM in that release.

The current supported releases are IBM i 7.5 and IBM i 7.6. IBM i 7.6 runs on Power10 and Power11 systems.

Can You Upgrade IBM i 7.4 on Power9?  

No. IBM's Power9 maintenance notice announced End of Standard Service for several Power9 models, including the S914, S922, and S924, effective January 31, 2026. After that date, IBM no longer provides preventive service, new updates or fixes, or new machine code updates, patches, or fixes, including security fixes. IBM offers a Hardware Support Extension for customers who need more time.

For many organizations, the operating system and hardware decisions are linked. Upgrading to IBM i 7.6 means moving to Power10 or Power11. Staying on Power9 limits OS options. Treating the two separately often leads to paying extension fees on both.

Is IBM i 7.4 Service Extension Worth the Cost?

Yes, IBM i 7.4 Service Extension has legitimate uses. It gives organizations time to complete upgrades that are already planned, to coordinate with vendor software support, or to align hardware refresh with budget cycles. Used that way, it is a sensible bridge.

The problem arises when extension becomes the default:

• Costs rise each year while the underlying platform ages.
• Vendor software support may lag as application providers certify newer releases and drop older ones.
• Skills erode as experienced staff retire, making later upgrades harder.
• Moving beyond standard support can narrow the support and update options available for the release, making lifecycle planning increasingly important.
• Upgrade complexity increases when multiple releases or hardware generations must be crossed later.

Every year of deferral can increase migration risk and cost as hardware ages, dependencies accumulate, and experienced staff leave.

How Does the IBM i Skills Shortage Affect an Upgrade?

IBM i skills are now the leading concern for IBM i organizations. Fortra's 2026 IBM i Marketplace Survey found that 69% of respondents named IBM i skills as a top concern, displacing cybersecurity from first place for the first time in nine years. Application modernization was cited by 62%.

Skills shortages make deferral riskier. Upgrades require people who understand the system, its applications, and its integrations. Organizations that wait may find fewer internal experts available when the upgrade finally happens.

What Should an IBM i 7.4 Upgrade Plan Include?

IBM i services should replace open-ended renewal with a plan that has dates and owners:

Assessment

Inventory hardware, OS release, licensed programs, third-party software, applications, integrations, high availability, and backup configurations. Identify dependencies that constrain the upgrade.

Target Decision

Choose between IBM i 7.5 and 7.6, and between Power10 and Power11 hardware, on-premises or in the cloud. Consider application vendor certifications and future support timelines.

Vendor Coordination

Confirm that third-party applications and tools are supported on the target release.

Test Environment

Build a test partition on the target release and run application testing, including batch jobs, integrations, and performance.

Hardware Plan

Size and procure new Power hardware or cloud capacity, with migration and high availability plans.

Cutover Schedule

Set a firm date for production cutover, with rollback options and support coverage.

Extension Scope

Use Service Extension only for the period needed to complete the plan, with an exit date written into the contract.

What Should IBM i/AS400 Managed Services Include After 7.4?

IBM i/AS400 managed services contracts often focus on uptime, monitoring, backups, and incident response. Those remain important, but a contract signed around a support deadline should also include:

• A lifecycle roadmap for OS and hardware, with dates.
• Upgrade planning and execution as defined deliverables, not optional extras.
• Vendor coordination for third-party software certifications.
• Knowledge documentation so the client understands its own systems.
• Reporting on release currency, patch levels, and hardware support status.
• Clear pricing for extension periods and upgrade projects.

Managed services providers benefit from stable, current platforms too. A system on supported releases is easier to maintain and less likely to generate emergencies.

Is It Cost-Effective to Upgrade IBM i 7.4 or Use Service Extension?

Yes, a simple comparison often changes the conversation. On one side sits the cumulative cost of Service Extension for 7.4, hardware support extensions for Power9, rising managed services fees, and the growing cost of emergency work on an aging platform. On the other sits the one-time cost of an upgrade project, new hardware or cloud capacity, and a period of parallel running.

When these figures are laid out over three years, the upgrade frequently costs less than continued extension, especially once hardware support and staff time are included. Even when the numbers are close, the upgrade leaves the organization on a platform with years of standard support ahead, while extension leaves it facing the same decision again with fewer options.

Finance teams also value predictability. A dated plan with a fixed project budget and a known end to extension fees is easier to approve than an open-ended series of annual premiums. Providers of IBM iSeries services can help by presenting both scenarios side by side, with assumptions stated clearly.

What Do Good iSeries Managed Services Look Like After the Upgrade?

The upgrade is not the end of the relationship. Strong iSeries managed services after a move to a current release include regular technology refresh planning, quarterly review of PTF and group PTF levels, security configuration reviews, capacity monitoring, and tested high availability and recovery procedures. They also include a standing plan for the next release, so the organization never again reaches a support deadline without a path.

For many companies, the right model combines IBM AS400 services from an external provider with a small internal team that owns business knowledge. The provider handles platform operations and upgrades, while internal staff focus on applications and business priorities. Clear documentation, shared runbooks, and defined responsibilities make that split work.

Can You Upgrade IBM i 7.4 Without Buying New Power Hardware?  

Organizations that do not want to buy new Power hardware have options. IBM Power Virtual Server and other Power cloud offerings let companies run IBM i on current hardware without owning it. Moving to the cloud can coincide with the OS upgrade, combining two projects into one.

Cloud options still require planning: network connectivity, latency for integrated systems, backup and recovery design, licensing, and cost modeling. For small IT teams, reduced hardware management can be a significant benefit.

When Does Staying on IBM i 7.4 Makes Sense?

Some situations justify a period on Service Extension:

• A major application upgrade or replacement is scheduled within the extension period.
• Vendor software is not yet certified on the target release.
• Hardware procurement is underway but not yet complete.
• A merger or divestiture makes platform decisions premature.

In each case, the extension should have a defined end date tied to the event it is waiting for. Extension without a trigger is simply deferral.

What Are the Security and Compliance Risks of Staying on IBM i 7.4?

Running software beyond standard support can create additional compliance and audit questions, depending on the organization's industry, regulatory obligations, and internal security policies. Systems on extended support can still meet those expectations, but documentation matters. Organizations should be able to show why they are on an older release, what compensating controls are in place, and when they will move. A dated upgrade plan provides that evidence. An open-ended renewal does not.

What Should You Ask an IBM i Services Provider Before Upgrading?

When reviewing IBM i services proposals around the 7.4 deadline, organizations can ask:

• What is the recommended target release and hardware, and why?
• What is the upgrade timeline, and what are the key milestones?
• How long will Service Extension be needed, and what will it cost each year?
• How will third-party software be validated on the target release?
• What knowledge documentation will be delivered?
• How will high availability and backup be handled during migration?

A provider that proposes only renewal, with no roadmap, may be optimizing for continuity of its own contract rather than the client's platform.

Return to the regional distributor. Instead of signing a simple renewal, the CIO asks the provider for a dated plan. The provider recommends moving to IBM i 7.6 on Power11 capacity in a Power cloud service, with a test partition within three months, vendor certifications confirmed within four, and production cutover within nine. Service Extension for 7.4 covers the period until cutover, with an explicit end date. The provider also documents key applications and integrations as part of the project, reducing dependence on the retiring staff.

The company pays extension fees for less than a year instead of indefinitely, moves to current hardware and software, and gains documentation it lacked.

IBM i/AS400 services after 7.4 end of support should be scoped around a decision, not a renewal. Service Extension is a useful bridge, but its fee is the price of deferral, and that price grows each year alongside hardware, skills, and security risk. Professional IBM i services cover assessments, upgrades, managed services, and cloud migration for IBM i environments. Before the next renewal is signed, it is worth asking what date the plan says the system will be current again.