Open Source

hideshow 5 child comments

parent

[–] girsaysdoom@sh.itjust.works 2 points 5 months ago (3 children)

Logseq leverages centrally hosted databases while obsidian works directly from files and directory structures. There should be a way to import individual files but I'm not sure if it will parse your entire vault.

hideshow 3 child comments

parent

[–] sunstoned@lemmus.org 3 points 5 months ago* (1 child)

Logseq still supports plain .md files ("Logseq OG") in addition to the new DB backend., so a convoluted import isn't necessary.

parent

hideshow 1 child comment

[–] brisk@aussie.zone 0 points 5 months ago

It's fine for input, but Logseq ".md" files are only suitable for import back into Logseq (at least if they have any links)

parent

[–] flandish@lemmy.world 2 points 5 months ago

gotcha. thanks! i kinda like the idea that the place is just a series of md files, in obsidian to be honest but will give logseq another look!

parent

[–] INeedMana@piefed.zip 1 point 5 months ago

In the past I migrated my notes from Obsidian to Logseq. Both have a bit different approach, but basically the move was to modify dir/file.md to be dir__file.md