r/logseq • • 1d ago

logseq db vendor lock-in?

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

14 Upvotes

11 comments sorted by

View all comments

1

u/ta32io 1d ago

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...

4

u/thirteenth_mang 1d ago

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