Migration & Modernization Competency
Validated for moving production estates onto AWS without a maintenance window, and for decomposing what remains once they are there.
- Validated
- March 2026
- March 2028
- 2 submitted
What it covers
Assessed on method, not just outcome.
AWS reviews how a partner plans, rehearses, and reverses a migration — not only whether the workloads eventually landed. These are the four areas examined.
Portfolio assessment
Workload inventory, dependency mapping, and a 6R pattern chosen per application.
Wave planning
Sequencing by risk and dependency, each wave with measurable go/no-go criteria.
Cutover execution
Traffic shadowing, dual writes, and progressive read shifting before any switch.
Rollback discipline
Reverse paths rehearsed at production data volume and left armed after cutover.
Validation criteria
What AWS assessed.
Competency validation for this practice required evidence across four gates, reviewed by AWS solutions architects against real engagement artifacts.
How validation worksCertified practitioners
Solutions Architect and DevOps certifications held across the delivery bench.
Customer references
Two named engagements with contactable clients and full architecture detail.
Technical review
Migration runbooks and rollback procedures examined against the AWS checklist.
Documented method
A repeatable delivery method, not a one-off success.
Evidence
The engagements behind it.
These are the customer references submitted to AWS for this competency. Ask us about any of them.
62%
Cost reduction
Twelve-branch retail estate consolidation
Twelve disconnected store systems moved onto one cloud platform in rehearsed waves, with zero planned downtime.
99.98%
Settlement accuracy
Payments platform replatform
Five payment rails migrated behind an orchestration layer with per-provider retries and reconciliation.
Architecture
Patterns behind this practice.
Services
What we build it on.
- AWS DMS
- Application Migration Service
- Aurora
- EKS
- Route 53
- CloudWatch
Team on this practice
Staffed from the platform and engagement benches — the same architects who wrote the runbooks sit on the delivery.
Other competencies.
All designationsCloud Operations
Validated for operating what we build — observability, incident practice, cost management, a…
Data & Analytics
Validated for warehouses, streaming pipelines, and managed ETL that stay operable after the …
Machine Learning
Submitted for applied AI that acts inside a product rather than alongside it — agent tooling…
Security
Submitted for residency-first architecture, least-privilege identity, and audit trails desig…
Work with this practice
Moving an estate without a window?
Discovery comes first — a short, bounded review that ends in an architecture, a scope, and a price. You keep the output either way.