Legacy IT modernization cases test whether you can quantify the cost of doing nothing, prioritize migration sequences, and recommend architectures that balance risk with business velocity. Based on our analysis of 200+ technology-focused consulting cases, roughly 30% of digital transformation interviews now include a legacy modernization component — making this a must-prepare area for candidates targeting McKinsey, BCG, and Bain.
Why Legacy Modernization Dominates Tech Consulting
Every Fortune 500 company carries technical debt. In our experience working with technology strategy cases, the typical enterprise runs 40-60% of critical operations on systems built before 2010. These legacy systems create compounding costs: rising maintenance spend, inability to integrate modern tools, and talent scarcity as fewer engineers know older platforms.
Consulting firms bill approximately $15-20 billion annually on IT modernization engagements globally. Interviewers use these cases because they test multiple consulting skills simultaneously — financial analysis, risk assessment, stakeholder management, and technology judgment.
The decision framework for legacy modernization cases:
flowchart TD
A[Legacy System Assessment] --> B{Business Criticality?}
B -->|High| C[Risk-Mitigated Migration]
B -->|Medium| D[Phased Modernization]
B -->|Low| E[Retire or Replace]
C --> F{Data Complexity?}
F -->|High| G[Strangler Fig Pattern]
F -->|Low| H[Parallel Run + Cutover]
D --> I[API Wrapping + Gradual Rebuild]
E --> J[SaaS Replacement or Decommission]
The Four Migration Strategies
Every legacy case eventually requires you to recommend a migration approach. Interviewers expect you to match strategy to context rather than defaulting to a single answer.
| Strategy | When to Use | Risk Level | Timeline | Cost Profile |
|---|---|---|---|---|
| Rehost (lift-and-shift) | Urgent data center exit, minimal changes needed | Low | 3-6 months | Low upfront, savings from infrastructure |
| Replatform | Need cloud benefits without full rewrite | Medium | 6-12 months | Moderate; 20-40% cost reduction achievable |
| Refactor | System must scale or integrate with modern tools | High | 12-24 months | High upfront, 50-70% long-term savings |
| Replace | Off-the-shelf SaaS covers 80%+ of requirements | Medium | 6-18 months | Predictable subscription cost |
In our experience coaching candidates, the strongest answers recognize that most enterprises use a portfolio approach — different strategies for different systems based on business criticality and technical condition.
Quantifying Technical Debt
Interviewers at top firms frequently ask: “How would you assess whether this modernization is worth the investment?” The answer requires a structured cost-benefit framework.
Cost of Inaction (annual):
- Maintenance overhead: legacy systems typically consume 60-80% of IT budgets for maintenance vs. new development
- Opportunity cost: delayed feature launches averaging 3-6 months longer than competitors on modern stacks
- Talent premium: legacy skill premiums of 20-40% for COBOL, mainframe, and older Java developers
- Security exposure: unpatched systems represent 60% of enterprise breach vectors
Migration Investment:
- Direct costs: development, testing, data migration, parallel running
- Indirect costs: productivity dip during transition (typically 15-25% for 6 months)
- Risk costs: potential business disruption, estimated by probability-weighted scenarios
A strong candidate structures this as a net present value calculation over 5-7 years, demonstrating that the breakeven point for most modernization efforts falls between year 2 and year 4.
Common Interview Scenarios
Based on our analysis of technology cases in the case library, three legacy modernization scenarios appear most frequently:
1. Bank Core System Replacement
A retail bank running a 30-year-old core banking platform faces rising maintenance costs and cannot launch mobile features competitors already offer. The case tests your ability to sequence a multi-year migration without disrupting daily transactions processing millions of operations.
Key considerations: regulatory requirements, data migration integrity, phased rollout by product line, and managing vendor dependency.
2. Manufacturer ERP Consolidation
A global manufacturer with 15 acquired subsidiaries runs 8 different ERP systems. The case asks you to recommend a consolidation strategy that reduces operating costs while preserving subsidiary-specific workflows.
Key considerations: process harmonization vs. customization trade-offs, change management across geographies, and total cost of ownership analysis.
3. Retailer Monolith Decomposition
A mid-market retailer’s monolithic e-commerce platform cannot handle peak traffic and takes 6 months for any feature release. The case tests whether you can recommend a microservices migration path that delivers incremental value.
Key considerations: identifying bounded contexts, prioritizing high-value service extraction, and maintaining system stability during decomposition.
For related build-vs-buy analysis, see our tech build vs. buy decision guide.
Framework for Structuring Your Answer
When you receive a legacy modernization case, structure your approach in four phases:
flowchart LR
A[1. Assess Current State] --> B[2. Define Target Architecture]
B --> C[3. Plan Migration Sequence]
C --> D[4. Build Business Case]
A -.-> |Document pain points,\ncosts, risks| A
B -.-> |Align with business\nstrategy| B
C -.-> |Minimize disruption,\ndeliver early wins| C
D -.-> |NPV, timeline,\nrisk mitigation| D
Phase 1 — Assess Current State: Map existing systems by business criticality and technical condition. Identify which systems are “burning platforms” (high cost, high risk) vs. “stable but limiting” (functional but constraining growth).
Phase 2 — Define Target Architecture: Align technology choices with 3-5 year business strategy. A company pursuing M&A needs integration-friendly architecture; a company optimizing margins needs cost-efficient infrastructure.
Phase 3 — Plan Migration Sequence: Start with high-value, lower-risk systems to build organizational confidence. Avoid “big bang” migrations for critical systems — use strangler fig or parallel-run patterns instead.
Phase 4 — Build Business Case: Quantify costs, benefits, and risks. Include a sensitivity analysis showing outcomes under optimistic, base, and pessimistic scenarios.
Metrics That Signal Expertise
Dropping specific metrics during a legacy modernization case demonstrates genuine technology fluency:
- Technical debt ratio: maintenance spend as a percentage of total IT budget (industry average: 60-75%; best-in-class: 30-40%)
- Deployment frequency: legacy systems average quarterly releases; modern targets are weekly or daily
- Mean time to recovery (MTTR): legacy systems average 4-8 hours; cloud-native targets under 1 hour
- Integration cost per connection: legacy point-to-point integrations cost 3-5x more than API-based connections
- Developer productivity: measured by features delivered per sprint; typically improves 2-3x post-modernization
For more on technology cost frameworks, see our tech cost optimization guide and enterprise tech stack cases.
Key Takeaways
- Legacy modernization cases test financial judgment as much as technology knowledge — always quantify the cost of inaction before recommending investment
- Use the four-strategy framework (rehost, replatform, refactor, replace) and match strategy to each system’s business criticality and technical condition
- Never recommend a “big bang” migration for critical systems — interviewers reward answers that manage risk through phased approaches
- Structure your answer in four phases: assess current state, define target architecture, plan migration sequence, build business case
- Demonstrate fluency with specific metrics (technical debt ratio, deployment frequency, MTTR) rather than generic technology buzzwords
- Most enterprises need a portfolio approach — different migration strategies for different systems based on risk tolerance and strategic priority
Ready to practice legacy modernization scenarios? Explore technology industry cases in our case library, or sharpen your structuring skills with an AI Mock Interview that simulates real consulting case dialogue.