Mintlify's mint migrate lets AI agents move your docs site for you

Guides built from repeated agent mistakes

Mintlify says it has migrated hundreds of docs sites to its platform. The first ones were done by hand, while agents now handle most of the work. The company noticed that agents kept making the same errors: pasting shared content into every page instead of keeping it in a single snippet, copying resized images instead of originals so screenshots turned out blurry, and moving pages without keeping their old URLs working.

Each time Mintlify fixed one of these problems, it wrote the fix into guides used by its internal agents. mint migrate ships those guides so that a customer's own agent can use them.

The tool has guides for 21 platforms, including ReadMe, GitBook, Docusaurus, Confluence, Jekyll and PDFs. Each guide states what carries over and what does not. For example, the company lists Try It API key state, Recipes and custom HTML pages as items that do not carry over from ReadMe, and Swizzled components, custom React pages and Algolia config for Docusaurus. When something is missing from an export, such as GitBook's OpenAPI specs, the agent knows to ask the user for it.

Works from a repo, an export or a live site

Docs do not need to be in a repository. According to Mintlify, the agent uses the best source available, in this order:

• Your repo: if docs live in Git, the agent works from the source, and navigation, URLs and the OpenAPI spec come over as the config declares them.
• An export: for platforms behind a login, such as Confluence, the user exports the content and the agent works from that folder.
• Your live site: for hosted platforms with no repo, the agent first saves a copy of every published page, then converts from those files.

If a platform is not on the list, the agent follows a general workflow and the manual migration guide covers the rest. Running mint migrate on its own shows every supported platform.

Agents must verify their own work

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

Before handing the site back, the agent runs checks. mint validate must pass, so every page parses and builds. mint broken-links must find no broken links. A manifest must list every page from the source as done, excluded or blocked, with a reason for each page that is not done. The agent then reports anything it could not carry over, such as a custom landing page or an embed with no Mintlify equivalent, so the user decides what to do with it.

On privacy, Mintlify says the migration runs on the user's machine, in their agent, under their own login. The company says content never passes through Mintlify and that it never needs the user's API keys. The rules are readable: mint migrate --topic conversion shows how pages are converted, and mint migrate --from gitbook shows how a GitBook site is handled.

Getting started and what it costs

Users install the Mintlify CLI with npm i -g mint, or run npx mint@latest migrate. After opening a new folder for the project, they start with a command such as mint migrate --agent claude. The --agent flag launches Claude Code, Codex, Cursor or Gemini CLI, and the agent's own CLI must be installed first. Other agents can run mint migrate and follow the instructions it prints. Adding --from, for example --from gitbook, selects the source platform. The user then tells the agent where the docs live: a repo path, an export folder or a URL.

Mintlify says mint migrate is free and that the migration runs on the user's own agent subscription. For API references, the agent uses an existing OpenAPI spec. If none exists, it builds one from the reference pages only if the user agrees, and marks it as rebuilt in the report. For versions and languages, the agent asks whether to bring them over and maps them to Mintlify's versions and languages.

Once checks pass, mint deploy publishes the site and mint claim attaches it to a Mintlify account, so the whole move can happen in the terminal. Mintlify also offers a hands-on migration for teams that prefer to have someone else do it.