The reason for taking a costly step like migration into the unknown, risking the organization's carefully tailored systems, workflows, and infrastructure, is often driven by management's fear of the platform's ability to adapt to future changes and integration needs, as well as the potential loss of knowledge and resources when aging IT personnel retire.

Follow our five-step plan and see how simple it can be to upgrade your old ERP into a modern, user-friendly system with a future-proof architecture - all while easing management's fears and doubts. 

1. Change the circumstances and regain crucial insights into the legacy system immediately. 

2. Change the perspective and migrate to the web from day one.

3. Change the approach and modernize the existing interface to support users better. 

4. Change the method by optimizing workflows and integrating other platforms to align with business demand and strategy. 

5. Change the mindset and transform to a service-based Architecture enforced by DevOps. 

View key point as presentation in this 4 min video

Most people would agree with this plan, but they would argue that it is easier said than done and would take many years to complete. Therefore, they would claim that it is not a feasible plan for an organization under daily pressure to modernize or shift to another platform. 

We have spent over 20 years developing tools to automate and streamline this process, achieving perfection and ensuring the organization sees visible results within the first few days.

We offer a comprehensive platform that utilizes existing programs and business logic to run faster and natively on IBM i. Our process delivers tangible results weekly. It can also be paused if the organization needs to focus on other activities for a shorter or longer period, without affecting the overall outcome. 

These five core modules handle the modernization and transformation:

1. Sitemule Blueprint - Provides visual clarity, multilingual documentation, and intelligent guidance

2. Sitemule Platform - Combines IBM i systems and modern applications into a single unified ecosystem.

3. Sitemule Workspace - Turn 5250 programs into intuitive applications and workflows or modern web services.

4. Sitemule Architect - Deploy domain-driven applications and microservices within minutes - no coding required.

5. Sitemule Enterprise - Bridge modern technologies with RPG and COBOL to run applications and web services natively on IBM i. 

Step 1.

Change the Circumstances with Sitemule Blueprint

It's commonly believed that IBM i modernization is impossible for systems that are largely undocumented and have evolved over decades through the work of multiple developers using different technologies, coding standards, and programming practices. Without comprehensive documentation, a deep understanding of the application landscape, and a highly skilled team, embarking on a transformation initiative can seem like an overwhelming - if not reckless - undertaking; therefore, many have given up or postponed the decision.

We want to challenge this belief and show how these very circumstances can be changed and even become an advantage throughout the whole transformation process, supporting our theory and assessing its effectiveness.

Modernizing an IBM i application is rarely about rewriting code. For most organizations, success depends on first understanding decades of accumulated business logic, hidden dependencies, and architectural decisions that were never documented. Many IBM i environments have evolved continuously for 30 or 40 years. They contain thousands of RPG and CL programs, database files, service programs, stored procedures, triggers, and interfaces that support critical business operations. While these systems remain reliable, their complexity often makes modernization expensive and risky.

This is where Sitemule Blueprint changes the equation. A common misconception is that modernization starts with converting RPG to another language or replacing green-screen applications with graphical interfaces. In practice, a successful transformation journey begins with understanding. Without reliable answers, transformation projects rely on assumptions rather than facts. System analysts and developers need answers to questions such as: Which applications use this business rule? What happens if this database field changes? Which interfaces depend on this program? Is this module still in use? Can this component safely be replaced? Which business processes will be affected?

"Modernizing an IBM i application is rarely about rewriting code. It begins with understanding decades of business logic that was never written down."

Sitemule Blueprint provides those answers by building a complete structural model of the IBM i application landscape. Instead of manually tracing code across thousands of objects, developers gain immediate visibility into relationships, dependencies, execution flows, and embedded business rules - as if the original system architect were available to explain exactly how the application works.

Blueprint is used continually throughout the transformation journey, delivering current documentation and recommendations to every step of the process. The result is a living architectural model that accurately reflects the current system rather than documentation written years ago. When optimizing workflows with Sitemule Workspace, Blueprint identifies core business applications, shared components, reusable services, obsolete code, high-risk dependencies, frequently used database objects, and cross-application relationships, allowing architects to identify modernization candidates based on objective analysis rather than assumptions.

