I too had the same issue. I applied a little 'hack' to the agent files that was able to make it work. Essentially, I told the migration wizard to ignore the error and move on. To my suprise, this actually worked and sent the database over.
NOTE - this is a hack, so do this at your own...