{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/support.export-knowledge-and-archive/",
    "json": "https://www.anchorterminal.com/niches/support.export-knowledge-and-archive/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/support.export-knowledge-and-archive/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/support.export-knowledge-and-archive/index.min.md"
  },
  "markdown": "Two or three companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 3 | 18 | 18 | 5 | 4 |\n\n## What counts as done\n\nAll articles or tickets retrieved with bodies and attachments by paged or bulk calls, before any seat or plan change.\n\nMeasured, for our own tests: the counts match the UI.\n\nHow agents ask for it: export our help centre to markdown; pull every ticket before we cancel; sync articles into our docs; keep the archive after we downgrade\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Help Scout API + MCP (Help Scout PBC)**: The Docs API lists articles per collection, 50 a page up to 100, with an article fetch for bodies, and conversations and threads page to completion through the Inbox API.\n- **Intercom API + MCP (Intercom, Inc. (with Intercom R\u0026D Unlimited Company in Ireland))**: Articles and internal articles list and search with paging, conversations page by cursor, and export jobs cover content and reporting data.\n- **Plain API + MCP (Not Just Tickets Ltd)**: Help centers and articles can be fetched through GraphQL, and threads page by cursor with chosen fields.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Chatway MCP (Poptin Ltd)**: Conversations page at up to 100 with messages by cursor, but the knowledge base is reachable only through search-knowledge-base, not a list, and Free keeps 30 days of history.\n- **Chatwoot API (Chatwoot Inc.)**: Conversations and messages page to completion, but the application API has no list-articles call (only add), and acc-20 notes the free hosted tier keeps limited history.\n- **Crisp API + MCP (Crisp IM SAS)**: Knowledge Base articles list and read through MCP helpdesk tools one at a time, and conversations page at up to 50.\n- **Dixa (Dixa ApS)**: Knowledge collections have a catalog and articles are fetched one by one; conversations come through search and per-conversation message calls, with no bulk export endpoint found.\n- **Drag (DragApp.com Ltd)**: list_articles and get_article cover the knowledge base, and cards list per column, but email bodies come one thread at a time.\n- **FreeScout (FreeScout)**: Conversations with threads page to completion at 100 a page, but the API covers no knowledge base, which is a separate module.\n- **Freshdesk API + MCP (Freshworks Inc.)**: Solution categories, folders and articles have list endpoints, but ticket lists cap at 300 pages (30,000 tickets) and archived tickets drop out of search.\n- **Front API + MCP (FrontApp, Inc.)**: Knowledge base articles and categories list per knowledge base and conversations page by cursor, but bodies come one message at a time and Starter's 50 requests a minute makes a large archive slow.\n- **Gladly (Gladly Software, Inc.)**: Export jobs cover the lifetime of delivered communications, but schedule changes go through Gladly Support, files expire after 14 days and one-time exports over six months may carry a fee.\n- **Gorgias API + MCP (Gorgias Inc.)**: Tickets list by cursor, but email headers and original bodies are dropped after 30 days (only stripped versions kept), and Help Center tools work article by article.\n- **HelpDesk (Text, Inc.)**: Tickets page by next cursor and silo reaches archive, spam and trash, but HelpDesk has no help centre in this API, and each call counts against the monthly allowance.\n- **Kustomer (Kustomer, LLC)**: Knowledge base and archive search endpoints exist, but standard search covers two years of updates and archived records need the separate archive search.\n- **LiveAgent (Quality Unit, s. r. o.)**: MCP lists knowledge bases and categories and gets articles one by one; tickets come through filtered pages capped at 10,000 per filter, so a large archive needs date slicing.\n- **Missive API + MCP (Heliom Inc.)**: Conversations page with until, but bodies need one Get a Message call each, and Missive has no help centre to export.\n- **Pylon API + MCP (Pylon Labs, Inc.)**: Issues page by cursor and MCP lists knowledge bases, collections and articles, but article export goes one get_article at a time.\n- **Zammad (Zammad GmbH)**: Tickets and articles page with page and per_page under fixed hard limits, and the Knowledge Base has an API, with no bulk export endpoint.\n- **Zendesk Support API (Zendesk, Inc.)**: Incremental cursor export covers tickets, and acc-09 imported a Zendesk help centre, but acc-26 lost archive access while downgrading seats.\n- **Zoho Desk (Zoho Corporation Private Limited)**: Tickets, archived tickets and articles have list operations, but paging is from and limit at 50 with credit costs rising to 100 a call past 100,000 records.\n\n- not this job: Landbot MCP server (Landbot): list_knowledge_sources shows what an agent knows, but nothing exports conversations or help centre articles.\n\n## What stops agents finishing\n\n- archive access needs a paid seat\n- hosted free tier retention limit\n- articles only reachable one at a time\n\n## Around it\n\nAfter: document-extraction.html-to-markdown, knowledge.ingest.\n\n## Where this comes from\n\nWeight 5 of 100 in Customer support \u0026 helpdesk: 4 of 42 accounts (acc-08, 09, 20, 26); kept low because two are about leaving rather than agents working\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/support.export-knowledge-and-archive.json, or the MCP tool get_use_case with id support.export-knowledge-and-archive. Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Export tickets and help centre content",
        "url": ""
      }
    ],
    "description": "Export tickets and help centre content: 3 companies fully do it, 18 with a limit, 18 carry the tag. Every listing in Customer support \u0026 helpdesk with the reason and a source.",
    "facts": null,
    "h1": "Export tickets and help centre content",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/support.export-knowledge-and-archive/",
    "published": "",
    "section": "agents",
    "title": "Export tickets and help centre content: who does it | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/support.export-knowledge-and-archive/"
  },
  "tokens": {
    "markdown": 1600,
    "slim": 380
  },
  "version": 1
}
