Building a Cloud Migration Team: Roles, Skills, Staffing

Executive Summary

A cloud migration is not primarily a technology project — it is a people project. The wrong roles, a late start on upskilling, or staffing decisions left to chance will cause delays that cost more than the infrastructure itself. This article describes the six key roles every cloud migration team needs, how the staffing plan scales across Road.MAP phases, and which AWS certification paths deliver the fastest return on training investment — with concrete benchmarks for DACH enterprises.

Audience: CIOs, IT directors, and program managers planning an enterprise cloud migration in Germany who need to understand who to bring on board and when.

The Skills Gap as a Migration Bottleneck

According to IDC, the economic cost of cloud and digital skills gaps in Europe will exceed USD 5.5 trillion by 2026 (IDC, "Cloud Skills and Organizational Influence", 2022). In Germany, demographic pressures compound the effect: Bitkom estimates the skills shortage in the German IT sector at over 137,000 open positions (Bitkom, 2023).

The implication: organizations planning an AWS migration rarely have all the required skills in-house. Waiting for the perfect team to come together means waiting too long. The pragmatic path is a deliberate hybrid approach — internal upskilling for core competencies, an external partner for temporary specialist knowledge, and targeted hiring for permanent roles.

What typically remains missing is a concrete blueprint: which roles are needed when? Which certifications make sense? How large should the team be? Storm Reply's Road.MAP framework provides structured answers to all three questions.

Key Definitions: Core Roles at a Glance

Cloud Center of Excellence (CCoE)

An interdisciplinary team of cloud architects, security specialists, FinOps practitioners, and governance leads that sets standards, distributes best practices, and acts as an internal center of competence for all cloud topics. The CCoE is the permanent core organization after the migration project ends.

Migration Lead

The program management role responsible for timelines, stakeholder communication, and escalations. The Migration Lead does not need to be deeply technical — but must be able to bridge technology and business.

Application Owner

The functional owner of one or more applications. The Application Owner knows dependencies, users, SLAs, and business processes — and is indispensable during the assessment phase and at cutover decision points.

Cloud Architect

Designs the target architecture on AWS, defines landing zone standards, selects migration patterns (Rehost, Replatform, Refactor), and is responsible for technical consistency across all waves. Large projects often have multiple specialized architects (Network, Security, Data).

The 6 Key Roles in a Cloud Migration Team

Every enterprise migration needs the following six roles — scope and timing are determined by the staffing plan below.

Supplementary roles that may be added depending on scope: Data Engineer (for database migrations with AWS DMS), FinOps Analyst (for portfolios exceeding 100 workloads), Change Manager (for projects with significant works council involvement), and a Training Coordinator for the internal upskilling program.

Staffing Plan by Road.MAP Phase

The Road.MAP framework structures every enterprise migration into three main phases. Staffing needs scale significantly — from a small assessment team to a full-scale migration factory.

Phase 1: Assess (3–5 people, duration: 4–8 weeks)

The Assess phase focuses on discovery and inventory: which workloads exist, what dependencies are there, and which migration strategies apply?

1. Migration Lead (50% part-time) — project setup, stakeholder engagement, scope definition
2. Cloud Architect (50% part-time) — discovery tooling (AWS Migration Hub), target architecture sketch
3. 2–3 Application Owners (25–50% each) — providing application data, documenting dependencies

External support: Storm Reply typically provides 1–2 senior consultants in this phase for discovery tooling and assessment methodology.

Phase 2: Mobilize (8–12 people, duration: 8–16 weeks)

Mobilize builds the foundations: landing zone, security baseline, runbooks, and pilot migration. The team grows significantly because parallel workstreams (infrastructure, security, operations, migration factory training) run concurrently.

1. Migration Lead (full-time)
2. Cloud Architect (full-time) — landing zone implementation
3. Security Engineer (full-time) — IAM, SCPs, compliance framework
4. 2 Migration Engineers (full-time) — pilot wave, tooling setup
5. Cloud Operations Engineer (full-time) — monitoring, runbooks
6. 3–4 Application Owners (part-time) — wave 1 preparation
7. Training Coordinator (part-time) — setting up AWS Skill Builder learning paths

