Zendesk → Fin / Intercom Fin

Catalog plan outline

General guidance from the Afterstack catalog for Zendesk → Fin / Intercom Fin. Not Zendesk or Fin / Intercom Fin vendor documentation.

Migration friendliness

Zendesk 7/10 · Fin / Intercom Fin 5/10

Speed to live

Zendesk 5/10 · Fin / Intercom Fin 6/10

Catalog migration difficulty

Zendesk not set · Fin / Intercom Fin medium

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. Fin / Intercom Fin is not, so the map is a redesign rather than a field-for-field copy.
• Fin / Intercom Fin is not flagged for: custom objects, call and voice logs.
• Fin / Intercom Fin adds catalog flags Zendesk does not have: campaign and automation records.
• Zendesk is flagged with an open API, which is the export path to test.
• Fin / Intercom Fin 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.
• Fin / Intercom Fin is cataloged as a fit for: Teams already on Intercom.

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 Fin / Intercom Fin only after the field map is written down. Intercom’s AI agent — listed on its own because teams shop Fin, not a new helpdesk. Zendesk is flagged for custom objects. Fin / Intercom Fin is not, so the map is a redesign rather than a field-for-field copy.

3. Prove a sample

   Fin / Intercom Fin scores 6/10 on speed to live and 5/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 Fin / Intercom Fin. 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 Fin / Intercom Fin: what the vendor docs actually cover

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

What to export from Zendesk

Fin does not replace the Zendesk account, and it does not ask you to dump tickets into a new desk. The connector page opened 2026-10-18 says Zendesk stays the system of record for tickets, conversations, and reporting. What Fin does consume from Zendesk is content you sync, plus the live ticket it is assigned. The Help Center sync article, dated May 18, 2026, requires Zendesk Guide. The help center stays on Zendesk. Setup is Train, Content, See all, Connect external app content, Zendesk articles, then API token or OAuth, then the subdomain. A metadata filter can limit categories, labels, or timestamps. Targets are Fin AI Agent, Copilot, Help Center, and an audience. Staff-permission articles are enabled for Copilot only and are not used in customer answers. The first sync cannot be cancelled. Later changes re-sync every hour, with no email for those runs. Labels, categories, and content tags become tags in the Fin workspace. Synced articles are view-only in Fin. Videos have to be Zendesk's Add video iframe. Custom HTML video embeds are not supported. The article says the legacy importer is deprecated on 25 April and does not print a year. Historical tickets and private comments are excluded from answer generation. The ticket setup article, dated July 31, 2026, uses a separate OAuth connection under Connect, Connect to Zendesk. New customers must use OAuth. API tokens are being deprecated. An existing token keeps working until you disconnect it. Popups for app.intercom.com have to be allowed. You create a Zendesk agent, role Agent, with a real mailbox (the guide's example appends +fin), verify it, and select it as the Fin Zendesk agent. Fin only replies to tickets assigned to that agent. The pricing page the same day shows Support Team at $19 per agent per month paid yearly, Suite Team at $55, and Suite Professional at $115. Monthly figures on the compare grid are $25, $69, and $149. The trial is 14 days of Suite Professional. Committed automated resolutions are $1.50 and pay-as-you-go resolutions are $2.00 on those columns. The catalog starting price of $19 matches yearly Support Team. The catalog trial flag matches the 14-day trial.

• Sync content from your Zendesk help center — checked 2026-10-18
• Fin for Zendesk tickets setup — checked 2026-10-18
• Zendesk pricing — checked 2026-10-18

How Fin / Intercom Fin imports

Fin's Zendesk ticket setup is an OAuth connection and a trigger, not an importer of old tickets. After connect, a default workflow includes follow-up, CSAT, and inactivity. When Fin closes a conversation for inactivity, the Zendesk ticket status does not follow, because Zendesk's Closed status is permanent and cannot be set through the API. The article tells you to solve that with a Zendesk automation, for example requiring the fin-resolved tag, that sets Solved. Fin creates five triggers: Fin Test, an optional assignment trigger, Conversation updated, Resolution, and Failsafe. Test mail must use the subject Fin Test. Go live is per channel. Tickets Fin touches get fin-involved. A knowledge answer can mark the ticket solved and add fin-resolved and fin-soft-resolution. A customer confirmation swaps that for fin-hard-resolution. A handoff unassigns Fin, removes the resolution tags, and adds fin-routed-to-team. Spam Fin detects after Zendesk's filter gets fin-marked-as-spam and does not count as a resolution. fin-failed lands on open tickets assigned to Fin with no progress within one hour. Fin's own closed state is not Zendesk Closed. Fin uses up to 50 Zendesk API requests per minute. The article says Zendesk's general limit is 200 to 700 per minute by plan, and an HTTP 429 is retried. Messaging needs Sunshine API access, which the connector page says is included in Suite Professional and above. The Intercom pricing page's existing-helpdesk block, which names Zendesk as an example, is $0.99 per Fin outcome, a minimum commitment (the example is 50 outcomes), no seat fee, and no setup or platform fee. The Fin catalog starting price stays empty. Intercom's pricing page and fin.ai/pricing say $0.99 per outcome with a 50-outcome minimum and no platform fee, while the September 17, 2026 outcomes article and the HubSpot explainer say a $49 monthly base that includes 50 resolutions. The same pricing page's Fin trial language is the 14-day trial that starts when Fin is set live inside Intercom. This connector page does not restate that day count. Sierra is a different product. This pair does not use Sierra's password-gated docs.

