en un clic
notion-to-markdown
// Migrate a Notion export into clean, organized markdown. Interviews you about your knowledge base structure, builds a config file, then migrates in progressive phases so both you and the skill get better over time.
// Migrate a Notion export into clean, organized markdown. Interviews you about your knowledge base structure, builds a config file, then migrates in progressive phases so both you and the skill get better over time.
| name | notion-to-markdown |
| description | Migrate a Notion export into clean, organized markdown. Interviews you about your knowledge base structure, builds a config file, then migrates in progressive phases so both you and the skill get better over time. |
| triggers | ["notion migration","migrate from notion","notion export","clean up notion"] |
Migrate content from a Notion export into your own markdown-based knowledge base, with progressive learning phases.
This skill operates in three phases. Each phase migrates increasingly complex content, refines the config based on your feedback, and builds your understanding of what "clean" looks like.
If no .notion-migrate.yml config exists, start with the setup interview:
setup.md and run the interview.notion-migrate.yml from their answersWhat gets migrated: Templates, frameworks, raw data, simple reference docs.
How it works:
references/cleanup-checklist.md)/docs/templates/ because your config maps templates there".notion-migrate.yml with any correctionsWhat the user learns: How Notion artifacts get cleaned up. What their filing structure looks like in practice.
What gets migrated: SOPs, guides, how-tos, process docs — content that requires filing judgment.
How it works:
What the user learns: The difference between content types. How to make filing decisions themselves.
What gets migrated: Policy docs, personal writing, identity content, IP — material that needs human review.
How it works:
What the user learns: By now they've seen 20+ examples and could almost do it manually. The skill saves time; the user has the judgment.
For each file being migrated:
Meeting Notes abc123def456.md)Apply the full cleanup checklist from references/cleanup-checklist.md:
Use the config's target_paths mappings. If uncertain:
Update the migration tracker (if the user has one) or report status:
Follow the user's git workflow preference from config:
per_file: Commit after each fileper_batch: Commit after each phase batchmanual: Stage changes, let the user commitSee references/decision-patterns.md for detailed guidance on:
See references/config-schema.md for the full .notion-migrate.yml specification.