UK

United Kingdom · Technology and data · Lead (8-12 years)

Lead Cloud Migration Architect

Here is the whole job, in plain words. What it is, what you decide, how you're judged, how people get here and where they go next. Then the part no course gives you: twelve AI tutors who learn your work.

See how AI is changing this job, and get the full read by email.

Start my free Growth Mindset module

The first step towards FinOps & Cloud Cost Governance is taking your people with you, so start with Building a Department's Capacity to Learn, free.

Free to start, no card.

Keep this job description

Where should we send it?

One email: what AI is changing in this job, the new skills it asks for, where it leads, and where to start free. With a link back here. Nothing else follows unless you confirm your address.

Your employer, or 'self-employed'

Leading a team? Try this with up to five of them for 14 days, free.

  • Experience bandLead (8-12 years)
  • Direct reports3-8 reports
  • Reports toCloud Migration Assistant Manager
  • UK framework levelUsually a manager, or the deepest specialist in a team

Also advertised as Principal Cloud Migration Engineer · Cloud Migration Lead · Senior Cloud Solutions Architect (Migration Focus) · Cloud Transformation Lead

Built on 43,079 real UK job descriptions we analysed · grounded in what real qualifications cover

Two short quizzes about you

1From this job to a course

The qualifications matched to this job

NOCN Level 5 Diploma in Electronic and Communications Engineering NOCN · Level 5 · covers 7 of 12 standards
ATHE Level 5 Extended Diploma in Computing ATHE Ltd · Level 5 · covers 4 of 12 standards
Cambridge OCR Level 3 Cambridge Technical Certificate in IT Cambridge OCR · Level 3 · covers 3 of 12 standards
Cambridge OCR Level 3 Cambridge Technical Introductory Diploma in IT Cambridge OCR · Level 3 · covers 3 of 12 standards
Cambridge OCR Level 3 Cambridge Technical Extended Diploma in IT Cambridge OCR · Level 3 · covers 2 of 12 standards
Cambridge OCR Level 3 Cambridge Technical Subsidiary Diploma in IT Cambridge OCR · Level 3 · covers 2 of 12 standards

Matched from the standards this job is measured against: a suggestion, not an official ruling.

The units you would start with

Cloud Computing NOCN Level 5 Diploma in Electronic and Communications Engineering
Network and Cloud Design and Configuration ATHE Level 5 Extended Diploma in Computing
Cloud computing in business Cambridge OCR Level 3 Cambridge Technical Certificate in IT

The future skills this job leans on

AI Governance Fluency using AI responsibly
Your Plan Illustration

Built for Lead Cloud Migration Architect

3 units that map to this job, from the qualifications that cover it.

  1. Cloud Computing NOCN · covers 7 of 12 standards Level 5
  2. Network and Cloud Design and Configuration ATHE Ltd · covers 4 of 12 standards Level 5
  3. Cloud computing in business Cambridge OCR · covers 3 of 12 standards Level 3
These are the real units behind this job, in the order they rank for it. Nothing here is marked done, because this plan has not been started by anyone yet. Yours would fill in as you go.

2AI and this work

Will AI change your work as a Lead Cloud Migration Architect?

Nobody can say exactly how. Here is what this job is being asked for next, and where to start.

The new skills this role is being asked for

  • FinOps & Cloud Cost Governance
  • Platform Engineering & Developer Experience
Why each one is rising

The future skills this job leans on

We'll only ever tell you what we can actually back up. No hype, no scare tactics.

What happens when you start

Next, a free account. We build your Lead Cloud Migration Architect plan as you set up, starting with the free Growth Mindset module. No card.

Your first Future Fluency module is free. After that, your AI tutor is £70 a month.

Ready to pay? Subscribe for £70 a month

Keep this read. One email with what AI is changing in this job, the new skills it asks for and where to start free. Nothing else follows unless you confirm your address.

3What this role really is

A Lead Cloud Migration Architect designs how core systems move from old data centres into the cloud.

4What you'd actually use

The tools this job runs on, and how well you'd need to know each one.

AWS Management Console / Azure Portal / GCP Console Expert

Deep-diving into cloud resource configurations, troubleshooting complex issues, and validating architectural designs across IaaS, PaaS, and networking services.

