You don't need a special importer for your current tool. If your docs are public, usedocs can read them from the web: Help Scout Docs, Document360, Mintlify, Docusaurus, HelpDocs, a hand built site, or anything else. Here's how the move works.

What moves

  • Every page it can reach. usedocs discovers pages from your sitemap and links, then imports the main content of each, leaving out navigation, sidebars, and footers.
  • Content that converts cleanly. Headings, paragraphs, lists, code blocks, quotes, simple tables, and images (linked to where they're hosted today) come across as Markdown.
  • Collections from folders. Pages under /docs/billing/ land in a Billing collection, and so on, so your structure carries over.
  • A redirect for every page. Each old path, like /docs/billing/refunds, becomes a redirect to its new article.

Steps

  1. Paste your docs URL. In the usedocs dashboard, open Help center, then Import, and choose Any docs site, or use the “Where are your docs today?” step during onboarding. Paste the URL of your help center or docs home.
  2. Choose drafts or publish. Import as drafts to review first, or publish right away if your current docs are in good shape.
  3. Review and organize. Check the collections and drafts. For a large site, run the import again per section; pages already imported are skipped.
  4. Connect GitHub and turn on the assistant. Install the GitHub app and usedocs reports which imported articles disagree with your code, with proposed fixes. Turn on Ask AI or the widget so unanswered questions start your gap list.
  5. Point your domain at usedocs. Point your docs domain at usedocs, or serve the help center from a subfolder like yourapp.com/help. Old paths redirect to the new articles.

After the import

Imported docs are rarely fully current, so usedocs starts by checking them. Connect GitHub and it reads each imported article against your code and lists the ones that disagree, with proposed fixes, often within minutes of the import. After that, merged pull requests propose edits to the articles they affect, and the questions your assistant couldn't answer, plus “not helpful” votes, become ranked gaps with drafted articles.

Good to know

  • Up to 100 pages per import run; run it again per section for bigger sites.
  • Pages must be public; for private docs, use an API import (Zendesk, Intercom, GitBook, Notion) where available.
  • Images stay hosted where they are today; re-upload any you need before closing the old account.
  • Interactive widgets, embeds, and complex layouts come across as plain content to tidy up.