Migrate from Mintlify
See what moves when you migrate a Mintlify site to Documentation.AI, and what you decide along the way.
You can migrate a Mintlify site from its live address or from its repository. The steps are the same as for every platform. See Migrate to Documentation.AI.
What you can migrate from
- Your live site, such as
https://docs.acme.com. The migrator reads the Markdown copy that Mintlify publishes for each page. If a page does not serve one, the migration stops rather than guessing that page's content, and your assistant tells you which page it was. - Your repository, with its
docs.jsonormint.jsonfile. Tell your assistant the folder where you cloned it.
What moves
| In Mintlify | In Documentation.AI |
|---|---|
| Tabs, groups, anchors, dropdowns, menus, languages, and versions | The same navigation, in the same order |
| Hidden pages and tabs | Copied. At the first decision, you choose whether to add them to the sidebar |
| Sidebar icons and tags | Sidebar icons and badges |
Note, Tip, Info, Warning, Check, and Danger | Callout |
Accordion and AccordionGroup | Expandable and ExpandableGroup |
Card, CardGroup, and Columns | Card and Columns |
Tabs, Steps, CodeGroup, and Update | The same components |
Frame and videos | Image and Video |
ParamField, ResponseField, RequestExample, and ResponseExample | API components |
Tree and FileTree | Expandable folders |
| Snippets imported without props | The snippet's content, on each page that uses it |
| OpenAPI endpoint pages | Endpoint pages with method badges in the sidebar |
| Redirects | Exact redirects. Wildcard rules are listed in the report for you to add |
| Custom heading IDs | Links to those headings keep working |
| Colors, logo, favicon, and navbar links | Your site's look, which you review at the second decision |
What needs your decision
At the second decision, your assistant shows each of these with the pages that use it:
- Custom React components from your
snippetsorcomponentsfolder - Snippets used with props
- Expressions written in braces, such as
{user.name}
What does not move
- Generated SDK reference pages
- Your footer, custom fonts, and banner. See What does not move.
Your footer uses the same field names on both platforms, so you can copy it by hand. Paste the footer object from your docs.json into documentation.json, with its links and socials as they are. To keep their icons, rename the twitter and x-twitter platforms to x, and earth-americas to website. A footer set inside a language in your Mintlify navigation goes in the same place here: copy it into that language's entry in your navigation. See Give a language its own footer.