# Migrate docs into Mintlify from a ZIP export (/help-center/migrate-docs-from-a-zip-export) Mintlify does not have a direct "import ZIP" feature. Mintlify builds your site from files in a Git repository, so migrating from a ZIP export means converting the exported files into Markdown or MDX pages in your docs repo. The right path depends on which platform produced the ZIP. ## If the ZIP came from Document360 [#if-the-zip-came-from-document360] Follow the dedicated [Document360 migration guide](/migration/document360). It walks through exporting each workspace and language as a project ZIP and converting the articles, categories, media, and reusable content. ## If the ZIP came from ReadMe [#if-the-zip-came-from-readme] Follow the dedicated [ReadMe migration guide](/migration/readme). It covers the structure of a ReadMe ZIP export, including guides, recipes, custom pages, and OpenAPI files. Note that ReadMe ZIP exports reference hosted images by URL instead of including the image files, so download those assets separately. ## If the ZIP came from another platform [#if-the-zip-came-from-another-platform] Use the [manual migration workflow](/migration/manual): 1. Unzip the export and keep the original ZIP unchanged as a source snapshot. Do conversion work in a copy. 2. Create an inventory of pages with each page's source, destination path, and migration status. 3. Convert the exported Markdown, HTML, or JSON content into MDX pages. 4. Recreate your navigation in `docs.json` and review pages for leftover source-platform syntax. If the source site is also publicly available, scraping it can be faster than converting exported files. See [Scrape individual pages](/migration/index#scrape-individual-pages). ## Exporting your Mintlify docs as a ZIP [#exporting-your-mintlify-docs-as-a-zip] If you want the opposite direction, a ZIP archive of your published Mintlify docs for offline viewing or private distribution, use `mint export`. See [Offline export](/deploy/export). Offline exports require an Enterprise plan.