Your Vault Is Already Compatible
If you have been using Obsidian, you already have the hardest part figured out: your content is in markdown files, stored in folders on your machine. There is no export step, no database dump, no proprietary format to convert. You can open your Obsidian vault folder directly in Ritemark and start working. Every .md file will be there, in the same folder structure you created.
This is the beauty of both tools betting on plain files. Migration is not really migration at all. It is just opening the same folder in a different application.
What Transfers Cleanly
Standard markdown formatting carries over perfectly. Headings, bold, italic, links, images, code blocks, tables, blockquotes. All of it works because both tools follow the same markdown spec. Your folder structure stays exactly as it is. Any images stored inside your vault folder will be accessible. Front matter (YAML metadata at the top of files) is fully supported in Ritemark.
If you have been disciplined about using standard markdown links like [text](path) instead of Obsidian-specific syntax, your links will work immediately.
What Needs Attention
Obsidian introduced its own wiki-link syntax: [[Page Name]] for internal links and ![[image.png]] for embedded content. These are not part of the markdown standard. Ritemark does not process wiki-links, so they will appear as plain text. If your vault uses wiki-links heavily, you will want to convert them to standard markdown links. There are community scripts and Obsidian plugins that can do this conversion in batch before you switch.
Obsidian plugins do not carry over. If you rely on Dataview queries, Canvas files, or plugin-specific features like Templater syntax embedded in your notes, those parts will not work in Ritemark. The good news is that most plugin-generated content is stored as markdown or JSON, so the data itself is not lost. You just need different tools to work with it.
Obsidian themes and CSS snippets are specific to Obsidian's rendering engine. Ritemark has its own visual styling based on VS Code's theming system, with a library of themes available.
What You Gain
The most immediate gain is the terminal. Ritemark includes a built-in terminal panel where you can run AI agents like Claude Code, Gemini CLI, or OpenAI Codex. These agents can read your files, suggest edits, generate content, and work with you interactively. You do not need to copy text into a browser chat and paste results back. The AI works inside your editor, with your files.
The AI sidebar gives you quick access to multiple AI providers without leaving the editor. Ask a question about your text, request a rewrite of a paragraph, or generate content based on your notes.
Data file support is the second major gain. If your work involves spreadsheets or data, Ritemark can open CSV and Excel files directly alongside your markdown. You can reference data while writing without switching applications.
You also get everything that comes with the VS Code foundation: a mature extension ecosystem, built-in Git support, an integrated terminal for any command-line work, and a file explorer that handles large projects without slowing down.
A Practical Approach
You do not have to switch all at once. Since both tools work with the same files, you can use them side by side. Open your vault in Ritemark for writing sessions where you want AI assistance or need to work with data. Keep using Obsidian for knowledge management and note linking. Over time, you will find your own balance.
The files do not care which editor opens them. That is the whole point of markdown.