# Migrate your docs to Mintlify > [llms.txt](https://www.mintlify.com/llms.txt) Migrate your documentation to Mintlify from ReadMe, GitBook, Docusaurus, Fern, or any platform. Get migration support and up to 12 months free. URL: https://www.mintlify.com/switch Switch to docs that stay in sync with your product. Migrate to Mintlify and get up to 12 months free on us. [Preview my docs](/switch#preview) · [Talk to sales](/contact/sales). Free preview. Migration support available. Join 20,000+ of the world's most ambitious companies building for agents. [Read customer stories](/customers) ## Built to scale with the agent web Mintlify powers millions of developers, agents, and AI-native products with enterprise-grade reliability and performance. [For enterprises](/enterprise) - 99.99% uptime - 2B+ agent visits in the past year - 300M+ visitors - 20,000+ customers ## Why teams switch Your product ships fast. Your docs platform should keep up. ### Documentation drift compounds at scale As products and teams grow, docs drift across versions and surfaces, leaving stale examples and gaps. ### Your docs have a new audience Claude Code, Cursor, and Codex read your docs. Most platforms still optimize only for humans. ### Every unanswered question has a cost When developers or agents can't find an answer, they guess or ask support, slowing users and growing queues. ## Built differently One platform for every reader and contributor. ### Built for humans and agents Give people a fast, beautiful documentation experience and give agents clean, structured access to the same knowledge. ### Self-updating by design Connect your product repositories and define what should happen when code changes via Mintlify automations. Your product ships. Your docs follow. ### Edit in Git, the browser, or Slack Work in Git and the CLI, the visual editor, or prompt the agent from Slack. Every change lands in the same version-controlled repo, with the same review and publishing flow. ### Answer questions, cut support tickets Mintlify sites ship with an AI assistant that answers questions with cited sources and generated code examples, tuned with your team's guidance. ### See how your docs perform Track traffic from humans and agents, assistant conversations, searches with no results, and reader feedback. Know what to fix next, and see what your old platform never showed you. "Moving our documentation to Mintlify was the obvious choice." — Product Manager, Developer Growth, HubSpot ## Teams see the difference - [Coinbase](/customers/coinbase): <60 sec documentation update time per change, down from 20+ minutes - [Zapier](/customers/zapier): 30% increase in internal API usage after unifying internal and external documentation - [Anaconda](/customers/anaconda): 5x faster content publishing after moving to Mintlify ## Live data Your docs have two readers now: developers and their agents. A growing share of your docs traffic isn't human. Claude Code, Cursor, and Codex read your docs to answer questions, write integrations, and make decisions on a developer's behalf. [Read the report](/blog/state-of-docs-traffic) Agents make up about two-thirds of docs traffic on Mintlify; humans the remaining third. - 66% agent traffic: share of documentation traffic coming from agents this month - 64% more precise: agent answers when working from structured documentation - 50% fewer tokens: consumed per task when agents used structured documentation ## Already made the switch Join teams that moved their docs to Mintlify. - From ReadMe: [Anthropic](/customers/anthropic), [Perplexity](/customers/perplexity), Scale, [Harvey](/customers/harvey), Benchling, Banc of California - From Fern: [OpenRouter](/customers/openrouter), LaunchDarkly, AssemblyAI, Astronomer, Cartesia - From GitBook: Hedera, Cortex, Kameleoon - From Docusaurus: MX, Semgrep, [Coinbase](/customers/coinbase) ### Startups Launch now. Grow Faster. Build a world-class developer experience without building and maintaining the documentation infrastructure yourself. [Explore Mintlify for startups](/startups) ### Enterprise Modernize without the rebuild. Bring your existing content, workflows, and teams onto an enterprise-ready platform with hands-on migration support, security, and reliability. [Explore Mintlify for enterprise](/enterprise) ## Don't let your old vendor hold you back Switch before your current contract ends. We'll match every month remaining on your contract with a free month of Mintlify, up to 12 months. Your free months begin when you migrate. Your paid term begins only after they end. Terms apply. Proof of your current contract term may be required. [See if I qualify](/contact/sales) · [Talk to sales](/contact/sales) ## Guided migration From scoping to go-live, we're with you through the switch. For teams that want hands-on migration support, Mintlify helps scope the move, port and QA your content, prepare your new site, and support your launch. 1. **Scope your migration.** We review your existing content, information architecture, integrations, and technical requirements upfront so we can align on the migration plan before work begins. 2. **Port and QA your content.** The Mintlify team assembles your existing documentation into your new site, checks the migrated content for quality, and gives you a preview to review. 3. **Review and give feedback.** Your team reviews the migrated content and sends feedback. Mintlify works through changes and gets the site ready for final setup. 4. **Prepare for launch.** We move the migrated content into your repository and help you work through the go-live checklist. Your team can make final content touch-ups and configure the documentation dashboard before launch. 5. **Go live.** Attach your custom domain and launch your new documentation experience. Mintlify provides dedicated migration support for 14 days after go-live. [Talk to us about your migration](/contact/sales) ## Frequently Asked Questions ### What platforms can Mintlify migrate from? Mintlify provides automated migration tooling for Docusaurus and ReadMe. Teams moving from GitBook or another platform can use the manual migration path or work with Mintlify on a supported migration. ### What does enterprise migration support include? For larger or more complex documentation sites, Mintlify can work with your team on a hands-on migration. We scope your content, technical requirements, integrations, authentication, design, and launch plan, then help move your documentation and prepare it for go-live. ### How do you handle large or complex migrations? We scope the migration around your existing documentation, integrations, and launch requirements. Depending on the size and complexity of your site, content can be migrated in sections while your team reviews and validates the new experience before cutover. ### How long does migration take? Timing depends on the size and complexity of your documentation, including custom components, authentication, integrations, and review requirements. We scope the migration with your team upfront and align on a launch plan before work begins. ### Can we try Mintlify before migrating? Yes. You can request a free preview of your current docs and test Mintlify using your own content before making a decision. ### Can we test everything before going live? Yes. Your team can review the migrated experience before cutover, test content and workflows, and complete QA before the new documentation becomes your production site. ### What happens to our existing URLs and SEO? Redirects and URL changes can be planned as part of the migration so existing links continue to send users to the right content and SEO impact is minimized after the switch. ### Can Mintlify support our existing authentication and enterprise setup? Enterprise migrations can account for authentication, SSO, domain configuration, and other technical requirements as part of scoping. We review your current setup with your team so those requirements are incorporated into the migration plan. ### Do we need an OpenAPI specification? No. An OpenAPI specification can help generate and migrate API reference content, but it is optional. ### What happens when the free contract-match period ends? Your paid Mintlify term begins after your matched free months end, so you are not paying for Mintlify and your previous platform at the same time. ### Will engineers need to manage every documentation update? No. Engineers can continue working through Git and the CLI, while writers, product teams, and other contributors can use the visual editor. Automations can also propose updates when your product changes. ## See what your docs look like on Mintlify [Preview my docs](/switch#preview) · [Talk to sales](/contact/sales) ## Test the experience with your content Get a free preview with your current documentation, and choose when to make the switch. Still under contract? Ask about getting up to 12 months free. Teams that made the switch: [Anthropic](/customers/anthropic), [Harvey](/customers/harvey), [Coinbase](/customers/coinbase), [OpenRouter](/customers/openrouter), LaunchDarkly, Astronomer. Request a preview with the form on the page: first name, last name, work email, role, company, documentation URL, and an optional OpenAPI specification URL. Your OpenAPI specification is optional. A link to your current documentation is enough to get started.