Large IBM i environments cannot usually be modernized all at once. Blueprint helps divide complex systems into logical business domains by visualizing application boundaries and dependencies, revealing manageable modernization units that can be transformed with Sitemule Architect or Sitemule Enterprise into modern web applications. Many modernization projects also focus on exposing existing business logic through REST APIs. Before services can be created in Sitemule Architect and exposed, organizations need to understand which programs implement the required business functions, which files they update, which programs they call, and which side effects they trigger - visibility that Blueprint provides.

Complete application replacement is rarely practical. Most successful IBM i modernization initiatives follow an incremental approach where existing functionality is gradually improved while the business continues operating. Blueprint supports this strategy by allowing organizations to modernize one business area at a time, replace individual components safely, validate dependencies before deployment, document every architectural change, and reduce modernization risk throughout the project - enabling continuous transformation without disrupting daily operations.

Perhaps the greatest modernization risk is losing business knowledge rather than technical knowledge. Many critical business rules exist only within legacy source code or in the experience of long-serving developers. Blueprint extracts and documents these relationships, making business logic visible, searchable, and understandable across the organization, so every developer works from the same trusted architectural model instead of relying on tribal knowledge.

Sitemule Blueprint is also designed for the next generation of AI-assisted software engineering. Through support for the Model Context Protocol (MCP), Blueprint exposes its complete application graph - including programs, files, tables, stored procedures, triggers, and their relationships - to any generative AI assistant or agent, including IBM BOB, ChatGPT, Gemini, Claude, and Copilot. Rather than asking AI to interpret isolated source files, organizations can provide agents with a complete understanding of the application's architecture, enabling AI-assisted impact analysis, code exploration, documentation generation, modernization planning, and developer guidance based on accurate structural information instead of fragmented context. 

Summary

We changed the circumstances and proved that modernization succeeds even when starting from undocumented, decades-old IBM i systems. By replacing assumptions with facts, we addressed the core barrier to transformation: the absence of reliable knowledge about how applications actually work. Blueprint solved this by building a complete structural model of the application landscape, giving developers immediate visibility into relationships, dependencies, execution flows, and embedded business rules that would otherwise take years to uncover manually.

We tackled the risk of large-scale, all-at-once modernization by using Blueprint to divide complex systems into logical business domains, revealing manageable units that can be modernized independently with Sitemule Architect or Sitemule Enterprise. This same visibility enabled organizations to expose existing business logic safely through REST APIs, identifying service boundaries without unintentionally affecting unrelated processes.

We addressed the danger of disruptive, big-bang transformation by supporting an incremental approach - modernizing one business area at a time, validating dependencies before deployment, and documenting every architectural change, all without pausing daily operations. At the same time, we solved the deeper problem of vanishing business knowledge by extracting and documenting rules that previously existed only in source code or in the minds of long-serving developers, replacing tribal knowledge with a shared, trusted model.

Finally, we positioned the organization for the future by exposing Blueprint's complete application graph through the Model Context Protocol to any generative AI assistant or agent - whether IBM BOB, ChatGPT, Gemini, Claude, Copilot, or others - enabling AI-assisted impact analysis, code exploration, and modernization planning grounded in accurate structural information rather than fragmented guesswork. 

Through this first step, we showed that the foundation for the entire transformation journey can be established from any IBM i solution in a matter of hours - even when it initially seems impossible. Done in hours!

Step 2.

Change the perspective with the Sitemule Platform 

It's commonly believed that one of the main obstacles to modernization is the 5250 interface, which is why many are talking about a graphical interface as a universal solution. While the interface is limited and quite basic, the main problem is the lack of integration between the emulator and other platforms. Additionally, the 5250 sessions are restricted to functioning as standalone screens, with no ability to communicate with each other, requiring users to run multiple sessions simultaneously to work more efficiently.

We want to challenge this perspective and migrate the entire 5250 environment to the web on the first day, supporting our theory and assessing its effectiveness. While the emulator program has been an isolated area, the web browser has been the complete opposite, widely adopted as a standard for integrating modern applications and technologies.

We aim to integrate IBM i systems, third-party applications, and other modern web technologies into a unified, seamless browser environment, enabling users to access all resources from a single platform. 

