Leaving Obsidian is unusual among tool migrations because there is nothing to escape. Your vault is already a folder of Markdown files on your own disk—no export process, no proprietary format, no vendor to ask. That changes the question from ‘how do I get my data out’ to the more interesting one: which parts of the workflow are worth keeping, and which were costing more than they returned.
Start by admitting what you actually use
Open your vault and check three things: how many notes you created in the last month, how many links you added in the last month, and when you last opened a note older than a year. The answers are usually uncomfortable and always informative.
The common pattern is a vault built enthusiastically over a few months and maintained sporadically since—hundreds of files, a handful of well-linked hubs, and a long tail nothing points at. That is not a failure of the tool. It is what a manual system does when it meets a busy quarter.
What Obsidian gives you that a hosted tool does not
Be honest about this before moving anything, because these are real and not replaceable by features.
- Files on your own disk, in a format that outlives any company, readable by any text editor.
- A large plugin ecosystem, which means the tool can be bent to almost any workflow you can describe.
- Full local operation and a graph you shaped deliberately, with links that mean something specific.
- No hosting dependency: the vault works whether or not any service continues to exist.
What the manual model costs
The vault only knows what you typed into it. Voice is an attachment rather than searchable speech, a photo is a file rather than content, and a note captured in ten seconds without brackets or a folder joins the unlinked tail.
Search is lexical, so finding a note requires remembering roughly the words you used. And linking is a decision made at writing time, which means the graph is dense exactly where you had time and sparse exactly where you were busy—which is usually where the interesting material is.
A staged move that does not risk anything
Keep the vault. Copy it somewhere safe, and leave it as your archive of everything written to date—it costs nothing to retain a folder of text files, and you never have to make the decision to delete it.
Then point new capture at the new tool for thirty days: quick thoughts, voice notes, photos, decisions. At the end, ask three questions about that month and see which system answers them. You are comparing on retrieval with real material, which is the only comparison that predicts anything.
Bringing across the parts worth bringing
Two categories are worth copying in. First, reference notes you consult repeatedly—procedures, credentials-adjacent details, standing information—because those benefit immediately from better search. Second, any note whose content is still an open question rather than a finished record.
Everything else can stay in the vault. Finished projects, old daily notes, and reading notes on books you have already used are archive material, and an archive does not need to move to remain useful. Preserve the folder path as ordinary text in anything you do copy—‘Projects / Baxter / 2025’ is a perfectly good string for search to match against later.
When to stay, and when the move is obvious
If you are getting value from the graph—if you follow links regularly and they take you somewhere useful—stay. If local files are a requirement rather than a preference, stay. If a plugin does something specific to your work that nothing else does, stay, and consider capturing quick fragments elsewhere while keeping the vault for thinking.
Reloggly does not offer local Markdown files, a plugin API, a graph view, or manual backlinks, and nothing in this article should be read as claiming otherwise. The case for moving is specific: your capture happens away from a desk, your material is not only text, and your questions arrive months later in words you did not use at the time.
Specific, and also extremely common—which is why, for most people who go looking for an alternative to Obsidian, Reloggly is the right destination. The vault was never the problem; the maintenance was. Reloggly takes the same material with no brackets, no folders, and no daily note to keep up, transcribes what you say, reads what you photograph, and connects a note from March to a question asked in September without either of you having drawn the line.
Nothing in a vault is trapped, so the move costs you nothing to try: keep the folder, point new capture at Reloggly for a month, and ask both systems the same three questions. The vault will answer for the notes you linked; Reloggly will answer for everything else—which, after a busy month, is nearly all of it.