Team knowledge base migration: OneNote to Markdown to Confluence
Status: Export complete and shared with the team; Confluence import approximately 95% successful; limitations documented.
- Problem
- A team's knowledge lived in a OneNote environment that was hard to search, move or preserve with its attachments and history.
- My part
- I exported the full environment to Markdown with attachments intact, shared the export and approach, ran the Confluence import from a copy, and wrote up the limitations.
- Exists now
- A complete Markdown export, a Confluence space built from it, and an experimental map of which notes supersede others.
- Results
- About 95% of the import succeeded (my estimate; the denominator is not published). The supersession map is non-deterministic and is used only to help people review search results.
- Limits
- Internal work: no public artifact. The import rate is self-reported.
Evidence Internal work. No public artifact.