Terraform (HCL) Expert

Writing modular, reusable Terraform code from scratch to define complex target state infrastructure, managing state files, and integrating with CI/CD pipelines. You'll be setting the IaC standards for your team.

AWS Application Migration Service (MGN) / Azure Migrate / GCP Migrate for Compute Engine Advanced

Designing and troubleshooting migration jobs, setting replication schedules, and scripting pre/post-migration tasks. You'll be the go-to person for complex migration challenges with these tools.

Ansible Advanced

Designing and maintaining Ansible playbooks to automate application configuration, patching, and hardening post-migration. You'll also be debugging playbook execution failures and optimising them for efficiency.

Jira & Confluence Advanced

Creating and managing Jira backlogs for migration waves, authoring detailed technical runbooks, architectural decision records, and post-mortem documents in Confluence. You'll also use these for executive reporting.

Cloudamize / Flexera One (or similar discovery tools) Advanced

Configuring and troubleshooting these tools to handle complex network segments and gather accurate dependency data. You'll be interpreting their outputs to inform your architectural designs.

5What you get to decide, and how that grows

Power in a job isn't your title. It's what you're allowed to decide. Here's how it grows as you move up.

The choiceComing in Where you are nowThe step above
Migration Strategy (e.g., Rehost vs. Replatform) Follows defined strategy in runbook, escalates any deviation. Proposes alternative strategies for routine applications, seeks manager approval. Designs strategy for complex applications, recommends to lead architect for approval.
Technical Architecture Design (Cloud) Deploys resources based on existing IaC templates. Modifies existing IaC templates for minor changes, proposes small architectural improvements. Designs specific components (e.g., new subnet, security group rules) within a defined architecture.
Tooling Selection for Migration Uses pre-selected migration tools as per runbook. Suggests specific features or workarounds for existing tools. Evaluates alternative features within existing toolset, makes recommendations.
Team Member Mentorship & Task Assignment Receives tasks and seeks guidance. Provides informal guidance to new joiners on specific tasks. Mentors 1-2 junior engineers, provides technical guidance on specific problems.

6How you'll be judged

The scoreboard, and what is not on it. The hard targets, how often each is actually looked at, and the quiet signals that never reach a dashboard.

Migration Wave Success Rate
Percentage of planned applications within a migration wave that successfully complete their cutover to the cloud without significant post-migration issues (P1/P2 incidents).
Target · >95% first-time-right cutovers

If a wave targets 20 applications, and 19 migrate without major issues, that's a 95% success rate. We're aiming for near-perfection here, because outages cost us real money and reputation.

Cost Optimisation (Post-Migration)
Average percentage reduction in estimated cloud infrastructure costs for migrated applications within the first 3 months post-cutover, compared to initial 'lift and shift' sizing.
Target · Achieve 15-20% cost reduction through right-sizing and optimisation

You design a migration for an application initially estimated at £1,000/month. After your team's right-sizing efforts, it's running at £800/month. That's a 20% saving, which is exactly what we want to see.

Infrastructure as Code (IaC) Adoption
Percentage of new cloud infrastructure deployed for migrated applications that is fully defined and managed via IaC (Terraform, CloudFormation).
Target · 100% IaC for all new deployments

Every new VPC, subnet, EC2 instance, or database for a migrated app should be deployed through code. If we find resources manually provisioned, that's a miss. We want repeatable, auditable infrastructure.

Technical Debt Reduction (Post-Migration)
Number of identified legacy technical debts (e.g., outdated OS, unsupported databases) that are remediated or upgraded as part of the migration design.
Target · Remediate 75% of identified critical technical debts per wave

You identify 10 critical servers running Windows Server 2008. Your migration design includes upgrading 8 of them to Windows Server 2019 during the move. That's a solid win for reducing future headaches.

Architectural Soundness & Resilience
Your migration designs lead to cloud environments that are robust, secure, and scalable, capable of handling expected loads and recovering gracefully from failures.
  • Security team sign-offs are smooth, with few critical findings. Post-migration performance is stable or improved. Disaster recovery drills for migrated apps pass with flying colours. Other architects seek your input on complex designs.