Phase 3: Migrate (15–25 people, duration: 3–18 months)

In the Migrate phase, multiple wave squads run in parallel. Each squad migrates 2–4 waves per month. Team size is directly tied to portfolio size and the target migration velocity.

1. Migration Lead + 1–2 Wave Coordinators
2. Cloud Architect (available as escalation point, no longer full-time)
3. 4–8 Migration Engineers (depending on number of parallel squads)
4. Security Engineer (part-time — reviews and incident response)
5. 2 Cloud Operations Engineers (full-time — monitoring, FinOps)
6. Application Owners (per wave — for cutover sign-offs)
7. FinOps Analyst (from month 2 of the Migrate phase)

Rule of thumb for scaling: each parallel wave squad needs 3–4 Migration Engineers and 1 Wave Coordinator. A squad can migrate 10–30 servers per wave, depending on complexity.

AWS Certification Paths for Migration Teams

AWS offers structured learning paths for all roles via AWS Skill Builder (skill.aws.amazon.com). The most relevant paths for migration teams in DACH:

For Migration Engineers and Application Owners

1. AWS Certified Cloud Practitioner — mandatory as a shared knowledge baseline (approx. 40 hours preparation)
2. AWS Certified SysOps Administrator – Associate — for all roles technically executing migrations
3. AWS Certified Advanced Networking – Specialty — for teams with complex hybrid network requirements

For Cloud Architects

1. AWS Certified Solutions Architect – Associate — entry point, ~80 hours
2. AWS Certified Solutions Architect – Professional — for lead architects, ~120 hours
3. AWS Migration Learning Path on Skill Builder — knowledge validation for migration-specific scenarios

For Security Engineers

1. AWS Certified Security – Specialty — required for all security roles
2. Supplementary: AWS Security Learning Path on Skill Builder (GuardDuty, Security Hub, IAM Access Analyzer)

For Operations and FinOps

1. AWS Certified DevOps Engineer – Professional — for Cloud Operations Engineers
2. AWS Certified Cloud Financial Management — for FinOps roles (Cost Explorer, Budgets, Savings Plans)

Storm Reply is an AWS Training Partner and can organize in-house private training sessions — including hands-on labs on real AWS accounts. This is particularly relevant for works-council-sensitive upskilling programs, as training measures may be subject to co-determination rights.

Upskilling vs. Hiring vs. Partner: Decision Matrix

There is no universally correct answer — but there are structured criteria for the decision. The following matrix helps CIOs and IT directors evaluate the three options by role:

Note on temporary employment arrangements: When external specialists are deployed under a temporary employment arrangement (Arbeitnehmerüberlassung / AÜG) — meaning they are functionally integrated and subject to direction — German law requires notification to the works council (BetrVG § 99) and imposes a maximum assignment duration of 18 months. Service contracts (Werkverträge) have different requirements but must not create a de facto employment arrangement. Storm Reply structures its engagements to maintain clear service contract boundaries.

Storm Reply as Enabler: Training, Staffing Models, and CCoE Build-Out

Storm Reply is an AWS Premier Consulting Partner and AWS Training Partner — a combination that enables technical project work and knowledge building to be directly linked.

Training-as-Enablement

In Road.MAP projects, migrations are not simply executed for the customer — Storm Reply works in a tandem model: an external expert and an internal employee share a role and its tasks. The internal employee learns through real project work, documents learnings in runbooks, and takes over the role by the third wave at the latest. This model reduces dependence on the external partner and accelerates internal capability development.

CCoE Bootstrapping

For organizations without an existing cloud organization, Storm Reply offers a structured CCoE bootstrapping engagement: within four to six weeks, governance structures, role definitions, escalation paths, and an initial AWS account structure are established. The CCoE is then progressively staffed with internal employees — supported by monthly office hours with Storm Reply architects.

Staffing Flexibility by Phase

Storm Reply offers different engagement models: from phase-bound project support (Assess: 2 FTEs, Mobilize: 4–6 FTEs, Migrate: scaling) to managed services after the migration, through to dedicated residency models where a Storm Reply architect is permanently embedded in the client organization. Residency is particularly suited for large portfolios (>500 workloads) or regulated industries with high security requirements.

