No side-track at all, Nick
Your links were very interesting....
With regard to your wish-list, I scanned it rather quickly and, presumably, you are aware that Vee-HIve has no functionality that permits it to integrate into a NLE package(?) so I won't dwell on those aspects. However, the program does support custom context-menus that could, I suppose, assist with such functionality (assuming that the NLE supports appropriate command-line functions). At the end of the day, the program was developed as a general, stand-alone media manager so is not ultra-strong in that area....
The ease-of-use elements of your wish-list are, I believe, largely already present in Vee-Hive but it is yours (and others) opinion in this regard that matters, of course. All feedback and suggestions are welcome, particularly from those managing very large collections as you guys here appear to be....
As far as market presence is concerned, I am all-to-aware that Vee-Hive isn't widely known about; I didn't originally develop it as a commercial application and have no budget for advertising and so forth. I'm also aware that it is very cheap. Part of the reason for this is that I have yet to write a proper user manual and I also lack the ability to guarantee its usability across a myriad of operating systems and machine configurations. Being a sole developer, I lack the hardware for such testing, I'm afraid. I do believe, however, that there is no comparable application with the search power of Vee-Hive. In many respects it's a sledge-hammer for cracking nuts, at least that is what it is to the vast majority of my users whose Libraries are pretty tiny. To you guys, it may be the sledge hammer you need to crack an, erm, giant nut!
As far as your migration question is concerned, I observe from your thread that MM stores its data in an MS SQL Server database. That being the case, I see no reason why an 'Import to Vee-Hive' function cannot be developed. As a matter of fact, your screenshots allayed one of my concerns that the tag structure in MM might not be compatible; it turns out that the structure in Vee-Hive could acommodate a translation quite easily. I would add to that Vee-Hive can further enhance that structure since it supports the concept of 'tagging tags' via links and synonyms. Perhaps you could make an MM file available to me via a file host and I can take a look at it?