Yes, it would be amazing to have but probably the migration 0.8 -> 1.0 is actually the more important migration. So it is okay to release 0.9.4 without the migration tool. If there are some delays in the release, we can of course already ship 0.9.4 with the tool, potentially also with little testing as the tool is not immediately mission critical. (If there is a problem, people will be able to wait for 0.9.5 or even later).

The least we should do is package this #3575 (comment) into a script and ship it as a kdb tool. Then there is at least something, even if it isn't well tested.

Thank you for reminding. If we provide such a hack, it is imho better if we are transparently about it and paste the script into the release notes. Then the people have some idea about which limitations the script might have.

if we are transparently about it and paste the script into the release notes

Yes that might be better. Ideally with an link to the issue, in so that there is a common location to report problems.

The script was added to the release notes. I will close the issue for now. If there are any plans to improve the upgrade procedure (e.g. shipping a tool) please reopen.