Software Transfer Dilemma: Why Migrating Legacy Applications to IBM i is Worth the Effort
IBM offers a variety of cloud-based solutions, but some organizations may not want to move all their apps to the cloud. For those who still want to keep some apps on IBM i, IBM provides various migration strategies. IBM offers a variety of cloud-based solutions, but some organizations may not want to move all their apps to the cloud. For those who still want to keep some apps on IBM i, IBM provides various migration strategies.
If your organization has applications on the IBM i (formerly iSeries) platform that you would like to keep running while migrating to newer systems, the easy solution may be to do nothing. However, the right strategy will enable you to combine the best features of IBM i with the best features of the cloud, and make both work together to maximize your business results.
First, let’s look at the legacy application environment on IBM i cloud. The biggest difference between legacy applications and new applications is the user interface (UI). Legacy applications often feature a 5250 green-screen interface while contemporary apps are typically browser-based. Today, people expect a more modern UI, and those green-screen applications that have a modern year will likely have little or no usability.
The UI is important, but it is not the only reason to migrate legacy apps. The platform itself is not getting any younger. If your legacy apps are running on a 33-year-old platform, it would be wise to migrate them to something newer. Migrating legacy apps is a big job, but it could be a worthwhile investment for your organization.
Let’s look at a couple of the options you have for migrating legacy apps to IBM .
With this approach, you will replace the 5250 green-screen interface with a web-based interface. This can be done in a number of ways and you will want to consult with a partner who has experience with this type of migration. This approach works best if your legacy application is already running in a web browser, such as in a Citrix environment.
The other option is to rewrite the code. This can be done either in-house or by a third-party company, and it will require a significant investment.
Which approach is best for your organization will depend on a number of factors, including the size and scope of your application, the resources available, and the level of investment you are willing to make.
The key to making the right decision is to have a clear understanding of your business goals and objectives, and to know the capabilities of IBM i and the cloud. By understanding these capabilities, you can make an informed decision about how to move your legacy apps to IBM i, and how to make the most of your investment in the cloud.