{"id":19167,"date":"2025-04-09T10:10:00","date_gmt":"2025-04-09T08:10:00","guid":{"rendered":"https:\/\/itpatagonia.com\/?p=19167"},"modified":"2026-04-20T14:54:05","modified_gmt":"2026-04-20T12:54:05","slug":"replatforming-vs-refactoring-it","status":"publish","type":"post","link":"https:\/\/itpatagonia.com\/en\/blog\/replatforming-vs-refactoring-it","title":{"rendered":"Replatforming: Should you migrate from mainframe to cloud? Our expert opinion"},"content":{"rendered":"

The modernization of IT infrastructures<\/a> It is key to improving the efficiency, security and scalability of business systems. <\/p>\n\n\n\n

And the options for achieving this are multiple and vary depending on the needs of each organization.<\/p>\n\n\n\n

Modernizing may involve migrating a mainframe infrastructure to a cloud environment, as part of a project. replatforming<\/em>. <\/p>\n\n\n\n

It may also include refactoring processes that involve a more in-depth restructuring of a system or application's code. <\/p>\n\n\n\n

Similarly, it may include the deployment of a microservices architecture<\/a> and\/or the process automation<\/a>And it may even involve an upgrade of mainframe infrastructures, which, far from shrinking, continue to expand. <\/p>\n\n\n\n

In this article we analyze how to evaluate the possibility of developing a project replatforming<\/em>, the implications and challenges it entails, and the most common mistakes that are made.<\/p>\n\n\n\n

We also focus on the differences with refactoring, and the trends that will mark the future of replatforming<\/em>.<\/p>\n\n\n\n

To address these issues we interviewed Leo Zrycki, director of the IT Patagonia Mainframe Center of Excellence<\/a> and quadruple IBM Champion zSystem, who provided us with his vision and perspectives to contribute to the development of this article.<\/p>\n\n\n\n

What is replatforming?<\/h2>\n\n\n\n

In some cases, the replatforming<\/em> It is a strategy that It involves moving applications from the mainframe to a new technological infrastructure, such as the cloud.<\/strong>.<\/p>\n\n\n\n

In order to be able to specify its definition, it is important to differentiate the types of projects that can be considered as replatforming<\/em>. <\/p>\n\n\n\n

A specific case is move entire mainframe systems to Microfocus COBOL<\/strong>A change of environment, which means that programs will no longer be run on the mainframe, but in the cloud.<\/p>\n\n\n\n

There are other projects that are closer to IBM's vision where The core of the applications remains on the mainframe, and the services in the cloud<\/strong>. <\/p>\n\n\n\n

IBM has a vision of a hybrid cloud, where a significant portion of the organization's processing goes through the mainframe (in COBOL), while some services in Java, Python and other programming languages<\/a>, move to the cloud. <\/p>\n\n\n\n

The new versions of IBM's mainframe infrastructures support just those possibilities, and even the option of having Linux on the mainframe so that all modern languages such as Python, Java, and C can be run from it.<\/p>\n\n\n\n

Furthermore, it is now possible to have DevOps on the mainframe. <\/p>\n\n\n\n

In fact, the IDz integrated development environment<\/a> (IBM Developer for System Z), allows for graphical interfaces and working like any other modern language, where a programmer can see the database model and have help for system management.<\/p>\n\n\n\n

In the first of the two cases, the mainframe is left behind. <\/p>\n\n\n\n

In the other, much of that infrastructure is leveraged and applications are left outside the mainframe.<\/p>\n\n\n\n

Differences between replatforming and refactoring<\/h2>\n\n\n\n

He replatforming<\/em> and the refactoring<\/em> are application modernization strategies<\/a>, but they differ in their scope and focus. <\/p>\n\n\n\n

He replatforming<\/em> involves moving an application to a new infrastructure, starting from the completion of the changes needed to make it work in the new environment without significantly altering its architecture or code<\/strong>. <\/p>\n\n\n\n

Instead, he <\/strong>refactoring<\/em><\/strong> It includes a deep restructuring of the code<\/strong> to optimize its operation, improve its scalability or adapt it to new technologies, without modifying its external behavior. <\/p>\n\n\n\n

While the replatforming<\/em> looking for speed and less impact on the business, the refactoring<\/em> It requires more time and effort, but offers greater long-term benefits.<\/p>\n\n\n\n

To illustrate this with specific examples, when moving from a mainframe COBOL to a cloud COBOL (Microfocus COBOL), the translation is almost straightforward. Almost, but not entirely, because everything related to the online environment can present differences. <\/p>\n\n\n\n

For example, there will no longer be platform-dependent screens through which bank staff view a transaction. <\/p>\n\n\n\n

In this case of replatforming<\/em>, the screens that are developed with the software disappear CICS commands on the mainframe<\/a> and they would have to be rewritten.<\/p>\n\n\n\n

Refactoring, on the other hand, is about the constant improvement of programs. For example, when moving forward with program reengineering or when seeking optimal maintenance conditions so that anyone reading a program can understand it almost immediately.<\/p>\n\n\n\n

\"Claves<\/a><\/figure>\n\n\n\n
<\/div>\n\n\n\n

Why are organizations considering replatforming?<\/h2>\n\n\n\n

The reasons that may lead a company to start a process of replatforming <\/em>are multiple.<\/p>\n\n\n\n

1) Economic reasons<\/strong><\/p>\n\n\n\n

Some companies are beginning to consider the possibility of migrating from a mainframe infrastructure to a cloud environment, understanding that this can provide a positive economic impact. This isn't necessarily the case. <\/p>\n\n\n\n

Before making a decision based on potential cost reduction, it's important to keep in mind that IBM's mainframes have incorporated new features. Now, Part of the processing can be done for a very small fee<\/strong>.<\/p>\n\n\n\n

Indeed, there are coprocessors within the mainframe that allow you to run artificial intelligence<\/a>Part of the database load, part of the mainframe Linux, runs on special zIIP processors, which are very economical. <\/p>\n\n\n\n

Therefore, there are also cost-effective options in the mainframe infrastructure space that should be evaluated to make the most favorable decision for each organization.<\/p>\n\n\n\n

2) Lack of mainframe talent<\/strong> <\/p>\n\n\n\n

