Skip to main content
Outcome: your existing Markdown is readable in Knowledge and in a new local replica without overwriting your original notes folder. You need: write access to a vault and a copy of your source notes. If you want a wiki template, apply it before importing into the empty vault.

​
1. Prepare a small first batch

Choose a representative folder with a few linked pages. Separate PDFs, images, and other binaries from the Markdown import plan. Keep a copy of the originals outside any new sync root. Check for names that end in spaces or dots, reserved device names, and siblings differing only by case. A batch can contain up to 500 files and folders combined.

​
2. Import

In Knowledge, choose + Folder → Import and select your batch. Pick the destination. Review skipped files and any renamed collisions. Existing same-name folders merge; matching files are renamed instead of overwritten.

​
3. Verify the result

Open the entry page, follow two internal links, inspect one source document, and search for a unique phrase. If you used a personal vault, select it explicitly in Search. Repair links affected by renamed files. Check remote images independently because they were not bundled into the vault.

​
4. Add the rest in batches

Repeat with the remaining folders. Use Convert for supported non-Markdown sources you want represented as Markdown; keep the originals in their source system.

​
5. Pair a new local root

Create a connection and follow its setup prompt using an empty dedicated root. Wait for the initial replica to become healthy. Open the mounted vault in your preferred editor or file-capable AI tool. Do not enroll directly over your original notes directory. Once you have verified the replica, use that mounted folder for ongoing edits. Check your result: edit a harmless test page locally, confirm its revision in the app, then make a web edit and confirm it arrives locally. Use a page you can safely change rather than a critical procedure.

​
If it did not work

If the result is incomplete, review the import report for skipped files and name collisions before importing again. If only the replica is stale, use sync troubleshooting. Next: Knowledge maintenance.