Team Mentorship & Development
You actively guide and upskill the Cloud Migration Engineers and Specialists in your team, helping them grow their technical capabilities and problem-solving skills.
  • Your direct reports consistently meet their performance goals. They report feeling supported and challenged. You're regularly conducting code reviews and providing constructive feedback. Junior team members are progressing to mid-level roles.
Proactive Risk Management
You identify potential migration risks early, develop mitigation strategies, and communicate these clearly to project managers and stakeholders, preventing surprises.
  • Few last-minute surprises during cutovers. Project managers rely on your risk assessments. You're often the one flagging potential 'hairball applications' long before they become a problem. You've got a reputation for thinking several steps ahead.
Documentation Quality & Completeness
Your architectural designs, decision logs, and team runbooks are clear, comprehensive, and easily understood by others, forming a reliable knowledge base.
  • New team members can pick up your documentation and understand the migration strategy without constant questions. Post-mortems rarely point to missing or unclear documentation. Your Confluence pages are actually useful, not just a dumping ground.

7Would you like it

Both sides. What people enjoy, and what grinds them down.

What people enjoy
Solving Complex Puzzles

You thrive on dissecting a 'hairball application' to understand its dependencies, then designing an elegant, robust migration path. The more obscure the problem, the more engaged you are. You love the challenge of making disparate systems play nicely in a new environment.

Spending a week mapping out the intricate network flows and database connections for a critical, 15-year-old ERP system, then architecting a multi-stage migration that minimises downtime.

Building for the Future

You get a real kick out of creating robust, scalable cloud infrastructure using Infrastructure as Code (IaC) that will serve the business for years. You're not just moving things; you're building a better foundation. Seeing your architectural patterns adopted widely is a big win for you.

Designing a new landing zone architecture that simplifies future migrations and provides a secure, compliant environment for all new cloud workloads.

Leading & Mentoring

You enjoy guiding a team of engineers, helping them overcome technical blockers, and seeing them grow. You like being the go-to person for tough technical questions and enjoy the responsibility of ensuring your team delivers high-quality work. You get satisfaction from seeing your team succeed.

Helping a junior engineer debug a tricky Terraform issue for an hour, then seeing them confidently resolve similar problems on their own the following week.

What frustrates people
  • Inaccurate 'official' discovery data (the 'CMDB is a lie' problem).
  • Application owners who drag their feet on providing information or sign-offs, jeopardising migration schedules.
  • Last-minute change freezes that cancel meticulously planned cutovers.
  • Being blamed for application performance issues post-migration that are actually due to bad code or network latency outside your control.
  • Discovering critical legacy applications have hard-coded IP addresses or obscure dependencies that turn a 'lift and shift' into a refactor.
  • Scope creep: the 'simple' migration that suddenly needs an OS upgrade, a database move, and a front-end containerisation.
What this role does not give you
  • A purely greenfield environment: you'll always be dealing with legacy.
  • Complete autonomy over every technical decision: you'll need to compromise with security, app owners, and budget holders.
  • A quiet, predictable routine: expect urgent issues during cutovers and shifting priorities.
  • The ability to ignore documentation: it's a critical part of making migrations repeatable and successful.

8Who you work with

This role directly impacts our company's ability to modernise its IT estate, reduce operational costs, and accelerate the delivery of new digital products and services. You're essentially paving the road for our future in the cloud. Get it right, and we're agile and competitive; get it wrong, and we're stuck with expensive, slow, and insecure legacy systems.

