Running a server of your own comes with a lot of responsibility. I think your judgement is good.
When you export a base in a dtable file, all current information is saved in this file. When you reimport the dtable file, the base will look just like the base you exported.
There is some data loss though. The history of a base is not exported. Nor are comments exported.
My comment was more in the direction of an Excel export. When you export a table into CSV/XLSX, a lot of data and metadata is lost. Images cannot be exported in these file types, same thing for geolocation, … Metadata is also lost because the links between tables, formulas, … are lost.
The formatted text column stores text and content in the markdown format: Markdown - Wikipedia That’s a very popular format (i.e., Github uses it). When you copy-paste the content in a markdown editor (i.e., typora), the editor will interpret the “control characters” like SeaTable does.
But just to be clear: You cannot simply import a markdown text into another database. The support of markdown in the base editor is a feature of SeaTable.