Direct answer: The easiest way to migrate your Zendesk help center is to use a destination platform’s help center importer, or its assisted migration service, that explicitly supports Zendesk Help Center articles. Use the Zendesk Help Center API only when no importer covers your content. In either case, the migration is done only when sampled articles render correctly and old URLs land on the right new pages.
You want to move your help articles without rebuilding them by hand or sending customers to broken links. This guide covers the simplest transfer method and the checks that tell you whether it actually worked.
What’s the easiest way to migrate your Zendesk help center?
Start by scoping the job to the knowledge base. Full help desk migration tools are built around tickets, contacts, and agents, which is a much larger project. If your goal is moving articles, list your articles, languages, and media first, then pick a method.
Use a help center importer, not just a ticket importer
Your simplest route is a destination importer that explicitly supports Zendesk Help Center articles. Read the importer’s documentation before you start. Some importers move tickets and customers but leave knowledge-base content behind.
Ferndesk offers a Zendesk help center import and a done-for-you assisted migration. Treat moving the article content and keeping old links working as two separate checks, because one can succeed while the other fails. If your destination has no suitable importer, you can pull every article through Zendesk’s Help Center API and load the content yourself.
What needs to move besides article text?
A Zendesk help center is more than a pile of article bodies, and the gaps usually show up in the parts nobody listed before the import.
Check the content your customers actually use
- Structure: Article titles, bodies, and their category and section placement.
- Variants and visibility: Translations, drafts, and access restrictions on articles meant for specific users.
- Media and links: Inline images, downloadable attachments, and links between articles.
- Original URLs: A full list of old article URLs for link checks and redirects.
- Formatting: One representative article, especially if you use Zendesk content blocks, which the API returns as inline text rather than reusable blocks.
Keep help center content separate from help desk data
Your tickets, customer history, and support workflows are not automatically part of an article migration. Treat article comments and community posts as separate items, since whether they transfer depends entirely on the destination.
Which transfer method fits your help center?
The right method depends on how many articles you have, how many languages you publish in, and how much custom handling your content needs.
Compare the work involved
| Method | When it is simplest | What you still need to check |
|---|---|---|
| Destination importer or assisted migration | When it supports your article types, languages, and media | Verify its stated coverage against your actual content, including translations, restricted articles, and attachments |
| Help Center API export and destination import | When you need custom handling, such as restructuring sections or transforming content blocks | Account for authentication, pagination, translations, and attachments, which you must fetch and re-upload yourself |
| Manual copying | When you have only a handful of simple pages | Expect heavy labor for a larger help center, plus manual relinking of images and internal links |
Use an importer even for around 40 articles if one is available. Reserve manual copying for a handful of simple pages, and still check every image and cross-link. For 400 articles across four languages, a supported importer saves you from writing and debugging a script.
Check a sample before assuming the import is complete
No importer’s coverage should be assumed. An attachment can be skipped or a translation left out, and you may not see it until a customer does. Run these checks first:
- Compare article counts and category placement. Totals should match per section, not just overall.
- Open an article in each language you publish. Confirm the translation exists and is not the source language.
- Check an article with images, attachments, and internal links. Links should point to new pages, not back to Zendesk.
- Test a draft or restricted article with the appropriate access level. It should stay hidden from anonymous visitors.
Will your existing article links still work?
This is where migrations quietly lose search traffic and break links buried in product UI, onboarding emails, and saved macros.
If you control the old help center domain
You can keep a URL unchanged only if the new platform can serve the same hostname and path. Otherwise, map each old article to its new page and configure permanent redirects on a host you control.
For example, help.example.com/hc/en-us/articles/360012345678-Reset-your-password might move to example.com/help/reset-your-password. Confirm the old URL returns a permanent redirect, lands on the correct article, and appears updated in internal links and your sitemap. A matching article title is not URL preservation.
If your links use a Zendesk-owned subdomain
If customers reach your articles at yourcompany.zendesk.com, your new platform cannot preserve that hostname simply by importing the articles. Confirm what forwarding is possible for those URLs before you retire the old help center, and update every link you control, from in-app tooltips to email templates.
Redirects work only where you control the old host. Do not close the old help center until you have tested a sample of old URLs end to end.
When is Ferndesk a good destination?
Migration solves where your docs live, but it does nothing about the reason many teams leave: articles that drift out of date every time the product ships.
When your problem continues after the import
- Skip the rewrite. You can import your Zendesk help center, or use the done-for-you migration with URL preservation, instead of rewriting articles from scratch.
- Catch stale instructions early. After the move, Fern watches GitHub pull requests and support conversations, including ones in Zendesk, then drafts updates when instructions no longer match the product.
- Review instead of rewrite. You approve suggested content and refreshed screenshots as your UI changes, so migration stops being the last documentation task you remember doing.
Zendesk remains strong for ticketing and agent workflows, and Ferndesk is a help center platform, not a replacement for your shared inbox or ticket routing.
Frequently asked questions
Can you move the help center and keep Zendesk for tickets?
Yes. Help center content and ticket records are distinct migration scopes. After the move, check where links in your macros, automated replies, and other support workflows send customers.
Will your translations and private articles transfer?
That depends on the destination importer. Confirm language coverage up front, then test restricted articles with the intended audience before you rely on the new help center.
Will comments and old article IDs transfer?
Do not assume they will. Check whether your destination imports comments, and keep an old-to-new URL map if article identifiers or paths change.
Conclusion
To migrate your Zendesk help center with the least effort, use a help center-specific importer when it covers your content, and fall back to the Help Center API for exceptions or custom needs. The move is complete for your readers only when articles render correctly and every old link reaches the right page.
Book a demo