Logseq

Logseq stores graphs as local files, usually Markdown or Org files. If your graph uses Markdown, you can open the graph folder directly in Octarine. If it uses Org mode, convert the important notes to Markdown before migrating.

Direct Migration

Find your Logseq graph folder. It usually contains folders such as:

journals/
pages/
assets/
logseq/

Open Octarine and click the Workspace Switcher in the top-left corner. Select Create Workspace, give it a name, and toggle Use an existing folder?. Choose the root of your Logseq graph and press Create.

Pages and Journals

Logseq stores regular pages in pages/ and journal notes in journals/. Octarine will show those folders in the file tree.

If you want Logseq journals to behave like Octarine daily notes, create a Daily folder and move the journal files into it. Rename them to Octarine's daily note format if needed:

YYYY-MM-DD.md

Keep a backup of the original graph before moving files, especially if you still plan to open it in Logseq.

Outliner Formatting

Logseq is an outliner, so many pages are written as nested bullet blocks. Octarine can display the Markdown, but long notes may feel better if you remove unnecessary top-level bullets and turn major blocks into headings.

For example:

- Project plan
  - Goals
  - Risks

can become:

# Project plan

## Goals

## Risks

Assets

Logseq stores media files in assets/. Octarine's convention is .attachments at the workspace root.

You can keep assets/ if the existing Markdown links work, or rename it to .attachments and update references. If you still use the folder in Logseq, keep assets/ and avoid changing paths.

Compatibility Notes

Logseq wikilinks and tags are close to Octarine's syntax, so many links will continue to work. Block references, block embeds, queries, TODO workflows, page properties, and Logseq plugin data are Logseq-specific and may need manual cleanup.

Org mode files are not Octarine notes. Convert .org files to Markdown before expecting them to behave like regular notes in Octarine.