COBOL Migration Services

Section 02

How to Evaluate Providers

COBOL migration providers must demonstrate three capabilities: code archaeology (understanding undocumented business logic), architecture design (strangler fig patterns), and talent transition management (knowledge capture before developers retire). Providers with only automated translation tool expertise routinely underestimate scope by 40–60%.

Migration strategy comparison:

Red flags:

• Providers who propose big-bang rewrites for systems over 100K LOC (industry failure rate >60%)
• No code archaeology methodology — providers who rely on developer interviews without automated static analysis miss critical logic
• Automated translation output that isn't reviewed by developers before production deployment
• No rollback strategy for migrated modules — every migrated module must have a tested rollback path

What to look for: Case studies from your specific COBOL environment (IBM z/OS, CICS, IMS, VS COBOL II vs COBOL/400), references from organizations with similar codebase size, and specific methodology for handling undocumented business logic in copybooks.

Section 03

Implementation Patterns

The strangler fig pattern is the only consistently successful approach for mission-critical COBOL systems. It requires wrapping existing COBOL with an API facade, then replacing functionality incrementally while the mainframe continues running.

Strangler fig implementation sequence:

1. API facade layer (months 1–3): Build REST API wrapper around COBOL programs using IBM API Connect, MuleSoft, or custom microservices. All new integrations route through the facade, not directly to COBOL. This decouples consumers from COBOL before migration begins.
2. Module identification and prioritization (months 2–4): Static analysis identifies seams — independent COBOL programs with clear input/output contracts. Batch-only programs (no real-time CICS transactions) are safest to migrate first. Identify "crown jewels" (programs handling >80% of transaction volume) and plan to migrate last.
3. Pilot module migration (months 4–8): Migrate one low-risk module. Run in parallel with COBOL for 3–6 months, reconciling outputs daily. This validates the migration approach and builds team confidence before high-stakes migrations.
4. Wave execution (months 8–36+): Migrate modules in waves, starting with batch jobs and ending with online transactions. Each wave follows the same parallel-run pattern.

Automated translation considerations: Tools like AWS Blu Age (COBOL→Java), Microfocus COBOL to Java, and TSRI AUTOPILOT can accelerate translation 3–5× compared to manual rewriting. However, the output requires significant refactoring: automated tools produce single-class Java files that replicate COBOL's procedural style, not idiomatic Java. Budget 30–50% of the automated translation cost for code cleanup before teams will accept ownership.

Talent transition pattern: Schedule knowledge capture workshops with retiring COBOL developers in the first month of the engagement. Record sessions, document business rules in structured formats, and create COBOL program-level "intent documentation." Every month of delay increases the risk that a critical developer retires before their knowledge is captured.

Section 04

Total Cost of Ownership

COBOL migration is the highest-cost, longest-timeline modernization engagement in the enterprise software portfolio. The median engagement cost of $290K covers assessment and roadmap only — execution costs are 5–15× larger depending on codebase size and strategy.

Cost model by strategy:

Cost of inaction: Mainframe MIPS costs growing at 10% annually double in 7 years. A $1M/year mainframe costs $1.7M in year 7 with no action. Additionally, talent costs escalate as the COBOL developer pool shrinks — median COBOL developer compensation is $175K–$220K, 40–60% above equivalent Java developer rates.

Hidden costs: Knowledge capture workshops ($40K–$100K), regulatory compliance documentation for migrated systems ($50K–$150K for banking/insurance), and parallel system maintenance costs during strangler fig migration ($100K–$400K/year for multi-year migrations).

Section 05

Post-Engagement: What Happens Next

After a COBOL migration assessment, you own a codebase complexity analysis, strategy recommendation with TCO models, and a detailed roadmap. The execution phase — which is 5–15× the assessment cost — begins immediately if executive approval is granted.

Typical post-engagement sequence:

• Month 1–3: API facade layer implementation. All new development routes through REST APIs over COBOL. This is the first irreversible commitment to migration.
• Month 4–12: Pilot module migration with parallel run validation. This is the highest-risk phase — if pilot fails, the strategy must be revised before proceeding.
• Month 12–36: Wave execution for batch and non-critical online modules. Internal teams take increasing ownership of the migration pattern.
• Month 36–60+: Online transaction migration. This requires the most careful parallel-run validation and has the lowest risk tolerance for discrepancies.

