How to move an Obsidian vault to Raven, and what to check first
Try Raven on a copy of your Obsidian vault. What stays the same, what is Obsidian-only, and the notes to check before you switch.
Start with a copy of the vault
Duplicate the whole vault folder in Finder and work on the copy. Name it something you will not confuse with the original, like Notes (Raven test).
A copy matters for two reasons. Raven adds a stable id field to the YAML frontmatter of notes it opens, and completing a task appends a completedAt comment to that task’s line. Neither breaks a Markdown file, but you should see them on a copy before they reach the vault you rely on. A copy also means any test you run is free.
If your vault lives in iCloud Drive, keep it downloaded and wait for downloads to finish before you duplicate it.
Your notes and Obsidian’s settings are separate
Obsidian stores notes as Markdown files in a folder, the vault. Its own preferences for that vault, such as hotkeys, themes, and community plugins, live in a hidden .obsidian folder at the vault’s root. On a Mac, press Command-Shift-period in Finder to show hidden folders.
That split is what makes a move possible. The .md files are yours and any Markdown app can read them. The .obsidian folder holds Obsidian’s settings for the vault. Leave it where it is, so the vault still opens in Obsidian exactly as before.
Find the notes that depend on Obsidian
Obsidian supports CommonMark and GitHub Flavored Markdown, and adds its own syntax on top. Its documentation says some of it, such as internal links, comments, and highlights, is specific to Obsidian, and other Markdown apps may show it as plain text.
Search your copy for the patterns you use most, and pick a few notes that lean on each:
- Internal links,
[[Note name]], and links to a heading or block,[[Note#Heading]]and[[Note#^id]]. - Embeds,
![[Note]]or![[image.png]], which show another file inside the note. - Callouts like
> [!note], comments between%%marks, and highlights between==marks. - Live plugin queries. A Dataview or Tasks query is text in the file that Obsidian runs each time you open the note. Another app shows the query, not its result. Text a plugin has already written into a note, like a filled-in template, is ordinary text.
- Canvas and Bases. These are Obsidian features with their own files, not Markdown notes.
Your untouched original keeps all of this available in Obsidian. In the copy, check how Raven reads and saves these notes. I haven’t confirmed that wiki-link aliases, attachment embeds, or Tasks-plugin checkbox syntax stay as written, so look at those first.
Open the copy in Raven
On Mac, point Raven at the copied folder. It reads the same .md files in place. Nothing is imported, folder structure and YAML frontmatter are kept, and there is nothing to export later.
Raven reads [[wiki-style]] links and shows backlinks for the note you are reading. It has no graph and no canvas. Images you add in Raven go into a managed folder in the vault and travel with sync. Raven has no plugin system. Journal, tasks, tables, and search are built in instead.
Check five notes before you switch
Open a handful of notes from your search above and compare each one with Obsidian, side by side. The files are ordinary Markdown, so both apps can have the folder open at once.
- A note with internal links, including one to a heading.
- A note with embedded images.
- A note that uses callouts or highlights.
- A note with a live plugin query, like a Dataview table.
- Your busiest daily note.
If a link or image looks wrong, the guide to fixing Markdown links after a move covers what to look for. When the five notes read the way you want, you know what moving costs you, with your own notes rather than a feature list.
When to stay with Obsidian
Stay if your vault depends on things only Obsidian runs: community plugins, Canvas, Bases, or a graph view. Stay if you need Windows, Linux, or Android. The Obsidian alternative page lists the rest, and it starts with who should stay.
If you do move, keep the original vault untouched for a while, and keep a backup. The guide to backing up Markdown notes shows how to make one and check that it restores.