Obsidian

Since both Obsidian and Octarine work with standard markdown files stored locally, migration is straightforward. Your vault can become an Octarine workspace with minimal adjustments.

Direct Migration

The simplest approach is to create a workspace from your existing Obsidian vault:

1. Open Octarine
2. Click the Workspace Switcher (top-left corner)
3. Select Create Workspace
4. Enter a name for your workspace
5. Toggle Use an existing folder?
6. Press Create

Adjusting Folder Structure

To fully align with Octarine's conventions:

1. Attachments: If your Obsidian vault uses a different attachment folder:
   • Create a .attachments folder in your vault root
   • Move all images and media from your current attachment folder
   • Update attachment links in your notes (Octarine expects [[filename.png]] for attachments)
2. Linked Notes: While Obsidian allows you multiple options of storing wikilinks in notes, Octarine follows a more stricter rule. Notes are expected to have entire path (except the workspace path) in the link. For example a note called Hello that is present in folder New Folder will be linked as [[New Folder/Hello]] . Just linking it as [[Hello]] would not identify the one in New Folder since it’ll look for in the root folder.
3. Templates: If you use templates in Obsidian:
   • Create a .templates folder in your vault root
   • Move your template files there
4. Daily Notes: If your daily notes aren't already in a Daily folder:
   • Create a Daily folder
   • Move existing daily notes there
   • Ensure they follow the YYYY-MM-DD.md naming format

Compatibility Notes

• Wikilinks: Octarine supports Obsidian's [[wikilink]] syntax natively. Aliases are not yet supported. Absolute paths are needed for storage, but you can change the setting for UI treatments.
• Tags: Both #tag and #nested/tag formats work seamlessly
• Frontmatter: YAML frontmatter is supported partially currently with a full fledged properties feature on the way.