One of the (valid, actually) criticisms of "home-grown databases" made on here over the years has been:- what happens when the developer leaves the team? That was why I mentioned being careful with your source code.
I agree with your first paragraph. Like you (I imagine) I have been around long enough to see many Big Ideas (about how to deliver biomed services) come and go; yet the fundamentals remain.
Meanwhile, exporting to, and importing from, other applications - such as Ansur, or any other - is generally possible as long as you can dig into the file structures they use (or have access to detailed technical documentation - not always easy). Then, if you have the time, you can usually write some sort of interfacing code.
Well, that is OK as long as those proprietary files can be presented in common-or-garden ASCII format, but it seems that (like seemingly everything else these days) "clever people" are not satisfied with that, and insist on using the latest Gee-Whiz file formats that can be very difficult to de-code (or simply not worth the effort). In my experience, that stuff adds nothing of real (practical) value; unless "bloatware" is seen as a Good Thing!
What we want is utility and reliability ... not "bells and whistles"! A practical "workplace" to help you get the (real) work done.