After installing the Sitemule Platform, our first task is to synchronize it with the existing menu system in the 5250 interface. This allows the Sitemule Platform to display the full menu as a tree structure, complete with helpful icons and a search function, enabling users to work more quickly and intuitively. The original 5250 programs will open in tabs or windows, allowing users to experience the freedom and efficiency of a multitasking environment immediately. We haven't even modified the 5250 interface, yet the perspective has shifted. Every tab and window represents a separate session on IBM i, coexisting like individual Windows applications within a unified environment alongside other web and cloud systems solutions. 

"We haven't even modified the 5250 interface, yet the perspective has shifted. Every tab is a separate IBM i session, coexisting in one unified workspace."

Sitemule Platform runs natively on IBM i without external infrastructure or middleware, ensuring maximum stability, minimal risk, and full use of IBM i's built-in reliability and performance. This is made possible by the integrated engine, IceBreak, which provides the most powerful Web Server and Web Application Server directly on IBM i.

The IBM i authorization system remains unchanged, and users will continue to use the original authorization. Everything will stay the same - the menu system's content and the program's behavior - just from a different perspective. 

By integrating the IBM i Authorization and Security System with a detailed, role-based user directory in the Sitemule Platform, users from different platforms can be granted secure access while coexisting with IBM i users, thereby enhancing cross-platform collaboration. 

Sitemule Platform runs in any modern browser on Windows, macOS, or Linux and supports standard functions, such as downloading files from the IFS. We have developed a Client that enables tighter integration with the local machine, allowing applications to be part of IBM i managed workflows. The Sitemule Client offers a wide range of features, such as replacing ACS support for PCO on IBM i and sending IBM i Break Messages to the local computer's notification system.  

Summary

We changed the perspective and showed that modernization starts not by replacing IBM i applications, but by transforming how the system is accessed, integrated, and experienced. Instead of viewing the 5250 interface as the main obstacle, we demonstrated that the real issues stemmed from isolated emulator sessions, a lack of interoperability, and the inability to unify IBM i with other platforms. By moving the entire 5250 environment to the web on the very first day, we addressed these problems. We created a seamless, browser-based workspace that consolidates all IBM i resources and modern technologies into a single environment.

We addressed the fragmentation of traditional workflows by synchronizing the platform with the existing menu system and presenting it as an intuitive tree structure, with search, icons, and tabbed multitasking. This provided immediate efficiency improvements without changing any programs or screens. Users could run multiple sessions at the same time, switch tasks easily, and take advantage of modern navigation tools - all while interacting with the same trusted applications they use every day.

We solved the risk and complexity issues typically associated with modernization by ensuring the platform runs natively on IBM i, without the need for external servers or middleware. This maintained system stability, reduced implementation risks, and utilized IBM i's inherent performance through the IceBreak engine. We also preserved the existing IBM i security and authorization framework while enhancing it with role-based capabilities to enable secure access for users across different platforms.

We removed barriers to cross-platform accessibility by allowing the environment to run in any modern browser and by adding a dedicated client for better integration with the local machine. This enabled features such as file downloads, break message notifications, and IBM i managed workflows to work seamlessly across Windows, macOS, and Linux.

This change in perspective shows that modernization can start immediately by building a unified, web-based ecosystem that improves integration, usability, security, performance, and accessibility - delivered in days and achieved without adjusting existing business logic or infrastructure.

Done in days!

Step 3.

Change the Approach with Sitemule Workspace

After redefining the perspective in Step 2, the next phase focuses on changing how users interact with the system. Step 3 introduces Sitemule Workspace, designed to refactor and modernize the existing 5250 interface, improving usability, productivity, and integration - without altering the existing programs. This step ensures that users receive immediate benefits through a modern, intuitive interface while organizations maintain the reliability and security of IBM i.

Sitemule Workspace is delivered with eight different color themes and four predefined presentation modes:

• Flat - Provides a flat, one-to-one 5250 emulation on the web. 

• Flex - Displays screens with a proportional font for a more flexible appearance. 

• Flow - Converts subfiles into tables with right-click options. 

• Flip - Transforms the entire screen into a Windows-like interface. 

It's easy to develop new, customized presentation modes and modify existing ones using predefined keywords to match differences between systems. Prepare the ERP system for globalization with an intuitive feature that translates field labels, column headings, and other text into the user's native language, correcting any misleading text or labels. 

