Most open source projects, elementary, missing quality, even in common scenario, or in developers language I'm calling that as "positive scenario". When your program works if everything is done as expected.
Usually there are only few positive scenarios, and usually they are developed first and working first.
This project started good, but now I see that you can't even complete the "positive scenario" of migration.
I'm afraid from only thinking about all the "negative scenarios", which exists infinitely much more than positives (they can heat hard even well organized company/project!), it does not looks like you are ready to this, it looks like you failed in very basic step of creating "working user-friendly product".
The main problem of such projects(why they do fail), because open source developers do not recognize the level of responsibility they do have, once they started to develop the end user application. They think server/c++/java/problem/solution..., while they should think like user thinks. Before releasing anything to public, imagine that somebody's grandmother will use it, not you.
This is my statement, as developer and technical leader in some company.
Currently, I'm leaving any attempts to restore my wallet, I'm waiting for single click solution.
Only if you success to provide it, the project will have a chance to live...(and its not because of me).