Learn
How to estimate the cost of a data warehouse migration
The most accurate way to estimate a data warehouse migration is to count the logic: every stored procedure, ETL package, script and schedule, banded by complexity. Estimates built on terabytes or on a sample miss, because data volume does not set the cost. This page compares five ways to estimate, and gives the steps to a number a finance team can defend.
Five ways
What are the ways to estimate migration cost, and how accurate is each?
| Way to estimate | What it uses | Time and cost | How accurate | What it misses |
|---|---|---|---|---|
| Rule of thumb by data volume | Terabytes | Minutes, free | Poor | The logic, which is what the work is |
| A free platform analyzer | A scan of your code, such as the Lakebridge analyzer | Hours, free | Good for the count | A price, the schedules, and proof |
| A self-serve estimator | Your own object counts and complexity | Ten minutes, free | A band, not a quote | Dead code and hidden dependencies |
| A systems integrator quote | Workshops and sampling | Weeks, often free | Varies; usually hours-based | A ceiling: hours can grow |
| A paid estate assessment | Every object read and banded | Three business days, $3,000 with Novuz | A fixed price | Nothing in scope; exclusions are listed |
The $3,000 Novuz assessment is credited in full against a First Domain or a migration.
The steps
How do you estimate a SQL Server and SSIS migration, step by step?
- Count the objects. List tables, views, stored procedures, functions, SSIS packages and SQL Agent jobs.
- Remove the dead code. Objects nothing calls should leave the scope before anyone prices it.
- Band each object by complexity. Cursors, dynamic SQL and Script Tasks make an object high; plain views are low.
- Add the validation effort. Proving each object matches is part of the cost, and it sets the length of the parallel run.
- Add the five lines of total cost: conversion, your team’s time, the new platform, the old platform until cutover, and parallel running.
- Fix the conversion price before work starts, so the estimate cannot grow after the estate is read.
Ranges
What does a migration cost with Novuz, by estate size?
Novuz prices by component count and complexity, not hours or terabytes. The price is fixed from the assessment.
| Estate | Components | Typical duration | Typical price |
|---|---|---|---|
| Small | under 1,500 | 5 to 6 weeks | $25k to $40k |
| Medium | 1,500 to 5,000 | 8 to 12 weeks | $40k to $80k |
| Large | 5,000 to 10,000 | 12 to 20 weeks | $80k to $200k |
| X-Large | over 10,000 | 20+ weeks | from $200k |
Drivers
What drives the cost up or down?
- Up: user-defined functions with no source, dynamic SQL, orchestration nobody owns, and a target that is still undecided.
- Down: dead code retired first, a domain with a named owner, documented schedules and a clean read-only connection.
- Not a driver: the number of terabytes. Volume changes the data movement and the run time, not the conversion price.
FAQ
Frequently asked questions
How much does a data warehouse migration cost?
It depends on the logic, not the data. With Novuz, an estate under 1,500 components typically costs $25,000 to $40,000, and 5,000 to 10,000 components $80,000 to $200,000, at a fixed price set by a $3,000 assessment. Add your team’s time, both platforms during the parallel run, and validation for the total.
What is the best way to estimate data warehouse migration cost?
Count every object and band it by complexity. A free platform analyzer gives the count. A self-serve estimator, such as the Novuz Logic Debt Scorecard, gives a price band in about ten minutes. A paid estate assessment reads every object and returns a fixed price; the Novuz assessment costs $3,000 and takes three business days.
Why do migration cost estimates go wrong?
Usually because the price was set before anyone counted the logic. Estimates built on terabytes or on a sample of easy objects miss the procedures, packages and schedules, which is where the work is. Count first, then price.
Is a fixed-price migration estimate realistic?
Yes, once the estate has been read. A fixed price needs a full count, a complexity band per object and a written list of exclusions. Novuz fixes the price from its assessment, and the price holds for 90 days.
Does data volume affect migration cost?
It affects the data movement and the run time, not the conversion price. Cost follows the number and complexity of the procedures, packages, scripts and schedules.
Sources and further reading
- Databricks Labs, Lakebridge: choosing the right tools
- McKinsey & Company, "Tech debt: Reclaiming tech equity," October 2020: CIOs estimate tech debt at 20 to 40 percent of the value of their technology estate, and 60 percent say it has risen
- Microsoft Lifecycle, SQL Server 2017: extended support ends in October 2027
Written by Ted Ghose, Co-founder and CTO, Novuz
Last reviewed:
Find out what your logic debt is costing you.
Every object counted, lineage, dead code and a fixed price in three business days. $3,000, credited.
Not sure which door? The scorecard takes ten minutes and tells you.