Hi Pankaj,
Yes, it is possible to migrate the documents without using Mendix Runtime, but I would not recommend directly reading the Mendix database tables and extracting the binary data unless you fully understand the database structure.
A System.FileDocument is the Mendix system entity used for storing files, and its file content is binary data. Mendix also supports binary attributes directly in the database, although for most file scenarios Mendix recommends using a FileDocument association.
For a migration, I would suggest this approach:
FileDocument records, including metadata such as:If you still have access to the Mendix application, a safer migration approach is to expose/retrieve the files through Mendix rather than querying the internal database directly. Mendix supports retrieving FileDocument content through REST and storing the binary response as a file.
Also, depending on the deployment architecture, don't assume that the document binary is necessarily stored in the MSSQL database. For example, current Mendix environments can use separate blob/file storage for System.FileDocument contents.
So before writing SQL queries, Expose as REST API and Use in Non Mendix Application.
Kindly mark this as the accepted answer if it helps.