1 Technical Success Criteria

a) Functionality Validation

• All migrated applications and services function as expected post-migration.
• Application dependencies (databases, APIs, fileshares, DNS, IAM roles) are correctly re-mapped and reachable.
• No critical errors in system logs post-migration.

b) Performance & Latency

• Application response times meet or exceed pre-migration benchmarks.
• Network latency between tiers (app ↔ DB, app ↔ external APIs) remains within acceptable limits.
• AWS instance type sizing matches performance and cost expectations.

c) Data Integrity

• 100% data consistency verified between source and target (checksums, row counts, object validation).
• Database and filesystem replication verified with no corruption.
• Point-in-time recovery and backup integrity confirmed.

d) Security & Compliance

• All IAM roles, security groups, and NACLs adhere to least-privilege principles.
• Encryption in transit (TLS) and at rest (KMS, EBS, S3) confirmed.
• Compliance checks pass (CIS, NIST, PCI DSS, ISO 27001 as applicable).

e) Monitoring & Observability

• Amazon CloudWatch metrics, logs, and alarms configured for CPU, memory, disk, and network.
• Centralized logging (e.g., CloudWatch Logs, OpenSearch, or Splunk) integrated.
• Application health checks configured via ALB/ELB.

2 Operational Success Criteria

a) Cutover and Rollback

• Cutover completed within maintenance window with minimal downtime.
• Validated rollback plan (AMI snapshot, DMS rollback, or DR restore) tested and documented.
• No orphaned or untagged resources left behind post-migration.

b) Automation & Manageability

• Backups automated (AWS Backup, EBS snapshots, RDS automated backups).
• Patch management via Systems Manager Patch Manager or 3rd-party tool configured.
• Infrastructure-as-Code (CloudFormation/Terraform) implemented for repeatability.

c) Access & Identity

• Correct IAM mappings for system/service accounts.
• No hardcoded credentials; secrets stored in AWS Secrets Manager or Parameter Store.
• MFA enforced for administrative access.

3 Business & Financial Success Criteria

a) Cost Efficiency

• Cost comparison shows ≥10–30% reduction from on-prem TCO or expected parity with improved elasticity.
• Reserved Instances or Savings Plans adopted where workloads are steady-state.
• Resource utilization optimized (no oversized instances).

b) Uptime & Availability

• Meets SLAs (e.g., ≥99.9% uptime).
• Multi-AZ or multi-region high-availability tested successfully.
• Recovery Time Objective (RTO) and Recovery Point Objective (RPO) achieved.

c) Stakeholder Sign-Off

• Application owners validate successful migration.
• End-users report no degradation in usability.
• Security, compliance, and operations teams approve go-live state.

4 Sample Success Criteria Summary Table