Committee document
RFP section: requirements for migration tooling
Seven requirements to paste into an RFP for data warehouse migration tooling. Each asks for evidence a vendor can produce, not a claim it can make. Every vendor can answer them, including Novuz.
Requirements
The seven requirements, and the evidence to demand
| # | Requirement | Evidence the vendor must attach |
|---|---|---|
| 1 | Repeatable conversion: the same source object converted twice gives the same output. | Both outputs for one object we name, and the diff. |
| 2 | A written counting rule: what counts as converted, what counts as manual, how dead code is treated. | The rule, in one paragraph, before any percentage. |
| 3 | Evidence per object: each converted object compared with the original on the same inputs. | A full reconciliation report for an object we choose. |
| 4 | Coverage of our estate: procedures, ETL packages, scripts and schedules, not only SQL. | A coverage list against our inventory: converts, needs review, manual, not supported. |
| 5 | A stated data boundary: where code, converted code and reports live at each stage. | A deployment diagram with the network boundary drawn and every crossing labelled. |
| 6 | Commercial certainty: a fixed price after the estate is read, with a remedy if a threshold is missed. | The price, the date it holds until, and the guarantee clause as contract text. |
| 7 | Ownership and continuity: we own the output from the day it is produced, with no vendor runtime. | The ownership and escrow clauses, for counsel to review. |
Scoring
How responses should be scored
Publish the weights to every vendor with the RFP, before any demo. Score each requirement from 0 to 5 and ask for the artifact behind any score above 3. The shortlist comparison table holds a ready weighting.
RFP or pilot
Should we run an RFP or a pilot first?
A pilot first, when the estate has a date and the shortlist is under four vendors. Ten to twenty of your own objects, converted twice and reconciled on frozen inputs, separates approaches faster than written answers.
An RFP first, when procurement requires one or the shortlist is long. Then use the pilot to verify the two or three best responses, on the same objects for every vendor.
Below the document
Where to read next
Print or save this page as the RFP section. The scoring sheet and the evaluation guide carry the detail.
FAQ
Frequently asked questions
What should an RFP for data warehouse migration tooling require?
Evidence, not claims: a two-run diff, a written counting rule, a reconciliation report for an object you choose, coverage against your own inventory, a deployment diagram, a fixed price with a remedy, and ownership and escrow clauses.
Should we run an RFP or a pilot first for a migration tool?
A pilot first when the estate has a date and the shortlist is short: ten to twenty of your own objects, converted twice and reconciled. An RFP first when procurement requires it or the list is long, then pilot the best two or three responses.
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.