Skip to main content
Move your existing documentation to Mintlify with an automated scraper, an export from your current platform, or a manual migration. The best path depends on whether your site is public, whether you can access its source files, and which platform-specific features you use.

Docusaurus

Scrape a public site, or migrate from source to preserve private pages, versioned docs, localized content, and custom React components.

ReadMe

Export project files to preserve private content and OpenAPI files, or scrape a public site for a faster starting point.

GitBook

Export each section with Git Sync for the most complete migration, or scrape a public site.

Fern

Migrate MDX, assets, API specifications, and docs.yml configuration from the source repository.

Document360

Export every workspace and language as a project ZIP, including articles, categories, and media files.

Other platforms

Follow the manual workflow for another platform or a project with mixed content sources.

​
Scrape individual pages

The Docusaurus, ReadMe, and GitBook guides use the scraper’s section command, which converts every page it can reach from the URL you give it. To convert a single page instead, use the page command from your migration directory.
Use page to check how the scraper converts your content before a full run, or to fill in individual pages that a section run missed. For a large site, narrow a section run with --filter rather than scraping everything at once.

​
Generate a site from a repository

Mintlify can generate a complete documentation site for any GitHub repository, whether it already contains documentation or just code. Replace github with mintlify in your repository URL.
Browse generated documentation sites to see more examples.

Related topics

Migration overviewAutomations overviewComponents overview