Alexandria
Alexandria stores Markdown notes with YAML frontmatter and local media. The Notion importer crawls your pages through Notion's API rather than reading an export, so relations, typed properties and toggles survive. See Imports for the crawl, preview and backup steps.
Pages become notes. Content is converted to Alexandria's Markdown/editor storage, with native toggles, internal note links, media and captions.
Databases become native tables/tags. Rows become distinct notes beneath their database. Notion's property definitions and values become editable native properties, rather than a fixed Project schema, including dates with ranges and offsets, currencies, files, places and two-way relations.
Hierarchy stays meaningful. Notion's own parents determine placement, and databases reached only through a relation keep their place under title-only copies of their ancestors. Links to another page are not mistaken for child ownership.
Identity comes from Notion IDs, not titles. Duplicate names stay separate; renamed pages update the same note. Reimport replaces source-owned content and relationships while preserving unrelated notes/memberships and absent source pages. It does not delete stale pages automatically.
The API does not return everything: blocks such as Google Drive embeds become placeholders linking to Notion, and links to pages outside the crawl stay Notion URLs. Both are listed in the import report.
Formula and rollup results, permissions/history, comments, database views and arbitrary embeds are not reconstructed.
Back up before importing into an existing vault. Filesystem failures can leave partial progress; resume with the same crawl and keep the backup until representative notes, database fields, media and hierarchy have been verified.