Really there's not much that can be done in this situation. The "easy mode" auto migration should handle this automatically, similarly to how other IoError and UnsuitableEnvironmentPath errors are ignored. The non-auto migration is still available for manual/complex handling of such problems.
I've added a commit that addresses comments and makes error handling less surprising. It also documents which migration method is suitable for which kind of task to make it easier to pick between them.
Really there's not much that can be done in this situation. The "easy mode" auto migration should handle this automatically, similarly to how other IoError and UnsuitableEnvironmentPath errors are ignored. The non-auto migration is still available for manual/complex handling of such problems.