Skip to content
notdocs
notdocs
Use itFeaturesEverything notdocs does, from the editor and query blocks to merges, search and agents, with the page that explains each.AgentsGive Claude Code, Cursor or any MCP client the workspace: tokens, tools, resources and prompts.CLIEvery notdocs command: documents, import, comments, tokens and the organization, for a local folder or a hosted workspace.TemplatesEvery built-in template with the file it starts, from a task to a data processing agreement.PricingFree for one person, Solo and Team for a few. What each plan allows.
Move inSwitch from NotionImport a Notion export as typed markdown documents in your repository.Switch from ObsidianImport an Obsidian vault and keep working on the same files.notdocs vs NotionMarkdown in your git repository or pages in Notion's database: how agents reach each, and what each tool does better.notdocs vs ObsidianBoth keep markdown files. What differs is where they live, who edits them, and how.ChangelogWhat changed in notdocs, from the CHANGELOG in the repository.
notdocsAboutWhy the repository should be the workspace, and the decisions notdocs is built on.SecurityWhere data lives, how access is scoped, and how to report a vulnerability.ContactHow to reach notdocs for support, privacy, security and legal matters.
PoliciesLegalEvery policy and agreement that applies to notdocs.

Switch from Obsidian

Import an Obsidian vault and keep working on the same files.

Last revised

DocumentationSwitch from Obsidian
On this page

Your vault is already most of the way there

An Obsidian vault is a folder of markdown, which is what a notdocs workspace is. The import keeps your files where they are and makes the few changes needed for them to work outside Obsidian too.

Import

From the workspace, open a project's import page and drop a zip of the vault. From the CLI, with a folder or a zip:

sh
notdocs import obsidian ~/Vaults/work --into docs --dry-run
notdocs import obsidian ~/Vaults/work --into docs

The default destination is docs.

Before and after

In the vault
See [[Pricing launch]] and the ![[tiers.png]] mockup.

> [!note]
> Annual billing is two months free.
In the repository
See [Pricing launch](launches/pricing-launch.md) and the ![tiers](assets/tiers.png) mockup.

> [!note]
> Annual billing is two months free.

The wikilink becomes a relative link that resolves anywhere; the embed becomes an image; the callout is already valid GFM and is left alone.

What the importer does

  • Rewrites [[wikilinks]] to relative markdown links, resolved against the vault's file list, so the links keep working in any markdown tool and on GitHub. Pass --keep-wikilinks (or tick the box on the import page) to leave them as written: notdocs reads wikilinks natively, which is the right choice for a vault Obsidian or Anasa keeps editing.
  • Turns ![[embeds]] into images or links.
  • Leaves callouts alone: Obsidian callouts are already GFM alerts, and notdocs renders them as callouts.
  • Keeps your frontmatter, and stamps an id on each document on first sight. An id a note already has that is not a ULID (id: intro, a Zettelkasten number) moves into aliases, so a wikilink by that id still finds the note.

Or skip the import

A vault does not have to be imported at all. Point the daemon at it (notdocs serve ~/Vaults/work) or push it to GitHub and connect it: wikilinks, embeds and callouts render as they are, indexing only adds the id, type and title frontmatter a note lacks and never touches the body, and the checkbox lines inside notes show on task boards. This is how an Anasa vault is meant to be used with notdocs.

What you keep

Your folder structure, your frontmatter, your history if the vault was already in git. Add type: task to notes that are tasks and they show up on boards; add a query block anywhere to see them. Keep editing in Obsidian if you like: the daemon watches the folder, and a hosted project re-indexes on every push.