# Migration overview

> Choose a migration path for moving existing documentation from Docusaurus, ReadMe, GitBook, Fern, Document360, or another platform to Mintlify.

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.

:::card{title="Docusaurus" href="/guides/get-started-migration-docusaurus"}
Scrape a public site, or migrate from source to preserve private pages, versioned docs, localized content, and custom React components.
:::

:::card{title="ReadMe" href="/guides/get-started-migration"}
Export project files to preserve private content and OpenAPI files, or scrape a public site for a faster starting point.
:::

:::card{title="GitBook" href="/guides/get-started-migration-gitbook"}
Export each section with Git Sync for the most complete migration, or scrape a public site.
:::

:::card{title="Fern" href="/guides/get-started-migration-fern"}
Migrate MDX, assets, API specifications, and `docs.yml` configuration from the source repository.
:::

:::card{title="Document360" href="/guides/get-started-migration-document360"}
Export every workspace and language as a project ZIP, including articles, categories, and media files.
:::

:::card{title="Other platforms" href="/guides/get-started-migration-manual"}
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.

```bash theme={null}
npx @mintlify/scraping@latest page https://docs.example.com/getting-started
```

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.

```text theme={null}
https://github.com/org/repo -> https://mintlify.com/org/repo
```

Browse [generated documentation sites](https://www.mintlify.com/wiki) to see more examples.

## Related topics

- [Automations overview](/docs/automations/index.md)
- [Components overview](/docs/components/index.md)
- [Analytics overview](/docs/analytics/index.md)

## Related pages

- [Admin](./admin-index.md)
- [Agent](./agent-2-index.md)
- [Agent](./agent-index.md)
- [Agent-ready content](./agent-ready-content-index.md)
- [AI](./ai-index.md)
- [Analytics](./analytics-index.md)
- [API docs](./api-docs-index.md)
- [API reference](./api-reference-index.md)
- [Assistant](./assistant-2-index.md)
- [Assistant](./assistant-index.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.