Export Articles from Zendesk
Guide has no export button worth the name. To export articles from Zendesk you use the API, and the parts people forget are the parts that break the migration.
What Guide gives you natively to export articles from Zendesk
Very little, and it's worth saying plainly. There is no admin screen that hands you a zip of your help centre.
What exists is a set of adjacent things that people mistake for an export. You can print an article. You can pull a content list. Some accounts have article-level import and export tooling around translations. None of that is a backup of a knowledge base with two hundred articles, forty images and three languages.
So the real answer is the Help Center API, or a tool that wraps it.
The API route
The Help Center API exposes articles, sections and categories as ordinary JSON, paginated. A basic export is a loop.
GET /api/v2/help_center/categories.json
GET /api/v2/help_center/sections.json
GET /api/v2/help_center/articles.json
GET /api/v2/help_center/incremental/articles.json?start_time=0Pull categories and sections first, because articles reference them by ID and a folder structure you rebuild afterwards from memory is a folder structure you get wrong. The incremental endpoint is the one to use for a repeatable backup, since it only returns what changed.
Endpoint paths and pagination style do shift between API versions, so confirm against the current Zendesk developer docs rather than copying a snippet from a forum post that's four years old. The API guide covers authentication and rate limits.
Two things to get right in the loop itself. Follow the pagination links the response hands you instead of incrementing a page number, because cursor-style pagination is what survives a knowledge base that's being edited while you export it. And authenticate as a user who can see everything you want, since drafts, unpublished articles and anything restricted to an internal segment simply will not appear for a token with end-user visibility. An export that silently omits your unpublished content looks complete right up to the moment somebody goes looking for a draft.
The five things people forget
The article bodies are the easy part. Everything below is what turns a two-hour job into a two-week one.
The body HTML also carries Zendesk-specific structure. Content blocks, relative links between articles, and any theme-dependent markup. Expect a cleanup pass on the other side no matter where you're going.
Backup and migration are different jobs
A backup wants completeness and repeatability. Run the incremental endpoint nightly, write JSON plus the image files to storage, keep it boring. You're optimising for the day someone deletes a category.
A migration wants fidelity in a target format. That means converting HTML to whatever the destination eats, remapping every internal link, rehosting images, and rebuilding the category tree. It happens once, and it's mostly a data-cleaning exercise rather than a technical one.
Doing a migration with a script written for backups is the classic mistake. You end up with perfect JSON and a help centre full of broken links.
Third-party tools
Migration services and marketplace apps will do this for you, and for a one-off move they're usually cheaper than the engineering time. Ask four questions before you pay.
If the answer to any of those is no, you have bought the easy half of the job and you'll finish the other half yourself, under time pressure, in the week of the cutover.
Whatever route you take, export before you need to. A knowledge base is the most expensive content a support team owns, and it's the one thing nobody backs up.
Frequently asked questions
Is there a proper Zendesk Guide backup?
Only what you build. A Zendesk help center export through the API is how you export a Zendesk knowledge base, and running it on a schedule is the closest thing to a Zendesk Guide backup that exists.
Can I export Zendesk help centre articles without the API?
Not properly. There's no native full export, so you either use the Help Center API or a third-party tool that calls it for you.
Do exported articles include images?
The HTML includes image URLs pointing at your Zendesk domain. The files themselves have to be downloaded separately and rehosted.
How do I export translations?
Translations are separate records attached to each article. Pull the article list first, then the translations for each article and locale.
What format do the articles come out in?
JSON, with the article body as HTML. Converting that HTML to Markdown or another CMS format is a separate step.
Should I back up my help centre regularly?
Yes. An incremental article pull on a nightly schedule is cheap insurance against a bad bulk edit or a deleted section.
Good articles cut volume, they do not cut duplicates
Even a perfect help centre leaves the same customer writing in twice. Ticket Merger handles that half.
Start free trial14-day free trial. No credit card required.