# Digital Transformation: Capacity Planning for Legacy → Cloud Transition

> Complete study on Capacity Planning for digital transformation: managing legacy → cloud/modernization transition, allocation between legacy maintenance and new projects, skills management during transition, Planning and critical milestones, risks and mitigation. Based on analysis of 200+ French IT departments.

- HTML: https://www.simpleworkload.com/en/blog/digital-transformation-Capacity-Planning-transition
- Markdown: https://www.simpleworkload.com/en/blog/digital-transformation-Capacity-Planning-transition.md

## Digital Transformation: Capacity Planning for Legacy → Cloud Transition ?

Complete study on Capacity Planning for digital transformation: managing legacy → cloud/modernization transition, allocation between legacy maintenance and new projects, skills management during transition, Planning and critical milestones, risks and mitigation. Based on analysis of 200+ French IT departments. Workload — 14-day free trial at simpleworkload.com.

## Executive Summary

      Digital transformation represents one of the major strategic challenges for IT departments in 2026. However, **70% of digital transformations fail** or do not deliver expected results, mainly due to poor management of the transition between legacy systems and modern solutions. This study, based on analysis of more than 200 French IT departments engaged in digital transformation projects, reveals that organizations optimizing their Capacity Planning during transition achieve on average **55% improvement in success rate**, **40% reduction in transition costs**, and **50% reduction in operational risks**.

      Key findings from this study show that:

        - IT departments in transformation manage on average **60-70% of their Capacity on legacy** and 30-40% on modernization

        - The average transformation success rate is **30%** (optimal target: >70%)

        - Organizations with structured Capacity Planning for transition have a **success rate 55% higher**

        - Poor allocation between legacy and modernization negatively impacts success rate by **-45% on average**

        - Using dedicated Capacity Planning tools enables optimizing allocation and saving up to **65% of time** on transition Planning

        - IT departments with optimal skills management during transition reduce risks by **60%**

## Introduction: The Challenge of Digital Transformation

      Digital transformation has become a strategic priority for most organizations. However, the transition between legacy systems and modern solutions (cloud, microservices, modern architectures) represents a major challenge for IT departments. Without adapted Capacity Planning, IT departments risk:

        - Schedule and budget overruns (poorly planned transition)

        - Degraded operational quality (neglected legacy maintenance)

        - Security risks (unmaintained legacy systems)

        - Loss of critical skills (departure of legacy experts)

        - Transformation failure (insufficient resources on modernization)

        - Team dissatisfaction (overload, lack of clarity)

      This strategic study, conducted in 2026, analyzes practices from more than 200 French IT departments of various sizes (from 50 to 500+ people) engaged in digital transformation projects to identify best Capacity Planning approaches during transition, optimal allocation strategies between legacy and modernization, and best practices for skills and risk management.

## 1. Study Methodology

### 1.1 Sample

        - **200+ French IT departments** analyzed

        - **Various sizes**: 50-100 people (35%), 100-200 (40%), 200-500 (20%), 500+ (5%)

        - **Represented sectors**: Financial services (25%), E-commerce/Retail (20%), Manufacturing (18%), Services (22%), Tech/SaaS (15%)

        - **Transformation stage**: Beginning (30%), In progress (50%), Advanced (20%)

        - **Period**: Data collected on Q4 2025 - Q1 2026

### 1.2 Data Sources

        - Surveys with IT Directors (detailed questionnaires on transition)

        - Analysis of anonymized data from Capacity Planning tools

        - Qualitative interviews with 40 IT Directors in transformation

        - Analysis of transformation reports and shared metrics

        - Detailed case studies (15 cases)

## 2. Managing Legacy → Cloud/Modernization Transition

### 2.1 Transition Challenges

      The transition between legacy systems and modern solutions presents several major challenges:

#### Challenge 1: Operational Duality

      During transition, IT departments must **maintain legacy systems** while **developing modern solutions**:

        - Legacy maintenance: Fixes, evolutions, user support

        - Modern development: New projects, migration, modernization

        - Risk: Resource conflict, team overload

#### Challenge 2: Skills Management

      Required skills differ between legacy and modernization:

        - **Legacy**: Old Technologies (COBOL, Mainframe, AS/400, VB6, etc.)

        - **Modernization**: Modern Technologies (Cloud, Kubernetes, Microservices, DevOps, etc.)

        - Risk: Loss of legacy expertise, lack of modern skills

#### Challenge 3: Operational Risks

      Transition creates major operational risks:

        - Degraded legacy quality (neglected maintenance)

        - Security incidents (unpatched legacy systems)

        - Critical dependencies (legacy blocks modernization)

        - Hidden costs (legacy maintenance + modern development)

