all I can tell you is the obvious. If you actually have a programmer who can clip code out of your old fox 2.5 program and knows either fox 2.5/6 for either dos or windows and has developed for years in one of those and then also has similar experience in VFP and in the specific class library/framework that you want him to work in. Hopefully your vfp programmer has one he prefers and can show you samples of his work in it. If he has known good productivity in both skills, then you migrate. If he doesn't, then you invest money otherwise.

Also, if you switch it to vfp, then you may not want to merely rely on the microsoft 'migration' systems. If you rely on the migration, then it should definitely be only temporary as your programmer re-does everything, but gets exact same results with as much re-used code as possible. With the model code from the old fox, the programmer should be able to translate the code into his prefferred vfp system with much better results than by using microsoft's migrate. I've never done the migrate, but that's my impression and that's what someone I know experienced when they migrated successfully a fox 2.6 windows app to vfp.