Another reason that may lead to the need to advance in an infrastructure migration is the shortage of mainframe and COBOL programmer talent<\/a>. <\/p>\n\n\n\n

We are experiencing a situation where the demand for IT talent exceeds the available supply, which often requires hiring and training young people with little experience. <\/p>\n\n\n\n

Or, retrain people who are already working within the organization, so that they acquire new skills<\/a>.<\/p>\n\n\n\n

Without a doubt, the Lack of the number of professionals that the IT industry demands today<\/a> It is a real bottleneck, and The industry needs answers to meet its own demand for employability<\/strong>.<\/p>\n\n\n\n

These responses can be generated from the technology sector companies themselves, as is the case with IT Patagonia and its ally Codeki<\/a>.<\/p>\n\n\n\n

3) Market trend<\/strong> <\/p>\n\n\n\n

Companies are increasingly interested in migrating their applications, data, servers, and storage from traditional on-premise infrastructure to hybrid cloud services, or 100% cloud. <\/p>\n\n\n\n

By 2024, end-user spending on public cloud services worldwide was estimated to total $678.8 billion. This was reported by Gartner<\/a>, noting that, compared to the $563.6 billion generated by the cloud market in 2023, the estimated figure for 2024 would represent an annual increase of 20.41% in 3Q.<\/p>\n\n\n\n

As this trend evolved, many companies that had been working practically 100% on-premise with local physical infrastructures, They began to evaluate the migration of their resources to the cloud<\/a>.<\/p>\n\n\n\n

What are the most common mistakes organizations make in replatforming projects?  <\/h2>\n\n\n\n

A project of replatforming <\/em>It is a process that extends over time, which can take months or even years, and which has a high risk threshold<\/strong>.<\/p>\n\n\n\n

The investment in the software stock that organizations that work with the mainframe platform have is not easy to rewrite. <\/p>\n\n\n\n

In parallel, it is not easy to generate programs that run on other platforms and have adequate performance.<\/p>\n\n\n\n

This calls into question the effectiveness and efficiency of this type of migration, which involves significant risks that must be properly assessed.<\/p>\n\n\n\n

Therefore, the most common errors associated with this type of project are that a company:<\/p>\n\n\n\n