Hi Donald!

Rocketeers may have some standard formulas they use (probably for converting in the opposite direction), but my experience in this realm leads to an answer of "it depends".

"It depends" on the complexity of your current database.
"It depends" on the structure of the data itself.
"It depends" on how many indices you have, and how complex those are as well.
"It depends" on the complexity of your dictionaries.  How often are you referencing data in other files (tables), or other fields in the same file, where in a relational database that information might have to be duplicated?
"It depends" on the structure of the database in SQL.  Are you building a new environment, or migrating the data into an existing structure?

Whenever we've had to provide estimates, we usually try to build a POC scenario.  We do a migration of a 'typical' file (or multiple types of files) and then extrapolate from there as to what the rest of the database migration would look like.  And along the way we also have to remember that it's not just migrating the physical data, but also the functionality.  As mentioned above in regards to dictionaries - some things that you can do in U2 might require only a single instance of a piece of data, while in a relational database, that piece of data *might* need to be duplicated in another table (or in multiple additional tables).

Not sure if that actually helps or not.