For years, IBM i modernization has been one of the most discussed topics across the IBM i/AS400 community. Large enterprises rely on IBM i to power critical operations, yet in recent years, many are simultaneously exploring ways to improve user experience, integrate with modern technologies, support mobile workforces, and prepare for the next generation of IT professionals.
Recently, our team hosted a panel discussion featuring contributors to IBM’s latest IBM i Modernization Redbook, Modernizing IBM i Applications, published July 10th of 2026. The discussion featured perspectives from Mike Pavlak, Khushi Wadhwa, and Vikas Sonwal, all contributors to the Redbook and active members of the IBM i community. This article breaks down each of their perspectives as developers, architects, and thought leaders, touching on the practical aspects of IBM i modernization and strategy while sharing their projections on what the platform will look like in the future.
While the conversation covered a wide range of topics, we’ll cover several of the key themes that emerged throughout the webinar.
Modernization Is About Extension, Not Replacement
One of the strongest messages from the discussion was that modernization does not necessarily mean moving away from IBM i.
Many organizations hear the term “modernization” and immediately assume it requires a complete platform migration, application rewrite, or costly rehosting initiative. According to the panelists, the most successful modernization efforts often take a very different approach.
As Programmers.io IBM i developer and Redbook contributor Khushi Wadhwa explained, businesses can continue building on IBM i through web applications, external integrations, and AI-assisted development without replacing the systems they have relied on for years. The goal is to meet evolving business and user expectations while preserving the strengths of the existing platform.
As several of our panelists noted, people still often underestimate the IBM i. As a platform that has stood for decades, it is often perceived as something not as “advanced” as the other platforms we see on the market today. IBM Champion Mike Pavlak emphasized the importance of looking beyond that perception and truly trying to understand what IBM i can do:
“I really like the idea of helping IBMi clients understand the possibilities. There’s a perspective that the IBMi isn’t as cool or isn’t as advanced as a Linux or a Windows environment … Let’s just see what this thing can do before you start thinking about moving away.”
Three Forces Driving Modernization Efforts
What businesses need from their systems today looks very different from what they needed a decade ago. If modernization is about building on existing IBM i systems rather than replacing them, the next question is: what’s driving the need for change?
The panel identified the three key forces shaping modernization efforts as changing customer expectations, evolving user needs, and a changing workforce.
1. Changing Customer Expectations
Today’s business applications rarely operate in isolation. Customers, partners, suppliers, and SaaS platforms expect systems to exchange information in real time.
Organizations increasingly require integration between IBM i applications and external platforms. Technologies such as REST APIs and other modern integration tools have become essential for enabling this exchange.
Khushi Wadhwa shared an example of a project involving a logistics company, where her team integrated an existing IBM i application with an external system using REST APIs. The integration streamlined customer creation, invoice generation, and billing, reducing manual touchpoints while improving consistency across these processes.
2. Evolving User Expectations
Users now expect intuitive, responsive, and mobile-friendly experiences.
As Technical Architect Vikas Sonwal discussed elsewhere in the panel, this doesn’t mean every user needs to abandon familiar tools. In one project, his team maintained the existing green-screen interface for experienced employees who could process orders more efficiently with it, while introducing a modern or mobile-friendly interface for users who needed a different experience.
The takeaway is that modernization should account for how people actually work. A successful approach gives users the tools that best support their needs rather than forcing everyone into the same interface.
3. Workforce Transformation
Many experienced IBM i professionals are approaching retirement, creating both challenges and opportunities.
The panel noted that new generations of developers often expect tools such as Visual Studio Code, Git, DevOps workflows, and AI-assisted development. Modernization initiatives increasingly include the adoption of these practices to make IBM i development environments more attractive and accessible to new talent.
Common Modernization Misconceptions
The webinar also tackled several misconceptions that continue to shape conversations around IBM i.
Myth #1: Modernization Means Leaving IBM i
The panelists repeatedly emphasized that modernization and migration are not synonymous. As we touched on earlier, many successful initiatives take the approach to extend existing systems with new capabilities.
Khushi shared an example of using IBM Integrated Web Services (IWS) to expose an existing RPG program or service program as a web service, which allows modern applications to access established business logic through web services without necessarily rewriting the original code.
She also described a project in which a client wanted customers to receive notifications as soon as their orders shipped. Her team triggered SMS notifications through an external messaging API and sent the same information by email, all from IBM i—no middleware or replatforming required.
Myth #2: Modernization Is Just a User Interface Refresh
Modern user interfaces can certainly improve adoption and productivity, but true modernization extends much further.
The discussion highlighted automation, integration, security enhancements, API enablement, DevOps processes, deployment practices, and data accessibility as equally important components of modernization initiatives.
Myth #3: AI Can Automatically Modernize Applications
Artificial intelligence is creating exciting opportunities for IBM i teams, but the panel cautioned against viewing AI as a one-click modernization solution.
AI can assist with code analysis, documentation, development acceleration, and design recommendations. However, business knowledge, system architecture expertise, governance, and human oversight remain essential components of any modernization effort. Teams still need a clear understanding of existing business logic and the expertise to make sound architectural decisions.
As Khushi put it, “AI is an accelerator to modernization, but it is not an autopilot.”
APIs Are Becoming the Bridge to Modern Experiences
Another major takeaway from the discussion was the growing importance of APIs in modern development.
As Vikas Sonwal explained, IBM i doesn’t limit organizations to a particular front-end technology. Secure REST APIs allow developers to build experiences with frameworks such as React, Angular, and Flutter while continuing to leverage existing investments in RPG, COBOL, and Db2-based applications.
Whether organizations are building web applications, mobile apps, customer portals, AI integrations, or cloud-connected services, APIs frequently serve as the foundation connecting modern experiences to existing IBM i business logic.
AI’s Growing Role in IBM i Development
Artificial intelligence was another topic that generated significant discussion. The panelists described several use cases in detail that are providing value today such as, analyzing and understanding legacy applications, generating documentation, improving knowledge transfer between teams, and of course, boosting productivity.
However, the panelists also stressed the importance of human oversight and governance. As Vikas emphasized, “A human review is always needed,” especially when working with business-critical logic that has operated reliably for years. Before allowing AI tools to have broader interaction with sensitive data, organizations should clearly define what information AI systems can access, and begin with lower-risk use cases.
Why the Future of IBM i Remains Strong
Perhaps the most encouraging aspect of the discussion was the optimism surrounding IBM i’s future.
The panel pointed to several reasons for continued confidence:
- IBM continues to deliver regular technology enhancements and updates
- The platform has an expanding ecosystem of APIs, open-source technologies, and modern development tools
- The IBM i community demonstrates strong participation and knowledge sharing
- Mentorship efforts to develop future talent are growing
- Enterprises continue to rely on IBM i for mission-critical workloads
The contributors also highlighted one of the platform’s greatest strengths: its community. The Modernization Redbook itself was created through extensive collaboration between IBM experts and community members who volunteered their time and expertise to help fellow IBM i professionals navigate modernization journeys.
Mike Pavlak, who contributed extensively to the Redbook’s open-source content, offered another perspective. He hopes readers come away with a greater appreciation for the range of capabilities available on IBM i today, from modern interfaces and APIs to open-source development tools. He described the Redbook as a practical resource for organizations looking to explore those capabilities and begin experimenting.
Final Thoughts
Modernization means something different for every organization. For some, it may involve API enablement and integration. For others, it may focus on mobile access, AI adoption, DevOps practices, or user experience improvements.
What remains consistent is that modernization no longer requires organizations to choose between innovation and stability.
As the authors of the IBM i Modernization Redbook emphasized throughout the discussion, many of today’s most successful initiatives build upon the strengths of IBM i rather than replacing them. By extending trusted applications with modern technologies, organizations can continue delivering business value while preparing for the future.
Want to hear more from the panel? Watch the full discussion on our YouTube channel.
For support with an upcoming IBM i/AS400 modernization project, talk to an expert today.
