Migrate to superlore
Move your existing docs — Mintlify, Docusaurus, Fumadocs, Nextra, GitBook, or plain Markdown — into superlore. Plan-first, you review and comment, then it migrates and proves it built.
Migration is plan-first. Your agent doesn't bulk-convert blindly — it writes a migration plan as a superlore doc, you review and comment on it in the editor or the Viewer, and only then does it convert your content, verify the build, and hand you a summary with screenshots.
Start it
Install the superlore Claude plugin, then just ask:
Migrate my Mintlify docs to superloreThe superlore-migrate skill takes over from there. Point it at your existing docs repo (or run
it from inside it).
Comes from anywhere
What you get
- Reviewed, not dumped
- A plan you approve (or comment on) before anything converts.
- Upgraded, not transliterated
- Markdown tables → DataTable, diagrams → Canvas, roadmaps → Timeline — real dual-representation.
- Agent-ready
- Every page serves a typed knowledge face over MCP, not a flat render.
- Proven
- It builds + Playwright-renders key pages and screenshots them before calling it done.
Diagrams become Canvas
Mermaid blocks, PlantUML, and even images of diagrams are migrated to a real superlore Canvas — typed nodes and edges an agent can read, not a picture. superlore does diagrams via Canvas.
The flow, in steps
Plan + review It writes a migration plan as a superlore doc — open it in the
Viewer or the editor preview, leave comments, approve.
Migrate Each page becomes superlore MDX with the right components, led by a Canvas; nav and
links are preserved.
Verify + summarize It builds, Playwright-checks key pages, and writes a summary with
screenshots and per-page status.
Already have just one file? You don't need to migrate a whole site — see a single doc.