HoorTotal Cost of Ownership: AS/400 Maintenance vs. Modernization
"We'll modernize when the budget allows it" is the most expensive sentence in enterprise IT. Keeping an AS/400 running exactly as-is is never actually free — the costs are just distributed differently, spread across specialist salaries, integration workarounds, and opportunity cost, rather than appearing as a single modernization line item on a budget someone has to approve.
Standing still isn't free. It's just billed differently.
The visible cost: specialist staffing
RPG and CL developers are a shrinking, aging talent pool, and compensation reflects it — specialist contractors for legacy AS/400 work often command a premium over general-purpose developers, precisely because there are fewer of them each year. Organizations that "save money" by not modernizing are frequently paying scarcity premiums on staffing that would shrink significantly with a modernized, better-documented system.
The hidden cost: integration tax
Every new business initiative that needs to touch the AS/400 — a new CRM, a new analytics platform, a new supply chain tool — pays a custom integration cost because there's no reusable API layer to build on. Multiply that cost across every integration project over several years, and it usually dwarfs the cost of building the API layer once. This is the cost most likely to be invisible in a budget conversation, because it's spread across a dozen different project budgets rather than appearing in one place.
The compounding cost: institutional knowledge risk
Every year without investment in documentation or modernization is another year closer to a key retirement that takes undocumented business logic out the door with it. When that happens, the cost isn't a line item — it's an emergency engagement at a premium rate, under time pressure, to reverse-engineer logic that could have been documented calmly years earlier.
The opportunity cost: what the business can't do
Perhaps the largest cost is the hardest to quantify: initiatives the business doesn't pursue because the core system can't support them without months of custom integration work. Real-time inventory visibility, self-service customer portals, modern supply chain orchestration — all of these are harder to justify when the underlying system adds friction to every attempt.
What a phased modernization actually costs
The alternative isn't a single, enormous rewrite — it's the incremental approach described in our piece on zero-downtime modernization: an API layer built function by function, prioritized by which integrations are currently costing the most in workarounds. Each phase delivers a standalone return — reduced integration cost, reduced specialist dependency, faster reporting — rather than requiring the full investment before any value is realized.
Running the numbers for your organization
The right comparison isn't "AS/400 costs $0, modernization costs $X." It's the fully loaded cost of specialist staffing, integration workarounds, and knowledge risk over the next five years, compared against a phased modernization that reduces all three over the same period. See Hoorbit's engagement pricing to start building that comparison for your own environment.