KMS Obsidian Import (one click)
Omniscio finds the Obsidian vaults on this computer and shows each one with its note, image and folder counts. One press of Import copies that vault into the Vault under Obsidian › <vault name> — notes, folders, pictures, wiki-links and callouts — and Open in Vault takes you straight to it. The Obsidian files are never changed, running it again only adds what is new — though it also puts back a note you have since removed from the Vault, see Running it again — and it works in the desktop app only.
On this page
What it is
A one-click way to bring an Obsidian vault into the Omniscio Vault. It reads Obsidian's own list of vaults, so there is no folder hunting, and it starts copying the moment Import is pressed — no separate scan, preview or start step.
Where to find it
- Vault command palette → Import from Obsidian.
- The Vault's empty screen (no note open) → Coming from Obsidian? Bring your vault over. Shown only when an Obsidian vault is found on this computer.
- Settings → Features → Show advanced → The Vault → Import from Obsidian. Searching Settings for "import obsidian" opens that fold for you.
- Mission Control's "Got data somewhere else?" screen → I have notes in Obsidian, above "I have a file". The setup screen stays open behind the import and is still there when it closes.
- Tasks → ⋯ More → Import notes from Obsidian…, right under "Import tasks…".
The first three need the Vault switched on with a vault folder set. The Mission Control and Tasks entries also work when the Vault is off: they first ask Turn on your Vault?, naming where the notes will go — the folder you already chose, or a new Omniscio Notes folder in your Documents — and switch the Vault on only after Turn on. The import then opens once the Vault is ready. When it does not switch on, the message names the reason and nothing is imported: a folder that could not be set up points you at choosing a different Vault folder in Settings, while a Vault that is merely still starting up asks you to try again in a moment. Not now changes nothing. Each press is a one-time copy, not an ongoing sync.
Every entry needs the desktop app — the import reads this computer's folders, so it is not offered on a phone or in the browser.
How it behaves
Finding vaults
- Omniscio reads Obsidian's vault list:
%APPDATA%\obsidian\obsidian.jsonon Windows,~/Library/Application Support/obsidian/obsidian.jsonon macOS, and~/.config/obsidian/obsidian.json(or the Flatpak / Snap equivalent) on Linux. It only ever reads it. - Each listed folder that still exists and contains a
.obsidianfolder becomes a card, most recently opened first. - Counts fill in one vault at a time. A vault that was imported before says so: running it again only adds what's new.
- Choose a different folder… opens a folder picker and counts the chosen folder right away. A folder without
.obsidianstill imports its Markdown notes, with a note saying it isn't an Obsidian vault. - No vaults found (Obsidian not installed) → a "No Obsidian vaults found" screen with Choose folder.
- The search itself failed (Obsidian's vault list is missing or unreadable) → a screen saying Omniscio could not look for Obsidian vaults automatically, with Choose folder to pick one by hand and Try again to run the search a second time.
What transfers
- Markdown notes, with their folder structure, under
Obsidian/<vault name>/. - Pictures (PNG, JPG, JPEG, GIF, WebP, SVG, AVIF) into the content-addressed asset store, de-duplicated by content.
- Wiki-links and callouts.
What does not transfer
- Plugins, themes, CSS snippets and Obsidian settings (
.obsidian/), plus.git/,.trash/, other dot-folders andnode_modules/. - Canvas files, non-picture attachments (PDFs, video, audio) and files over 5 MB — listed as skipped on the finish screen.
- Symbolic links, and anything inside a folder the app cannot open. A symbolic link — a linked file, or a linked folder such as the one you share between two vaults — is not followed, and a folder the app is not allowed to read is left out along with everything under it. Unlike the items above, neither shows up in the finish screen's skipped list and neither raises an error: the import simply copies what it could read. If a whole folder seems to be missing afterwards, link and permission problems are the first thing to check.
Links and pictures
![[picture.png]]and![[folder/picture.png|alias]]become standard Markdown pictures pointing at the asset store. A numeric alias such as|300is a size, not alt text. Pictures are matched by their path first, then by name, preferring the one in the same folder, so two same-named pictures in different folders stay distinct.- Standard Markdown pictures
that point at an imported picture are rewritten the same way. Web and data URLs are left alone. - Path-style wiki-links (
[[folder/note]], with or without#headingor|alias) that point at an imported note are re-pointed intoObsidian/<vault name>/. Title links ([[note]]) are left as written — the Vault resolves them by title. ![[note]]embeds become plain[[note]]links. An embed whose picture was not imported is left as written.
Running it again
- A note whose copy in the Vault is identical is skipped and counted as Already up to date.
- A note edited in Omniscio is never overwritten: if the Obsidian version differs, it is saved alongside as
name 2.md, and later runs recognize that copy instead of adding another. - A re-run puts back notes you removed. The import looks for its copy at the same path it made last time. So a note you imported and then trashed, moved or renamed inside the Vault is created again at its original location the next time you press Import — a moved or renamed one comes back as a duplicate as well. Organize imported notes only after you have stopped re-running the import, or delete the Obsidian copy first.
- A note whose Vault copy cannot be read right now (an online-only cloud file, or one another program holds open) is reported as a failed file, never quietly copied again as
name 2.md. Close the file or let the cloud drive finish syncing, then run the import again.
Progress, cancel and the finish screen
- Progress shows "Bringing over <vault>…", a count, a bar and the current file. Closing the dialog or pressing Cancel asks first; anything already copied stays.
- A big vault takes as long as it takes: the import is not cut off after a couple of minutes. The bar keeps moving while it is working, a run that goes quiet for a long stretch is reported as stuck, and the finish screen appears when the import really ends. Starting a second import while one is running is refused.
- The finish screen shows notes, folders, pictures and already-up-to-date counts, skipped files and errors, and Open in Vault. A cancelled run says Import stopped; a run with failed files names the error count and offers Copy error report.
Refusals
- A folder with more than 50,000 entries: "This folder is too big to be an Obsidian vault. Choose the vault's own folder."
- A folder that cannot be reached at all (a disconnected drive or network folder): "This folder cannot be reached right now. Check that the drive or network folder is connected, then try again."
- A folder that takes too long to read (a network or cloud drive still syncing, a slow share): "This folder is taking too long to read. If it is on a network or cloud drive, make sure it is fully synced and try again." The size limit and the time limit are told apart, so a slow folder is never reported as "too big".
- An Obsidian folder that is, contains, or sits inside the Omniscio Vault folder.
- A second import while one is running.
A partly-read folder
A subfolder that cannot be read mid-walk (a lock held by a sync client, a momentarily unreachable network path) does not stop the import and does not silently vanish from it either. The walk reports truncated, which reaches ObsidianScanResult.incomplete and ObsidianImportResult.incomplete, and the scan summary and the finish screen both say plainly that part of the folder could not be read and to check the drive and run the import again. Re-running is safe: notes already in the Vault are counted as unchanged rather than copied twice.
Related
- kms.md — the parent Vault editor
- kms-vault-overview.md — the searchable note inventory
Last verified 2026-10-30