In an older migrate 7.x-2.5 installation I had to reimport a complete hierarchical vocabulary after a crash in the destination system with a term migration. The terms had an image field and beside the term migration there is a file migration for these images that is used as dependency for the term migration. In the file migration the FILE_EXISTS_REUSE method is used.

The vocabulary in the destination system had no terms before starting the migration job and I also cleaned the migrate_map_... tables of both migrations (term + file) before the new migration from the source system.
As expected all terms were in the destination system after running the migration, but not the images.

A simple workaround was to delete the files in the file system of the destination system and re-run the migration again - and the images were re-connected with their terms.

This issue is to document this simple workaround and maybe there is someone with deeper knowledge of this really cool migrate module who can give me a hint what could prevent the need for my workaround (for the next crash ;-)

Thanks in advance.