Migrate from Document360

Export a Document360 project as a ZIP, then convert its workspaces, languages, categories, and articles into a Mintlify project. Use the Document360 API and published site to audit content that the export may not represent completely.

​

Create a migration snapshot

Before exporting, create a named manual backup in Document360. Navigate to Settings > Knowledge base portal > Backup & Restore. Download a project export for the migration itself. In Document360, navigate to Content tools > Import and export > Import and export project.

1. Click Export project.
2. Select the export format. Choose JSON for a complete project export.
3. In Include new or modified articles in, select All so the export is not limited to recently modified articles.
4. Select every maintained workspace, language, category, and subcategory.
5. Select Include media files.
6. Click Export. The export runs in the background and notifies you when it is ready.
7. Download the ZIP from Recent files as soon as it is ready. Each new export overwrites the previous ZIP.
8. Export the All articles list as CSV. This list of metadata is useful for reconciling titles, publication status, dates, categories, and URLs.

​

Inventory content outside the export

Record project features that require separate migration work.

• Homepage Builder content and navigation
• Custom pages linked from the header, footer, or sidebar
• Snippets, variables, glossary terms, and templates
• Custom CSS, JavaScript, and integrations
• Reader groups, roles, SSO, and private-content rules
• Redirect rules and custom domains
• Analytics, feedback, forms, and search configuration
• API reference source specifications
• Drive files, decision trees, and embedded content

Use the published sitemap and the Document360 Customer API to compare the export with public and private content. The API is particularly useful when you need to traverse category metadata or recover fields that are difficult to derive from exported files.

​

Recreate navigation

Map the Document360 hierarchy to docs.json. Choose the mapping for workspaces based on how your readers use them. A workspace named v1 is usually a version, while separate product knowledge bases may map better to products or tabs. See Navigation for more information on Mintlify navigation elements. Document360 category API responses include only direct children. If you use the API to build an inventory, request each child category recursively and retrieve content separately for index and page categories.

​

Convert article content

Copy Markdown articles into .mdx files and convert exported HTML or JSON to MDX. Add frontmatter with at least a title, and retain descriptions, keywords, publication metadata, and canonical routes where useful. Review each editor’s platform-specific output: Both Document360 and Mintlify render the title frontmatter as the page H1, so page bodies begin at H2. Do not add a duplicate H1 during conversion.

​

Convert reusable content

Inventory variables, snippets, glossary terms, and every usage before replacing them.

• Convert reusable content blocks to Mintlify snippets.
• Replace variables with explicit text, generated content, or another maintainable source of truth.
• Replace glossary tooltips with links or supported tooltip components.
• Preserve language-specific variations rather than consolidating text that only appears identical in one locale.

Check the rendered source site as well as the export to determine whether each reusable item appears as expanded content or as a platform-specific reference.

​

Migrate API references

Download the original OpenAPI file from each Document360 API reference category or retrieve it from the system that syncs the specification.

1. Add the original specification to the Mintlify repository.
2. Configure OpenAPI-generated pages.
3. Preserve custom endpoint descriptions or examples that editors added after import.
4. Compare tag hierarchy, endpoint order, servers, authentication, examples, and code samples.
5. Replace any Document360 resync automation with the Mintlify deployment workflow.

Do not convert generated endpoint articles when the source specification is available.

​

Migrate media and files

Include media in the project export and copy owned files into your Mintlify project repository. Check Document360 Drive links, thumbnails, SVGs, downloadable files, CSS background images, and content embedded from external services. Update asset paths after reorganizing pages. Do not leave required production assets on Document360 domains unless you intend to keep that hosting active.

​

Preserve URLs and access rules

Document360 routes can include workspace and language slugs plus category and article slugs. Build a URL map from the published sitemap and the exported article CSV, then add redirects for every changed route. Recreate private documentation with authentication and access control. Create reader groups and role-based restrictions that mirror your previous access control setup. Test as each group before you publish your site.

​

Review your migration

Check that your exported ZIP, article CSV, API inventory, and published sitemap align, then test language switching and every workspace selector. Search your converted files for unconverted Document360 content: raw HTML, snippet and variable references, private notes, and widget embeds.

​

Launch your new site

• Set a content freeze on your former site and track every change made to it after your migration snapshot.
• Confirm your production branch and repository on the Git settings page of your dashboard.
• Record your existing DNS records and keep your former site running until you verify your Mintlify deployment is live.
• Review the navbar, footer, favicon, logo, colors, and typography.
• Review site and page metadata, canonical URLs, and indexing preferences. See SEO and search settings.
• Install any required analytics integrations, and optionally add a custom 404 page.
• If you migrated an API reference, compare endpoint pages, navigation structure, server URLs, authentication schemes, and examples with your former site.
• Preview your exact launch commit in a preview deployment. Check desktop and mobile layouts, pages from every navigation section, search, and your redirects.
• Check the browser console and network tab for any errors on pages that use custom components or scripts.
• Switch your domain with the custom domain guide, which covers the zero-downtime cutover for a domain that already serves documentation.
• After launch, monitor for 404 errors, redirect failures, and build failures.

​

Document360 references

• Export a project ZIP
• Export all articles
• Backup and restore
• Workspaces and languages
• Markdown editor
• Snippets
• Manage API references
• Category API
• Custom pages