Works Council and Co-Determination: What You Need to Know

In German organizations with a works council, team composition for cloud migration projects is not purely an operational matter — it has co-determination dimensions:

• Temporary employment (AÜG): Deploying temporary workers requires works council approval under BetrVG § 99. The works council may withhold approval under certain conditions. Plan lead time accordingly.
• Training measures (BetrVG § 98): When systematic upskilling is conducted — for example through AWS Skill Builder or external training — the works council has a right of input in selecting measures and the employees affected.
• Transfers and changes in responsibilities: Permanently reassigning an employee to a new cloud role may qualify as a transfer under BetrVG § 99.
• Introduction of monitoring systems: AWS monitoring tools such as CloudWatch or AWS Config may qualify as technical monitoring facilities (BetrVG § 87 Para. 1 No. 6) — particularly where employee activities on AWS accounts are logged.

Recommendation: involve the works council early — ideally already during the Assess phase. A shared roadmap for training and workforce planning reduces resistance and builds trust. Storm Reply supports the preparation of works council documentation and presentations.

Benefits and Challenges

Benefits of Structured Team Building

• Clear responsibilities reduce friction and duplicate work between teams
• Phase-appropriate staffing prevents over-engineering in early phases and resource shortages during Migrate
• Internal upskilling builds durable cloud competence that outlasts the project
• Early works council engagement prevents legal and organizational delays
• AWS Training Partner access via Storm Reply enables high-quality training without lengthy vendor selection

Typical Challenges

• Application Owner availability: This role is internally irreplaceable and cannot be substituted by an external partner — but these employees often have full-time day jobs. Solution: explicit time release agreements from the start of the project.
• Certification timelines: An AWS Professional certification requires 3–6 months of preparation alongside full-time work. Setting certifications as prerequisites for roles means planning for lead time.
• Attrition in the migration team: Cloud specialists are in demand — especially during an active migration project. Retention measures and clear career paths into the post-migration organization are essential.
• Knowledge transfer at project close: Without a structured handover, project knowledge leaves with the consultants. Runbooks, architecture documentation, and CCoE standards must be continuously maintained throughout the engagement.

Frequently Asked Questions

How many people does a cloud migration team need?

Team size depends on the Road.MAP phase: the Assess phase needs 3–5 people. Mobilize requires 8–12. The Migrate phase requires 15–25 people depending on portfolio size — distributed across multiple migration factory squads of 3–4 engineers each.

Which AWS certification matters most for a migration team?

For cloud architects, AWS Certified Solutions Architect – Professional is the most important. For Migration Engineers, AWS Certified SysOps Administrator – Associate. For all team members, AWS Certified Cloud Practitioner provides an essential shared knowledge baseline. AWS Skill Builder offers role-specific learning paths for structured preparation.

Does the works council need to be involved in team staffing?

Yes, in several dimensions. Temporary employment arrangements require works council approval under BetrVG § 99. Systematic upskilling is subject to co-determination under BetrVG § 98. Monitoring tools may qualify as technical monitoring facilities under BetrVG § 87 Para. 1 No. 6. Early engagement from the Assess phase is strongly recommended.

Upskilling, hiring, or partner — what is the best strategy?

A hybrid model is typically best: core competencies (cloud governance, security, FinOps) are built internally. Specialized migration knowledge and temporary capacity come from a partner. Hiring makes sense for permanently needed roles like Cloud Architect or Platform Engineer — particularly when the organization wants to build its own cloud capability.

Sources

• IDC: "Cloud Skills and Organizational Influence", 2022 — estimate of the economic cost of cloud skills gaps in Europe through 2026
• Bitkom Research: "IT Skills Shortage", 2023 — 137,000 open IT positions in Germany
• AWS: AWS Migration Acceleration Program (MAP) — role recommendations for migration teams
• AWS Skill Builder (skill.aws.amazon.com) — official learning paths and certification preparation
• BetrVG (German Works Constitution Act): §§ 87, 98, 99 — co-determination rights for training, temporary employment, and technical monitoring systems
• Storm Reply: Road.MAP Framework — phase model for enterprise cloud migrations, internal project statistics 2022–2024