migrating-to-amazon-redshift

Guides end-to-end Teradata data warehouse migration to Amazon Redshift.

2.5k|282|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/aws/agent-toolkit-for-aws --skill migrating-to-amazon-redshift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrating-to-amazon-redshift
Source: https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/analytics-skills/migrating-to-amazon-redshift
Command: npx skills add https://github.com/aws/agent-toolkit-for-aws --skill migrating-to-amazon-redshift

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Migrating a Teradata (Vantage) data warehouse to Amazon Redshift requires converting DDL, SQL, stored procedures, macros, and BTEQ scripts, moving data reliably, and validating results — a complex, error-prone process with many dialect differences and no direct equivalents for some constructs.

Core Features & Use Cases

  • Six-phase migration workflow: discovery (read-only DBC catalog queries), conversion (72 validated Teradata-to-Redshift rules), data migration (extract to S3 then COPY), validation, performance comparison, and reporting, with resumable state tracking.
  • Conversion knowledge base: deterministic rules for type mapping, PRIMARY INDEX to DISTKEY, PPI to SORTKEY, stored procedures to PL/pgSQL, and BTEQ to RSQL, plus a flagged manual-rewrite backlog for constructs like RESET WHEN, EXPAND ON, and cursors.
  • Use Case: A team needs to move a Teradata warehouse to Redshift. The AI inventories the source with read-only queries, converts schemas and SQL with confidence scoring, generates restartable extract/COPY scripts staging through S3, validates row counts and aggregates, and produces a migration report.

Quick Start

Ask the AI to assess and migrate your Teradata database to Amazon Redshift, starting with a read-only discovery inventory of the source system.

Frequently Asked Questions about migrating-to-amazon-redshift

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Teradata to Amazon Redshift?

Follow the six-phase workflow: run read-only discovery queries against DBC catalog views, convert DDL and SQL using the validated conversion rules, extract data to S3 and load with COPY, validate row counts and aggregates, compare query performance, and generate a migration report.

How to convert Teradata SQL and stored procedures to Redshift?

Apply the 72 conversion rules covering function replacements (SUBSTR to SUBSTRING, ZEROIFNULL to COALESCE), statement transformations, and DDL changes. Stored procedures become PL/pgSQL, and constructs without direct equivalents like cursors or RESET WHEN are flagged for manual rewrite.

Does Teradata PRIMARY INDEX map to Redshift DISTKEY?

Yes, a single-column PRIMARY INDEX maps to DISTKEY on that column, while multi-column primary indexes default to DISTSTYLE EVEN. PARTITION BY RANGE_N maps to SORTKEY, and join indexes become materialized views.

Can I run Teradata BTEQ scripts on macOS during migration?

No, BTEQ and TPT require the Teradata TTU client, which is Linux and Windows only. On macOS, use WRITE_NOS for in-database export to S3 or the cross-platform teradatasql Python driver for discovery and extraction.

What Teradata constructs cannot be automatically converted to Redshift?

Triggers, cursors, RESET WHEN, EXPAND ON, TD_UNPIVOT, NONSEQUENCED temporal, ALTER TABLE MODIFY, and PERIOD types have no direct Redshift equivalent. These are flagged in a manual review backlog with suggested structural rewrites such as CTEs or generate_series.

Is discovery safe to run on a production Teradata system?

Yes, discovery is strictly read-only, using SELECT-only queries against DBC catalog views with a read-only user. It never enables query logging or modifies production state; if DBQL is disabled it falls back to the always-on AMPUsageV view.