> For the complete documentation index, see [llms.txt](https://doc.anytype.io/anytype/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.anytype.io/anytype/data/import-and-export/migrate-from-obsidian.md).

# Migrate from Obsidian

#### Step 1: Export from Obsidian

* Clean up your notes
  * Convert embeds like `![[Note Title]]` into simple links `[[Note Title]]`
  * Remove or convert plugin-specific syntax, such as Dataview queries, Templater fields, etc.
* Locate your vault
  * Open the Vault switcher (shown at launch or via `File → Open Vault`).
  * Right-click the vault you want to export and choose “Reveal in system explorer.”

#### Step 2: Import into Anytype

* Open `Channel Settings → Import → Obsidian` and click on Import files.
* Select your vault folder (or a subfolder) for import.
  * On some platforms (like Linux and Windows), folder selection may not be supported.\
    In that case, compress the folder into a .zip archive and import the archive instead.
* Anytype will process the contents and automatically create a separate object for each Markdown file.

{% hint style="info" %}
**Content mapping**

* `[[Internal Links]]` → become linked objects in Anytype, so the connections between your notes are preserved.
* `#tags` → become values in the Tag property. You can use them to filter, group or search across objects.
* Frontmatter (the `---` metadata at the top) → becomes object properties.
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.anytype.io/anytype/data/import-and-export/migrate-from-obsidian.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.