Spot on Jim.

You should check out some of the tools we've developed at EPS Software to take some of the pain out. For instance, even though the upsizing wizard in Sedna is much better than the stock VFP9 wizard, it's still designed for a one-shot deal which doesn't work very well in real life. We've developed some tools that look at your DBFs (and DBC if you use one) and 1) generate a SQL script that creates SQL tables making smart choices for field types 2) create SSIS packages for upsizing each table to SQL 3) run the packages as a group This give you an automated, FAST, repeatable, industrial strength upsizing process. It even carries metadata from the DBFs into the SQL DB so that you can map between the old and the new. For example, you may want to (or have to) change some field names in SQL. Now you have both the old and new field names in one place. The SSIS package creator will create a package that does this mapping for you.

There is also a free tool that gathers metrics about your VFP project(s). Even if you're not trying to determine the scope of a conversion project to .Net this free tool gives you a lot of valuable information about what you already have.

EPS also have some cool tools to convert forms and reports and has developed some libraries that makes converting to SQL back end with VFP much easier. We've done a LOT of conversion work and are happy to share some of what we've learned.