Import from Mintlify
Free on every plan
No credits
Works from your public site
Undo until you publish
IMPORT CONTENTTrusted by product teams worldwide
Getting your docs
out of Mintlify.
Your Mintlify pages already live as MDX files in a Git repo, so the text is yours. The catch is the components. Notes, cards, tabs and steps are Mintlify syntax other tools can’t read, and the offline HTML export needs Enterprise. Clevera reads your public site or your repo and turns those components into its own blocks.
Works with your public site
Paste your docs address and Clevera reads every published page.
Or bring the repo
Your repo, or a zip of it, comes over the same way.
Components become blocks
Notes, tabs, steps, cards and accordions keep their shape.
Your changelog comes too
Changelog updates arrive as drafts for you to check.
What comes over.
What stays behind: older versions (your default version comes over), the interactive part of API playground pages (their text comes over), custom components and styling, files other than images, and analytics. Pages limited to signed-in readers come over from the repo or zip like any other page, so untick them in the preview before you publish.
How it works.
1
Connect Mintlify.
Paste your public docs address or your repo address. No developer needed.
2
Check the preview.
See every page before anything moves, and untick what you don’t want.
3
Import.
Pages, images and links come over. It’s free and uses no credits.
4
Publish on your domain.
Go live when you’re ready. Old links redirect once your domain points to Clevera.
Keep Mintlify for your API docs.
If developers write your docs in Git and review changes as pull requests, Mintlify is built for that. Its API playground turns an OpenAPI file into interactive reference pages, and its free plan already includes your own domain. Clevera is built for help centers that support and product teams write in an editor and keep current. So you can keep Mintlify for your API reference and run the customer help center on Clevera. Our own, help.clevera.ai, moved from Mintlify to Clevera. Agents can keep your help center current too, through the Clevera MCP server on Pro.
What you get
after the move.
Your Mintlify pages land in a full help center. Four things you get on day one:
Answers with sources
Ask AI replies to readers from your published pages and lists the pages it used. It uses no credits: 300 answers a month on Free, 1,000 on Starter, 5,000+ on Pro.
See what readers miss
Insights show searches with no result and what readers asked, with Write article next to each gap.
Your own domain
Free sites live at your-site.clevera.help. Use help.yourcompany.com from Starter.
A video in every article
Record your screen and Clevera writes the article and makes the how-to video that sits in it. Videos and articles use credits.
Mintlify vs Clevera for a help center.
Questions.
Does the Mintlify import cost anything?
What comes over from Mintlify?
What happens to my old links?
My docs are in several languages. Does that work?
How long does it take?
Can I keep Mintlify live during the move?
What about API reference pages?
Do I need a developer?