Enterprise Cloud Cutover Execution Checklist

Role: Enterprise Cloud Solutions Architect specializing in mission-critical workload migrations and infrastructure cutover execution.

Context

• System name: {{system_name}}
• Source environment: {{source_environment}}
• Target cloud platform: {{target_cloud_platform}}
• Allowable downtime window: {{allowable_downtime_window}}
• Data volume scope: {{data_volume_scope}}
• Rollback threshold: {{rollback_threshold}}

Task

Construct a rigorous technical cutover execution checklist to guide systems engineering teams through moving {{system_name}} from {{source_environment}} to {{target_cloud_platform}} within {{allowable_downtime_window}}.

Method

1. Evaluate {{data_volume_scope}} against network bandwidth and delta synchronization schedules prior to initiating maintenance.
2. Define pre-flight environment validations for networking, IAM roles, and security groups on {{target_cloud_platform}}.
3. Sequence data freeze checkpoints on {{source_environment}} to halt write traffic and prevent split-brain anomalies.
4. Establish final delta replication and database consistency verification procedures.
5. Detail traffic redirection steps covering DNS propagation, load balancer weight shifting, and TLS certificate bindings.
6. Formulate post-migration smoke testing items covering core application transactions and third-party integrations.
7. Establish unambiguous rollback execution triggers aligned directly with {{rollback_threshold}}.

Constraints

• MUST express cutover steps chronologically relative to T-minus and T-plus timeline notation within {{allowable_downtime_window}}.
• MUST establish explicit quantitative criteria for initiating a rollback based on {{rollback_threshold}}.
• MUST NOT omit data integrity validation prior to updating production routing.
• Keep instructions concise, technical, and operational without conversational filler.

Output format

• Section 1: Cutover Window Overview (table with maintenance window start, stop, target platform, and critical contacts).
• Section 2: T-Minus Pre-Cutover Preparation Checklist (5-7 pre-flight validation items).
• Section 3: T-Zero Live Migration Checklist (6-8 sequential technical execution items with estimated durations).
• Section 4: T-Plus Smoke Testing & Validation Checklist (4-6 functional verification checks).
• Section 5: Rollback Execution Plan (3-4 deterministic abort criteria and rollback steps).

Self-review

1. Does every phase reflect the constraints of {{allowable_downtime_window}} and {{data_volume_scope}}?
2. Are the rollback triggers in Section 5 explicitly tied to {{rollback_threshold}}?
3. Are all cutover steps ordered chronologically using relative timeline notation?