{"id":75016,"date":"2026-04-16T09:43:45","date_gmt":"2026-04-16T09:43:45","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/lead-cloud-migration-specialist-role-blueprint-responsibilities-skills-kpis-and-career-path\/"},"modified":"2026-04-16T09:43:45","modified_gmt":"2026-04-16T09:43:45","slug":"lead-cloud-migration-specialist-role-blueprint-responsibilities-skills-kpis-and-career-path","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/lead-cloud-migration-specialist-role-blueprint-responsibilities-skills-kpis-and-career-path\/","title":{"rendered":"Lead Cloud Migration Specialist: Role Blueprint, Responsibilities, Skills, KPIs, and Career Path"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">1) Role Summary<\/h2>\n\n\n\n<p>The <strong>Lead Cloud Migration Specialist<\/strong> is a senior individual contributor who plans and drives complex application, data, and infrastructure migrations from on-premises or hosted environments into public cloud and hybrid cloud platforms. The role combines deep technical migration expertise with program-level orchestration\u2014ensuring migrations are secure, reliable, cost-aware, and aligned to platform standards and business outcomes.<\/p>\n\n\n\n<p>This role exists in software companies and IT organizations because cloud migration is both <strong>a transformation program<\/strong> (changing operating models, patterns, and controls) and <strong>an engineering execution problem<\/strong> (moving workloads with minimal risk, downtime, and regression). The Lead Cloud Migration Specialist creates business value by accelerating time-to-cloud, reducing technical debt, improving service resilience, enabling faster product delivery, and optimizing infrastructure cost and compliance posture.<\/p>\n\n\n\n<p>Role horizon: <strong>Current<\/strong> (widely established across IT organizations running modernization, data center exit, or platform adoption programs).<\/p>\n\n\n\n<p>Typical interactions include: Cloud Platform Engineering, SRE\/Operations, Security\/GRC, Network Engineering, Application Engineering, Data Engineering, Enterprise Architecture, FinOps, Product\/Program Management, and key business owners for the migrating systems.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">2) Role Mission<\/h2>\n\n\n\n<p><strong>Core mission:<\/strong><br\/>\nDeliver predictable, secure, and efficient migrations of workloads to the target cloud environment\u2014using standardized patterns, automation, and governance\u2014while minimizing business disruption and improving long-term operability.<\/p>\n\n\n\n<p><strong>Strategic importance to the company:<\/strong><br\/>\nCloud migration is often a top-3 technology initiative because it directly impacts cost structure, product velocity, security posture, scalability, and the ability to adopt modern platform capabilities (managed services, elastic scaling, automation, advanced observability, and AI-ready data foundations). The Lead Cloud Migration Specialist ensures the organization achieves cloud adoption outcomes without accumulating \u201ccloud-shaped technical debt.\u201d<\/p>\n\n\n\n<p><strong>Primary business outcomes expected:<\/strong>\n&#8211; Achieve migration targets (apps, services, data stores, and infrastructure) on schedule with controlled risk.\n&#8211; Reduce outage risk and improve reliability during and after cutover.\n&#8211; Standardize migration approaches to lower per-workload effort and increase throughput.\n&#8211; Improve security, compliance, and audit readiness of migrated workloads.\n&#8211; Improve cloud unit economics through right-sizing, licensing optimization, and architectural choices.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">3) Core Responsibilities<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Strategic responsibilities<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Define migration strategy and sequencing<\/strong> for portfolios (waves, dependency grouping, and criticality tiers), aligning with platform readiness and business constraints.<\/li>\n<li><strong>Select migration patterns per workload<\/strong> (rehost, replatform, refactor, retire, retain) with documented rationale and total cost of ownership (TCO) implications.<\/li>\n<li><strong>Establish repeatable migration frameworks<\/strong> (playbooks, templates, automation, landing-zone adherence) to improve throughput and reduce variance.<\/li>\n<li><strong>Partner with Enterprise Architecture<\/strong> to ensure target architectures, reference patterns, and guardrails are practical and adoptable.<\/li>\n<li><strong>Contribute to the cloud roadmap<\/strong> by identifying platform capabilities required for upcoming migration waves (networking, identity, observability, secrets, CI\/CD, data services).<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Operational responsibilities<\/h3>\n\n\n\n<ol class=\"wp-block-list\" start=\"6\">\n<li><strong>Lead end-to-end migration execution<\/strong> for a set of workloads: discovery, assessment, remediation planning, build, migration, validation, cutover, and hypercare.<\/li>\n<li><strong>Coordinate migration wave planning<\/strong> with program\/project managers, including integrated timelines, checkpoints, and risk management.<\/li>\n<li><strong>Own migration runbooks<\/strong> and coordinate dry runs to reduce cutover uncertainty.<\/li>\n<li><strong>Drive hypercare and stabilization<\/strong> post-cutover, ensuring operational readiness, alert tuning, and incident response alignment.<\/li>\n<li><strong>Manage migration backlogs<\/strong> (technical tasks, remediation items, access needs, firewall rules, pipeline changes) and remove blockers through escalation paths.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Technical responsibilities<\/h3>\n\n\n\n<ol class=\"wp-block-list\" start=\"11\">\n<li><strong>Perform workload discovery and dependency mapping<\/strong>, using tools and engineering judgment to identify upstream\/downstream systems, data flows, and latency-sensitive integrations.<\/li>\n<li><strong>Design and implement landing-zone compliant connectivity<\/strong> (VPC\/VNet design alignment, routing, DNS, private connectivity, load balancing, firewall\/security group rules).<\/li>\n<li><strong>Execute data migration approaches<\/strong> (online replication, batch transfer, database migration services, storage sync) with integrity validation and rollback plans.<\/li>\n<li><strong>Implement infrastructure-as-code<\/strong> for migrated components and shared migration scaffolding (networking modules, IAM roles, baseline policies, logging).<\/li>\n<li><strong>Modernize operational capabilities<\/strong> for migrated workloads: monitoring\/observability, backup\/restore, patching approach, secrets management, and disaster recovery alignment.<\/li>\n<li><strong>Optimize workloads post-migration<\/strong> through right-sizing, autoscaling, storage tiering, and managed service adoption where appropriate.<\/li>\n<li><strong>Ensure secure identity and access design<\/strong> (least privilege IAM, service principals, workload identities, privileged access workflows).<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Cross-functional or stakeholder responsibilities<\/h3>\n\n\n\n<ol class=\"wp-block-list\" start=\"18\">\n<li><strong>Translate technical migration decisions for non-technical stakeholders<\/strong>, including risk, downtime windows, and cost implications.<\/li>\n<li><strong>Partner with application teams<\/strong> to remediate code\/config issues (TLS changes, OS dependencies, hard-coded endpoints, legacy auth).<\/li>\n<li><strong>Coordinate with Security, Risk, and Compliance<\/strong> to ensure controls are implemented and evidence is produced for audits (logging, encryption, access reviews).<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Governance, compliance, or quality responsibilities<\/h3>\n\n\n\n<ol class=\"wp-block-list\" start=\"21\">\n<li><strong>Implement migration quality gates<\/strong> (pre-migration readiness, cutover go\/no-go criteria, post-migration validation, operational acceptance).<\/li>\n<li><strong>Maintain migration documentation and evidence<\/strong> (architecture diagrams, change records, test results, rollback plans, signoffs).<\/li>\n<li><strong>Ensure policy adherence<\/strong> to data residency, encryption standards, vulnerability management, and change management requirements.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Leadership responsibilities (Lead scope\u2014primarily IC leadership)<\/h3>\n\n\n\n<ol class=\"wp-block-list\" start=\"24\">\n<li><strong>Provide technical leadership and mentorship<\/strong> to migration engineers and application teams on patterns, tooling, and troubleshooting.<\/li>\n<li><strong>Set technical direction for migration squads<\/strong> (standards, checklists, definition of done) and review\/approve key migration designs.<\/li>\n<li><strong>Lead major cutover events<\/strong> as technical incident commander or cutover lead, coordinating cross-team execution and communications.<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">4) Day-to-Day Activities<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Daily activities<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Triage migration blockers (network routes, IAM permissions, pipeline failures, DNS cutover issues).<\/li>\n<li>Review migration plans and runbooks for upcoming cutovers; refine rollback steps.<\/li>\n<li>Pair with application teams on remediation items (dependency upgrades, config externalization, secrets integration).<\/li>\n<li>Validate infrastructure-as-code changes and review pull requests for landing zone compliance.<\/li>\n<li>Monitor migration environments and hypercare dashboards for newly migrated workloads.<\/li>\n<li>Coordinate with Security on exceptions, findings remediation, or control evidence requests.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Weekly activities<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Run migration wave planning sessions: dependency review, schedule alignment, readiness checks.<\/li>\n<li>Present status updates: progress against plan, risks, upcoming cutovers, decision requests.<\/li>\n<li>Conduct architecture\/design reviews for complex migrations (stateful services, legacy databases, tightly-coupled integrations).<\/li>\n<li>Analyze migration throughput and bottlenecks; propose improvements (automation, templates, enabling platform features).<\/li>\n<li>Hold technical office hours for application teams migrating in the next 2\u20136 weeks.<\/li>\n<li>Participate in FinOps reviews for cost anomalies and post-migration optimization opportunities.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Monthly or quarterly activities<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Refresh migration factory metrics: lead time, success rate, rollback frequency, defects, cost outcomes.<\/li>\n<li>Update portfolio migration strategy based on learnings (pattern selection, sequencing changes, dependency realities).<\/li>\n<li>Conduct post-migration retrospectives across squads; publish playbook updates and new templates.<\/li>\n<li>Align with platform teams on upcoming capabilities needed (private endpoints, managed DB options, central logging enhancements).<\/li>\n<li>Support quarterly resilience and DR exercises for migrated Tier-1 services.<\/li>\n<li>Contribute to audit readiness activities (control testing, evidence collection improvements).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Recurring meetings or rituals<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Migration wave standup (2\u20133x\/week during active waves).<\/li>\n<li>Go\/No-Go cutover checkpoint (per migration, often 48\u201372 hours prior).<\/li>\n<li>Change Advisory Board (CAB) \/ change management forum (weekly, context-specific).<\/li>\n<li>Architecture Review Board (bi-weekly\/monthly depending on governance model).<\/li>\n<li>Incident review \/ postmortems for migration-related outages (as needed).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Incident, escalation, or emergency work (when relevant)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Lead troubleshooting during cutover when unexpected behavior occurs (latency spikes, auth failures, DNS propagation issues).<\/li>\n<li>Execute rollback if validation gates fail and business impact is imminent.<\/li>\n<li>Coordinate emergency access requests (break-glass) following privileged access procedures.<\/li>\n<li>Act as escalation point for migration-related incidents during hypercare, coordinating with SRE\/Operations.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">5) Key Deliverables<\/h2>\n\n\n\n<p><strong>Migration planning and governance<\/strong>\n&#8211; Cloud migration strategy for assigned portfolio segment (wave plan, pattern selection, sequencing rationale).\n&#8211; Workload assessment reports (dependencies, risk tiering, readiness scoring, remediation backlog).\n&#8211; Cutover plans and runbooks (step-by-step actions, validation checks, comms plan, rollback plan).\n&#8211; Go\/No-Go criteria and signoff artifacts (operational acceptance, security acceptance, business owner acceptance).<\/p>\n\n\n\n<p><strong>Technical architecture and implementation<\/strong>\n&#8211; Target-state architecture diagrams (logical and physical) aligned to landing zone standards.\n&#8211; Infrastructure-as-code modules and environment definitions (network, IAM, compute, storage, logging).\n&#8211; Connectivity and integration designs (DNS, routing, private connectivity, API gateway\/LB patterns).\n&#8211; Data migration plans and validation scripts (checksums, row counts, reconciliation approach).\n&#8211; Observability implementation pack (dashboards, alerts, SLOs, logging\/trace configuration).<\/p>\n\n\n\n<p><strong>Operational readiness<\/strong>\n&#8211; Operational handover documentation (support model, escalation paths, runbooks, on-call readiness).\n&#8211; DR\/backup configuration documentation and evidence (RPO\/RTO mapping, test results).\n&#8211; Post-migration optimization report (right-sizing recommendations, reserved capacity plans, service substitutions).<\/p>\n\n\n\n<p><strong>Continuous improvement<\/strong>\n&#8211; Migration playbooks and templates (checklists, standardized test plans, preflight scripts).\n&#8211; Automation pipelines for common migration tasks (agent deployment, config validation, drift detection).\n&#8211; Knowledge base articles and enablement materials for app teams (patterns, pitfalls, FAQs).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">6) Goals, Objectives, and Milestones<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">30-day goals (onboarding and baseline control)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Understand the organization\u2019s cloud landing zone, reference architectures, and governance gates.<\/li>\n<li>Review the current migration portfolio and categorize workloads by complexity and risk.<\/li>\n<li>Establish working relationships with Platform Engineering, Security, Network, SRE, and key application owners.<\/li>\n<li>Lead at least one workload assessment end-to-end and produce a migration plan with risks and dependencies.<\/li>\n<li>Identify the top 3\u20135 systemic blockers slowing migration throughput (e.g., IAM request latency, network approvals, missing platform capabilities).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">60-day goals (execution and repeatability)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Lead 2\u20134 migrations (depending on complexity), including at least one stateful component (database, queue, file store).<\/li>\n<li>Standardize cutover runbook format and validation checklist across migration squads.<\/li>\n<li>Implement or improve at least one migration automation asset (IaC module, preflight check tool, CI\/CD template).<\/li>\n<li>Reduce variance in readiness assessments by implementing a consistent scoring model and evidence requirements.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">90-day goals (predictability and optimization)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Demonstrate predictable migration delivery: clear plans, low rework, stable cutovers.<\/li>\n<li>Establish post-migration optimization workflow with FinOps (cost baseline, anomaly alerts, right-sizing cadence).<\/li>\n<li>Improve hypercare outcomes: reduce incident rate for migrated workloads and shorten stabilization time.<\/li>\n<li>Mentor at least 2 engineers\/teams on migration patterns and operational readiness expectations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6-month milestones (scale and governance maturity)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Increase migration throughput through standardization and automation (measurable reduction in per-workload effort).<\/li>\n<li>Implement migration quality gates and ensure &gt;90% adherence without excessive bureaucracy.<\/li>\n<li>Contribute to platform improvements that remove recurring blockers (central logging, secrets integration patterns, private connectivity).<\/li>\n<li>Establish a validated approach for complex migrations (e.g., mainline database migration pattern, blue\/green cutover model).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12-month objectives (business outcomes and transformation impact)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Achieve portfolio-level migration targets for assigned domain with high success rate and low rollback frequency.<\/li>\n<li>Deliver measurable improvements in reliability (SLO attainment) for migrated Tier-1 services.<\/li>\n<li>Demonstrate cost and performance improvements through modernization (managed services, autoscaling, right-sizing).<\/li>\n<li>Mature the organization\u2019s \u201cmigration factory\u201d to reduce time-to-cloud and increase confidence from business stakeholders.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Long-term impact goals (beyond 12 months)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Enable data center exit \/ hosting contract reduction through complete workload transition and decommissioning.<\/li>\n<li>Institutionalize cloud-native operational practices (IaC-first, SRE-aligned monitoring, automated compliance evidence).<\/li>\n<li>Reduce \u201cshadow infrastructure\u201d and configuration drift through guardrails and self-service patterns.<\/li>\n<li>Increase organizational capability so that app teams can execute standard migrations with minimal specialist involvement.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Role success definition<\/h3>\n\n\n\n<p>Success is defined by <strong>secure, stable migrations delivered predictably<\/strong>, with clear stakeholder buy-in, minimal business disruption, measurable cost and reliability outcomes, and reusable patterns that improve future migrations.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What high performance looks like<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Migration plans are realistic, dependency-aware, and consistently executed with low surprises at cutover.<\/li>\n<li>The Lead is sought out for solving the hardest problems (state, identity, network complexity) and for improving the system (automation and standards), not just heroics.<\/li>\n<li>Stakeholders trust the role\u2019s risk calls, timelines, and technical direction.<\/li>\n<li>Post-migration operational outcomes improve rather than regress (alerts, incident frequency, cost stability).<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">7) KPIs and Productivity Metrics<\/h2>\n\n\n\n<p>The metrics below are designed for practical use in quarterly business reviews (QBRs), program steering committees, and engineering performance management. Targets vary by baseline maturity and workload complexity; example benchmarks assume a mid-to-large organization running multiple parallel migration waves.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Metric name<\/th>\n<th>What it measures<\/th>\n<th>Why it matters<\/th>\n<th>Example target \/ benchmark<\/th>\n<th>Frequency<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Workloads migrated (count)<\/td>\n<td>Number of workloads\/services migrated to target cloud and accepted<\/td>\n<td>Measures throughput and portfolio progress<\/td>\n<td>3\u201310\/month (varies widely by complexity)<\/td>\n<td>Weekly \/ Monthly<\/td>\n<\/tr>\n<tr>\n<td>Migration lead time<\/td>\n<td>Time from \u201cassessment complete\u201d to \u201cproduction cutover complete\u201d<\/td>\n<td>Predictability and efficiency of delivery<\/td>\n<td>Median 4\u20138 weeks for moderate apps<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>On-time cutover rate<\/td>\n<td>% of cutovers executed as scheduled<\/td>\n<td>Planning quality and dependency management<\/td>\n<td>&gt;85%<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Cutover success rate<\/td>\n<td>% of cutovers without rollback<\/td>\n<td>Direct indicator of migration execution quality<\/td>\n<td>&gt;95% for standard patterns<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Rollback frequency<\/td>\n<td>Rollbacks per cutover<\/td>\n<td>Measures risk, validation quality, and readiness<\/td>\n<td>&lt;5%<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Sev1\/Sev2 incidents in hypercare<\/td>\n<td>Incidents attributable to migration within hypercare window<\/td>\n<td>Reflects stability and operational readiness<\/td>\n<td>Downward trend; &lt;0.2 Sev1 per migration wave<\/td>\n<td>Weekly \/ Monthly<\/td>\n<\/tr>\n<tr>\n<td>Time to stabilize<\/td>\n<td>Time from cutover to meeting steady-state SLO\/alert levels<\/td>\n<td>Measures operational maturity and handover quality<\/td>\n<td>&lt;2 weeks for standard apps<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Defect leakage rate<\/td>\n<td>Post-cutover defects not detected in validation<\/td>\n<td>Measures test rigor and gating quality<\/td>\n<td>&lt;10% of issues found after cutover<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Change failure rate (DORA-aligned)<\/td>\n<td>% of migration changes causing service impairment<\/td>\n<td>Reliability of release\/change practices<\/td>\n<td>&lt;15% (target depends on baseline)<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Compliance control pass rate<\/td>\n<td>% of required controls implemented and evidenced (logging, encryption, access reviews)<\/td>\n<td>Audit readiness and risk reduction<\/td>\n<td>&gt;95%<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Landing zone adherence<\/td>\n<td>% of workloads meeting platform standards (network, tagging, logging, IAM)<\/td>\n<td>Reduces long-term support cost and risk<\/td>\n<td>&gt;90%<\/td>\n<td>Monthly \/ Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Cost variance vs forecast<\/td>\n<td>Difference between forecasted vs actual cost post-migration<\/td>\n<td>FinOps maturity and trustworthiness<\/td>\n<td>Within \u00b110\u201315% after 60 days<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Rightsizing coverage<\/td>\n<td>% of migrated workloads reviewed and optimized within X days<\/td>\n<td>Prevents long-term waste<\/td>\n<td>&gt;80% within 45 days<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Automation reuse rate<\/td>\n<td>% of migrations using standard templates\/pipelines<\/td>\n<td>Indicates scalable migration factory<\/td>\n<td>&gt;70%<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Manual steps per cutover<\/td>\n<td>Count of human-run steps during cutover<\/td>\n<td>More manual steps = higher risk<\/td>\n<td>Downward trend; target reduction 20\u201330% over 6 months<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Stakeholder satisfaction (CSAT)<\/td>\n<td>App owner\/business owner rating for migration process<\/td>\n<td>Measures trust and collaboration quality<\/td>\n<td>\u22654.2\/5<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Documentation completeness<\/td>\n<td>% of migrations with complete runbooks, diagrams, evidence, handover docs<\/td>\n<td>Reduces operational and audit friction<\/td>\n<td>&gt;95%<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Mentorship\/enablement impact<\/td>\n<td>Number of teams enabled, office hours held, playbook contributions adopted<\/td>\n<td>Measures \u201clead\u201d leverage<\/td>\n<td>2\u20134 enablement activities\/month<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<p><strong>Notes on measurement design<\/strong>\n&#8211; Avoid comparing raw throughput across portfolios without normalizing for complexity (tiering or story-pointing migrations).\n&#8211; Track both <strong>portfolio outcomes<\/strong> (migrated and decommissioned) and <strong>operational outcomes<\/strong> (incidents, SLOs, cost).\n&#8211; Maintain a lightweight \u201cmigration score\u201d per workload (readiness, risk, compliance, operability) to identify systemic issues.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">8) Technical Skills Required<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Must-have technical skills<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Cloud migration methodologies (Critical)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Structured approaches for discovery, assessment, migration pattern selection, and cutover management.<br\/>\n   &#8211; <strong>Use:<\/strong> Creates consistent execution across workloads; reduces surprises.<br\/>\n   &#8211; <strong>Importance:<\/strong> Critical.<\/p>\n<\/li>\n<li>\n<p><strong>Public cloud core services (AWS\/Azure\/GCP) (Critical)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Compute, networking, storage, IAM, managed databases, load balancing, DNS.<br\/>\n   &#8211; <strong>Use:<\/strong> Designing target architectures and troubleshooting migrations.<br\/>\n   &#8211; <strong>Importance:<\/strong> Critical (at least one major cloud deeply; multi-cloud awareness is common).<\/p>\n<\/li>\n<li>\n<p><strong>Networking and connectivity (Critical)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> VPC\/VNet design, routing, DNS, VPN\/Direct Connect\/ExpressRoute\/Interconnect, firewalls, private endpoints.<br\/>\n   &#8211; <strong>Use:<\/strong> Migration dependencies often fail due to network assumptions; this skill prevents major cutover issues.<br\/>\n   &#8211; <strong>Importance:<\/strong> Critical.<\/p>\n<\/li>\n<li>\n<p><strong>Identity and access management (IAM) (Critical)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Roles\/policies, least privilege, service identities, privileged access patterns, federation\/SSO.<br\/>\n   &#8211; <strong>Use:<\/strong> Secure access design for workloads and migration tooling.<br\/>\n   &#8211; <strong>Importance:<\/strong> Critical.<\/p>\n<\/li>\n<li>\n<p><strong>Infrastructure as Code (IaC) (Important)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Terraform\/CloudFormation\/Bicep\/Pulumi concepts, module design, state management, policy-as-code integration.<br\/>\n   &#8211; <strong>Use:<\/strong> Reproducible environments and scalable migrations.<br\/>\n   &#8211; <strong>Importance:<\/strong> Important (often critical in IaC-first organizations).<\/p>\n<\/li>\n<li>\n<p><strong>Linux\/Windows server administration fundamentals (Important)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> OS services, patching, certificates, performance basics, file systems, system logs.<br\/>\n   &#8211; <strong>Use:<\/strong> Troubleshooting legacy workloads and lift-and-shift migrations.<br\/>\n   &#8211; <strong>Importance:<\/strong> Important.<\/p>\n<\/li>\n<li>\n<p><strong>Application runtime and integration basics (Important)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Web\/app servers, API gateways, TLS, load balancing, service discovery, config management.<br\/>\n   &#8211; <strong>Use:<\/strong> Prevent runtime failures post-migration.<br\/>\n   &#8211; <strong>Importance:<\/strong> Important.<\/p>\n<\/li>\n<li>\n<p><strong>Database and data migration fundamentals (Important)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Replication concepts, schema compatibility, migration tooling, cutover approaches, data validation.<br\/>\n   &#8211; <strong>Use:<\/strong> Planning safe migrations for stateful workloads.<br\/>\n   &#8211; <strong>Importance:<\/strong> Important.<\/p>\n<\/li>\n<li>\n<p><strong>Observability (Important)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Metrics, logs, traces, dashboards, alerting, SLO basics.<br\/>\n   &#8211; <strong>Use:<\/strong> Hypercare stabilization and long-term operability.<br\/>\n   &#8211; <strong>Importance:<\/strong> Important.<\/p>\n<\/li>\n<li>\n<p><strong>Security hardening and cloud controls (Important)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Encryption, key management, secure network boundaries, vulnerability management integration, audit logging.<br\/>\n   &#8211; <strong>Use:<\/strong> Building secure-by-default migrations.<br\/>\n   &#8211; <strong>Importance:<\/strong> Important.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Good-to-have technical skills<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Containerization and orchestration (Kubernetes) (Optional\u2013Important)<\/strong><br\/>\n   &#8211; <strong>Use:<\/strong> Replatforming into managed Kubernetes; modernizing deployment model.<br\/>\n   &#8211; <strong>Importance:<\/strong> Depends on company platform direction.<\/p>\n<\/li>\n<li>\n<p><strong>CI\/CD and release engineering (Optional\u2013Important)<\/strong><br\/>\n   &#8211; <strong>Use:<\/strong> Automating infrastructure deployment and application release during migration.<br\/>\n   &#8211; <strong>Importance:<\/strong> Often important in DevOps-oriented orgs.<\/p>\n<\/li>\n<li>\n<p><strong>Configuration management tooling (Optional)<\/strong><br\/>\n   &#8211; <strong>Use:<\/strong> Managing OS-level config during transitional hybrid phases.<br\/>\n   &#8211; <strong>Importance:<\/strong> Optional if mostly PaaS\/container.<\/p>\n<\/li>\n<li>\n<p><strong>Scripting and automation (Python\/Bash\/PowerShell) (Important)<\/strong><br\/>\n   &#8211; <strong>Use:<\/strong> Preflight checks, data validation automation, log parsing, bulk tagging, account\/project setup.<br\/>\n   &#8211; <strong>Importance:<\/strong> Important.<\/p>\n<\/li>\n<li>\n<p><strong>FinOps fundamentals (Optional\u2013Important)<\/strong><br\/>\n   &#8211; <strong>Use:<\/strong> Cost forecasting, tagging standards, optimization recommendations.<br\/>\n   &#8211; <strong>Importance:<\/strong> Increasingly important.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Advanced or expert-level technical skills<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Complex cutover architectures (Expert)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Blue\/green, canary, traffic shifting, dual-write, replication and failback, DNS strategies.<br\/>\n   &#8211; <strong>Use:<\/strong> Minimizing downtime and rollback risk for Tier-1 workloads.<br\/>\n   &#8211; <strong>Importance:<\/strong> Critical for lead-level ownership.<\/p>\n<\/li>\n<li>\n<p><strong>Hybrid cloud and enterprise networking (Expert)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Hub-and-spoke, transit gateways, segmentation, zero trust connectivity patterns.<br\/>\n   &#8211; <strong>Use:<\/strong> Large enterprises with strict connectivity\/security requirements.<br\/>\n   &#8211; <strong>Importance:<\/strong> Important\u2013Critical depending on environment.<\/p>\n<\/li>\n<li>\n<p><strong>Cloud security architecture (Advanced)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Threat modeling, guardrails, policy-as-code, security posture management integration.<br\/>\n   &#8211; <strong>Use:<\/strong> Building secure migration defaults and handling exceptions.<br\/>\n   &#8211; <strong>Importance:<\/strong> Important.<\/p>\n<\/li>\n<li>\n<p><strong>Performance engineering during migration (Advanced)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Baseline collection, capacity planning, load testing, latency analysis, tuning cloud resources.<br\/>\n   &#8211; <strong>Use:<\/strong> Avoiding regressions when moving to cloud networks\/storage.<br\/>\n   &#8211; <strong>Importance:<\/strong> Important.<\/p>\n<\/li>\n<li>\n<p><strong>Reliability engineering alignment (Advanced)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> SLOs, error budgets, incident response integration, resilience patterns.<br\/>\n   &#8211; <strong>Use:<\/strong> Ensuring migrated services are operable at scale.<br\/>\n   &#8211; <strong>Importance:<\/strong> Important.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Emerging future skills for this role (next 2\u20135 years)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Policy-as-code and continuous compliance automation (Important)<\/strong><br\/>\n   &#8211; Example: integrating controls into pipelines and drift detection workflows.<\/li>\n<li><strong>Platform engineering patterns for migrations (Important)<\/strong><br\/>\n   &#8211; \u201cGolden paths,\u201d self-service migration templates, paved roads for common workloads.<\/li>\n<li><strong>AI-assisted discovery and dependency mapping (Optional\u2013Important)<\/strong><br\/>\n   &#8211; Using AI to accelerate app analysis, log mining, and migration risk identification.<\/li>\n<li><strong>Cloud-native data governance and lineage (Optional)<\/strong><br\/>\n   &#8211; More relevant as data platforms become central and regulated.<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">9) Soft Skills and Behavioral Capabilities<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Structured problem solving<\/strong><br\/>\n   &#8211; <strong>Why it matters:<\/strong> Migration issues often combine network, identity, application behavior, and operational gaps.<br\/>\n   &#8211; <strong>How it shows up:<\/strong> Uses hypotheses, isolates variables, and runs controlled tests during incidents and cutovers.<br\/>\n   &#8211; <strong>Strong performance:<\/strong> Diagnoses root causes quickly, documents learnings, and prevents repeat issues via automation or standards.<\/p>\n<\/li>\n<li>\n<p><strong>Risk management and judgment<\/strong><br\/>\n   &#8211; <strong>Why it matters:<\/strong> Cutovers carry business risk; overly aggressive plans cause outages, overly conservative plans stall progress.<br\/>\n   &#8211; <strong>How it shows up:<\/strong> Builds go\/no-go criteria, insists on evidence, and knows when to escalate or roll back.<br\/>\n   &#8211; <strong>Strong performance:<\/strong> Low rollback rate without sacrificing migration velocity; stakeholders trust the role\u2019s risk calls.<\/p>\n<\/li>\n<li>\n<p><strong>Systems thinking<\/strong><br\/>\n   &#8211; <strong>Why it matters:<\/strong> Migrating a workload changes monitoring, security posture, cost model, and operating procedures\u2014not just hosting.<br\/>\n   &#8211; <strong>How it shows up:<\/strong> Considers downstream operations, audit evidence, and team support readiness early.<br\/>\n   &#8211; <strong>Strong performance:<\/strong> Migrated workloads are stable, compliant, and maintainable, not \u201cmoved and forgotten.\u201d<\/p>\n<\/li>\n<li>\n<p><strong>Cross-functional leadership without authority<\/strong><br\/>\n   &#8211; <strong>Why it matters:<\/strong> The role coordinates app teams, platform, security, network, and operations\u2014often with competing priorities.<br\/>\n   &#8211; <strong>How it shows up:<\/strong> Aligns stakeholders on plans, timelines, and responsibilities; drives closure on blockers.<br\/>\n   &#8211; <strong>Strong performance:<\/strong> Decisions are made quickly; dependencies are surfaced early; fewer last-minute surprises.<\/p>\n<\/li>\n<li>\n<p><strong>Clear technical communication<\/strong><br\/>\n   &#8211; <strong>Why it matters:<\/strong> Migration success depends on shared understanding of risk, downtime, and validation.<br\/>\n   &#8211; <strong>How it shows up:<\/strong> Writes concise runbooks, communicates cutover status, and translates technical detail into business impact.<br\/>\n   &#8211; <strong>Strong performance:<\/strong> Cutover calls are calm and structured; stakeholders always know the current state and next step.<\/p>\n<\/li>\n<li>\n<p><strong>Coaching and enablement mindset<\/strong><br\/>\n   &#8211; <strong>Why it matters:<\/strong> Sustainable migration requires raising capability across teams, not creating a bottleneck specialist.<br\/>\n   &#8211; <strong>How it shows up:<\/strong> Runs office hours, shares patterns, reviews designs constructively.<br\/>\n   &#8211; <strong>Strong performance:<\/strong> App teams increasingly execute migrations using standard patterns with reduced specialist involvement.<\/p>\n<\/li>\n<li>\n<p><strong>Stakeholder empathy and negotiation<\/strong><br\/>\n   &#8211; <strong>Why it matters:<\/strong> Business owners care about downtime, risk, and deadlines; engineers care about technical correctness.<br\/>\n   &#8211; <strong>How it shows up:<\/strong> Negotiates cutover windows, scopes remediation pragmatically, and manages expectations.<br\/>\n   &#8211; <strong>Strong performance:<\/strong> Fewer escalations; stakeholders feel heard; outcomes are achieved without friction.<\/p>\n<\/li>\n<li>\n<p><strong>Operational discipline<\/strong><br\/>\n   &#8211; <strong>Why it matters:<\/strong> Migration work touches production systems; weak discipline leads to outages and audit failures.<br\/>\n   &#8211; <strong>How it shows up:<\/strong> Uses change management properly, keeps evidence, and follows incident protocols.<br\/>\n   &#8211; <strong>Strong performance:<\/strong> Clean audits, reliable cutovers, and consistent operational handovers.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">10) Tools, Platforms, and Software<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Category<\/th>\n<th>Tool \/ platform \/ software<\/th>\n<th>Primary use<\/th>\n<th>Common \/ Optional \/ Context-specific<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Cloud platforms<\/td>\n<td>AWS<\/td>\n<td>Primary migration target\/source services, IAM, networking, compute, storage<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Cloud platforms<\/td>\n<td>Microsoft Azure<\/td>\n<td>Primary migration target\/source services, IAM, networking, compute, storage<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Cloud platforms<\/td>\n<td>Google Cloud (GCP)<\/td>\n<td>Migration target in some orgs<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Cloud migration<\/td>\n<td>AWS Application Migration Service (MGN), CloudEndure<\/td>\n<td>Lift-and-shift server replication<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Cloud migration<\/td>\n<td>Azure Migrate<\/td>\n<td>Discovery, assessment, and migration coordination<\/td>\n<td>Common (Azure shops)<\/td>\n<\/tr>\n<tr>\n<td>Cloud migration<\/td>\n<td>Database Migration Service (AWS DMS \/ Azure DMS)<\/td>\n<td>Database replication and cutover<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Cloud migration<\/td>\n<td>Storage transfer tools (AWS DataSync \/ Azure Data Box \/ rsync)<\/td>\n<td>Large data movement<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>IaC<\/td>\n<td>Terraform<\/td>\n<td>Provision infrastructure consistently across migrations<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>IaC<\/td>\n<td>AWS CloudFormation<\/td>\n<td>AWS-native IaC option<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>IaC<\/td>\n<td>Azure Bicep\/ARM<\/td>\n<td>Azure-native IaC option<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Policy-as-code<\/td>\n<td>Open Policy Agent (OPA) \/ Conftest<\/td>\n<td>Guardrails for IaC and configs<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>CI\/CD<\/td>\n<td>GitHub Actions<\/td>\n<td>Automate IaC\/app pipelines<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>CI\/CD<\/td>\n<td>Azure DevOps Pipelines<\/td>\n<td>Build\/release pipelines<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>CI\/CD<\/td>\n<td>Jenkins<\/td>\n<td>CI\/CD in legacy environments<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Source control<\/td>\n<td>GitHub \/ GitLab \/ Bitbucket<\/td>\n<td>Version control and PR workflows<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Observability<\/td>\n<td>CloudWatch \/ Azure Monitor<\/td>\n<td>Metrics\/logs\/alarms native<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Observability<\/td>\n<td>Datadog<\/td>\n<td>Unified monitoring, APM, dashboards<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>Observability<\/td>\n<td>Prometheus + Grafana<\/td>\n<td>Metrics and dashboards (esp. Kubernetes)<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Logging<\/td>\n<td>ELK\/Elastic Stack<\/td>\n<td>Centralized log analytics<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>ITSM<\/td>\n<td>ServiceNow<\/td>\n<td>Change, incident, request management<\/td>\n<td>Common (enterprise)<\/td>\n<\/tr>\n<tr>\n<td>Collaboration<\/td>\n<td>Microsoft Teams<\/td>\n<td>Cutover bridges, stakeholder communication<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Collaboration<\/td>\n<td>Slack<\/td>\n<td>Engineering collaboration<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Documentation<\/td>\n<td>Confluence<\/td>\n<td>Runbooks, playbooks, KB articles<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Documentation<\/td>\n<td>Jira<\/td>\n<td>Work tracking for migration epics\/stories<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Security<\/td>\n<td>Vault (HashiCorp Vault)<\/td>\n<td>Secrets management<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>Security<\/td>\n<td>AWS Secrets Manager \/ Azure Key Vault<\/td>\n<td>Cloud-native secrets management<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Security<\/td>\n<td>Wiz \/ Prisma Cloud<\/td>\n<td>CSPM and cloud risk visibility<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>Identity<\/td>\n<td>Okta \/ Entra ID (Azure AD)<\/td>\n<td>SSO\/federation, access control<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Containers<\/td>\n<td>Docker<\/td>\n<td>Packaging and build workflows<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Orchestration<\/td>\n<td>Kubernetes (EKS\/AKS\/GKE)<\/td>\n<td>Replatforming target for containerized apps<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Networking<\/td>\n<td>F5 \/ NGINX<\/td>\n<td>Load balancing\/reverse proxy patterns<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Testing<\/td>\n<td>k6 \/ JMeter<\/td>\n<td>Performance validation pre\/post migration<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>Scripting<\/td>\n<td>Python<\/td>\n<td>Automation, validation scripts, API calls<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Scripting<\/td>\n<td>PowerShell<\/td>\n<td>Windows-centric automation<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Cost management<\/td>\n<td>AWS Cost Explorer \/ Azure Cost Management<\/td>\n<td>Cost tracking and optimization<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Architecture<\/td>\n<td>Lucidchart \/ draw.io<\/td>\n<td>Architecture diagrams and dependency maps<\/td>\n<td>Common<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">11) Typical Tech Stack \/ Environment<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Infrastructure environment<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Mix of <strong>on-prem data centers<\/strong>, <strong>VMware-based private cloud<\/strong>, and\/or legacy hosting (colocation\/managed hosting).<\/li>\n<li>Target environment is typically <strong>AWS or Azure<\/strong>, often with hybrid connectivity (VPN or dedicated links).<\/li>\n<li>Common constructs: shared landing zones, hub-and-spoke network topology, centralized logging accounts, separate dev\/test\/prod subscriptions\/accounts.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Application environment<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Portfolio includes a mix of:<\/li>\n<li>Legacy monoliths on VMs (Windows IIS, Linux + NGINX\/Apache, Java app servers).<\/li>\n<li>Modern services (containers, managed Kubernetes, serverless for select workloads).<\/li>\n<li>Vendor packages (CRM\/ERP adjacencies) with integration points.<\/li>\n<li>Integration patterns: REST APIs, message queues, batch jobs, SFTP transfers, event streaming (context-specific).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Data environment<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Typical sources: SQL Server, PostgreSQL, MySQL, Oracle (context-specific), file shares, object storage.<\/li>\n<li>Migration targets: managed relational databases, managed storage, cloud-native backups, replication services.<\/li>\n<li>Data validation and reconciliation are critical for stateful workload acceptance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security environment<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Enterprise IAM with federation (Okta\/Entra ID) and privileged access management (PAM) processes.<\/li>\n<li>Mandatory controls: encryption in transit\/at rest, centralized audit logging, vulnerability scanning, key management, segmentation.<\/li>\n<li>Security approvals may be integrated into change management and architecture review boards.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Delivery model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Often a <strong>migration factory<\/strong> model:<\/li>\n<li>Central Cloud &amp; Infrastructure team provides platform, patterns, and migration specialists.<\/li>\n<li>Application teams execute remediation and testing with specialist guidance.<\/li>\n<li>Alternatives: centralized execution team in early phases; later shifts toward self-service migrations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Agile or SDLC context<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Migration work commonly managed as a program with agile delivery:<\/li>\n<li>Epics per application\/domain.<\/li>\n<li>Sprints for remediation\/build\/migration tasks.<\/li>\n<li>Separate governance gates for readiness and cutover.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scale or complexity context<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Mid-to-large organization: tens to hundreds of applications, multiple environments, strict controls, and multiple concurrent migration waves.<\/li>\n<li>Complexity drivers: network segmentation, identity dependencies, data gravity, vendor constraints, and regulatory requirements.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Team topology<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The Lead Cloud Migration Specialist typically works within:<\/li>\n<li>Cloud Migration squad(s) (2\u20138 engineers, plus PM\/TPM).<\/li>\n<li>Strong dependencies on Platform Engineering, Security, Network, SRE\/Operations, and application teams.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">12) Stakeholders and Collaboration Map<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Internal stakeholders<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Cloud Platform Engineering:<\/strong> landing zone, shared services (logging, secrets, CI\/CD templates), guardrails.  <\/li>\n<li>Collaboration: align migration designs to platform standards; request platform enhancements.<\/li>\n<li><strong>Network Engineering:<\/strong> routing, firewall rules, DNS, private connectivity, load balancers.  <\/li>\n<li>Collaboration: dependency mapping, change coordination, cutover readiness.<\/li>\n<li><strong>Security Engineering \/ SOC:<\/strong> threat controls, logging, detection, vulnerability remediation.  <\/li>\n<li>Collaboration: control validation, exception handling, incident support.<\/li>\n<li><strong>GRC \/ Compliance \/ Audit:<\/strong> evidence requirements, control testing, data handling constraints.  <\/li>\n<li>Collaboration: ensure migration artifacts produce audit-ready evidence.<\/li>\n<li><strong>SRE \/ IT Operations:<\/strong> operational acceptance, monitoring, on-call readiness, incident processes.  <\/li>\n<li>Collaboration: handover, runbooks, hypercare, alert tuning.<\/li>\n<li><strong>Application Engineering teams:<\/strong> code\/config remediation, app testing, performance validation.  <\/li>\n<li>Collaboration: migration planning, remediation backlog, acceptance criteria.<\/li>\n<li><strong>Data Engineering \/ Analytics:<\/strong> data migration, ETL refactoring, data platform integration.  <\/li>\n<li>Collaboration: data cutovers, validation and lineage considerations.<\/li>\n<li><strong>FinOps:<\/strong> cost forecasting, tagging policies, optimization and anomaly response.  <\/li>\n<li>Collaboration: right-sizing, savings plans\/reservations, cost governance.<\/li>\n<li><strong>Enterprise Architecture:<\/strong> target patterns, reference architectures, technology standards.  <\/li>\n<li>Collaboration: design reviews, exception handling, future-state alignment.<\/li>\n<li><strong>Program\/Project Management (PM\/TPM):<\/strong> overall plan, dependencies, RAID logs, steering committees.  <\/li>\n<li>Collaboration: sequencing, reporting, milestone management.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">External stakeholders (as applicable)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Cloud vendors \/ partners \/ SIs:<\/strong> migration tooling expertise, managed services, specialized migrations.  <\/li>\n<li>Collaboration: ensure partner work aligns to internal standards and quality gates.<\/li>\n<li><strong>Third-party software vendors:<\/strong> licensing, support for cloud deployments, upgrade guidance.  <\/li>\n<li>Collaboration: validate supported configurations and migration paths.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Peer roles<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Lead Platform Engineer, Cloud Security Architect, SRE Lead, Network Architect, FinOps Analyst, TPM for Cloud Programs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Upstream dependencies<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Landing zone readiness (accounts\/subscriptions, IAM, logging, network baseline).<\/li>\n<li>Network connectivity provisioning and approvals.<\/li>\n<li>Security approvals, tooling, and access workflows.<\/li>\n<li>Application remediation work completion.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Downstream consumers<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Operations teams who inherit the runbooks and monitoring.<\/li>\n<li>Application teams responsible for ongoing enhancements.<\/li>\n<li>Business owners consuming improved reliability\/performance.<\/li>\n<li>Compliance\/audit teams consuming evidence and control reporting.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Nature of collaboration<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>High collaboration intensity during assessment and cutover windows.<\/li>\n<li>The role often acts as the \u201cglue\u201d between platform controls and real-world application constraints.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Typical decision-making authority<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Owns technical recommendations for migration patterns and cutover designs (within standards).<\/li>\n<li>Shares decision authority with application owners on acceptable downtime and functional tradeoffs.<\/li>\n<li>Security and Network typically hold approval authority for certain controls and changes.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Escalation points<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Infrastructure Manager \/ Head of Cloud Platform (resource conflicts, timeline tradeoffs).<\/li>\n<li>CISO org (security exceptions, risk acceptance).<\/li>\n<li>Architecture Review Board (non-standard patterns, exceptions).<\/li>\n<li>Program steering committee (major re-sequencing, budget, vendor decisions).<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">13) Decision Rights and Scope of Authority<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Decisions this role can make independently<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Recommend and implement standard migration patterns for workloads that fit established guardrails.<\/li>\n<li>Define migration runbooks, validation steps, and operational readiness criteria for assigned migrations.<\/li>\n<li>Prioritize technical migration tasks within the migration squad backlog (within program constraints).<\/li>\n<li>Approve IaC and configuration changes within delegated repositories and environments (subject to PR review policy).<\/li>\n<li>Initiate incident response steps during cutover\/hypercare, including convening cross-team bridges.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Decisions requiring team approval (peer or cross-functional)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Non-standard network topology changes affecting shared environments.<\/li>\n<li>Changes to shared IaC modules that impact multiple teams.<\/li>\n<li>Observability\/alerting standards changes that affect operations broadly.<\/li>\n<li>Significant changes to migration wave sequencing impacting multiple application teams.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Decisions requiring manager\/director\/executive approval<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Risk acceptance for migrations that do not meet required controls (security exceptions).<\/li>\n<li>Budget-affecting choices (major managed service adoption with cost implications, tooling purchases).<\/li>\n<li>Major program re-plans (timeline shifts, scope changes, data center exit date changes).<\/li>\n<li>Vendor selection and contract commitments (often procurement-led, requires leadership signoff).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Budget, architecture, vendor, delivery, hiring, compliance authority<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Budget:<\/strong> Typically influence-based; may propose savings\/expense tradeoffs and participate in business cases.<\/li>\n<li><strong>Architecture:<\/strong> Strong influence; may have delegated authority for migration architectures within reference patterns.<\/li>\n<li><strong>Vendor:<\/strong> Evaluates tools\/partners; final decisions usually by leadership\/procurement.<\/li>\n<li><strong>Delivery:<\/strong> Leads execution for assigned waves; accountable for technical delivery outcomes.<\/li>\n<li><strong>Hiring:<\/strong> May interview and provide technical evaluation; rarely owns headcount decisions.<\/li>\n<li><strong>Compliance:<\/strong> Ensures compliance implementation and evidence; formal approvals generally with Security\/GRC.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">14) Required Experience and Qualifications<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Typical years of experience<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>8\u201312 years<\/strong> in infrastructure, cloud engineering, SRE\/operations, or platform roles, with <strong>3\u20136 years<\/strong> specifically in cloud migration or large-scale cloud adoption initiatives.  <\/li>\n<li>Scope varies by organization; \u201cLead\u201d typically implies ownership of complex migrations and mentorship responsibility.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Education expectations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Bachelor\u2019s degree in Computer Science, Information Systems, Engineering, or equivalent practical experience.<\/li>\n<li>Advanced degrees are not required but can be helpful in architecture-heavy environments.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certifications (Common \/ Optional \/ Context-specific)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Common (helpful, not always required):<\/strong><\/li>\n<li>AWS Certified Solutions Architect \u2013 Associate\/Professional<\/li>\n<li>Microsoft Certified: Azure Solutions Architect Expert<\/li>\n<li><strong>Optional \/ Context-specific:<\/strong><\/li>\n<li>Google Professional Cloud Architect<\/li>\n<li>Certified Kubernetes Administrator (CKA) if Kubernetes is a primary target platform<\/li>\n<li>HashiCorp Terraform certification (useful but not required)<\/li>\n<li>ITIL Foundation (context-specific; more relevant in ITSM-heavy enterprises)<\/li>\n<li>Security certifications (e.g., CCSP) for security-heavy scopes (optional)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Prior role backgrounds commonly seen<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Engineer \/ Senior Cloud Engineer<\/li>\n<li>Systems Engineer \/ Infrastructure Engineer (Linux\/Windows)<\/li>\n<li>DevOps Engineer \/ Platform Engineer<\/li>\n<li>SRE (with infrastructure and release experience)<\/li>\n<li>Network Engineer with cloud networking specialization<\/li>\n<li>Data\/platform engineer with strong migration experience (for data-heavy organizations)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Domain knowledge expectations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Strong understanding of enterprise IT constraints: change management, audit evidence, segmentation, identity governance.<\/li>\n<li>Experience with at least one migration program involving production cutovers and post-cutover operations.<\/li>\n<li>Familiarity with application dependency patterns and common migration pitfalls (DNS, TLS\/certs, latency, filesystem semantics).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Leadership experience expectations (Lead-level)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Has led cross-team migration efforts and cutover events with multiple stakeholders.<\/li>\n<li>Demonstrated mentorship and standard-setting across engineering teams.<\/li>\n<li>Comfortable presenting risk tradeoffs to senior engineering leadership and business stakeholders.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">15) Career Path and Progression<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Common feeder roles into this role<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Senior Cloud Engineer (infrastructure\/platform)<\/li>\n<li>Senior DevOps Engineer \/ Platform Engineer<\/li>\n<li>Senior SRE with infrastructure focus<\/li>\n<li>Senior Systems Engineer (with cloud adoption exposure)<\/li>\n<li>Cloud Migration Engineer (senior)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Next likely roles after this role<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Principal Cloud Migration Specialist<\/strong> or <strong>Principal Cloud Architect<\/strong> (broader scope, portfolio architecture ownership)<\/li>\n<li><strong>Cloud Platform Engineering Lead<\/strong> (building paved roads and self-service platforms)<\/li>\n<li><strong>Cloud Infrastructure Architect<\/strong> (enterprise architecture alignment, reference patterns)<\/li>\n<li><strong>SRE Lead \/ Reliability Architect<\/strong> (operational excellence at scale)<\/li>\n<li><strong>Cloud Program Technical Lead \/ TPM (technical)<\/strong> (program-level leadership with strong engineering grounding)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Adjacent career paths<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Cloud Security Architect<\/strong> (if the role leans heavily into controls and governance)<\/li>\n<li><strong>Network Architect (Cloud)<\/strong> (if the role\u2019s strength is connectivity and segmentation)<\/li>\n<li><strong>FinOps Lead<\/strong> (if the role develops deep cost optimization and forecasting capability)<\/li>\n<li><strong>Data Platform Architect<\/strong> (if migrations focus on data modernization)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Skills needed for promotion<\/h3>\n\n\n\n<p>To progress from Lead to Principal-level:\n&#8211; Demonstrate portfolio-level strategy (not just workload-level execution).\n&#8211; Drive measurable throughput gains via automation and standardization.\n&#8211; Influence governance models to be both safe and enabling.\n&#8211; Build repeatable patterns for complex classes of workloads (stateful, regulated, low-latency, high-availability).\n&#8211; Show strong executive communication and cross-org alignment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How this role evolves over time<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Early: heavy hands-on execution, deep troubleshooting, building core runbooks and templates.<\/li>\n<li>Mid: scaling migration factory, reducing per-workload effort, enabling app teams.<\/li>\n<li>Mature: portfolio strategy, platform influence, shifting focus from \u201cmove\u201d to \u201cmodernize and optimize,\u201d and institutionalizing continuous compliance and operational excellence.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">16) Risks, Challenges, and Failure Modes<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Common role challenges<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Hidden dependencies:<\/strong> Unmapped integrations, batch jobs, IP allowlists, legacy DNS, undocumented certificates.<\/li>\n<li><strong>Network complexity:<\/strong> Segmentation, routing constraints, firewall approval cycles, hairpinning, latency.<\/li>\n<li><strong>Identity friction:<\/strong> Slow IAM approvals, unclear ownership, misconfigured federation, service identity sprawl.<\/li>\n<li><strong>Data gravity and downtime constraints:<\/strong> Large datasets, near-zero downtime requirements, replication complexity.<\/li>\n<li><strong>Platform readiness gaps:<\/strong> Landing zone missing critical features (central logging, secrets, private endpoints).<\/li>\n<li><strong>Change management overhead:<\/strong> CAB schedules and evidence requirements conflicting with agile migration needs.<\/li>\n<li><strong>Application remediation backlog:<\/strong> Teams under-resourced to fix OS\/app dependencies, leading to stalled migrations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Bottlenecks<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Security approvals and exception processes without clear SLAs.<\/li>\n<li>Network change throughput limitations.<\/li>\n<li>Limited non-prod parity causing pre-prod testing to be misleading.<\/li>\n<li>Tooling limitations in discovery\/dependency mapping.<\/li>\n<li>Key-person dependency on a small number of migration specialists.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Anti-patterns<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>\u201cLift-and-shift everything\u201d without operability upgrades:<\/strong> results in unstable, expensive workloads.<\/li>\n<li><strong>Ignoring landing zone guardrails:<\/strong> creates long-term drift and security risk.<\/li>\n<li><strong>Cutover without rehearsal:<\/strong> increases rollback likelihood.<\/li>\n<li><strong>Over-customizing per application:<\/strong> prevents scaling a migration factory.<\/li>\n<li><strong>Treating migration as purely infrastructure work:<\/strong> misses application behavior, data consistency, and operational acceptance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Common reasons for underperformance<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Strong cloud knowledge but weak stakeholder leadership and communication.<\/li>\n<li>Weak operational discipline (documentation gaps, ad hoc changes, insufficient validation).<\/li>\n<li>Lack of structured planning (no readiness scoring, no dependency mapping).<\/li>\n<li>Over-reliance on heroics rather than building repeatable patterns.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Business risks if this role is ineffective<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Increased production outages and customer impact during migrations.<\/li>\n<li>Missed strategic milestones (data center exit, cost reduction targets).<\/li>\n<li>Audit findings due to missing controls or evidence.<\/li>\n<li>Escalating cloud costs due to poor sizing and unmanaged sprawl.<\/li>\n<li>Loss of stakeholder trust, leading to migration program slowdowns or reversals.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">17) Role Variants<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">By company size<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Startup \/ small company (rare to have \u201cLead Migration Specialist\u201d):<\/strong><\/li>\n<li>Role may be combined with DevOps\/Platform Engineering.<\/li>\n<li>Less governance, faster decisions, but fewer standardized controls.<\/li>\n<li><strong>Mid-size software company:<\/strong><\/li>\n<li>Role focuses on accelerating migrations, improving operability, and enabling product teams.<\/li>\n<li>Mix of hands-on and cross-team coordination.<\/li>\n<li><strong>Large enterprise IT organization:<\/strong><\/li>\n<li>Strong governance, more stakeholders, heavier emphasis on compliance evidence and change processes.<\/li>\n<li>Often part of a formal cloud migration program (PMO\/TPMO).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">By industry<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Regulated (finance, healthcare, public sector):<\/strong><\/li>\n<li>Heavier compliance requirements (data residency, encryption, audit trails).<\/li>\n<li>More formal risk acceptance and documentation.<\/li>\n<li><strong>Non-regulated (SaaS, tech):<\/strong><\/li>\n<li>Higher emphasis on automation, speed, and reliability engineering practices.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">By geography<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Generally similar globally; differences appear in:<\/li>\n<li>Data residency constraints and cross-border data transfer rules.<\/li>\n<li>Availability of cloud regions and required architecture for latency.<\/li>\n<li>On-call and change window practices across time zones.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Product-led vs service-led company<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Product-led SaaS:<\/strong><\/li>\n<li>Strong focus on reliability, SLOs, and minimizing customer impact.<\/li>\n<li>Often more modern workloads; replatform\/refactor more common.<\/li>\n<li><strong>Service-led \/ internal IT:<\/strong><\/li>\n<li>Broader app variety, more COTS and legacy systems.<\/li>\n<li>Rehost\/replatform patterns often dominate early waves.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Startup vs enterprise<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Enterprise:<\/strong> formal landing zones, segmentation, CAB, audit requirements; migration speed constrained by governance unless optimized.<\/li>\n<li><strong>Startup:<\/strong> fewer constraints; the role is more builder-oriented, but may lack mature operational practices.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Regulated vs non-regulated environments<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>In regulated environments, the role must be strong in:<\/li>\n<li>Evidence generation, control mapping, and secure design patterns.<\/li>\n<li>Stakeholder management with Compliance and Risk.<\/li>\n<li>In non-regulated environments, the role can optimize for:<\/li>\n<li>Speed, developer experience, and cost\/performance iteration cycles.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">18) AI \/ Automation Impact on the Role<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Tasks that can be automated (increasingly)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Discovery and inventory enrichment:<\/strong> automated collection of server\/app metadata, configuration, and runtime dependencies.<\/li>\n<li><strong>Dependency mapping support:<\/strong> AI-assisted analysis of logs, network flows, and configuration to propose dependency graphs (still needs validation).<\/li>\n<li><strong>Runbook generation drafts:<\/strong> AI can generate first-pass cutover steps, validation checklists, and comms templates from prior migrations.<\/li>\n<li><strong>IaC scaffolding:<\/strong> AI-assisted creation of Terraform\/Bicep templates aligned to standards (requires strict review).<\/li>\n<li><strong>Validation scripting:<\/strong> AI can draft reconciliation scripts and test cases based on patterns.<\/li>\n<li><strong>Cost anomaly detection and optimization suggestions:<\/strong> AI can identify idle resources and recommend rightsizing.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Tasks that remain human-critical<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Risk judgment and go\/no-go decisions:<\/strong> requires context, business understanding, and accountability.<\/li>\n<li><strong>Stakeholder alignment and negotiation:<\/strong> downtime windows, scope tradeoffs, and ownership decisions.<\/li>\n<li><strong>Architecture tradeoffs:<\/strong> especially for complex stateful systems, latency-sensitive dependencies, or regulatory constraints.<\/li>\n<li><strong>Incident leadership during cutover:<\/strong> coordinating teams and making real-time decisions under uncertainty.<\/li>\n<li><strong>Control interpretation and audit defense:<\/strong> ensuring controls are implemented correctly and evidence is meaningful.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How AI changes the role over the next 2\u20135 years<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The role shifts from \u201chands-on mover\u201d to <strong>migration systems designer<\/strong>, focusing on:<\/li>\n<li>Building standardized migration pipelines and validation frameworks.<\/li>\n<li>Curating and governing AI-assisted outputs (ensuring correctness and security).<\/li>\n<li>Driving higher migration throughput with fewer specialists via self-service.<\/li>\n<li>Increased expectation to implement <strong>continuous compliance<\/strong> and <strong>automated evidence<\/strong> as part of migration delivery (policy-as-code, drift detection, automated attestation).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">New expectations caused by AI, automation, or platform shifts<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Ability to evaluate AI-generated infrastructure and scripts for security, correctness, and maintainability.<\/li>\n<li>Stronger emphasis on <strong>platform engineering<\/strong>: golden paths, reusable modules, and paved roads.<\/li>\n<li>Greater accountability for reducing manual cutover steps through automation and safer deployment patterns (traffic shifting, progressive delivery).<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">19) Hiring Evaluation Criteria<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What to assess in interviews (competency areas)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Migration leadership and execution:<\/strong> Can they lead real cutovers and drive outcomes across teams?<\/li>\n<li><strong>Cloud architecture depth:<\/strong> Can they design secure, scalable target architectures within landing zone constraints?<\/li>\n<li><strong>Networking and IAM mastery:<\/strong> Can they troubleshoot the most common migration failure domains?<\/li>\n<li><strong>Stateful migration capability:<\/strong> Can they migrate databases\/data safely with validation and rollback?<\/li>\n<li><strong>Operational readiness mindset:<\/strong> Do they build monitoring, runbooks, DR alignment, and support handover?<\/li>\n<li><strong>Automation orientation:<\/strong> Do they standardize and automate rather than reinvent per app?<\/li>\n<li><strong>Communication and stakeholder management:<\/strong> Can they explain risk, timelines, and tradeoffs clearly?<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Practical exercises or case studies (recommended)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Migration plan case study (60\u201390 minutes):<\/strong><br\/>\n   Provide a sample application (3-tier web app + database + background jobs) with constraints (2-hour downtime window, compliance logging required, hybrid connectivity). Ask the candidate to produce:\n   &#8211; Pattern choice (rehost\/replatform\/refactor) and rationale\n   &#8211; Dependency risks and mitigation\n   &#8211; Cutover plan and validation steps\n   &#8211; Rollback plan\n   &#8211; Post-migration operability checklist<\/p>\n<\/li>\n<li>\n<p><strong>Troubleshooting scenario (30\u201345 minutes):<\/strong><br\/>\n   During cutover, the app fails auth to a downstream service and latency increases. Candidate should walk through:\n   &#8211; Hypotheses (DNS, routing, TLS\/certs, IAM tokens)\n   &#8211; Data to inspect (logs, traces, security group flow logs)\n   &#8211; Decision criteria for rollback vs continue<\/p>\n<\/li>\n<li>\n<p><strong>IaC review exercise (30 minutes, optional):<\/strong><br\/>\n   Provide a Terraform snippet with intentional issues (overly broad IAM, missing tags, public endpoints). Candidate identifies risks and improvements.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Strong candidate signals<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Describes migrations with concrete details: dependency discovery, validation, rollback, hypercare outcomes.<\/li>\n<li>Demonstrates comfort with network and identity troubleshooting (not just compute provisioning).<\/li>\n<li>Uses structured readiness gates and evidence-driven go\/no-go decisions.<\/li>\n<li>Communicates clearly with both engineers and business stakeholders.<\/li>\n<li>Has built reusable templates\/playbooks and improved migration throughput.<\/li>\n<li>Shows accountability: owns incidents and learns from them via postmortems.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Weak candidate signals<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Only describes \u201clift-and-shift\u201d without operational upgrades or guardrails.<\/li>\n<li>Cannot articulate rollback strategy or validation approach.<\/li>\n<li>Avoids networking\/IAM depth; relies on \u201csomeone else handles that.\u201d<\/li>\n<li>Focuses on tool names without explaining decisions and outcomes.<\/li>\n<li>Minimizes documentation and governance as \u201cbureaucracy\u201d without proposing better automation.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Red flags<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Willingness to cut over without rehearsals or clear rollback criteria.<\/li>\n<li>Comfort with broad, persistent admin access; weak least-privilege mindset.<\/li>\n<li>Blames other teams for blockers without demonstrating influence\/leadership to resolve them.<\/li>\n<li>Inability to articulate how migrated systems will be monitored and supported post-cutover.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scorecard dimensions (example)<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Dimension<\/th>\n<th>What \u201cExcellent\u201d looks like<\/th>\n<th>Weight<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Migration strategy &amp; planning<\/td>\n<td>Clear wave planning, dependency awareness, pattern selection tradeoffs<\/td>\n<td>15%<\/td>\n<\/tr>\n<tr>\n<td>Cloud architecture &amp; landing zone alignment<\/td>\n<td>Designs secure, scalable architectures within standards<\/td>\n<td>15%<\/td>\n<\/tr>\n<tr>\n<td>Networking &amp; IAM<\/td>\n<td>Deep troubleshooting ability; least privilege by default<\/td>\n<td>15%<\/td>\n<\/tr>\n<tr>\n<td>Data\/stateful migration<\/td>\n<td>Sound replication\/cutover\/validation\/rollback approach<\/td>\n<td>15%<\/td>\n<\/tr>\n<tr>\n<td>Operational readiness &amp; reliability<\/td>\n<td>Strong monitoring, runbooks, DR alignment, hypercare outcomes<\/td>\n<td>15%<\/td>\n<\/tr>\n<tr>\n<td>Automation &amp; IaC<\/td>\n<td>Reusable modules, CI\/CD integration, reduced manual steps<\/td>\n<td>10%<\/td>\n<\/tr>\n<tr>\n<td>Communication &amp; stakeholder leadership<\/td>\n<td>Clear, calm, structured; strong cross-team influence<\/td>\n<td>10%<\/td>\n<\/tr>\n<tr>\n<td>Quality &amp; governance mindset<\/td>\n<td>Evidence, controls, and disciplined change management<\/td>\n<td>5%<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">20) Final Role Scorecard Summary<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Category<\/th>\n<th>Summary<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Role title<\/strong><\/td>\n<td>Lead Cloud Migration Specialist<\/td>\n<\/tr>\n<tr>\n<td><strong>Role purpose<\/strong><\/td>\n<td>Lead secure, reliable, and repeatable migrations of applications, data, and infrastructure to cloud\/hybrid environments while improving long-term operability and cost efficiency.<\/td>\n<\/tr>\n<tr>\n<td><strong>Top 10 responsibilities<\/strong><\/td>\n<td>1) Portfolio wave planning and sequencing 2) Pattern selection (rehost\/replatform\/refactor\/retire\/retain) 3) Dependency mapping and readiness scoring 4) Cutover planning, rehearsal, and execution leadership 5) Network\/connectivity implementation and troubleshooting 6) IAM design and access governance alignment 7) Data migration planning, execution, and integrity validation 8) IaC-based environment provisioning and standardization 9) Observability, runbooks, and operational handover 10) Post-migration optimization with FinOps and platform teams<\/td>\n<\/tr>\n<tr>\n<td><strong>Top 10 technical skills<\/strong><\/td>\n<td>1) Cloud migration methods 2) AWS\/Azure core services 3) Cloud networking (routing\/DNS\/private connectivity) 4) IAM\/least privilege 5) IaC (Terraform\/Bicep\/CloudFormation) 6) Database\/data migration fundamentals 7) Observability (metrics\/logs\/traces\/SLOs) 8) OS fundamentals (Linux\/Windows) 9) Automation scripting (Python\/Bash\/PowerShell) 10) Secure cloud controls (encryption, logging, vulnerability mgmt integration)<\/td>\n<\/tr>\n<tr>\n<td><strong>Top 10 soft skills<\/strong><\/td>\n<td>1) Structured problem solving 2) Risk judgment 3) Systems thinking 4) Cross-functional leadership 5) Clear technical communication 6) Coaching\/enablement mindset 7) Stakeholder empathy &amp; negotiation 8) Operational discipline 9) Prioritization under constraints 10) Calm incident leadership<\/td>\n<\/tr>\n<tr>\n<td><strong>Top tools or platforms<\/strong><\/td>\n<td>AWS\/Azure, Azure Migrate (context), AWS\/Azure DMS, Terraform, GitHub\/GitLab, Azure DevOps\/Jenkins (context), CloudWatch\/Azure Monitor, ServiceNow (enterprise), Confluence\/Jira, Secrets Manager\/Key Vault, Datadog (optional), Kubernetes (context)<\/td>\n<\/tr>\n<tr>\n<td><strong>Top KPIs<\/strong><\/td>\n<td>Cutover success rate, on-time cutover rate, migration lead time, hypercare incident rate, time to stabilize, landing zone adherence, compliance control pass rate, cost variance vs forecast, rightsizing coverage, stakeholder CSAT<\/td>\n<\/tr>\n<tr>\n<td><strong>Main deliverables<\/strong><\/td>\n<td>Migration strategy &amp; wave plans, assessment reports and dependency maps, target architectures, cutover runbooks + rollback plans, IaC modules\/templates, data migration plans + validation scripts, observability dashboards\/alerts, operational handover packs, optimization reports, updated migration playbooks\/automation assets<\/td>\n<\/tr>\n<tr>\n<td><strong>Main goals<\/strong><\/td>\n<td>30\/60\/90-day: establish standards, deliver initial migrations, improve predictability; 6\u201312 months: scale migration factory throughput, reduce incidents and cost variance, mature governance and operational readiness, enable app teams to migrate with less specialist effort<\/td>\n<\/tr>\n<tr>\n<td><strong>Career progression options<\/strong><\/td>\n<td>Principal Cloud Migration Specialist, Principal\/Lead Cloud Architect, Cloud Platform Engineering Lead, Reliability Architect\/SRE Lead, Cloud Security Architect (adjacent), Cloud Program Technical Lead\/TPM (technical track)<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>The **Lead Cloud Migration Specialist** is a senior individual contributor who plans and drives complex application, data, and infrastructure migrations from on-premises or hosted environments into public cloud and hybrid cloud platforms. The role combines deep technical migration expertise with program-level orchestration\u2014ensuring migrations are secure, reliable, cost-aware, and aligned to platform standards and business outcomes.<\/p>\n","protected":false},"author":61,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","_joinchat":[],"footnotes":""},"categories":[24455,24508],"tags":[],"class_list":["post-75016","post","type-post","status-publish","format-standard","hentry","category-cloud-infrastructure","category-specialist"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/75016","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/61"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=75016"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/75016\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=75016"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=75016"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=75016"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}