Sitemule Workspace intercepts the 5250 data stream at the core of IBM i and converts it from a character-based console format into structured JSON, making it ready for web-enabled applications. This innovative approach not only provides an immediate, one-to-one, web-enabled emulation that transforms how 5250 functions in a modern, multitasking environment but also opens up the rigid 5250 data stream for further interpretation and manipulation, offering new possibilities for the interface. 

So, Sitemule Workspace does not create new applications; it simply emulates existing 5250 programs as modern web applications and web services. Because of this, the setup in Sitemule Workspace will operate across the entire system. Similarly, changes to the traditional 5250 screens will be reflected in the new interface immediately. Over time, the Sitemule Workspace emulation will become progressively smarter, covering all screens and any modifications in content or program flow. 

"Sitemule Workspace does not create new applications. It emulates existing 5250 programs as modern web applications and web services."

The intelligent emulation program can improve operations by adding new features, including usability elements, and changing data within the 5250 data stream as it processes. Screen identifiers, field descriptions, field contents, or on-screen text can trigger these actions. After a screen is completed, it can also direct the user to another application, run a web service, or update a database. The emulation program is highly flexible and can be customized in RPG to handle any task through a wide range of specialized VTS commands. 

Instead of making individual conversions to full-screen, the emulator concentrates on enhancing functionality and usability for specific fields or field patterns throughout the system. By focusing on the most frequently used fields or patterns, the impact is evident within the first week. That is why Sitemule Workspace doesn't require modifications to existing programs to introduce a modern interface to an old 5250 system. 

The transformation occurs within weeks, providing a modern, user-friendly experience that meets today's standards for efficiency and collaboration. 

Users gain from a more innovative and efficient workflow. Structured navigation, tab-based multitasking, and improved visibility enable seamless task switching while maintaining complete control over complex operations. Data entry becomes quicker and more accurate with features such as SQL breakouts, type-ahead functionality, dropdown menus, checkboxes, and calendar fields. These improvements not only speed up input but also boost data integrity and help reduce user errors that have lasted for decades.

Business workflows are further optimized by orchestrating multiple 5250 screens into seamless processes that reflect current procedures. This enables the organization to expand and modify functionalities without rewriting programs. Sitemule Workspace also supports integration with Microsoft Office and other third-party applications, allowing you to manage documents, reports, and communications directly within the IBM i environment.

Sitemule Workspace brings the 5250 environment into a modern service-based architecture by rendering 5250 screens as RESTful web services, allowing other platforms to access data that requires sign-on, multiple menu options, and completion of one or more screens. In practice, these web services imitate user actions without showing the screens. However, if necessary, they can open a web-enabled screen in an iframe and prompt the user to enter and update data. 

Using the same methods, web services from other platforms can access data from a 5250 screen to retrieve time-sensitive information, transaction details, maps, or charts. 

Security remains central to the transformation. The IBM i authorization and role-based access control systems are fully preserved, ensuring that modernization never compromises governance or compliance. Enhanced validation mechanisms further reinforce data accuracy and system reliability.

Summary

We changed the approach and proved that modernization succeeds when the existing 5250 interface is upgraded to a smarter, more intuitive, and fully integrated environment without changing the underlying programs. By redesigning the user experience with intelligent web-based emulation, we fixed long-standing issues with usability, navigation, data entry, and workflow efficiency. We added customizable display modes, multilingual support, and modern design elements, which immediately improved user productivity and reduced errors.

We addressed the rigidity of the traditional 5250 data stream by converting it into structured JSON, enabling advanced interpretation, field-level improvements, and dynamic behavior. This enabled capabilities such as SQL breakouts, type-ahead input, real-time validation, and automated redirection to related applications or services - all system-wide, without changing any program logic. We also tackled the issue of fragmented workflows by coordinating multiple screens into integrated processes that mirror current business practices, while ensuring seamless integration with Microsoft Office, third-party applications, and external web services.

We further bridged the gap between legacy and modern architectures by rendering 5250 screens into RESTful web services, enabling secure, automated access to workflows that traditionally required manual navigation. At the same time, we preserved IBM i’s security model and improved data integrity by implementing stronger validation and controlling user interaction.

Through this approach, we demonstrated that meaningful modernization can be achieved rapidly by improving the interface, elevating usability, enabling integration, and streamlining workflows across the entire system. The result is a more efficient, connected, and user-centric environment - delivered in weeks and fully aligned with modern business expectations.

