TCO Analysis — Teradata vs Azure¶

Audience: Finance leads, CIOs, and enterprise architects building the business case for Teradata-to-Azure migration. All numbers are representative ranges based on typical enterprise deployments; adjust to your actual contracts and environment.

1. Executive summary¶

A typical medium-size Teradata deployment (10-20 nodes, 100-300 TB) costs \(3M-\)7M/year fully loaded (license, hardware, datacenter, DBA team, tools). The equivalent Azure deployment at steady state costs \(1.2M-\)2.5M/year — a 50-65% reduction.

The migration itself costs \(3M-\)10M over 18-24 months (tooling, migration team, dual-run period). At steady state, the investment pays back in 2-3 years and delivers \(8M-\)20M cumulative savings over five years.

VantageCloud (Teradata's cloud offering) reduces hardware/DC costs but retains Teradata license premiums, landing at \(2.5M-\)5M/year — better than on-prem but still 2-3x Azure steady-state costs.

2. On-premises Teradata cost model¶

2.1 Hardware and datacenter¶

2.2 Teradata software license¶

Teradata licenses are typically priced per node or per TB of managed storage. Enterprise agreements include:

2.3 Operations team¶

2.4 Total on-prem Teradata (annual)¶

3. VantageCloud cost model¶

Teradata's cloud offering (VantageCloud Lake or VantageCloud Enterprise) moves hardware costs to Teradata/cloud provider but retains license premiums.

3.1 VantageCloud pricing¶

3.2 Operational cost remains¶

Even on VantageCloud, you still need:

• Teradata-skilled DBAs (same headcount, same rates)
• Teradata-specific ETL tooling knowledge
• Teradata SQL dialect expertise

VantageCloud reduces hardware/DC costs by 100% but reduces total TCO by only 25-40% because the license and people costs remain.

4. Azure target-state cost model¶

4.1 Compute¶

Note: Choose one primary compute engine (Synapse, Databricks, or Fabric). The table shows ranges per engine. Most organizations also use a secondary engine for specific workloads.

4.2 Storage¶

4.3 Supporting services¶

4.4 Operations team (Azure)¶

4.5 Total Azure steady-state (annual)¶

5. Migration cost (one-time)¶

5.1 Migration program costs¶

5.2 Dual-run detail¶

During migration (typically 12-24 months), both Teradata and Azure run simultaneously:

Plan for 3-5x steady-state cost at the peak of dual-run (months 13-18).

6. Five-year TCO projection (medium estate)¶

Using the midpoint of medium ranges:

Key assumptions¶

• Medium estate: 15 nodes, 150 TB, 3,000 tables
• 18-month migration timeline
• Azure steady state includes Databricks SQL + ADLS + Power BI + ADF
• Teradata includes one hardware refresh in year 3
• VantageCloud annual price escalator: 3%
• Azure consumption growth: 5%/year (workload growth)
• No reserved capacity discounts applied (would improve Azure case)

7. Sensitivity analysis¶

What changes the math¶

Break-even scenarios¶

Azure migration does not make financial sense if:

• Teradata estate is very small (<$1M/year total cost) — migration cost exceeds 5-year savings
• Teradata license was just renewed at a significant discount with 4+ years remaining
• Organization cannot fund 18-24 months of dual-run costs
• Teradata contract includes punitive early termination fees exceeding $2M

8. Hidden costs often missed¶

Teradata hidden costs (frequently underestimated)¶

Azure hidden costs (frequently underestimated)¶

9. Cost optimization strategies for Azure¶

Immediate wins (day 1)¶

Medium-term (months 3-6)¶

Long-term (months 6-12)¶

See docs/COST_MANAGEMENT.md for platform-wide cost optimization guidance.

10. Building the business case¶

Required inputs from your environment¶

To build an accurate TCO, gather:

1. Current Teradata contract — Annual license, maintenance, expiration date, renewal terms
2. Hardware inventory — Model, node count, age, next refresh date
3. Datacenter costs — Rack space, power, cooling allocated to Teradata
4. Staff allocation — FTEs dedicated to Teradata admin, ETL, support
5. Workload profile — Peak vs average utilization, seasonal patterns
6. Data volumes — Current size, growth rate, retention requirements
7. Tool licenses — BTEQ, TPT, third-party ETL, BI tools connecting to Teradata

Business case template¶

CURRENT STATE (Annual)
  Teradata license + maintenance:    $________
  Hardware / datacenter:             $________
  Operations team:                   $________
  Tools and training:                $________
  TOTAL CURRENT:                     $________

MIGRATION (One-time, 18-24 months)
  Migration tooling:                 $________
  Migration team:                    $________
  Dual-run costs:                    $________
  Training:                          $________
  TOTAL MIGRATION:                   $________

FUTURE STATE (Annual, steady state)
  Azure compute:                     $________
  Azure storage:                     $________
  Azure services:                    $________
  Operations team:                   $________
  TOTAL FUTURE:                      $________

SAVINGS
  Annual savings:                    $________
  Payback period:                    ________ months
  5-year cumulative savings:         $________

11. Related resources¶

• Why Azure over Teradata — Strategic rationale
• Benchmarks — Performance comparison data
• Best Practices — Migration planning guidance
• Teradata Migration Overview — Original cost section
• docs/COST_MANAGEMENT.md — Platform-wide Azure cost optimization
• Azure Pricing Calculator: https://azure.microsoft.com/pricing/calculator
• Databricks Pricing: https://www.databricks.com/product/pricing
• Fabric Pricing: https://azure.microsoft.com/pricing/details/microsoft-fabric

Maintainers: csa-inabox core team Last updated: 2026-04-30