IBM's $40B stock wipeout is built on a misconception: Translating COBOL isn't the same as modernizing it
Source: VentureBeat
📅 1 May 2024 – Anthropic’s Claude Code Announcement
On Tuesday, Anthropic published tools that let Claude read, analyze and translate legacy COBOL into modern languages like Java and Python. By the end of the trading day, investors had wiped roughly $40 billion from IBM’s market cap — the company’s biggest single‑day drop in 25 years — pricing the announcement as an existential threat to IBM’s mainframe business.
🔍 The Reaction – A Misreading of Mainframe Value
“The reaction was swift. It was also built on a fundamental misreading of why enterprises run mainframes in the first place.”
- IBM’s COBOL is 66 years old – designed in 1959, still running on IBM mainframes and powering transaction‑processing systems with an estimated 250 billion lines of COBOL in active production (Open Mainframe Project).
- The original engineers are retiring; their replacements largely cannot read the code.
- This skills gap has been one of enterprise IT’s most expensive unsolved problems for decades.
- IBM has been tackling it with AI since at least 2023, when it launched watsonx Code Assistant for Z to help migrate COBOL to modern Java.
🤖 Claude Code – What It Actually Does
- Analyzes entire codebases
- Maps hidden dependencies
- Generates working translations of code that most engineers today cannot read
“For enterprises running COBOL on distributed platforms — Windows, Linux and other non‑mainframe environments — that capability is genuinely useful and increasingly practical.” – Anthropic
🛠️ The Real Barrier – Not Technical, But Economic
“Modernizing COBOL has been a technically solved problem for a while,” Matt Braiser, analyst at Gartner, told VentureBeat. “The real problem is that the costs of modernization are high and the ROI is low.”
Competitive Landscape
| Vendor | Offering | Focus |
|---|---|---|
| Amazon (AWS) | AWS Transform | AI‑powered COBOL migration |
| Google Cloud | Comparable service | AI‑powered COBOL migration |
| IBM | watsonx Code Assistant for Z | Mainframe‑centric migration & modernization |
| Anthropic | Claude Code | Broad‑footprint translation for distributed environments |
“This is basically one more source of competition,” Raj Joshi, SVP at Moody’s Ratings, told VentureBeat. “IBM has always lived in a very competitive domain… there’s one more powerful competitor.”
“Applications don’t run on mainframes because they’re written in COBOL,” Steve McDowell, chief analyst at NAND Research, said. “They run on mainframes because mainframes deliver a class of determinism, scalable compute and reliability that general‑purpose servers can’t match.”
Determinism vs. Non‑Determinism
“GenAI tools are helpful, but their non‑deterministic nature means the resulting code is not consistent — the same operation will be implemented in different ways in different parts of the code,” Braiser added. “Leading tools combine deterministic and non‑deterministic approaches. None of this solves the ROI problem, though.”
📦 What COBOL Translation Leaves Unsolved
“Translating COBOL is the easy part,” Steven Tomasco, IBM communications director, told VentureBeat. “The real work is data‑architecture redesign, runtime replacement, transaction‑processing integrity, and hardware‑accelerated performance built over decades of tight software‑hardware coupling. That is the problem IBM has spent decades learning to solve, and AI is the most powerful tool we have ever had to do it.”
Real‑World IBM Use Cases
- Royal Bank of Canada
- National Organization for Social Insurance
- ANZ Bank
All have used watsonx Code Assistant for Z to accelerate COBOL modernization without moving off IBM Z.
Anthropic’s Niche
- For enterprises running COBOL outside the mainframe (distributed Windows/Linux systems), Claude Code enters a space where IBM’s vertical integration is less of an advantage.
- “IBM understands mainframe technology at a level that others can’t match. If I’m only looking at COBOL, I’m using IBM’s watsonx,” McDowell said. “Anthropic, however, has a broader footprint within a lot of development teams, where a single vendor makes it worthwhile.”
🧭 What Enterprise Buyers Should Actually Do
- Expect a flood of questions from executives who saw the headlines and assumed the hard problem was solved. It wasn’t.
- Recognize the broader ecosystem: “It’s COBOL, but there are numerous applications tied to it,” Joshi warned. “It’s not like you transform millions of lines and somehow you’re ready to go to cloud. It’s a massive risk assessment, dependencies and all those things.”
- Leverage the buzz for strategic review:
- Braiser: “Use the resulting board‑level and shareholder discussions to review postponed modernization initiatives and see if any of them now have ROI.”
- Assess competitive impact:
- McDowell: “Will Anthropic take business from IBM’s tool? Yes, of course. But I’d be surprised if that tool was making significant revenue for IBM.”
- Run a bounded pilot – not a wholesale rewrite:
- Chirag Mehta, analyst at Constellation Research, cautioned against emotional reactions. “Treat this as a reason to run a small, bounded pilot to measure outcomes, not as a reason to rip and replace vendors.”
- Pilot guidelines:
- Pick one well‑scoped application slice or workflow with clear inputs/outputs.
- Evaluate apples‑to‑apples on:
- Quality of dependency mapping
- Quality of recovered business‑logic documentation
- Test coverage & equivalence checks
- Performance & reliability regressions
“The bigger reminder is that modernization is more than converting code. The hard parts are extracting institutional knowledge, reworking processes and controls, change management, and containing operational risk in systems that cannot break. AI can compress the ‘analysis and translation’ work, but it does not eliminate the governa…” – sentence truncated in source
✅ Key Takeaways
| ✅ | Insight |
|---|---|
| 1 | COBOL translation is now easier, but modernization remains a high‑cost, low‑ROI challenge. |
| 2 | Mainframes survive because of determinism, scalability, and reliability, not because they run COBOL. |
| 3 | AI tools (Claude Code, watsonx, AWS Transform, GCP) are helpers, not replacements for deep architectural work. |
| 4 | Enterprise buyers should pilot, measure, and align with broader risk‑management goals before committing to any vendor. |
| 5 | Anthropic’s Claude Code offers a broader, non‑mainframe footprint, while IBM’s tools remain strongest for Z‑centric environments. |
Prepared for internal distribution – all quotes and data sourced from VentureBeat interviews and public IBM statements.
Cleaned Markdown
nce and accountability burden.
> "The teams that win will treat AI as an accelerator inside a disciplined modernization program, with measurable checkpoints and risk guardrails, not as a magic conversion button,"
> — Mehta