Disclaimer
Is this project open source? Yes
Is this project completely free? Yes
Is this project vibe-coded beyond the author’s ability to comprehend how it works? No
Community Directory: Not applicable. This is a workflow tip and checklist, not a plugin or theme.
Hi everyone,
I recently moved a large note archive into Obsidian.
I expected the import to be the hard part. It was not.
The harder part was knowing if I could trust the imported vault.
An import can finish and still leave problems behind:
- Empty or nearly empty notes
- Duplicate notes from retrying an import
- Missing attachment links
- Strange Markdown formatting
- Files that should be reviewed before deleting the source archive
So I wrote down the checks I now run before reorganizing the vault.
It is not tied to one source app or one language.
It should be useful for OneNote, Evernote, Apple Notes, Notion, Google Keep, or other note systems.
The main idea is simple:
Import completed does not mean migration verified.
The checks are:
- Count notes and attachments
- Find empty notes
- Find duplicate content
- Check missing attachments
- Review formatting issues
- Keep sensitive notes out of public tools
- Decide what needs human review before deletion
I also wrote a sample report and a local audit prompt.
The prompt is designed to report counts, paths and summaries first.
It should not print private note contents by default.
I put the checklist and sample report on GitHub.
Repo name: fnnikita/obsidian-migration-checklist
I would love feedback from people who have done large migrations.
What failure modes did you see that are missing from this checklist?