Moving data during a cloud migration can be complex and may cause latency and throughput issues if not done correctly. A well-planned database migration requires careful consideration of key areas such as assessment and planning, data assessment and cleansing, schema and code review, backup and recovery strategy, testing and validation, performance considerations, monitoring and logging, and post-migration support. Several factors can contribute to downtime during a database migration, including data volume, network issues, data structure changes, code changes, data cleansing and transformation, compatibility issues, and backup and restore processes. To achieve a zero-downtime database migration, three primary strategies are available: offline copy migration, master/read replica switch migration, and master/master migration. Each strategy has its own level of complexity and risk profile, and the choice of which one to use depends on the specific needs and capabilities of the application, data, and business. It is essential to mitigate migration risks by monitoring application performance during all aspects of the migration process and using tools such as New Relic to ensure data safety and security.