> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.crisp.chat/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to import a Knowledge Base from another provider

*Import articles from another help center into Crisp so you can move your self-service content faster.*

Crisp can automatically import Knowledge Base content from several providers. The importer helps you recreate articles in Crisp, but you should still review the result afterwards to confirm formatting, categories, images, and links.

---

# ${color}[#0080dd](Before importing)

Your existing knowledge base must be public so Crisp servers can fetch its content. If your source knowledge base is multilingual, import each language from the matching language URL, such as `example.com/en` for English or `example.com/fr` for French.

__Crisp can import from providers such as:__
* **BetterDocs**
* **Freshdesk**
* **Front**
* **GitBook**
* **Gorgias**
* **GrooveHQ**
* **HelpCrunch**
* **HelpDocs**
* **Helpjuice**
* **Help Scout**
* **HubSpot**
* **Intercom**
* **LiveAgent**
* **WordPress Knowledge**
* **WP Lore** by LSVR Themes
* **Zendesk**

|| Images from **GitBook** and **LiveAgent** may not be imported automatically. Once the import is complete, review those articles and add missing images manually.

---

# ${color}[#0080dd](Import articles into Crisp)

Start from [**app.crisp.chat**](https://app.crisp.chat), then open **Knowledge Base**.

__To start the import:__
* Click the **Actions** button in the upper-right corner
* Select **Import articles**
* Paste the public URL of the knowledge base you want to import
* Confirm the import and let Crisp process the content

![Import articles from the Knowledge Base actions menu](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-02-28-at-124303_1f737ro.png =1000xauto)

| Import time depends on the number of articles in your previous knowledge base. Crisp will notify you by email when the import is complete.

---

# ${color}[#0080dd](Review imported articles)

Imported articles should be checked before you consider the migration complete. Some content may need manual cleanup depending on the source provider and the original article structure.

__After the import, review:__
* **Categories** → confirm articles are assigned to the right categories
* **Images** → add any images that could not be imported
* **Videos and embeds** → reinsert videos manually when needed
* **Tables** → check whether table formatting still looks correct in Crisp
* **Links** → verify internal links point to the right Crisp articles
* **Markdown** → fix any malformed formatting, spacing, or line breaks

| If your imported content has formatting issues, compare it with the supported syntax in [How can I format Knowledge Base articles?](/en/article/how-can-i-format-knowledge-base-articles-oiurpj/).

---

# ${color}[#0080dd](Frequently Asked Questions)

*Still have questions which were not covered in this article? Here is a collection of the most frequently asked questions on this topic.*

###### ${color}[#F08820](My previous provider is not supported, what can I do?)

**You can still recreate the content manually or use the Crisp REST API.** If your articles are already written in Markdown, paste them into new Crisp articles. If they are written in HTML, you can convert them to Markdown first. For larger migrations, the [Crisp REST API](https://docs.crisp.chat/references/rest-api/v1/#website-helpdesk) can help you import content programmatically.

###### ${color}[#F08820](My articles were imported, but the content looks wrong. What should I check?)

**Start by checking the original Markdown and disabling custom code.** Broken formatting usually comes from malformed Markdown, unusual HTML, or custom code applied on the source knowledge base. Review the affected articles in Crisp, fix the markup, and re-add missing media manually.

###### ${color}[#F08820](Can Crisp import a private knowledge base?)

**No, the source URL must be publicly reachable during the import.** Crisp needs to fetch the pages from its servers, so protected, private, or restricted URLs cannot be imported unless you make them temporarily public.