Choose your migration path
- If you currently use Docusaurus or ReadMe -> Automated migration
- If you have a public GitHub repository -> Auto-generated migration
- If you are migrating from any other platform -> Manual migration
- Automated migration
- Auto-generated migration
- Manual migration
Migrate your documentation using the @mintlify/scraping package. The package scrapes your content and converts it to use Mintlify components.If you host your documentation on another platform, see the manual migration steps.Migrate single pages:Filter specific paths:Use the The filter matches the specified path and all nested paths. For example, Migrate OpenAPI specifications:
Supported platforms
Docusaurus
ReadMe
Installing the scraper
Install the@mintlify/scraping package to get started.Scraping pages and sections
The migration tool automatically detects your documentation platform and converts your content. It saves prepared files locally in the./docs folder by default.For large documentation sites, migrate smaller sections one at a time rather than the entire site at once.Migrate entire sections:--filter (or -f) option to scrape only URLs matching a specific path prefix.--filter=/docs matches /docs, /docs/getting-started, /docs/api/reference, and so on.You can also use the CLI command:Add prepared content to your Mintlify project
After scraping your existing documentation platform, you are ready to build your docs on Mintlify.Confirm that you scraped all of your pages. Then add these files to the documentation repository that you created during the onboarding process. This is usually a GitHub repository.Post-migration checklist
After completing your migration (automated or manual), we recommend checking:- All pages render
- Navigation works as intended
- Internal links resolve properly
- Images and assets load correctly
- Code blocks display with proper syntax highlighting
- Search works
- Correct deployment branch