Global Financial Services Provider Migrates from Teradata to Snowflake and Amazon Redshift
A Teradata migration to two cloud platforms: 19 million lines of SQL and stored procedure code translated, 72% faster than manual estimates.
Next Pathway is a Snowflake Elite partner, trusted by global enterprises to deliver end-to-end modernization, from discovery to production cutover.
Case study summary: Teradata to Snowflake and Amazon Redshift
A global financial services provider needed to move off Teradata and split its workloads across two cloud platforms, Snowflake and Amazon Redshift. Its estate held 19 million lines of SQL and stored procedure code, nearly 2 petabytes of historical data and more than 2,200 data sources.
Next Pathway began with a 4-week assessment that mapped end-to-end data lineage, found hot and cold spots, and showed which workloads belonged on each platform. Next Pathway's automated translation technology then converted 99% of the code out of the box, and reached 100% of the Teradata SQL and stored procedures within 4 weeks of execution starting.
The automated approach cut delivery timelines by 72% compared with earlier manual estimates.
Download your free case study
Get the full Teradata to Snowflake and Amazon Redshift story.
By providing information in this form, you agree to Next Pathway’s Privacy Policy
What the case study covers
How a global financial services provider planned and delivered a Teradata migration to Snowflake and Amazon Redshift.
Teradata migration assessment
The provider needed to decide which workloads suited Snowflake and which suited Amazon Redshift. A 4-week assessment by Next Pathway mapped end-to-end data lineage, hot and cold spots, and optimization opportunities.
Large-scale code translation
The Teradata estate held 19 million lines of SQL and stored procedure code, nearly 2 petabytes of historical data and more than 2,200 data sources. Automated translation reached 99% out of the box across both Snowflake and Amazon Redshift.
Faster delivery
Once execution began, 100% of the Teradata SQL and stored procedures were translated in 4 weeks, cutting delivery timelines by 72% compared with earlier manual estimates.
1B+
Lines of legacy code translated
160+
Migrations and modernizations delivered
80%
Faster than manual and semi-automated approaches
Frequently asked questions
Why did the company migrate from Teradata to both Snowflake and Amazon Redshift?
It wanted each workload on the platform that suited it best. A 4-week assessment mapped data lineage and usage so the team could decide which workloads went to Snowflake and which went to Amazon Redshift.
How much Teradata code was translated?
19 million lines of Teradata SQL and stored procedure code, alongside nearly 2 petabytes of historical data and more than 2,200 data sources. Automated translation reached 99% out of the box and 100% within 4 weeks of execution starting.
How much faster was the automated approach?
Delivery timelines were 72% faster than the earlier manual estimates for the same scope.
What does a Teradata migration assessment include?
Next Pathway's assessment maps end-to-end data lineage, finds hot and cold spots, flags optimization opportunities and sorts workloads by target platform, so the migration plan is set before any code is translated.
What Industry Analysts Say
Rob Enderle
ENDERLE GROUP
Eric Kavanagh
THE BLOOR GROUP
What a structured Teradata migration covers
A successful Teradata migration needs a clear plan across four disciplines.
Discovery and dependency mapping
Every code object, ETL pipeline and data dependency is identified and documented before migration begins, so the plan reflects the real estate.
Code translation and modernization
Legacy SQL, stored procedures and ETL pipelines are converted into optimized, cloud-native workloads for each target platform. Automated translation covers the full estate.
Validation and functional parity
Every migrated workload is validated against the legacy source to confirm data accuracy and functional equivalence before cutover.
Production cutover planning
Cutover runs on a defined plan covering resources, timing and business approval. Teams that plan cutover from the start move faster and with more confidence.
Latest Insights on Modernization
How to Capture Institutional Knowledge From Legacy Data Platforms for Modernization and AI
