Learn
Know what your migration will cost before it starts
The migration budget is the number a CFO remembers. When conversion is priced by usage, by tokens, compute or hours, the final cost is known only when the work ends, and every retry and rework adds to it. A fixed price set from a counted estate moves that risk to the vendor, before work starts.
3 days
From code to a fixed price
The estate assessment
$3,000
For the assessment
Credited in full
90 days
The price stays valid
Once it is set
0 tokens
For about 95% of objects
Converted by fixed rules
Where the money goes
Where does the money in a migration actually go?
Conversion is the line on the quote. The rest is where budgets overrun.
Conversion
Translating the code. The part most quotes price.
Retries and rework
Objects that fail, get fixed and are run again, often more than once.
Validation
Proving the converted objects give the same numbers. Often most of the effort.
Orchestration
Rebuilding the schedules and dependencies so the estate runs unattended.
Parallel running
Paying for both platforms until the old one can be switched off.
People
Engineers, testers and the business owners who sign off.
Usage pricing
Why is a usage-priced conversion hard to budget?
Because the bill grows with things nobody can count in advance. With any converter priced by tokens, compute or hours, the final cost depends on how the estate behaves, not on how big it is.
- Each attempt at an object costs, and the hard objects take several attempts.
- A fix to one pattern can mean running many objects again.
- Large estates run in batches, so the work and the bill repeat batch by batch.
- The estate is rarely counted first, so even the starting size is an estimate.
- Conversion is priced, but validation, orchestration and parallel running usually are not.
A budget needs one number. Usage pricing gives you a rate.
Ask any vendor for the final number for your estate, in writing, before work starts. If they cannot give one, the risk is yours.
Side by side
Usage-priced or fixed: what changes for the budget?
Priced by usage
The rate is known; the total is not
- Cost grows with retries and reruns
- Final number known when the work ends
- Validation and parallel running priced separately
- You carry the risk of hard objects
Fixed from a counted estate
The total is known before work starts
- Every object counted first, dead code removed
- One price per scope, valid for 90 days
- Token use never changes the price
- The vendor carries the risk of hard objects
How it works
How does Novuz fix the price?
From a count, not an estimate. Price follows object count and complexity, not hours, terabytes or tokens.
- 01
3 days
Estate assessment
Every object counted, dead code found, lineage mapped and a fixed price set per object.
- 02
5–6 weeks
First Domain
One business domain converted and reconciled, with the threshold written into the charter: 95% by default.
- 03
Pass or credit
Readout
Results against the charter. If the threshold is missed after the cure period and exclusions, the fee is waived or credited in full.
- 04
4–8 weeks typical
The rest of the estate
Domain by domain, on the same rules, with the same evidence for every object.
Tokens
Does model usage change the Novuz price?
No. About 95% of objects convert by fixed rules with no model call, so they use no tokens. The resolver handles the rest, at about 700 to 1,000 tokens per edge case, on a model you approve. Token use never changes the price.
Proof
What does cost certainty look like on a real estate?
Customers are described, not named, until each gives written permission.
Questions to ask
What should we ask any vendor before we sign?
- What is the final number for our estate, in writing, before work starts?
- Is it fixed from a count of our objects, and is dead code taken out first?
- Who pays for retries, reruns, model tokens or extra hours when an object fails?
- Does the price include validation, orchestration and cutover, or only conversion?
- How long will both platforms run, and who pays for that time?
- What happens to the fee if the result misses the agreed threshold?
Limits
When is a fixed price the wrong model?
When the estate cannot be counted first, or the scope will keep changing. For a small, SQL-only estate moving to one platform, that platform’s own tool may be enough. A fixed price needs a counted estate and agreed inputs.
Next question
Where to read next
Converted is not finished. What a complete migration includes, and what an unfinished one keeps costing.
FAQ
Frequently asked questions
How can we know what a data warehouse migration will cost before it starts?
Count the estate first, then get a fixed price from that count. The Novuz estate assessment counts every object, removes the dead code and sets a fixed price in three business days, for $3,000, credited in full. The price is valid for 90 days.
Can an AI-driven migration have a fixed price?
Only if the vendor carries the risk of retries and rework. Ask for the final number for your estate in writing before work starts, and ask who pays when an object fails. Novuz converts about 95% of objects by fixed rules with no tokens, so its price does not move with model usage.
What does a full data warehouse migration cost with Novuz?
A full estate is typically $40,000 to $200,000 for 1,500 to 10,000 objects, set as a fixed price from the assessment. A First Domain is $25,000 to $40,000, and the assessment is $3,000, credited in full.
What costs are usually left out of a migration quote?
Validation, rebuilding the orchestration, and the months of paying for two platforms. Ask whether each is in the price, and how long both platforms will run.
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.