The claim is that Mendix has no vendor lock-in for the data and the models. There is no claim for the applicationcode itself.
How that claim is executed in practice is:
Step 2 is already a hell of a job, and there is no template or example how to do that.
And then there is the application itself. You will have to manually write and/or refactor it by yourself. There is no tooling to convert a microflow, or any other documenttype, to Java, .Net etc.
And then there is the issue of the association tables. You will have to convert them to regular associations.
So technically there is indeed no lock-in. Data and model are always available to you. But there is no ‘Convert-to-.Net-application’.
Frankly, I am hoping that some one who has actually moved away from a Mendix app will step in. And that person will share his experience on how it is done, the hurdles that had to get taken and the tools that are available and can be used.
Once you decide to use low code, you are moving away from traditional coding. It is not make sense to reverse back to traditional coding, the cost to reverse back is always higher then maintanance one.