• Fin for Zendesk tickets setup — checked 2026-10-18
• Fin Zendesk connector — checked 2026-10-18
• Intercom pricing — checked 2026-10-18

Object and field mapping

• A Zendesk ticket stays a Zendesk ticket. Fin syncs the ticket, requester, and comments when the ticket is assigned to the Fin agent, and writes the reply back.
• Guide articles sync into Fin content. They are view-only there. Edits happen in Guide and arrive on the hourly re-sync.
• A Guide label becomes a Fin tag. That is not a Zendesk ticket tag. Ticket tags Fin writes are the fin-involved family.
• Staff articles do not feed customer answers. They default to Copilot.
• Zendesk Closed is not Fin's closed conversation. Do not map those words onto each other.
• fin-soft-resolution and fin-hard-resolution are successive states, not two objects.
• Sunshine messaging is a second OAuth connection and needs Suite Professional or above. Email tickets do not.
• Support Team at $19 does not include a statement that Guide or Sunshine is on that plan. The sync article requires Guide. The connector page ties Sunshine to Suite Professional and above, which is the $115 yearly card.
• Historical tickets are explicitly not an answer source. Do not map a ticket archive into Fin's knowledge.

What will not carry over

• The Zendesk agent UI, SLAs, and workforce add-ons. They stay.
• Private comments and old tickets, as sources for answers.
• A writable copy of a Guide article inside Fin.
• Custom HTML video embeds.
• Zendesk's Closed status, set by Fin's API. The article says that write is refused.
• Proactive outbound email from the Fin workspace on this connector. The setup FAQ says that needs the full Intercom suite.
• Fin reporting for tickets older than two years. The setup article says that window is fixed.
• A Fin seat price. The existing-helpdesk block says there is none. The catalog's empty Fin starting price was not filled with 0.99.
• The legacy importer after the date the article calls 25 April. The year is not printed.

Cutover checklist

1. Leave Zendesk as the desk. The connector page says it stays the system of record.
2. Confirm Guide is on the Zendesk plan before relying on the article sync.
3. Connect OAuth for tickets. Do not mint a new API token if you are a new customer.
4. Create a dedicated Agent user, verify the mailbox, and select it as Fin's identity.
5. Sync Guide content, then check that staff articles are not enabled for customer answers.
6. Migrate off the legacy importer if the source still shows it. The article says 25 April and does not give a year.
7. Send a test with the subject Fin Test before widening the assignment trigger.
8. Add a Zendesk automation that sets Solved from fin-resolved if you need the ticket to leave Pending. Fin will not set Closed.
9. If you also want Zendesk messaging, confirm Suite Professional or above for Sunshine, a separate OAuth connection.
10. Watch the 50-request-per-minute budget Fin says it uses.
11. Quote Zendesk from the $19 yearly Support Team card, and Fin from the $0.99 outcome with no seats. Do not edit either catalog price.
12. Keep macros and SLAs in Zendesk. Fin's tags are an overlay.

Common pitfalls

• Cancelling the first Guide sync. The article says you cannot.
• Editing a synced article inside Fin. It is view-only, and the next hourly sync follows Zendesk.
• Assigning tickets to a human and expecting Fin to answer. Fin answers only the agent it is configured as.
• Using a popup-blocked browser for OAuth and concluding the connector is down.
• Counting fin-marked-as-spam as a resolution.
• Buying Support Team at $19 and assuming Sunshine messaging is included. The connector page places that on Suite Professional and above.
• Copying a Sierra cutover onto this pair. Sierra's docs are a sign-in wall. Fin's Zendesk steps are public and different.

Related catalog pages

• Best AI-native Zendesk alternatives (2026) — Which tool, compared
• What should replace Zendesk? — Switch narrative
• Fin / Intercom Fin product page — Intercom’s AI agent — listed on its own because teams shop Fin, not a new helpdesk.
• Customer support category — Catalog hub for this category