Zendesk → Decagon

Catalog plan outline

General guidance from the Afterstack catalog for Zendesk → Decagon. Not Zendesk or Decagon vendor documentation.

Migration friendliness

Zendesk 7/10 · Decagon 4/10

Speed to live

Zendesk 5/10 · Decagon 5/10

Catalog migration difficulty

Zendesk not set · Decagon high

Data to export from Zendesk

• custom objects
• call and voice logs
• synced email and calendar links
• workflow rules
• saved reports
• installed marketplace apps
• AI assistant configuration
• records for the catalog use cases: accounts

How the catalogs differ

• Zendesk is flagged for custom objects. Decagon is not, so the map is a redesign rather than a field-for-field copy.
• Decagon is not flagged for: custom objects, call and voice logs, synced email and calendar links, installed marketplace apps.
• Zendesk is flagged with an open API, which is the export path to test.
• Decagon is flagged with an open API for the load.
• Zendesk is cataloged as a fit for: Multi-channel support orgs that need SLAs, QA, and a ticket system of record.
• Decagon is cataloged as a fit for: High-volume digital CX.

Phases

1. Export

   Take Zendesk as the source of truth for this pair. Export custom objects; call and voice logs; synced email and calendar links; workflow rules; saved reports; installed marketplace apps; AI assistant configuration; records for the catalog use cases: accounts. The default enterprise helpdesk — tickets, SLAs, and a marketplace around them.

2. Map

   Load into Decagon only after the field map is written down. AI support agents for high-volume CX teams that still have a desk. Zendesk is flagged for custom objects. Decagon is not, so the map is a redesign rather than a field-for-field copy.

3. Prove a sample

   Decagon scores 5/10 on speed to live and 4/10 on migration friendliness. Run one sample load and one report the team already uses in Zendesk before a full cutover.

4. Cut over

   Zendesk scores 7/10 on migration friendliness. Keep Zendesk readable until the team is working in Decagon. Zendesk is the procurement-safe customer service platform: ticketing, messaging, QA, and a large app ecosystem. AI Copilot and the Sunshine layer sit on top of a ticket model most support orgs already know. It is powerful, configurable, and easy to outgrow in cost once every add-on is on.

Zendesk to Decagon: what the vendor docs actually cover

Linked sentences come from vendor documentation opened for this page. Everything else is general guidance, not Zendesk or Decagon vendor documentation. This section does not move data and does not change the catalog outline above.

What to export from Zendesk

If this pair needs a ticket warehouse, Zendesk's incremental export is the public mechanism opened on 2026-10-17, and it has nothing to do with Decagon. The first call passes a Unix start_time older than one minute. Later cursor calls pass the cursor the previous body returned. Time-based calls reuse end_time as the next start. Pages hold up to 1,000 tickets. These routes allow 10 calls a minute. Deleted tickets can be left out with exclude_deleted. end_of_stream tells you the catch-up is finished. That file is yours. Decagon's site does not reference it. Zendesk's price page, same day, still shows a yearly Support Team amount that matches the catalog's 19-dollar starting price, with Suite Team and Suite Professional above it on the same card, and a 14-day Suite Professional trial in the FAQ. Resolution overages are a separate meter on that page. The catalog trial flag matches the 14-day sentence. Repeating every cell of the table is unnecessary on this URL because the Ada pair already quotes the grid. The figures were re-read, not copied from memory.

• Zendesk incremental exports — checked 2026-10-17
• Zendesk pricing — checked 2026-10-17

How Decagon imports

Decagon's homepage, opened the same day, describes agents you define with Agent Operating Procedures in natural language, across voice, chat, and email. It does not name Zendesk, a ticket import, a help-center sync, or a handoff object. No public import docs; onboarding is vendor-led, checked 2026-10-17. Customer quotations and percentages on that homepage are omitted. No pricing URL with a fee was found on the homepage. No public pricing, checked 2026-10-17. The catalog's null starting price and custom model match. A trial length is not on the homepage, so the catalog trial flag is unverified. The practical shape of this pair, given what is public, is an agent in front of a desk you already run. Zendesk stays the ticketing system unless a private statement of work says otherwise. Nothing opened here authorizes turning Zendesk off.

• Decagon homepage — checked 2026-10-17

Object and field mapping

• A Zendesk ticket remains a Zendesk ticket. Decagon's homepage never names a ticket field.
• An incremental export row is a JSON ticket for your warehouse. It is not an AOP.
• Voice, chat, and email are channels Decagon lists. Zendesk already has those channels. The homepage does not say which system owns the channel after launch.
• Agent Operating Procedures are natural-language workflow text. They are not Zendesk triggers or macros.
• Help-center articles are not mentioned on the Decagon homepage. Do not assume Guide is ingested.
• Resolution percentages on the homepage are marketing lines and are not a field map.
• The 14-day Zendesk trial is a Zendesk commercial fact. It is not a Decagon pilot.

What will not carry over

• Macros, triggers, views, and SLAs.
• A documented Zendesk connector. The homepage does not name one.
• Guide articles, which are not mentioned.
• A Decagon price or trial.
• Historical tickets, unless you store the incremental export yourself.
• Sunshine conversation ids. They are not on the Decagon page.
• Any claim that the agent replaces the desk. The public page does not say that.

Cutover checklist

1. Keep the Zendesk subdomain in production. This check found no public cutover.
2. Write AOPs against the intents you will automate, and name the Zendesk group that still receives the rest. That routing is general guidance, not a Decagon sentence.
3. If compliance wants a ticket archive, run the incremental export on your side and do not expect Decagon to store it.
4. Honor the one-minute delay and the 10-call minute cap if you do export.
5. Ask Decagon, under contract, whether a Zendesk handoff exists. The homepage is silent.
6. Leave Guide where it is until a private doc says articles are connected.
7. Quote Decagon as sales-led. Quote Zendesk from its own price page, whose Support Team yearly figure matches the catalog's 19.
8. Do not paste homepage resolution rates into the project plan.

Common pitfalls

• Using Ada's handoff steps on a Decagon project. They are a different vendor's document.
• Deleting Zendesk because an agent homepage lists email and voice.
• Treating a marketing percentage as an acceptance test.
• Assuming the catalog trial flag is a Decagon offer. The homepage does not offer one.
• Exporting tickets into a shared folder and calling that an import. Decagon did not publish a loader.

Related catalog pages

• Best AI-native Zendesk alternatives (2026) — Which tool, compared
• What should replace Zendesk? — Switch narrative
• Decagon product page — AI support agents for high-volume CX teams that still have a desk.
• Customer support category — Catalog hub for this category