Inside the business
  • Cloud Migration Assistant Manager (your boss)
  • Application Owners (the people whose apps you're moving)
  • Security Team (they'll need to sign off on everything)
  • Infrastructure & Operations Teams (who manage the old and new environments)
  • Product Development Teams (for refactoring opportunities)
  • Finance (they'll want to see the cost savings)
Outside the business
  • Cloud Platform Vendors (AWS, Azure, GCP)
  • Migration Tool Vendors (e.g., Zerto, Cloudamize)
  • External Consultants (sometimes we bring in specialists for tricky bits)

9What you need before you start

Not a wish list. The things you would be expected to already have.

  • Proven experience (5+ years) as a Senior Cloud Migration Engineer or similar role, where you've owned the end-to-end migration of complex, multi-tier applications.
  • Demonstrable experience leading technical discussions, making architectural decisions, and mentoring junior engineers.
  • Deep expertise in at least one major public cloud platform (AWS, Azure, or GCP), including advanced networking, security, and compute services.
  • Strong practical experience with Infrastructure as Code (e.g., Terraform) for deploying and managing cloud resources.
  • A solid understanding of application dependency mapping and cutover planning for production systems.
  • Experience in designing and troubleshooting complex migration patterns (e.g., database migrations with AWS DMS/Azure DMS).

10What to practise next

Where the job is going, and what to do about it starting this week.

Advanced Policy-as-Code (PaC)

Manual security and compliance checks don't scale. You'll need to embed governance directly into your IaC. This means writing policies that automatically enforce rules before anything gets deployed, not after. It's about preventing issues, not just detecting them.

Open Policy Agent (OPA) and Rego language · AWS Config Rules / Azure Policy / GCP Organization · Sentinel for Terraform Enterprise · Shift-left security principles · Automated compliance reporting

  • This month: Explore OPA and try writing a simple Rego policy for a common cloud resource.
  • Month 2: Implement a basic cloud provider policy (e.g., 'no public S3 buckets') in your test environment.
  • Month 3: Integrate a policy-as-code tool into your IaC CI/CD pipeline.
  • Month 4: Work with the security team to translate a manual security control into an automated policy.

Quick win: Identify one simple security rule (e.g., 'all EC2 instances must have tags') and write a basic policy-as-code check for it.

Containerisation & Orchestration (Advanced)

Many applications will be replatformed to containers. You'll need to design robust, scalable, and secure container platforms, understanding the nuances of different orchestrators and how they integrate with your migration strategy. It's not just about running Docker; it's about running it at scale.

Kubernetes (EKS, AKS, GKE) architecture and operat · Container security best practices (image scanning, · Service Mesh (Istio, Linkerd) concepts · Serverless containers (Fargate, Cloud Run) · Container networking and storage patterns

  • This month: Deep-dive into one cloud provider's managed Kubernetes offering (e.g., EKS).
  • Month 2: Deploy a sample containerised application to a Kubernetes cluster you've provisioned with IaC.
  • Month 3: Explore service mesh concepts and how they apply to microservices.
  • Month 4: Design a replatforming strategy for a legacy application to run on containers.

Quick win: Containerise a simple internal tool or legacy application component and deploy it to a test Kubernetes cluster.

11Staying current once you are in

What people here do to keep up
  • Regularly attend industry conferences (e.g., AWS re:Invent, Microsoft Ignite, Google Cloud Next) to stay on top of emerging trends and technologies.
  • Actively participate in cloud architecture communities of practice, both internally and externally, sharing your knowledge and learning from peers.
  • Contribute to open-source projects, especially those related to cloud automation, IaC, or migration tooling.
  • Dedicate time each quarter to hands-on experimentation with new cloud services or migration patterns in a sandbox environment.
  • Mentor junior engineers and participate in internal knowledge-sharing sessions; teaching is one of the best ways to learn.

12The rising capability

The rising capability

Zavmo analysis

What's rising in its place

This is where the work is heading, and the higher pay with it. Get fluent here and the shift stops being a threat and starts being your edge.

FinOps & Cloud Cost Governance

Cloud costs are spiralling for many organisations. As an architect, your designs directly impact our spend. The ability to build cost-aware architectures and implement governance policies will be as important as technical performance. Finance will be looking to you, not just the CloudOps team.

  • Cloud cost allocation and tagging strategies
  • Reserved Instances (RIs) and Savings Plans optimis
  • Spot Instances for fault-tolerant workloads
  • Cost anomaly detection and alerting
  • Showback/Chargeback models for cloud consumption

Platform Engineering & Developer Experience

As we mature in the cloud, the focus shifts from just 'migrating' to 'enabling developers'. Your architectural patterns need to be easily consumable by development teams, providing self-service capabilities and reducing their cognitive load. You'll be designing platforms, not just infrastructure.

  • Internal Developer Platforms (IDPs)
  • Golden Paths and opinionated templates
  • Self-service infrastructure provisioning
  • GitOps principles for platform management
  • Measuring developer productivity and satisfaction

13What you’ll use

What you’ll use

Skills this role draws on

Technical

  • The 6 R's of Migration Strategy
  • Wave Planning & Move Group Analysis
  • Cloud Adoption Framework (CAF)
  • Application Dependency Mapping
  • Cutover Planning & Execution
  • TCO & Business Case Development

14The pathway

The pathway

How you actually get there, here

How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.

  1. 1

    Senior Cloud Migration Engineer

    3-5 years in previous role

    Skills to master

    • End-to-end ownership of complex application migrations, advanced IaC development, deep troubleshooting skills, informal mentorship.

    You're ready to move on when

    • Successfully led 5+ multi-tier application migrations independently.
    • Consistently delivered high-quality IaC for cloud deployments.
    • Recognised as the go-to person for specific technical challenges within the team.
    • Actively mentored junior engineers and contributed to team best practices.
  2. 2

    Cloud Solutions Architect (Generalist)

    4-6 years in previous role

    Skills to master

    • Designing cloud solutions across various domains (not just migration), strong stakeholder management, understanding of broader cloud governance and security.

    You're ready to move on when

    • Designed and implemented cloud solutions for diverse business requirements.
    • Demonstrated ability to translate business needs into technical architectures.
    • Strong understanding of cloud cost optimisation and security principles.
    • Proven ability to influence technical decisions across different teams.
  3. 3

    Senior Infrastructure Engineer (Cloud Focus)

    5-7 years in previous role

    Skills to master

    • Deep on-premises infrastructure knowledge, experience with virtualisation (VMware, Hyper-V), networking, storage, and initial exposure to cloud platforms and IaC.

    You're ready to move on when

    • Successfully transitioned on-premises workloads to cloud environments (even if small scale).
    • Strong understanding of legacy system dependencies and operational challenges.
    • Developed automation for infrastructure provisioning or management.
    • Actively pursued cloud certifications and hands-on cloud projects.

15Where this role leads

The long view: This work can lead to a Director of Cloud Enablement role, or into wider architecture positions such as Chief Architect.

The ten Future Fluencies

Zavmo analysis

The credential is what you can do today. These are what keep you valuable.

A qualification proves you can do the job as it's defined today. These ten are what decide whether you're still the obvious person for it in five years. They're the capabilities employers are now writing into senior roles faster than people are learning them. Zavmo weaves them through whatever you study, so you come out with both: the credential and the fluency.

The highlighted ones are the Fluencies your role leans on hardest, from how Lead Cloud Migration Architect is actually changing.

Where it leads

Roles this leads to

The record names a next step, but the catalogue has no page for it yet:

  • Principal Cloud Strategist

How you would learn this

One to one, on the work you already do

A tutor sets the task against your own job and marks the reasoning, at your pace. There is no cohort to fall behind.

A lesson from Cloud Computing, worked against Lead Cloud Migration Architect.

Cloud Computing Level 5

Applied to your work in Lead Cloud Migration Architect

The objective of this unit is to enable learners to understand the principles, characteristics, and technologies underpinning cloud computing. Learners will be able to describe and evaluate cloud service models and functionalities, and apply cloud services for collaborative applications and content management.

How the thinking builds
  1. 1 Remember
  2. 2 Understand
  3. 3 Apply
  4. 4 Analyse
  5. 5 Evaluate
  6. 6 Create
An illustration of a Zavmo lesson, built from this role’s own route. The unit, its objective and every criterion above are the awarding body’s own words, not an example.

It is £70 a month, billed monthly. Your free first module is Future Fluency, and you can cancel any time.

See Your Progress Grow Illustration
Lead Cloud Migration Architect
  • The 6 R's of Migration Strategy
  • Wave Planning & Move Group Analysis
  • Cloud Adoption Framework (CAF)
  • Application Dependency Mapping
  • Cutover Planning & Execution
  • TCO & Business Case Development
This is your Mind Palace on learn.zavmo.ai. Every skill above comes from this role's own record, not an example borrowed from another job. A node lights up when you evidence it, and what you build stays yours between jobs. That is the part a course cannot do.

16The detail, folded away

Everything else the record holds

The career branches in full, how AI is already showing up in the day-to-day, and the questions people ask about this job. Here when you want them, out of the way while you decide.

Where it leads next, rung by rung

Where it leads

The career path, and where it branches

Lead Cloud Migration Architect is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. Principal Cloud Strategist

    3-5 years as Lead Cloud Migration Architect

    Level 5

    • Designing and implementing a full 'migration factory' process across multiple waves and teams.
    • Managing dependencies and risks across a portfolio of cloud programmes.
    • Owning the P&L for significant cloud initiatives (e.g., £500K-£2M budget responsibility).
    • Interfacing directly with C-suite and executive stakeholders on cloud strategy.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, cloud migration architecture involves a ton of repetitive tasks, from drafting runbook sections to sifting through dependency data. Imagine if you could offload some of that grunt work to an intelligent assistant. Well, you can. We're embracing AI to make our architects more effective, not replace them.

We're building an internal AI productivity hub specifically for our Technical_roles team. It's designed to help you with the heavy lifting, giving you back precious time to focus on the truly complex, strategic architectural challenges that only a human can solve. Think of it as having an incredibly fast, always-on research assistant and documentation drafter.

Runbook & Script Generation

Use AI assistants to generate boilerplate runbook sections or PowerShell/Bash scripts for common pre/post-migration checks. For example, 'generate a script to verify SQL Server service status' or 'draft a runbook section for DNS cutover steps.' This saves you from writing the same basic instructions over and over.

Dependency Analysis Accelerator

Feed outputs from discovery tools (like network traffic logs or server inventories) into an AI model. It can help identify and visualise potential application dependencies, suggest logical 'move groups,' and flag high-risk connections that might otherwise be missed. It's like having an extra pair of eyes that never gets tired.

Obscure Error Code Solver

When you're faced with a cryptic error code from a migration tool or a cloud provider API – and trust me, you will be – use an AI chat interface to instantly search forums, documentation, and knowledge bases. It'll often pull up known issues and solutions far quicker than you could manually, helping you unblock your team faster.

Stakeholder Comms Assistant

Generate first drafts of stakeholder communications, such as migration announcement emails, detailed status update summaries for project managers, or post-migration reports. Just give the AI the key data points, and it'll craft a professional, clear message, saving you time on tedious writing.

Common questions

Common questions

How do you become a Lead Cloud Migration Architect?

Common routes in include Senior Cloud Migration Engineer (3-5 years in previous role), Cloud Solutions Architect (Generalist) (4-6 years in previous role) and Senior Infrastructure Engineer (Cloud Focus) (5-7 years in previous role). Times vary with prior experience.

Where can a Lead Cloud Migration Architect progress to?

This role can lead on to Principal Cloud Strategist (3-5 years as Lead Cloud Migration Architect), depending on the skills you build.

What new skills matter most for a Lead Cloud Migration Architect?

Increasingly, FinOps & Cloud Cost Governance and Platform Engineering & Developer Experience. These are the skills our record of this role lists as growing.

Free tools

Want a read on where you stand?

Three free tools, no account needed. Each one ends with a role, a level and a way in.

Read the Zavmo manifesto to understand how you will be taught Meet your tutors

Or try another one

17Where to go from here

Other roles at Level 5

Same depth of qualification, different job. Useful if the work appeals but this particular role does not.

 More jobs in technology and data

Stay in the field you know and move sideways rather than up.
If you leave this industry

The skills involved apply across most industries, since many organisations move systems to the cloud. This can open paths into consultancies, tech companies, financial services, retail or public sector bodies.

This role profile is © 2026 Growth Engineering Technologies Ltd. Built from UK occupational standards and regulated qualification data, and written for Zavmo.

You're not behind. You're right on time. The shift is only just beginning. Your role won't look the same in two years. Be the one who leads the change, not the one it happens to. Start my free Growth Mindset module What happens next: a free account, then we build your plan as you set up. No card. Build your plan, see your roadmap and meet the twelve tutors matched to you. All free. When you're ready to start learning, it's £70 a month, billed monthly. Cancel any time and billing stops.