Skip to content
In progressAWS Competency

Migration & Modernization Competency

Practice area covering moving production estates onto AWS without a maintenance window, and for decomposing what remains once they are there.

Status
In progress
Reviewed
In progress
Renews
—
References
Pending approval

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.

The criteria AWS assesses for this competency, and our current status against each. Status is maintained in the CMS from AWS Partner Central.

How validation works

Certified practitioners

Solutions Architect and DevOps certifications held across the delivery bench.

In progress

Customer references

Two named engagements with contactable clients and full architecture detail.

In progress

Technical review

Migration runbooks and rollback procedures examined against the AWS checklist.

In progress

Documented method

A repeatable delivery method, not a one-off success.

In progress

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.

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.