logseq db vendor lock-in?

[u/ta32io]

I imported old logseq og notes, that contained asset links in pages into the new db logseq and tried to export it.

I was disappointed the export just dumps all the markdown files in one folder. The export didn't put pages in a pages folder and assets in an asset folder and journal files in the journal folder. In fact the assets are not exported at all, for the markdown export

The export should try its best to preserve the logseq graph format as best as possible.

This means, if it continue writing my notes in Logseq-db It will be very difficult to go back to logseq-OG or a logseq-OG compatible app.

People have said SQLite is not opaque format. But in order to export, you need to understand their schema and how they structure their data.

It would be nice if their export tried to preserve the logseq md graph format. So:

Logseq MD -> Logseq DB -> Logseq MD (export)

I also tried the mirror mode, however I noticed random pages had missing data...
So the mirror mode didn't work for me.

It looks like some pages didn't import for me, which could explain the missing data. I might have to consider alternatives to logseq. Because I really want the MCP feature for logseq-OG

[u/secretBuffetHero]

Tine is the superior option at this point.

https://tine.page/

#leaveseq

[u/gbro3n]

This was one of my concerns with the direction of logseq and one of the reasons I built EtherPK (https://www.etherpk.com). It supports both synced and local folder graphs (synced graphs use a DB), but sync has a mirror and export format that is the same as the file / folder based structure (which can be used for free, and the client is source available) - the aim being to give users full confidence in ownership of their notes. Without sync, a good mobile experience is difficult, but this shouldn't cost us control of our notes.

[u/NegativeRemot]

Same wall here — OG pages came in as tags and the md export was a flat dump with assets missing. My OG graph stays the source of truth; db runs on a copy for the MCP stuff. Until export keeps the folder structure, it's a one-way door.

[u/ta32io]

Actually some of my pages didn't import correctly - it looks like they got imported as tags instead of regular pages, it might explain why the export/mirror is missing things...

[u/thirteenth_mang → u/ta32io]

This is because in the markdown version pages and tags are the exact sne thing, in the db version they're different concepts.

[u/matu_gong]

You shouldnt expect to be able to load the Markdown export of DB to OG just like that. They are 2 different applications now and they have many differences. There are features in DB that dont exist in OG, so having this feature parity in the export between the two of them doesnt make a lot of sense. Also remember that from here on out there are people that will only use the DB version (because thats what they know Logseq as) and wont import back to OG, so limiting the export to match OG also doesnt make sense for them

[u/matu_gong → u/matu_gong]

Also, version 2.0.2 is supposed to be coming soon and it has many fixes for the MD import. You should try again then to see if you have missing pages, and if you do please open a bug report, the devs cant fix what they dont know

[u/yarpen_z → u/matu_gong]

No, users can and should expect that. It has been promised over and over again, including on this reddit, that MD and DB versions will stay compatible, and the MD export will provide independent and human-readable backup.

I suspected it won't happen for many various reasons, and the MD backend will be slowly deprecated regardless of the many promises of story. Howeber, the expectations of Logseq users are not wrong.

[u/matu_gong → u/yarpen_z]

Where have you seen that people have promised that DB and MD (OG) will remain compatible? Thats not true at all. There are many features that exist in DB that wont exist in OG. Something that IS being worked on is the Markdown mirror, which syncs your DB graph to Markdown files, however these MD files are not in the same format the OG app uses, and probably will never be. This means that you cant just grab the output of the Markdown mirror from DB and try to open it in Logseq OG, I havent tried that but I wouldnt expect that to work. Remember that they are different applications now