Our organization is evaluating a potential migration from a long-standing Teradata environment (20+ years) to AWS Redshift and would greatly value insights from anyone who has undertaken a similar journey. Our Current State: - Mature Teradata warehouse with extensive integrations - Multiple data products and analytics workloads - Established ETL processes and user base - Considering cloud modernization options Key Questions for the Community: 1. Migration Drivers: What were your primary motivations for moving from Teradata to Redshift? (Cost, performance, scalability, cloud-first strategy, etc.) 2. Technical Complexity: How did you handle the migration of: - Complex SQL and stored procedures - ETL/ELT processes - Data models and schemas - Existing integrations and APIs 3. Timeline & Resources: What was your migration timeline and team skills? 4. Performance Considerations: How did Redshift performance compare to your Teradata environment for similar workloads? 5. Change Management: How did you manage user adoption and training? What was the impact on business operations during transition? 6. Unexpected Challenges:What issues caught you off guard that we should plan for? 7. ROI Realization: How long did it take to see the expected benefits, and did they align with initial projections? Any high-level guidance, lessons learned, or "things I wish I knew before starting" would be incredibly helpful as we shape our strategy.
So, we are in the middle of a very similar transition. Here's my quick answers: 1. Teradata cost was the primary driver as we are estimating 70-75% savings with Redshift. The ability to scale on demand and an existing ...read more
1. Teradata cost was the primary driver as we are estimating 70-75% savings with Redshift. The ability to scale on demand and an existing ...read more