Snapshot complete
Confirm the initial copy finished and identify any failed or skipped tables.
MySQL Migration Cutover Checklist
Make MySQL cutover a checklist, not a war room guess.
Cupcake DRCP brings the moving parts of a MySQL migration into one flow: plan, snapshot, CDC catch-up, validate, compare, reconcile, and approve cutover.
Why It Matters
Turn database movement into an operating workflow.
CDC caught up
Watch stream lag and heartbeat freshness before asking teams to switch traffic.
Compare and repair clear
Use compare results and reconcile history as cutover gates, not after-the-fact surprises.
Product Workflows
Related Cupcake DRCP screens.
Checklist
Cutover readiness checklist
Step 1
Confirm the snapshot baseline completed for all in-scope tables.
Step 2
Verify CDC lag and heartbeat freshness are inside the cutover threshold.
Step 3
Run compare on cutover-critical tables and review unresolved drift.
Step 4
Repair or explicitly accept differences before promotion.
Step 5
Record blockers, approvals, and rollback notes before traffic moves.
Community Discovery
Useful MySQL operations topics to keep exploring.
FAQs
Quick answers.
What blocks a cutover?
High lag, stale heartbeat, failed snapshot tables, unresolved drift, failed reconcile jobs, or missing approval evidence should all pause cutover.
Can Cupcake support rollback planning?
Cupcake keeps project context and evidence for recovery workflows, making rollback and retry discussions easier to ground in facts.