When Not to Migrate Off AS400
Migration off AS400 is sometimes the right call, but it is decided correctly far less often than it is proposed. Heavy custom business logic, strong database reliability requirements, and unclear replacement ROI are the clearest signals that modernization, not migration, is the better investment.
Migration off AS400 is occasionally the right decision. It is proposed far more often than it is actually the right decision, usually driven by one of the myths covered in AS400 migration myths, rather than a clear-eyed business case. This article covers the signals that suggest staying and modernizing is the stronger option, and, for balance, the signals that point the other way.
Signal: Deep, Custom Business Logic
If the AS400 system encodes years or decades of custom business rules, pricing logic, regulatory edge cases, workflow exceptions, that were refined through real production experience rather than documented in a specification anywhere, migration risk is high. A new system built by a team without that accumulated context will re-encounter the same edge cases the original system already solved, at a much higher cost than modernizing the existing logic in place.
Signal: High Reliability and Transaction Integrity Requirements
IBM i's integrated DB2 for i database and object-based architecture give it a strong track record for transaction reliability and uptime in production. Systems where downtime or data integrity failures carry serious financial or regulatory consequences, core banking, manufacturing execution, healthcare records, are systems where the migration target needs to prove it can match an already-proven reliability bar, not just replicate feature parity.
Signal: Unclear or Unproven Migration ROI
A migration business case built primarily on "the technology is old" rarely survives a real cost-benefit analysis once data conversion, business logic rebuild, staff retraining, and dual-running transition costs are priced in. If nobody has produced a credible total cost of ownership comparison between modernizing the current environment and migrating to a proposed replacement, that is itself a signal the decision is not ready to be made yet.
When Migration Genuinely Makes Sense
Migration is a stronger case when the organization is consolidating multiple disparate systems (including non-AS400 systems) onto a single modern ERP platform for strategic reasons beyond the AS400 system itself, when the application logic is genuinely thin and well-documented rather than deep and tribal, or when there is no realistic path to maintaining IBM i skills, whether internal or through partners, over the system's remaining useful life. Even in these cases, a hybrid approach, modernizing the interface and integration layer while a longer migration plan proceeds, is often lower risk than a single cutover project.