Skip to content
METRIC OAK

New: the 3-week Data Platform Assessment: fixed fee, priced roadmap. See what's included →

Free tool

How long will your migration take?

Enter what you still use. You get engineer-days, calendar weeks for your team and a suggested number of waves. Runs in your browser.

Rule of thumb: 0.1 days per table, 1 day per job, 0.75 days per procedure or script, 0.25 days per report, 10 days per domain (parallel run and sign-off), plus 15 days of platform setup; scripted work is multiplied up by the custom-logic share.

Estimate

–

calendar weeks with your team

Engineer-days
Suggested waves
Largest effort

A rough planning range, not a quote. Real effort depends on code quality, test coverage and how quickly owners sign off.

Get a fixed price

Planning the move? Read our step-by-step migration guides for Teradata, Informatica, SSIS, Oracle, Hadoop and more.

Frequently asked questions

How is the estimate calculated?

Each object type has a typical effort in engineer-days (shown below the form), multiplied up for the share of custom or procedural logic. Each business domain adds time for its parallel run and sign-off, and a fixed amount covers platform setup. The total is spread across the team size you choose, with a range of 25% either side.

Why count only objects still in use?

Because the cheapest migration is not migrating. Query logs and job history usually show that a large share of legacy objects is no longer used; archive those instead of converting them.

How do I get a firm number?

A Data Platform Assessment inventories your estate from logs and code, measures effort by object type and ends with a fixed price for each migration wave.

Have 30 minutes? Get a senior architect’s view of your data platform.

No sales deck. You talk to the engineer who would lead the work.

Book an architecture review