Thanks for the report. It’s fixed in the just-released 2.3.7 Release 2.3.7
If you didn’t touch the migration after reporting the issue, you should be able to reopen the migration assistant and continue from where you left.
1 Like