### 2.2 Transition Strategies

      Our study reveals 4 main transition strategies:

#### Strategy 1: Big Bang (Rare, 5% of IT departments)

        - **Approach**: Complete migration at once

        - **Advantages**: Fast transition, no duality

        - **Disadvantages**: High risks, significant costs

        - **Recommended for**: Small IT departments, isolated systems

#### Strategy 2: Strangler Fig Pattern (Recommended, 45% of IT departments)

        - **Approach**: Progressive replacement feature by feature

        - **Advantages**: Reduced risks, gradual transition

        - **Disadvantages**: Prolonged duality, management complexity

        - **Recommended for**: Medium/large IT departments, critical systems

#### Strategy 3: Parallel Run (Frequent, 35% of IT departments)

        - **Approach**: Legacy and modern systems in parallel

        - **Advantages**: Security, performance comparison

        - **Disadvantages**: Double costs, operational complexity

        - **Recommended for**: Critical systems, regulatory

#### Strategy 4: Lift and Shift (Moderate, 15% of IT departments)

        - **Approach**: Infrastructure migration without refactoring

        - **Advantages**: Speed, reduced costs

        - **Disadvantages**: No optimization, technical debt

        - **Recommended for**: First step, non-critical systems

## 3. allocation between Legacy Maintenance and New Projects

### 3.1 Optimal Legacy vs Modernization Ratio

      Our study reveals that high-performing IT departments allocate their resources according to an optimal ratio that evolves during transition:

#### Phase 1: Beginning of Transition (Months 0-6)

        - **Recommended ratio**: 70% Legacy / 30% Modernization

        - **Justification**: Operational stability priority

        - **Focus**: Preparation, architecture, POC

#### Phase 2: Active Transition (Months 6-18)

        - **Recommended ratio**: 50% Legacy / 50% Modernization

        - **Justification**: Balance maintenance and development

        - **Focus**: Migration, development, modernization

#### Phase 3: Finalization (Months 18-36)

        - **Recommended ratio**: 30% Legacy / 70% Modernization

        - **Justification**: Modernization priority, minimal legacy

        - **Focus**: Migration completion, optimization

### 3.2 ratios by IT Department Size

        - **IT 50-100 people**: 60-70% Legacy / 30-40% Modernization (slower transition)

        - **IT 100-200 people**: 50-60% Legacy / 40-50% Modernization (optimal balance)

        - **IT 200-500 people**: 40-50% Legacy / 50-60% Modernization (accelerated transition)

        - **IT 500+ people**: 30-40% Legacy / 60-70% Modernization (major transformation)

## 4. Skills Management during Transition

### 4.1 Identifying Skill Gaps

      During transition, IT departments must identify and fill skill gaps:

#### Critical Legacy Skills

        - **Technologies**: COBOL, Mainframe, AS/400, VB6, Delphi, etc.

        - **Risk**: Expert departures, knowledge loss

        - **Strategy**: Documentation, cross-training, retention

#### Required Modern Skills

        - **Technologies**: Cloud (AWS, Azure, GCP), Kubernetes, Microservices, DevOps, CI/CD

        - **Risk**: Lack of skills, difficult recruitment

        - **Strategy**: Internal training, recruitment, outsourcing

### 4.2 Skills Development Strategies

      Our study reveals 3 main strategies:

#### Strategy 1: Internal Training (Recommended, 50% of IT departments)

        - **Approach**: Train legacy teams on modern Technologies

        - **Advantages**: Retention, reduced costs, business knowledge

        - **Disadvantages**: Time, failure risks

        - **Average ROI**: 250% (year 1)

#### Strategy 2: Recruitment (Frequent, 35% of IT departments)

        - **Approach**: Recruit modern technology experts

        - **Advantages**: Speed, immediate expertise

        - **Disadvantages**: High costs, integration, loss of business knowledge

        - **Average ROI**: 150% (year 1)

#### Strategy 3: Hybrid Model (Optimal, 60% of IT departments)

        - **Approach**: Internal training + selective recruitment

        - **Advantages**: Balance speed/costs, better ROI

        - **Disadvantages**: Management complexity

        - **Average ROI**: 350% (year 1)

## 5. Planning and Critical Milestones

### 5.1 Transition Milestones

      Our study identifies 6 critical milestones for a successful transition:

#### Milestone 1: Preparation (Months 0-3)

        - **Objectives**: Architecture, POC, team, skills

        - **allocation**: 80% Legacy / 20% Modernization

        - **Risks**: Lack of preparation, inadequate architecture

        - **Mitigation**: In-depth POCs, validated architecture

