Import from Mintlify
Migrate from Mintlify
to a help center.
Bring your Mintlify pages, languages and structure into a help center your support team edits, with Ask AI included. Old links redirect, and the import is free.
Free on every plan
No credits
Works from your public site
Undo until you publish
Trusted 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.
Connect Mintlify.
Check the preview.
Import.
Publish on your domain.
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. 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.
No. Import and export are free on every plan and use no credits.
Pages in sidebar order, tabs and groups, images, links between pages, reused snippets, changelog updates, and components like notes, tabs, steps, cards and accordions.
Each page gets a redirect to its new page. Redirects work once your help center’s own domain points to Clevera, which needs Starter or higher. A mintlify.site address stays with Mintlify, so it can’t redirect.
Yes. Each language in your Mintlify navigation comes over into a language on your site, from the public site or the repo. Free publishes 2 languages, Starter 5, Pro as many as you need.
The preview shows an estimate before you start. Large help centers come over in one go, up to 2,000 pages per import, and we email you when it’s done.
Yes. Nothing on your Clevera site goes live until you publish, so Mintlify stays your docs site until you switch.
Their text comes over, but the interactive playground doesn’t. If your API reference matters to developers, keep it on Mintlify and move your help center to Clevera.
No. Paste your public docs address and Clevera reads every published page. Your repo, or a zip of it, works too.
Your Mintlify docs,
live on Clevera.
Import is free on every plan, and nothing goes live until you publish.