Done in weeks!

Step 4. Change the Method with Sitemule Architect

After transforming the user interface and workflows in the previous steps, the third phase concentrates on optimizing business processes and integrating platforms to align technology with strategic goals. Sitemule Architect introduces a new method - transforming rigid, legacy-based environments into flexible, domain-driven, service-oriented architectures that empower organizations to innovate more quickly and respond more dynamically to changing business demands.

This phase redefines how IBM i applications are designed, structured, and extended. Sitemule Architect analyzes existing Db2 databases to generate domain models that serve as the foundation for building modern, data-driven applications and microservices. These applications can be designed, customized, and deployed suggestively, establishing a robust, future-proof application framework without manual coding.

The modernization is now at a stage where the immediate issues have been solved. In step four, our focus will shift to the database. The database forms the foundation of the system. It is usually organized into hundreds of files (tables) within a single data library, a typical arrangement when the system was developed decades ago. It was also the era of large monolithic programs that could handle every aspect of a colossal task, such as production planning or order entry, in a single program. Although these programs are robust and reliable, they are very complex to modify or expand, which is likely the biggest challenge on the IBM i platform today. In step five, we will explore how to break down these monoliths into smaller microservices within a modern service architecture. 

The size of the data library and limited documentation can be overwhelming even for skilled developers. Restructuring the database will require significant resources and might affect all existing programs and procedures. However, by visualizing the database from a different perspective, we can modernize the system more easily without physically changing its structure. To do this, we will use domain segregation to divide the existing database into smaller domains.

Through its Model Studio, Sitemule Architect visualizes data modeling, application design, and deployment processes. Legacy Db2 structures can be easily imported and enhanced with metadata for relations, constraints, validations, and presentation logic. This process supports the domain-segregation method and will result in the definition of multiple domains. Since it is impossible to restructure the files, the domain segregation will not be a textbook example, but it will assist us later in the transformation process. 

However, Model Studio enables us to add new fields, validations, and data extensions smoothly - even without downtime or risking the existing environment. The outcome is a unified, consistent data layer that supports both structured and unstructured data through secure JSON-based extensions managed directly within Db2.

Let's explore the architecture of a typical 5250 program and identify common user complaints. Most programs include a single subfile, a few options, some function keys, and a couple of screens. Most complaints focus on the subfile. The subfile should provide users with a complete overview of the data, but 80-character-wide screens can't display all columns. Usually, users can only search on the key field and sometimes another field. Users want a view that lets them search, filter, group, and sort all columns. They also want to export data in various formats for use on their local PCs.

The Sitemule Architect provides exactly the overview and functionality in a grid that the traditional subfile lacks. It can also integrate options and screens from the 5250 program through Sitemule Workspace. To connect the options in the grid to different screens, we use a scripting method in Sitemule Workspace that simulates the user journey to the specific option or function, then pops up the emulated 5250 screen. By combining the Architect and Workspace, users will experience a modernized interface that reuses underlying business logic. 

Applications built with Sitemule Architect share a consistent interface and operation with those modernized in Sitemule Workspace or deployed via Sitemule Enterprise. Users can design their applications using intuitive components like grids, forms, and tree structures. These elements foster cohesive and interactive user experiences, while workflow logic can be visually defined and tailored to meet specific business needs.

Sitemule Architect's no-code approach bridges the gap between business and IT. It enables domain experts to participate directly in application design and process improvement without programming knowledge, thereby accelerating development cycles, reducing reliance on specialized resources, and strengthening collaboration across departments.

Beyond design and deployment, Sitemule Architect improves business intelligence by making complex data easy to understand and act upon. Users can model, filter, sort, and group data, and visualize it through dynamic charts and reports to support data-driven decisions and gain real-time insights.

By adopting this method, we changed how modernization is carried out - shifting from isolated system upgrades to a unified, domain-driven model that aligns data, logic, and workflows. We showed that modern applications can be developed rapidly, with complete control over IBM i data, while incorporating legacy programs as fully integrated components of a modern, service-oriented ecosystem.

Summary