Build internal capability: The engagement provider should transfer the strangler fig pattern and parallel-run methodology to internal teams by month 12. Organizations that remain dependent on external providers for all migration waves pay 2–3× more over the full migration timeline.

Organizational readiness: COBOL migration requires organizational changes alongside technical changes. Application teams must accept ownership of migrated Java modules — create accountability structures before migration begins. Platform team capability (CI/CD, container infrastructure, monitoring) must be established before production COBOL modules are replaced.

When migration is complete: Budget 12–18 months for post-migration stabilization before decommissioning mainframe infrastructure. Edge cases that weren't captured in parallel-run reconciliation emerge over the first year in production.

---

Section 06

Pain Points

The 2027 COBOL Talent Cliff

Your COBOL developers are 58 years old on average. By 2027, 45% will retire. You can't hire replacements - CS graduates haven't learned COBOL since 1995. The clock is ticking.

The $2M 'Rewrite to Java' Disaster

You hired Accenture to rewrite COBOL to Java. 18 months later, you've spent $2M and the new system can't handle leap years. Why? Because the 200,000 lines of undocumented business logic in COBOL are now 300,000 lines of buggy Java.

Mainframe MIPS Costs Spiraling

Your mainframe license costs $800K/year and growing 12% annually. IBM knows you're trapped. Every 'modernization' project fails, so you keep paying. You need a strategy that actually ships, not another 3-year death march.

Regulatory Audit Nightmares

