SystemSculpt
Install free (opens Obsidian's plugin directory in a new tab)

Logseq to Obsidian: How to Move Your Graph (2026)

Published 7 min read

On this page

Point Obsidian's free, official Importer plugin at your Logseq graph folder. You don't need to export anything from Logseq first. Importer reads the graph's Markdown files and turns pages, journals, page properties, tags, tasks, block references and images into Obsidian notes. It works with Logseq's file-based graphs. Graphs made in Logseq's newer DB version aren't supported yet.

This guide covers the import, what changes on the way and what to check after. We make SystemSculpt, an AI plugin for Obsidian, so the last part shows how to add AI to the notes you bring over.

Checked on November 3, 2026, with Importer 3.1.16 and Obsidian's and Logseq's own docs, linked at the end.

Before you start

  1. Back up your Logseq graph folder, and your Obsidian vault if it already has notes in it.
  2. Find your graph's root folder. It's the one with pages, journals, assets and logseq folders inside.
  3. Install Obsidian and create a vault, or open the one you'll keep these notes in. A new, empty vault makes the first import easy to check.
  4. In Obsidian, open Settings, then Community plugins, and turn them on if they're off.
  5. Select Browse, search for Importer, then Install and Enable. Importer is made by the Obsidian team and is free.

If you want your journals to land in Obsidian's daily notes, set the folder and date format in the Daily notes core plugin before you import. Our daily note template shows one way to set it up.

File graph or DB version?

Logseq now has two kinds of graph, and only one of them imports today.

  • File graph. This is the classic Logseq, which Obsidian's help calls "Logseq OG". Every page is a Markdown file in a folder on your disk. Importer reads that folder directly. Skip Logseq's Export graph menu: Logseq says its standard Markdown export leaves out block properties.
  • DB version. The graph lives in a database, not in Markdown files. Obsidian's help says Importer doesn't support DB graphs yet. Logseq's own Export as standard Markdown (no block properties) option exists, but Logseq says it can't capture all of a graph's data.

How Logseq and Obsidian differ, for moving

You'll see these four differences in your imported notes.

  • Blocks and pages. Logseq is an outliner, so every line is a bullet. An Obsidian note is a plain Markdown page where bullets are optional. Importer keeps your bullets unless you turn on Flatten outlines.
  • Block references. Logseq points to a block by a long ID, like ((6730a1b2-...)). Obsidian points to a short anchor at the end of a line, like [[Reading#^6730a1]].
  • Properties. Logseq writes page properties as type:: project lines at the top of a page. Obsidian keeps them as properties in a YAML block at the top of the note.
  • Journals. Logseq keeps one file per day in journals, named like 2026_11_03.md by default. In Obsidian, the Daily notes core plugin does that job, with a folder and date format you choose.

Import into Obsidian

  1. Open Importer from the left ribbon or the command palette (Importer: Import notes).
  2. In the list of formats, choose Logseq (.md).
  3. Select Choose folders, then pick your graph's root folder. Pick the folder that holds pages and journals, not one of those folders.
  4. Review the folders Importer found, and leave out any you don't want. Then select Continue.
  5. Set the Output folder (it starts as Logseq) and the Attachment location for images and files.
  6. Check the options. Use daily notes settings, Keep queries and Keep flashcards start on. Keep time tracking starts off.
  7. Select Continue. Importer shows the note template it will use and previews a few of your notes. Flatten outlines is on this screen, off by default.
  8. Select Start import and wait for it to finish.

Pages go in your output folder. With Use daily notes settings on, journals use your daily notes folder and date format, so they can end up outside the output folder. Turn it off to put them in a Journals folder inside the output folder, named like 2026-11-03.

What carries over and what doesn't

We ran two small file graphs with page and block properties, an alias, a namespace page, a journal, TODO, DONE, NOW and LATER tasks, block references, embeds, two queries, time tracking, a flashcard and an image through Importer 3.1.16's Logseq converter, and checked them against Importer's own test output. Here is what came out.

Comes through:

  • Page properties, as Obsidian properties. tags:: becomes a tag list and alias:: becomes aliases.
  • Links between pages, pointed at each note's path in your vault, like [[Logseq/Reading]]. Links to an alias point at the real page, like [[Logseq/Reading|Books]].
  • Tags, including #[[deep work]], which becomes #deep-work.
  • Namespaces, as folders. A Projects/Garden page becomes a Garden note in a Projects folder.
  • Block references, as links to the block that show its text, like [[Logseq/Reading#^6730a1|Books to read this year]]. Block embeds become ![[Logseq/Reading#^6730a1]], and page embeds become ![[Logseq/Projects/Garden]].
  • Tasks, as checkboxes. TODO, LATER and WAITING become [ ], NOW and DOING become [/], DONE becomes [x] and CANCELED becomes [-].
  • Scheduled and deadline dates and priorities, as plain text after the task, with dates as links like [[2026-11-05]].
  • Journals, renamed to dates like 2026-11-03. Date links like [[Nov 3rd, 2026]] become [[2026-11-03]].
  • Images and files from assets, saved where you chose and shown in the note, like ![[cover.png]].

Changes or doesn't come through:

  • Queries. Obsidian can't run them. With Keep queries on, they're kept as query code blocks, so you can rebuild the ones you need, for example with Bases. With it off, they're dropped.
  • Block reference text. The link shows the block's text as it was at import. It won't follow later edits to that block.
  • Block properties. Your own ones, like rating:: 5 under a bullet, stay as plain text lines. Logseq's internal ones, like collapsed::, are removed.
  • Time tracking. LOGBOOK and CLOCK entries are removed unless you turn on Keep time tracking.
  • Whiteboards. They aren't imported. Importer lists them as skipped.
  • Flashcards. With Keep flashcards on, #card and cloze markers stay as plain text. Review schedules don't carry over.
  • Template macros like {{date:yyyy}} stay as literal text.
  • Missing files. If a note links to a file that's no longer in assets, the link is left as it was and Importer reports it.

Each note also gets a logseq-source property naming its original file. It lets a later import update notes you've moved or renamed. Turn off Save Logseq source on the template screen if you don't want it.

After the import, open a few of your busiest pages next to the originals in Logseq. Keep your Logseq graph until you're happy with the result.

Add AI to your imported notes

Once your notes are Markdown files, any AI tool that reads files can work on them. If you already use Claude Code or Codex, install the free SystemSculpt plugin from Obsidian's community plugins. It runs your signed-in Claude Code or Codex in a chat pane in your vault on desktop, and can ask for your approval before each edit. You can ask it to tidy imported notes, add links between related notes or summarize a notebook. Chats are saved as Markdown notes in your vault. It needs no SystemSculpt account or plan.

For mobile chat, audio transcription and related-note search, eligible new accounts can claim 500 one-time starter credits with no card. Paid plans are $9 a month or $90 a year. Compare plans.

Questions

Do I need to export my graph from Logseq first? No. For a file graph, Importer reads the graph folder directly. Choose the folder that holds pages and journals.

Can I import a Logseq DB graph? Not yet. Obsidian's help says Importer supports file-based graphs only. DB graphs aren't supported yet.

Is the Obsidian Importer plugin free? Yes. It's an official plugin made by the Obsidian team, free in Obsidian's community plugins.

Do Logseq block references still work in Obsidian? Yes. Importer gives each referenced block a short anchor and turns ((...)) references into links to it. Embeds become Obsidian embeds.

Logseq vs Obsidian: what's the main difference? Logseq is an outliner, where every line is a bullet block and each day gets a journal page. Obsidian is a Markdown editor where each note is a free-form page, kept as a file in your vault.

Sources

TopicsObsidianKnowledge ManagementObsidian AI

Try SystemSculpt inside your vault

SystemSculpt adds first-party AI chat, semantic search, transcription, and document workflows to Obsidian.

View pricing