We changed the method and demonstrated that modernization requires more than surface improvements; it requires a structured, domain-driven approach that unites data, logic, and workflows. By introducing Sitemule Architect, we tackled long-standing challenges like monolithic programs, undocumented databases, and complex Db2 structures that are hard to extend or maintain. Instead of reworking the entire database - which would be costly and disruptive - we rethought how we understand the data through domain segregation, allowing us to organize large, decades-old libraries into manageable, functional domains without changing the underlying files.

We overcame the limitations of traditional 5250 programs by replacing subfile constraints with modern grid views that support full search, filtering, sorting, grouping, and export. By combining the strengths of Architect and Sitemule Workspace, we integrated existing screens and options into these advanced views, allowing users to benefit from enhanced functionality while the original business logic continues to operate in the background.

We tackled the challenge of expanding data models by enabling the seamless addition of new fields, validations, metadata, and JSON-based structures without downtime or risk. This resulted in a consistent, enriched data layer that supports both structured and unstructured data. Simultaneously, the no-code design environment empowered business experts to participate directly in the modeling and application development process, reducing reliance on limited development resources.

We also addressed the challenge of limited data insight by offering user-friendly tools for modeling, visualization, filtering, and reporting - transforming legacy data into actionable intelligence to enable faster, better decision-making.

This method shows that successful modernization happens when inflexible legacy systems are transformed into adaptable, service-oriented architectures. By redefining how applications are designed, extended, and integrated, we sped up development, enhanced maintainability, and aligned technology with business goals - all accomplished within months without disrupting existing systems.

Done in months!

Step 5. Change the Mindset with Sitemule Enterprise

The final step in the transformation journey focuses on rethinking how applications are developed, deployed, and maintained. Sitemule Enterprise marks a decisive shift toward a service-based architecture driven by DevOps principles, enabling organizations to modernize sustainably and position IBM i at the heart of their digital ecosystems. This step shifts the mindset from isolated modernization projects to a continuous, scalable, and collaborative transformation process.

Sitemule Enterprise offers a native Web and Application Server that runs directly on IBM i, eliminating the need for third-party platforms, middleware, or external servers. Operating natively ensures seamless integration, easier system management, and greater reliability. This architecture allows modern web applications, APIs, and services to run alongside RPG, COBOL, and SQL programs, maintaining decades of proven business logic while expanding their capabilities into a modern web-based environment.

The platform allows organizations to utilize microservices and web services as a foundation for scalable, modular applications. Domain segregation supports a maintainable, flexible system structure in which each component can evolve independently. This modular method simplifies extending functionalities, enhancing performance, and ensuring long-term adaptability to evolving business needs.

In step four, we started the domain segregation process by breaking down the database into smaller domains to better understand the main functional areas. The main reason for using domain segregation is that it is the only organized approach for decomposing monolithic architectures into bounded domains, thereby increasing agility, resilience, and scalability while reducing development and maintenance costs. 

The Domain Model Definition reinforces this approach by providing a clear and adaptable blueprint for defining and managing domains. Combined with tools like Sitemule Architect, organizations can convert traditional IBM i systems into modern, service-oriented architectures that support long-term business goals. This organized approach to modernization also ensures that organizations can adapt to today's rapidly changing digital environment and shifting legislation.

Sitemule Enterprise bridges the gap between legacy and modern development by offering advanced tools and frameworks that appeal to a new generation of developers. Native integration with modern front-end technologies such as Angular, React, and Vue.js ensures that IBM i stays relevant and competitive in today's development landscape. Web services can be easily published as RESTful APIs with built-in OpenAPI documentation, simplifying integration and interoperability across systems.

Performance and scalability are achieved through intelligent load balancing and multithreaded job management, which dynamically distribute workloads across hundreds of concurrent sessions. This leads to faster response times, more efficient resource use, and stable operation even under heavy system load. Applications scale smoothly across on-premises and cloud environments, supporting millions of transactions while maintaining consistent performance.

Security remains a key part of the architecture. The platform upholds IBM i's strong security model and compliance standards, including SOX, while adding authentication options like SSL/TLS, OAuth, LDAP, and Active Directory integration. Development and production environments remain strictly separate to protect data integrity and meet compliance.

Developers benefit from web-native debugging, real-time monitoring, and structured logging, enabling precise troubleshooting through tools such as Visual Studio Code or the native 5250 environment. The inclusion of a powerful precompiler extends RPG, COBOL, and SQL with modern capabilities, allowing teams to build sophisticated, secure applications that leverage IBM i's native performance.

