How to Migrate from Obsidian to infolio: From File Vault to Desktop Knowledge Workspace
Evaluate which Obsidian Markdown files, plugin workflows, and personal records should move into infolio, and which should stay in a file-based Git workflow.
Quick answer
Obsidian migration is not about abandoning Markdown. It is about identifying what has outgrown the file vault: desktop workspaces, whiteboards, private records, and multi-device sync can move first.
Steps
Inventory what is inside the vault
Separate long-term Markdown writing, project references, plugin-generated content, backlinks, attachments, canvases, private records, and temporary drafts.
- Mark content that strongly depends on Markdown source files.
- Mark content that depends on plugins or Dataview.
- Mark content that fits better in workspaces, whiteboards, or vaults.
Keep plugin-heavy and Git workflows in Obsidian
If notes depend on many plugins, Git, scripts, or plain-text tooling, do not rush the migration. infolio is not meant to replace every Markdown workflow.
- Keep writing projects that need Git.
- Keep pages generated by plugins.
- Keep records that need plain-text interoperability.
Move projects that need a workspace
infolio fits projects that benefit from multiple windows, desktop widgets, document trees, and whiteboards. Choose one active project and move core docs, references, and planning boards first.
- Choose one active project.
- Move core documents and key attachments.
- Rebuild project relationships on an infolio whiteboard.
Move private records out of ordinary Markdown
Many Obsidian vaults contain account notes, key hints, and private material in ordinary Markdown. Move those records into infolio encrypted vaults to reduce plaintext sprawl.
- Search the vault for account, key, token, and ID hints.
- Move sensitive records into vaults.
- Delete or redact plaintext copies in old Markdown files.
Define the division between Obsidian and infolio
After migration, Obsidian can remain the plain-text and plugin environment while infolio carries workspace-oriented projects, private records, and multi-device knowledge flow.
- Define what stays file-based.
- Define what moves into infolio workspaces.
- Avoid maintaining the same project in both tools forever.
Related pages
FAQ
Will I lose Markdown files if I migrate from Obsidian?
infolio is not a plain Markdown file manager. If direct Markdown and Git are central, keep Obsidian. Move projects that need workspaces, whiteboards, vaults, and sync.
Can I use Obsidian and infolio together?
Yes. A practical split is Obsidian for plain text and plugin workflows, and infolio for desktop workspaces, encrypted vaults, and multi-device knowledge work.