Vimwiki Import converts your default wiki pages into Markdown notes

Name: Vimwiki Import
Author: theluckystrike

Preview Vimwiki conversion before you create Markdown notes.

MIT · no telemetry · core features free

Two converted notes with headings, tasks and links, plus an unresolved target. — Open larger

version: 1.1.0
released: 2026-10-21
downloads: 18
review: Passed
health: Excellent
license: MIT
listed for: Desktop, Mobile
obsidian: 1.13.4 or later

The README reports desktop tests on macOS with small fixtures and simulated sponsorship answers. Phones, tablets, live payments and a large real migration weren't tested.

Directory facts fetched 2026-10-23 07:28 UTC from community.obsidian.md/users/theluckystrike.

About Vimwiki Import

You have default Vimwiki pages and want to review their conversion before creating Markdown notes in your vault.

Vimwiki Import reads default .wiki pages you've placed in your vault and previews their Markdown conversion. Choose a new destination folder, check the converted text, then import. Your source pages stay in place.

The free version converts headings, basic lists, simple tasks, code blocks and mapped local links. Pro adds ISO diary mapping and a combined unresolved-link report from saved imports. Markdown and media modes aren't supported.

The demonstration moves from folder selection through conversion previews to an import result with warnings.

Free features

Select folders in the vault

Enter a source folder and a new destination, then select These files use default syntax. The plugin reads nested .wiki pages and keeps relative folder paths. Copy external pages into the vault first; source and destination folders can't overlap.

The dialog shows separate source and destination folders with default syntax selected. — Open larger

Review headings and mapped local links

Preview output paths and Markdown text before importing. Spaced headings become Markdown headings, and local links use the selected source map with their labels. Missing targets keep their original text and produce warnings.

Convert lists, tasks, and code blocks

Basic bullet and numbered lists become Markdown lists, with indentation retained. Unchecked and completed boxes become tasks; other states remain escaped text with warnings. Delimited code becomes a fenced block with its body unchanged, and an unclosed block gets a closing fence and warning.

The preview shows converted tasks, a retained partial state, a code block and image syntax warnings. — Open larger

Keep sources and read the import report

Import creates new notes and skips missing or changed sources and occupied output paths. A Markdown report lists created paths and review items. Cancel closes the preview without importing, but closing the dialog after Import doesn't cancel writes that started.

The import result lists one created note and warnings for a checkbox state and image syntax. — Open larger

ISO diary mapping and combined unresolved-link reports need Pro; the core import and its report are free.

Pro features

Pro costs $5 a month or $15 one time through GitHub Sponsors. One sponsorship turns on Pro in every plugin that has it.

Map ISO diary filenames Pro

Map valid YYYY-MM-DD.wiki names below the source diary/ folder into your chosen daily-note folder. Local links use the mapped paths too. Existing daily notes and duplicate mapped outputs are skipped; invalid dates keep their normal destination-relative paths.

The preview maps a dated diary page into Daily sample and shows an unresolved-link warning. — Open larger

Combine unresolved-link reports Pro

Create one report in the vault root from the latest saved import result for each source folder. This report uses saved warnings and doesn't scan imported notes again. Reimporting a source folder replaces its saved result.

A combined report lists unresolved targets from the Wiki and Other source folders. — Open larger

See how Pro works

Set up Vimwiki Import

needs

Obsidian 1.13.4 or later
Default Vimwiki .wiki pages already inside your vault.
A new destination folder that does not overlap the source.

steps

Back up your vault and place your source pages in a vault folder.
Run Vimwiki Import's Preview import command from the command palette.
Enter separate source and destination paths, then select These files use default syntax.
Select Preview and inspect output paths, converted text and warnings.
Select Import, then open the report in the destination folder.

If the app can't find a new plugin yet, try again later. Obsidian says a plugin that passes the review shows in the app within 24 hours.

How to import Vimwiki pages into Obsidian

Known limits of Vimwiki Import

Markdown and media modes are unsupported; copy default .wiki pages into the vault before starting.
The destination must be new and cannot overlap the source folder.
Attachments are not copied; images, tables, anchors, directives and rich text can need manual review.
Local links use the selected source map; absent targets stay unchanged with warnings.
Changed or missing sources and occupied output paths are skipped; completed writes remain if a later write fails.
Closing the preview cancels without importing, but closing the dialog after Import does not cancel writes that started.
Pro diary mapping accepts valid ISO dates below diary/ and skips existing daily notes or duplicate mapped outputs.
The combined Pro report uses saved import results, not a new scan; reimporting a source folder replaces its saved result.
Folder paths and review issues, including source text from some syntax warnings, remain in local plugin settings.
Tests used small fixtures and simulated sponsorship answers; phones, tablets, live payment and large real migrations were not tested.

Questions about Vimwiki Import

Do I need Vim installed?

The plugin has no runtime dependency on Vim. It reads default .wiki pages already inside your vault, so copy external pages there first.

Will it replace my existing notes?

Preview requires a new destination folder. Import skips a page when its planned output path already contains a file or folder. Existing daily notes are skipped too.

What happens to images and unsupported syntax?

Attachments aren't copied, and image syntax keeps its original path with a warning. Tables, anchors, directives and rich text can need manual edits. Markdown and media modes are outside this converter's scope.

How do I turn on diary mapping?

Sponsor theluckystrike through GitHub Sponsors for $5 a month or $15 once, then sign in through the plugin settings. A total payment of $15 meets the Pro payment requirement; sign-in and sponsorship checks still apply. Enter a daily-note folder in the import dialog to map valid ISO diary filenames.

Network use

After you select Sign in with GitHub, github.com receives the public client ID, read:user scope and device-flow polling requests. After sign-in, api.github.com receives an authenticated sponsorship query for your tier and total payment; cached checks can refresh automatically or through Refresh. The plugin sends no note content, file names or vault data, and makes no network requests before sign-in.

Read the full network disclosure