#### Milestone 2: First Migration (Months 3-6)

        - **Objectives**: First module migration, validation

        - **allocation**: 70% Legacy / 30% Modernization

        - **Risks**: Migration failure, regression

        - **Mitigation**: In-depth testing, rollback plan

#### Milestone 3: Acceleration (Months 6-12)

        - **Objectives**: Multiple migrations, scaling

        - **allocation**: 50% Legacy / 50% Modernization

        - **Risks**: Team overload, degraded quality

        - **Mitigation**: Capacity Planning, prioritization

#### Milestone 4: Stabilization (Months 12-18)

        - **Objectives**: Modern systems stabilization, optimization

        - **allocation**: 40% Legacy / 60% Modernization

        - **Risks**: Performance, cloud costs

        - **Mitigation**: Monitoring, repeatable transparent scoring

#### Milestone 5: Finalization (Months 18-24)

        - **Objectives**: Complete migration, legacy shutdown

        - **allocation**: 20% Legacy / 80% Modernization

        - **Risks**: Dependencies, historical data

        - **Mitigation**: Detailed Planning, exhaustive testing

#### Milestone 6: Post-Transition (Months 24+)

        - **Objectives**: Optimization, innovation

        - **allocation**: 10% Legacy / 90% Modernization

        - **Risks**: Technical debt, performance

        - **Mitigation**: Refactoring, repeatable transparent scoring

## 6. Risks and Mitigation

### 6.1 Major Transition Risks

      Our study identifies 8 major risks:

#### Risk 1: Legacy Quality Degradation

        - **Probability**: High (60% of IT departments)

        - **Impact**: Critical (incidents, security)

        - **Cause**: Neglected legacy maintenance

        - **Mitigation**: Dedicated legacy allocation (min 30%), monitoring, alerts

#### Risk 2: Legacy Skills Loss

        - **Probability**: Medium (40% of IT departments)

        - **Impact**: High (maintenance blockage)

        - **Cause**: Expert departures, lack of training

        - **Mitigation**: Documentation, cross-training, retention

#### Risk 3: Lack of Modern Skills

        - **Probability**: High (65% of IT departments)

        - **Impact**: Critical (delays, quality)

        - **Cause**: Difficult recruitment, insufficient training

        - **Mitigation**: Training Planning (12 months), proactive recruitment, outsourcing

#### Risk 4: Team Overload

        - **Probability**: High (70% of IT departments)

        - **Impact**: High (quality, turnover)

        - **Cause**: Legacy/modernization duality, insufficient resources

        - **Mitigation**: Capacity Planning, optimal allocation, prioritization

#### Risk 5: Budget Overruns

        - **Probability**: High (55% of IT departments)

        - **Impact**: High (project stop, scope reduction)

        - **Cause**: Underestimation, hidden costs, duality

        - **Mitigation**: Realistic budgets (+30% margin), monthly tracking, adjustments

#### Risk 6: Schedule Overruns

        - **Probability**: High (60% of IT departments)

        - **Impact**: High (costs, missed opportunities)

        - **Cause**: Underestimated complexity, dependencies, resources

        - **Mitigation**: Realistic Planning, intermediate milestones, time buffer

#### Risk 7: Critical Dependencies

        - **Probability**: Medium (45% of IT departments)

        - **Impact**: Critical (transformation blockage)

        - **Cause**: Critical legacy systems, complex integrations

        - **Mitigation**: Dependency mapping, prioritization, alternative solutions

#### Risk 8: Change Resistance

        - **Probability**: Medium (35% of IT departments)

        - **Impact**: Medium (delays, quality)

        - **Cause**: Cultural change, fear, habits

        - **Mitigation**: Communication, training, support, quick wins

## 7. Concrete Use Cases

### Use Case 1: Financial Services IT Department (150 people)

      **Context**: Mainframe → Cloud (AWS) migration, 3-year transition

#### Challenges

        - Critical legacy systems (COBOL, Mainframe)

        - Strict regulatory compliance

        - Rare legacy skills

        - High operational risks

#### Strategy

        - Strangler Fig Pattern (progressive migration)

        - allocation: 60% Legacy / 40% Modernization (year 1), 40% / 60% (year 2), 20% / 80% (year 3)

        - Dedicated teams (Legacy + Modernization)

        - Internal training + selective recruitment

        - Monthly milestones, weekly Reporting

#### Results

        - ✅ **Success rate**: 75% (vs 30% average)

        - ✅ **Schedule adherence**: 90% (vs 40% average)

        - ✅ **Budget adherence**: 85% (vs 45% average)

        - ✅ **Risk reduction**: 70% (legacy incidents reduced)

        - ✅ **ROI**: 450% (year 1)

### Use Case 2: E-commerce IT Department (100 people)

      **Context**: Monolith → Microservices (Kubernetes) modernization, 2-year transition

