Migration guide

Bring your Obsidian vault.

Everything Since imports Markdown as a copy. You review the scan before anything is written, while the source vault stays untouched.

Before you import

Make a current backup of the vault and close any active sync conflict.
Choose the vault folder itself, not its parent folder or only the .obsidian settings directory.
Keep the source available until you have completed the verification checklist below.

Import is not two-way sync

Later edits do not travel between Obsidian and Everything Since. Re-import only after reviewing duplicate and conflict behavior in the scan.

Open Settings → Import & migration, choose Obsidian, and select the vault.
Read the scan totals and warnings. Expand the review list for skipped or unsupported items.
Confirm the destination Space and naming. Do not continue if the counts are unexpectedly low.
Start the import and leave the app open until the completion summary appears.
Keep the generated report; it is the record of what was copied, skipped, or changed.

Vault content	Import behavior	Verify afterward
Markdown notes and folders	Copied into the selected Space with hierarchy retained where possible.	Names, headings, lists, code blocks, and a sample from every major folder.
Common local attachments	Copied when the scanner can resolve the referenced file.	Images and documents open from representative notes.
Tags, tasks, and links	Parsed from supported Markdown forms; ambiguous references are reported.	A linked note, a task list, and commonly used tags.
Obsidian-specific features	Plugin data and executable queries are not reproduced as app behavior.	Review Canvas, Dataview, custom plugin blocks, themes, and snippets manually.

Canvas files, community-plugin behavior, Dataview queries, themes, and CSS snippets do not become native Everything Since features.
Transclusions, block references, aliases, embeds, callouts, or uncommon wiki-link forms may need manual cleanup when reported by the scanner.
Remote-only, missing, hidden, permission-restricted, or unsupported binary files cannot be copied.
An encrypted or externally mounted vault must be unlocked and locally available to the operating system first.
Very large vaults take longer; do not assume a stalled-looking progress indicator means the source should be force-removed.

Compare imported note and attachment totals with the report, not only the vault’s filesystem total.
Open old, recent, deeply nested, linked, tagged, attachment-heavy, and task-heavy examples.
Search for distinctive text from several source folders.
Review every warning and retain your backup until you are satisfied.
If the result is wrong, remove only the newly created destination Space from inside the app, correct the source or mapping, and scan again. Never delete the source vault as part of cleanup.

Need help interpreting a report? Search support or email support@everythingsince.com.