During a planned database migration, we experienced sustained and escalating CPU spikes on the new primary database instance shortly after cutover. Despite scaling the infrastructure, adding replicas, creating missing indexes, deploying multiple hotfixes, and engaging appropriate support, performance issues persisted—ultimately traced to an improper index strategy and heavy update/truncate activity—leading to a full rollback to restore customer performance and stability.