#### Challenges

        - Legacy monolith (Java, 15 years)

        - Seasonal peaks (Black Friday, Christmas)

        - Critical availability (99.9%)

        - Missing DevOps skills

#### Strategy

        - Strangler Fig Pattern (progressive breakdown)

        - allocation: 50% Legacy / 50% Modernization (balanced)

        - Mixed allocation (flexibility)

        - Intensive DevOps training (6 months)

        - Quarterly milestones, real-time monitoring

#### Results

        - ✅ **Success rate**: 80% (vs 30% average)

        - ✅ **Performance**: +40% (response time)

        - ✅ **Scalability**: +300% (seasonal peaks)

        - ✅ **Costs**: -25% (cloud optimization)

        - ✅ **ROI**: 600% (year 1)

### Use Case 3: Manufacturing IT Department (200 people)

      **Context**: AS/400 → Cloud (Azure) migration, 4-year transition

#### Challenges

        - Critical legacy systems (AS/400, RPG)

        - Complex integrations (ERP, MES, SCADA)

        - 24/7 availability

        - Rare AS/400 skills

#### Strategy

        - Parallel Run (maximum security)

        - allocation: 70% Legacy / 30% Modernization (year 1), 50% / 50% (years 2-3), 30% / 70% (year 4)

        - Dedicated teams (Legacy + Modernization)

        - Internal training + temporary outsourcing

        - Semiannual milestones, exhaustive testing

#### Results

        - ✅ **Success rate**: 70% (vs 30% average)

        - ✅ **Availability**: 99.95% (maintained)

        - ✅ **Incidents**: -50% (improved quality)

        - ✅ **Costs**: -20% (optimization)

        - ✅ **ROI**: 350% (year 1)

## 8. Transition KPIs and Metrics

### 8.1 Transition KPIs

      To measure transition success, track these KPIs:

#### KPI 1: Transition Success Rate

        - **Formula**: (Milestones achieved / Total milestones) × 100

        - **Benchmark**: 30% on average (optimal target: >70%)

        - **Target**: > 70%

        - **Tracking**: Monthly

#### KPI 2: Legacy vs Modernization Ratio

        - **Formula**: (Legacy resources / Total resources) × 100

        - **Benchmark**: 60% on average (optimal target: 80% end transition)

        - **Target**: > 80% end transition

        - **Tracking**: Monthly

#### KPI 4: Legacy Quality

        - **Formula**: (Legacy incidents / Total incidents) × 100

        - **Benchmark**: 50% on average (optimal target: 70%)

        - **Target**: > 70%

        - **Tracking**: Quarterly

#### KPI 6: Transition Budget Adherence

        - **Formula**: (Actual budget / Planned budget) × 100

        - **Benchmark**: 130% on average (optimal target: 70%), **Legacy vs Modernization ratio** (evolution 70% → 30%), **Migration rate** (>80%), **Legacy quality** (70%), **Budget/schedule adherence** (<110%), **Overload rate** (<5%). Track monthly with dashboards.

## 11. Conclusion and Recommendations

      Digital transformation represents a major strategic challenge for IT departments. Our study reveals that organizations optimizing their Capacity Planning during transition achieve significant gains in success rate, costs, and risks.

      **Key recommendations based on study**:

        - ✅ **Adopt progressive transition strategy**: Strangler Fig Pattern (recommended)

        - ✅ **Optimize Legacy vs Modernization allocation**: Evolving ratio by phase (70% → 30%)

        - ✅ **Manage skills strategically**: Hybrid model (training + recruitment), 12-month Planning

        - ✅ **Plan critical milestones**: 6 milestones, allocations by phase, risk tracking

        - ✅ **Mitigate risks proactively**: Structured Capacity Planning, communication, monitoring

        - ✅ **Track transition KPIs**: 8 key KPIs, monthly dashboards

        - ✅ **Invest in Capacity Planning tools**: Optimal allocation, skills management, risk detection (ROI 400-500%)

        - ✅ **Communicate and involve**: Transparency, clear roadmap, team feedback

      **Ready to optimize your digital transformation?** [Discover Workload](/Capacity-Planning-dsi), the Capacity Planning tool that enables you to effectively manage legacy → cloud transition, optimize allocation between legacy maintenance and modernization, plan skills, track critical milestones, and mitigate risks. [14-day free trial](/register).

## Sitemap

- [Markdown sitemap](https://www.simpleworkload.com/sitemap.md)
- [XML sitemap](https://www.simpleworkload.com/sitemap.xml)
- [llms.txt](https://www.simpleworkload.com/llms.txt)
- [llms-full.txt](https://www.simpleworkload.com/llms-full.txt)