By consolidating workloads on IBM i, organizations simplify operational management, enhance governance, and decrease reliance on fragmented external systems. Sitemule Enterprise transforms IBM i into a modern, service-oriented hub - capable of running mission-critical applications, integrating with cloud and web technologies, and supporting ongoing innovation through DevOps automation.

Summary 

We changed the mindset and showed that modernization becomes truly sustainable when the entire application landscape adopts a service-based architecture guided by DevOps principles. With Sitemule Enterprise, we addressed the issues of monolithic systems, fragmented infrastructures, and isolated modernization efforts by introducing a native Web and Application Server that runs directly on IBM i. This removed dependence on external platforms, lowered architectural complexity, and ensured smooth compatibility with existing RPG, COBOL, and SQL logic.

We addressed long-standing scalability and modularity issues by adopting microservices and domain segregation as fundamental design principles. This enabled individual components to evolve independently, supported long-term flexibility, and provided a clear method for breaking down monolithic programs into manageable, resilient, and extensible services. Building on the domain segregation foundation established earlier, we enhanced the system’s ability to adapt to changing business needs and new legislation.

We bridged the gap between legacy development and modern engineering practices by introducing contemporary frameworks and tools that attract new developers while preserving existing expertise. We enabled IBM i to natively support modern web applications, APIs, and front-end technologies, ensuring full interoperability and seamless integration across the enterprise. At the same time, we improved operational performance through intelligent load balancing, multithreaded job management, and real-time debugging capabilities, addressing scalability, responsiveness, and complex troubleshooting challenges.

Security and compliance were strengthened by maintaining IBM i’s established authorization model, integrating it with modern authentication standards, and enforcing strict separation between development and production environments. This ensured that modernization did not undermine governance or regulatory requirements.

By consolidating workloads on IBM i, we simplified operational management, reduced reliance on external systems, and enabled ongoing innovation through DevOps automation. This mindset shift demonstrated that modernization is a continuous, strategic process rather than a one-time task. Sitemule Enterprise transformed IBM i into a modern, service-oriented platform where performance, security, and flexibility coexist - creating a foundation for scalable digital growth in the years ahead.

Done in years!

The Transformation Journey

The journey through these five steps shows that modernization on IBM i is not only possible but can be achieved with precision, control, and measurable results. By changing the circumstances, perspective, approach, method, and ultimately the mindset, organizations can transform their legacy ERP systems into modern, integrated, and future-ready platforms without abandoning their existing investments or disrupting ongoing operations.

In Step 1, Sitemule Blueprint showed that even decades of lost, undocumented knowledge across multiple developer generations and technologies can be recovered. Through support for the Model Context Protocol, factual data from the Dependency Graph can also be exposed to any generative AI assistant or agent, guiding developers and enabling agentic development grounded in accurate structural information - turning legacy applications into well-understood, maintainable assets rather than liabilities of their legacy status. 

In Step 2, we demonstrated with the Sitemule Platform that transformation starts with reimagining how users interact with the system. Moving the 5250 environment to the web created a unified, browser-based workspace where traditional applications coexist seamlessly with modern technologies.

In Step 3, we improved usability and productivity by using Sitemule Workspace to refactor existing interfaces into intuitive, user-focused applications. This enabled users with smarter workflows, better validations, and direct integration with tools they use daily - all accomplished in weeks instead of years.

In Step 4, we introduced Sitemule Architect to change the approach. Using a domain-driven, no-code design method, organizations can quickly model, extend, and deploy modern applications and microservices directly from existing Db2 structures - transforming rigid legacy systems into flexible, service-oriented architectures.

Finally, in Step 5, Sitemule Enterprise shifted the mindset. By adopting a native, service-oriented architecture with DevOps principles, we redefined how applications are built, deployed, and scaled. This step reestablished IBM i as a robust, modern platform capable of supporting continuous innovation, secure integrations, and enterprise-level performance.

Together, these five steps create a comprehensive and proven approach to legacy transformation on IBM i - one that protects business continuity while enabling new levels of agility, collaboration, and scalability. The result is a unified ecosystem where legacy reliability combines with modern innovation, ensuring that IBM i remains not just a platform of the past, but a foundation for the future.