Migrate from MintlifyCopy Anchor Link

Mintlify repositories already contain Markdown or MDX, so the content move is usually direct. The main migration work is turning docs.json navigation and hosted dashboard behavior into source controlled Farming Labs and application configuration.

1. Inventory the sourceCopy Anchor Link

Collect:

• docs.json or legacy mint.json
• every referenced .md and .mdx page
• images/, logos, favicons, fonts, and downloadable assets
• snippets/ and imported MDX partials
• OpenAPI or AsyncAPI documents
• redirects and external navigation links
• custom React components and CSS
• dashboard-only authentication, analytics, domain, preview, and deployment settings

2. Map the filesCopy Anchor Link

Keep a copy of docs.json as migration input, but do not rename it to docs.config.ts; their configuration models are different.

3. Rebuild navigationCopy Anchor Link

Mintlify navigation can contain pages, groups, tabs, dropdowns, anchors, languages, and external links. Translate it in this order:

1. Turn groups into content directories.
2. Move pages into the same order and add numeric order frontmatter.
3. Use folder landing pages for group introductions.
4. Recreate top-level tabs or product areas using routes and application navigation.
5. Preserve external links in a custom sidebar or top navigation.
6. Map each language tree to its target locale content root.

Do not rely on alphabetical ordering when docs.json specifies a deliberate sequence.

4. Convert frontmatterCopy Anchor Link

Preserve portable fields such as title, description, icon, and OpenAPI operation metadata. Review Mintlify-only fields individually. Represent an explicit source URL through the destination file path or redirect rather than leaving unsupported routing fields in frontmatter.

Add Farming Labs fields where useful:

---
title: "Quickstart"
description: "Install the SDK and make the first request"
order: 2
related:
  - /docs/installation
agent:
  tokenBudget: 900
---

5. Convert componentsCopy Anchor Link

Some component names overlap while their props differ. Verify every converted component with a production build instead of assuming identical APIs.

6. Move assets and API definitionsCopy Anchor Link

Copy public assets without changing their public URL when possible. Check absolute /images/... paths, relative images, dark/light variants, video, and downloadable files.

For OpenAPI:

1. Preserve the exact specification file or hosted URL.
2. Configure apiReference.
3. Compare operation routes and examples.
4. Recreate API authentication and proxy behavior separately.

7. Recreate hosted behaviorCopy Anchor Link

Mintlify dashboard settings do not automatically move with the repository. Confirm and recreate:

• custom domain and DNS
• redirects
• authentication and protected pages
• analytics and consent behavior
• search
• Ask AI
• preview and branch deployment
• feedback and support links

Farming Labs page actions already expose Copy Markdown and Open in LLM when configured. Verify the matching .md route rather than copying a Mintlify-specific page action component.

8. Validate and recoverCopy Anchor Link

Run the production build, then compare:

• every path listed in Mintlify navigation
• navigation labels, order, nesting, and language selection
• images, snippets, cards, tabs, accordions, and code groups
• OpenAPI operation pages
• redirects and authentication boundaries
• search, AI, analytics, and page actions

If an MDX component fails, replace one component family at a time and keep the page route stable. If a dashboard behavior was missed, delay the domain cutover until it has an explicit replacement.

Source referencesCopy Anchor Link

• Mintlify navigation
• Mintlify components
• Mintlify migration model
• Farming Labs page actions
• Farming Labs configuration