Notion Open-Source Migration Fit Auditor

• Direct competitor truth table (5):
• AppFlowy: Imports Notion workspaces/pages/databases/media; open-core and self-hosted; Price: Cloud Pro $12.50/user/mo; Vault $6/user/mo annually
• AFFiNE: Local-first docs/whiteboard/database; Notion HTML ZIP/Markdown import; Price: Pro $6.75/mo; Team $10/seat/mo
• Anytype: Local-first/P2P knowledge OS; Notion importer preserves parent-child links as objects; Price: Business cloud €20/editor/mo; self-host €300/mo not yet launched
• Outline: Team wiki; Notion OAuth importer for documents, images, and video; Price: Business $4/user/mo annually, ten-user minimum
• Obsidian Importer: Official plugin; Notion API/ZIP import with some database/formula conversion to Bases; Price: Optional Sync $4/user/mo annually; Commercial $50/user/year Counterevidence: the market is neither competitor-free nor unique nor low-competition. AppFlowy and Obsidian cover most basic content migration. AFFiNE says not every feature maps one-to-one; Outline says authorship is lost; Obsidian documents primary-view, linked-data-source, and ZIP database limitations. The only plausible gap is a **vendor-neutral, cross-destination preflight loss map**, and that narrow gap has zero payment evidence.

Validation Actions

1. 1.Create one smoke-door page containing the problem, five destinations, an explicitly illustrative loss-map example, a `$299 Manual Migration Preflight`, and booking/Payment Link. State clearly that delivery is manual and no automated product exists.
2. 2.Contact 15 qualified prospects without paid ads: IT/Ops owners, 5–50-person team leads, or consultants publicly discussing Notion self-hosting or migration.
3. 3.Complete at least five 20-minute interviews covering migration reason, deadline, workspace complexity, current test method, largest rework risk, willingness to share a sanitized structure, and reaction to `$299`.
4. 4.Offer a manual paid pilot only to prospects with a 90-day deadline plus at least ten databases, complex relations, or multi-user permissions. Use a third-party Payment Link; do not build payments.
5. 5.With explicit authorization, manually inspect one sanitized export's directory/CSV/Markdown inventory and deliver an experimental loss map. Do not write a parser, upload unauthorized attachments, or claim automated accuracy.