In the first two articles of this series, we explored the Fight and Flight approaches to modernization. Organizations pursuing Fight choose to extend and modernize existing investments, while organizations pursuing Flight view migration as the best path toward achieving their long-term business goals.
In our third installment, this last category often receives less attention and, perhaps unfairly, the most criticism: Freeze.
At first glance, Freeze can sound like a decision to do nothing. But in reality, many organizations that adopt a Freeze strategy are making a very intentional business decision. Rather than replacing or significantly modifying core systems, they’re choosing to preserve proven applications while focusing resources on other strategic priorities.
As it turns out, preservation is not always the same thing as falling behind.
Why Organizations Choose to Freeze
It’s no secret that technology leaders are often under pressure to modernize. Alongside the almost daily release of new applications, consulting firms are continuing to promote digital transformation initiatives, and business leaders are always seeking new ways to improve efficiency and stay competitive.
Yet despite these pressures, many organizations continue to rely on IBM i applications that have successfully supported their operations for years, or even decades.
The reason is simple: these systems work.
These applications may have had longstanding roles in enabling the countless transactions and business processes that organizations depend on every day. Making significant changes to these applications can affect operations such as order processing, inventory management, logistics coordination, supporting manufacturing operations, handling financial transactions, and much more.
That’s where the reasoning behind the Freeze approach comes in. For some businesses, the risks associated with replacing or heavily modifying these systems outweigh the potential benefits. Instead, these organizations may choose to focus on stability, continuity, and maximizing the value of existing investments.
Freeze Doesn’t Mean Doing Nothing
One of the most common misconceptions about the Freeze approach is that organizations choosing this path are ignoring modernization altogether. That is rarely the case.
More often, these organizations are modernizing around their core applications rather than within them, meaning that while the underlying application remains largely unchanged, the business will continue to evolve.
Though this approach differs significantly from Fight or Flight, the main drivers for modernization remain largely the same. Businesses still need to adapt to new customer demands and expectations. Partner ecosystems are becoming more sophisticated than ever. Furthermore, data and advanced analytics continue to grow in prominence as AI projects move from experimentation to execution. Meanwhile, business stakeholders still expect data to be available wherever they need it, making business continuity a critical consideration when prioritizing your initiatives.
The result is a modernization strategy that’s less focused on changing the core system and more focused on improving what happens around it.
What Freeze Looks Like in Practice
The Freeze approach can take many forms depending on business priorities. For example, organizations may:
- Connect cloud-based CRM platforms to IBM i data
- Enable reporting and analytics initiatives
- Support AI and machine learning projects
- Introduce customer or partner self-service portals
- Improve visibility into operational data
- Integrate third-party applications and platforms
- Automate manual processes
While these projects may sound similar to the Fight approach of modernizing existing investments, Freeze differs because the IBM i applications themselves may remain largely unchanged. By evolving the information and business processes surrounding the applications, organizations can extend their value without taking on the cost, risk, and disruption of touching a system that runs the business.
What we’ve seen from IBM i organizations in particular is that the core application isn’t always the problem. The challenge is finding new ways to access its data, connect it with modern platforms, and support evolving business needs.
While IBM i has shown its resilience to adapting to modern demands, this issue can compound as experienced RPG skills become harder to find. The Freeze approach directly addresses that skills gap by adding modern capabilities around IBM i. This allows organizations to utilize other modern programming languages and extend their applications without requiring every new modification to involve changes to the underlying RPG code.
Real-World Perspective
One transportation and logistics company found itself in a position that many IBM i teams can probably relate to. The business had decided to introduce a new cloud-based transportation management system, but the existing IBM i-based TMS was still deeply woven into daily operations. It contained years of custom business processes, integrations, and institutional knowledge that the company relied on every day. Simply turning it off and moving everyone to a new platform wasn’t a realistic option.
What started as a modernization initiative quickly became a business continuity challenge. The organization needed to support a new platform while ensuring dispatchers, operations teams, and other stakeholders could continue working without interruption. They also needed information flowing seamlessly between both environments as different business units transitioned over time.
As the project progressed, the company came to an important realization: modernization wasn’t really about replacing the IBM i system. It was about creating the flexibility to introduce new technology without breaking the processes that were already working. Instead of treating modernization as a single migration event, the team focused on keeping both systems synchronized and allowing the business to evolve at a pace that made sense.
Matthew, a key contact for the project and integrations SME, reflected on his biggest takeaway from seeing the initiative evolve.
“One of the biggest lessons from the project was that modernization doesn’t always mean moving away from a platform,” he noted. “Sometimes it’s about removing barriers between systems and making trusted data available wherever it’s needed. By focusing on connectivity instead of replacement, the organization was able to introduce new capabilities, reduce disruption, and continue getting value from the systems that had supported the business for years.”
The Role of Integrations in the Freeze Approach
Throughout this series, we’ve seen that integrations are central to Fight, Flight, and Freeze. No matter the approach, data must move.
This is especially true for organizations pursuing Freeze. Core applications may remain unchanged, but business requirements continue to evolve. Organizations need better ways to access, share, and act on the data already stored within their business systems.
Within the various roles in an organization, we see that business leaders want real-time visibility into customer activity. Operations teams need faster access to inventory and fulfillment information. Sales teams want customer data available in CRM platforms. Executives need analytics to support better decisions. And increasingly, organizations want to leverage AI using the data already powering their business.
To accomplish this, we often connect core systems such as IBM i ERP and WMS platforms with CRM systems, business applications, partners, analytics platforms, and AI tools.
Integration can enable organizations to:
- Make data more accessible across applications, teams, and channels
- Enable analytics and AI with trusted operational data
- Connect CRM, ERP, WMS, and partner systems to keep information flowing where it’s needed
- Extend the value of existing applications without disrupting the operations that depend on them
For organizations pursuing Freeze, integration becomes a primary mechanism for modernization. Rather than replacing a trusted core application, organizations can extend what it already does and unlock more modern capabilities in the process.
The application may stay the same, but the value created from its data does not.
Common Misconceptions about Freeze
Misconception #1: Freeze Means Falling Behind
Reality: Maintaining a stable application does not automatically mean an organization is behind its competitors. Success is measured by business outcomes, not simply by the age of a platform.
Misconception #2: AI Requires Application Replacement
Reality: Organizations often assume AI initiatives require entirely new systems. In reality, many AI projects depend far more on accessible, high-quality data than on replacing the application where that data resides. In particular, IBM i/AS400 platforms can contain decades of valuable data that just needs reformatted and organized.
Misconception #3: Freeze Is a Permanent Decision
Reality: The Freeze approach is not necessarily a permanent strategy. Many organizations choose Freeze as a deliberate way to support current business priorities while preserving flexibility for future decisions.
Misconception #4: Modernization Requires Changing Everything
Reality: Some modernization efforts focus on applications, while others focus on processes or data accessibility. Organizations pursuing Freeze often prove that meaningful modernization can create focused results and ROI without altering the core system itself.
When Freeze Makes Sense
How do you know when the Freeze approach makes more sense than the others? We find that this approach is often a strong fit when:
- Existing applications continue to meet business needs
- Operational stability is a top priority
- Resources are focused on other strategic initiatives
- Migration costs outweigh expected benefits
- Business disruption must be minimized
- Leaders want to leverage existing investments while pursuing complementary initiatives
For these organizations, Freeze is less about racing to catch up to the “status quo” and more about making thoughtful, pragmatic business decisions.
Final Thoughts
In many modernization discussions, Freeze is portrayed as the least ambitious option. The reality is often quite different.
Organizations pursuing Freeze understand that technology investments should align with business goals. If a core application continues to provide value, reliability, and operational stability, replacing it may not represent the best use of time, budget, or resources.
Instead, they focus on maximizing the value of what already exists while still enabling new capabilities where they matter most.
Whether the objective is supporting AI initiatives, improving customer experiences, expanding analytics capabilities, or connecting new applications to trusted business systems, success ultimately depends on the organization’s ability to make information accessible. Regardless of whether an organization chooses to Fight, Flight, or Freeze, one reality remains unchanged:
The future of modernization isn’t solely about applications. It’s about putting data to work wherever the business needs it.
Where Do We Go from Here?
After exploring the Fight, Flight, and Freeze approaches, one thing becomes clear: there is no universal path to modernization.
In our final article, we’ll bring these three strategies together, examine the common themes that connect them, and explore the lessons organizations can apply regardless of which path they choose.