Your auditors flag the mainframe as 'key person risk.' If your lead COBOL dev (who's been there 35 years) gets hit by a bus, the company can't process payroll. The Board is asking hard questions you can't answer.

---

Section 07

Methodology

Discovery & Code Archaeology (3 weeks)

Activities:

• Static analysis of COBOL codebase (complexity metrics, dead code identification)
• Interview retiring COBOL developers (before they leave - this is urgent)
• Map data flows between COBOL, DB2, CICS, and downstream systems
• Identify 'Crown Jewels' (the 20% of code that drives 80% of business value) Outcomes:
• COBOL Complexity Heat Map (which modules are impossible to touch)
• Dependency Graph (what breaks if we migrate Module X first)
• Talent Risk Register (who knows what, and when do they retire)

Strategy Design & TCO Modeling (2 weeks)

Activities:

• TCO modeling for 3 strategies (Rehost/Refactor/Rewrite)
• Risk assessment (what's the blast radius if this fails?)
• Strangler Fig architecture design (API gateway, event streaming, dual-write patterns)
• Technology selection (AWS Mainframe vs Azure vs GCP, Java vs .NET vs Go) Outcomes:
• Board-ready business case with go/no-go recommendation
• Target architecture blueprint (where does COBOL live in 5 years?)
• Risk mitigation playbook (how do we de-risk this?)

Roadmap Creation & Wave Planning (2 weeks)

Activities:

• Identify migration waves (batch jobs first, then online transactions)
• Define 'done' criteria per wave (what does success look like?)
• Resource planning (when do we hire Java devs? When do we train COBOL devs?)
• Partner shortlist (who can execute automated COBOL translation? Microfocus? Blu Age? TSRI?) Outcomes:
• 12-quarter migration roadmap with dependencies
• Resource forecast (FTEs per quarter, skills mix)
• Partner recommendation (3 firms we trust to execute this)

Pilot Execution Support (Optional) (8-12 weeks)

Activities:

• Lead Wave 1 migration (prove the strategy works)
• Setup CI/CD for hybrid mainframe/cloud deployments
• Train internal team on Strangler Fig patterns
• Establish governance model for ongoing migration Outcomes:
• 1 migrated module running in production
• Playbook for internal teams to execute Wave 2-N independently
• Lessons learned report (what to avoid in future waves)

---

Section 08

Deliverables

• COBOL Codebase Complexity Analysis (Excel + Code Scan Report): Not a lines-of-code count. We identify: (1) Business logic buried in copybooks, (2) Undocumented JCL dependencies, (3) DB2 stored procedures hiding critical calculations, (4) The 15% of code that actually matters (Pareto principle). This is your attack surface.
• 3-Strategy TCO Model (Rehost/Refactor/Rewrite) (Unlocked Excel): Side-by-side comparison: (1) Lift-and-shift to AWS Mainframe (quick but expensive long-term), (2) Automated COBOL-to-Java (Microfocus/Blu Age), (3) Strangler Fig rewrite (slow but sustainable). We model 5-year TCO including hidden costs like talent premiums ($180K for COBOL devs vs $120K for Java).
• Strangler Fig Migration Roadmap (PPT + Mermaid Diagrams): The only strategy that works for mission-critical systems: Keep the mainframe running while you carve off modules one-by-one. We identify the 'seam' (APIs to wrap COBOL), the first candidate module (batch jobs, not real-time transactions), and the 12-quarter rollout plan.
• Talent Transition Plan (Documentation): The uncomfortable truth: Your COBOL team can't learn microservices at age 60. We design: (1) Knowledge extraction workshops (before they retire), (2) Hybrid team model (COBOL experts as 'translators', Java devs as builders), (3) Retention bonuses for critical SMEs during transition.
• Regulatory Risk Mitigation Strategy (Report): For banks/insurance/gov't: How to migrate while maintaining SOX/PCI/HIPAA compliance. Includes parallel run strategy, audit trail preservation, and rollback procedures. This is what keeps you out of regulatory hot water.

---

Section 09

Team Composition

• Lead Modernization Architect: Former mainframe developer (20+ years COBOL/CICS/DB2) who successfully escaped to cloud. Knows where the bodies are buried. This role MUST have hands-on COBOL experience - don't accept a cloud-only architect.
• Migration Strategist: The 'Pattern Matcher'. Has led 5+ mainframe migrations. Knows that Strangler Fig beats Big Bang 90% of the time. Challenges vendor pitches (especially automated translation tool snake oil).
• Financial Analyst: Translates mainframe MIPS into P&L impact. Essential for CFO conversations. Knows that TCO models must include talent retention bonuses and training costs (not just infrastructure).
• Engagement Manager: The PM who keeps this on track. Mainframe migrations are political nightmares (old guard vs new guard). This person navigates the org dynamics.

---

Section 10

Case Study

Industry: Regional Bank ($12B Assets)

Challenge: Core banking system: 300K lines of COBOL running on IBM z/OS. Average COBOL developer age: 62. Previous 'rewrite to Java' project failed after 24 months and $8M spent. CTO brought in to either fix this or sell the bank (seriously - the Board was exploring M&A because tech was a deal-breaker).

Solution: We designed a Strangler Fig strategy. Instead of rewriting 300K LOC, we identified the 'seam': the overnight batch processing jobs (40% of COBOL code). Wrapped them in REST APIs, migrated batch to AWS Lambda + Step Functions. Left real-time CICS transactions on mainframe (for now). Proved the concept in 90 days.

Results:

• Migrated 120K LOC of batch COBOL to serverless in 18 months (vs 24 months for failed rewrite)
• Reduced mainframe MIPS by 45% → saved $1.2M/year in IBM licensing
• Launched mobile banking features in 6 weeks (was impossible on mainframe)
• Board approved $15M phase 2 to migrate CICS transactions (based on proven success)

---

Section 11

Success Factors

• Access to retiring COBOL developers (interview them NOW before they leave)
• Realistic timeline expectations (mainframe migration = 3-5 years, not 12 months)
• Willingness to run dual systems during transition (hybrid is messy but necessary)
• Executive air cover for hard decisions (some COBOL devs won't transition - need to hire around them)
• Regulatory expertise (banks/insurance need SOX/PCI parallel run strategies)

---

Section 12

Decision Framework

When to proceed

• Your average COBOL developer age is 55+ and you have no succession plan for critical system knowledge
• Mainframe MIPS costs exceed $500K/year and are growing at 10%+ annually
• A previous big-bang COBOL rewrite attempt failed or was cancelled
• Regulatory auditors have flagged mainframe key-person dependencies as unacceptable risk
• An M&A transaction requires integrating or divesting a mainframe-dependent system within 18 months

When NOT to proceed

• Your COBOL codebase is under 50K lines with well-documented business logic — a targeted rewrite is feasible without formal assessment
• You have no executive sponsor with authority to approve multi-year migration budgets
• Your COBOL team has already retired and institutional knowledge is lost — different recovery approach needed
• You need real-time API integration added to mainframe — API gateway wrapping is faster than migration

Alternatives to consider

• Legacy Assessment: Full portfolio assessment needed before COBOL-specific migration planning — Best for: Organizations with mixed legacy portfolios needing prioritization before COBOL work
• Modernization Strategy: COBOL migration strategy requires broader organizational and technology roadmap alignment — Best for: Organizations where COBOL is one of several major legacy modernization challenges