Migrate to Mintlify with your agent

We've migrated hundreds of docs sites to Mintlify. We did the first ones by hand. Now agents do most of the work, but we noticed that they kept making the same mistakes.

They pasted shared content into every page instead of keeping it in one snippet. They copied resized images instead of the originals, so screenshots came out blurry. Pages moved and their old URLs stopped working.

Each time we fixed one of these, we wrote the fix into guides our internal agents use. mint migrate ships those guides, so your agent can use them to move your docs too.

Your agent starts with a guide for your platform

mint migrate has guides for 21 platforms, including ReadMe, GitBook, Docusaurus, Confluence, Jekyll and PDFs. Each one tells the agent what carries over and what doesn't. When something isn't in your export, like GitBook's OpenAPI specs, the agent knows to ask you for it.

Add your platform with --from, for example mint migrate --agent claude --from gitbook.

Moving from	Flag	Doesn't carry over
ReadMe	--from readme	Try It API key state, Recipes, custom HTML pages
GitBook	--from gitbook	Organization-level OpenAPI specs, visitor auth, integrations
Docusaurus	--from docusaurus	Swizzled components, custom React pages, Algolia config
Fern	--from fern	generators.yml SDK snippets, audiences, Ask Fern
Document360	--from document360	API specs, home page builder layouts, reader groups
Confluence	--from confluence	Page restrictions, dynamic macros, comments

Run mint migrate on its own to see every supported platform. If yours isn't on the list, the agent still follows the general workflow, and the manual migration guide covers the rest.

It works from your repo, an export or your live site

You don't need your docs in a repo. The agent uses the best source you have, in this order:

1. Your repo. If your docs live in Git, the agent works from the source. Your navigation, URLs and OpenAPI spec come over exactly as your config declares them.
2. An export. For platforms behind a login, like Confluence, you export from the platform and the agent works from that folder.
3. Your live site. For hosted platforms with no repo, the agent saves a copy of every published page first, then converts from those files.

The agent isn't done until it can prove it

The guides carry the rules we wrote after watching agents get migrations wrong. When the source keeps its shared files, each one becomes one snippet, imported wherever the source used it. Images come over at their original size. Every moved URL gets a redirect.

Before it hands the site back, the agent checks its own work:

• mint validate passes, so every page parses and builds.
• mint broken-links finds no broken links.
• A manifest lists every page from your source as done, excluded or blocked, with a reason for each one that isn't done. No page goes missing without a record.

Then the agent reports anything it couldn't carry over, such as a custom landing page or an embed with no Mintlify equivalent, so you decide what happens to it.

Your docs stay with you

The migration runs on your machine, in your agent, under your own login. Your content never passes through Mintlify, and we never need your API keys.

The guides aren't a black box either. Every rule your agent follows is readable: run mint migrate --topic conversion to see how pages are converted, or mint migrate --from gitbook to see exactly how a GitBook site is handled.

Get started

1. Install the Mintlify CLI:

   npm i -g mint
   

   Already have it? Update first, or run npx mint@latest migrate in place of mint migrate below.
2. Open a new folder for your Mintlify project and start a migration with your agent:

   mint migrate --agent claude
   

   Swap claude for codex, cursor or gemini to use a different agent. The agent's own CLI needs to be installed first.
3. If you know your current platform, add it with --from:

   mint migrate --agent claude --from gitbook
   

4. Tell your agent where your docs live: a repo path, an export folder or a URL.

Already working in an agent? Ask it to run mint migrate and follow the instructions. It pulls the guide for your platform and the detail for each step as it goes.

From migrated to live

Once the migration checks out, your agent can publish it too. mint deploy puts the site live, and mint claim attaches it to your Mintlify account. Your docs go from another platform to live on Mintlify without leaving the terminal.

Frequently Asked Questions

Which agents does it work with?

--agent launches Claude Code, Codex, Cursor or Gemini CLI. Any other agent can run mint migrate and follow the instructions it prints.

What does it cost?

mint migrate is free. The migration runs on your own agent subscription.

What if my platform isn't listed?

The agent follows the general workflow, which works for any docs framework. The manual migration guide covers the details.

What happens to my API reference?

The agent uses your existing OpenAPI spec. If you don't have one, it builds one from your reference pages only if you agree, and marks it as rebuilt in the report.

What about versions and languages?

The agent asks whether you want to bring them over, then maps them to Mintlify's versions and languages.

Will my old URLs keep working?

Yes. Every URL that moves gets a redirect, and the agent checks that each source URL resolves before it finishes.

Can someone do the migration for me?

Yes. Talk to our team about a hands-on migration.