HubSpot Service Hub → Fin / Intercom Fin

Catalog plan outline

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

Migration friendliness

HubSpot Service Hub 6/10 · Fin / Intercom Fin 5/10

Speed to live

HubSpot Service Hub 6/10 · Fin / Intercom Fin 6/10

Catalog migration difficulty

HubSpot Service Hub high · Fin / Intercom Fin medium

Data to export from HubSpot Service Hub

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

How the catalogs differ

• HubSpot Service Hub 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.
• HubSpot Service Hub 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.
• HubSpot Service Hub is cataloged as a fit for: Teams already on HubSpot CRM.
• Fin / Intercom Fin is cataloged as a fit for: Teams already on Intercom.

Phases

1. Export

   Take HubSpot Service Hub as the source of truth for this pair. Export custom objects; call and voice logs; synced email and calendar links; workflow rules; saved reports; campaign and automation records; installed marketplace apps; AI assistant configuration; records for the catalog use cases: inbound, accounts. Tickets, help center, and Breeze AI attached to the HubSpot CRM you already run.

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. HubSpot Service Hub 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 HubSpot Service Hub before a full cutover.

4. Cut over

   HubSpot Service Hub scores 6/10 on migration friendliness and is marked high difficulty in the catalog. Keep HubSpot Service Hub readable until the team is working in Fin / Intercom Fin. HubSpot Service Hub is the support SKU in the HubSpot suite: tickets, customer portal, knowledge, and Breeze. It is an incumbent for teams whose ‘helpdesk’ was always a Hub. A Sierra or Decagon is not a like-for-like swap if marketing and CRM still live in HubSpot. Confirm current Service Hub and Breeze packaging on HubSpot’s site.

HubSpot Service Hub 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 HubSpot Service Hub or Fin / Intercom Fin vendor documentation. This section does not move data and does not change the catalog outline above.

What to export from HubSpot Service Hub

Fin on HubSpot Service Hub does not start by relocating tickets. HubSpot's record-export article, updated April 2, 2026, is still the way to take a snapshot if you want one. Tickets are under CRM, Tickets. Open the All tickets view, or a board view and Export view. Export permission is required. The file includes the properties in the view unless you customize it. Association columns include up to 1,000 associated record ids by default, plus the associated record name. All associated records is a CSV-only option. The download link arrives by email and expires after 30 days. Historical export rows stay in the log for 3 years. You can run 300 exports in a rolling 24 hours, three at a time. CSV or XLSX files split above 1,000,000 rows. XLS splits above 65,535 rows. A CSV over 2 megabytes is zipped. XLS allows 256 columns and XLSX allows 16,384. CSV has no column cap. Knowledge-base article export is a different article, updated August 28, 2026. It requires Service Hub Professional or Enterprise, an assigned Service Hub seat, and Service Access with the Knowledge base articles permission. The path is Service, Knowledge Base, Actions, Export knowledge base articles, then CSV, XLS, or XLSX. The file includes title, language, URL, and more. It is article metadata, not the HTML body. The Service Hub pricing URL opened 2026-10-18 rendered a pricing-data error after the Service Hub heading. No seat fee, no free-tool card, and no trial length were readable. The catalog starting price of 0, the free-plan flag, and the trial flag were neither confirmed nor contradicted by a number, and they were not edited.

• HubSpot export your records — checked 2026-10-18
• HubSpot export web content and data — checked 2026-10-18
• HubSpot Service Hub pricing — checked 2026-10-18

How Fin / Intercom Fin imports

Fin's HubSpot ticket guide, dated September 11, 2026, is a connector. Prerequisites are HubSpot Service Hub Professional so that tickets are enabled, a dedicated HubSpot user with a support seat, and a Fin workspace admin. Connection is OAuth2 from Connect, Connect to HubSpot, and tokens refresh. On success Fin creates three ticket properties in a Fin AI Agent group: Fin Status, Fin Tags, and Fin Assignment. It also deploys four workflows, initially disabled: Assign New Tickets, Resolution, Pending, and Route to Team. You map pipeline stages to four Fin states. The default Support Pipeline example is New for a new ticket, Waiting on contact for waiting on the customer, Waiting on us for waiting on the team, and Closed for resolved. Custom pipelines are allowed. Reply buttons and a create-ticket step are unavailable on the HubSpot email channel. The only handoff is Hand-off to agent in HubSpot. The integration has to be Live before Fin answers, including during a test. The test recipe adds a workflow criterion that ticket Description equals FIN test. Go live enables the four workflows, and Assign New Tickets then routes new tickets immediately. A webhook makes Fin fetch the ticket, thread, and contact. Image attachments sync from HubSpot to Fin. Ticket titles stay static. Knowledge-base sync is optional for the rest of the integration and, when you want it, requires Content Hub Professional or Enterprise because HubSpot's GraphQL Collector API needs the collector.graphql_query.execute scope. One knowledge base per sync. The HubSpot article's pricing block says $49 per month including 50 resolutions, then $0.99 per additional resolution, unlimited teammates, and a minimum commitment. The Intercom pricing page's existing-helpdesk block, opened the same day, says $0.99 per outcome, a minimum illustrated as 50 outcomes, and no seat fee, and it does not print $49. Both are Intercom pages. The Fin catalog starting price stays empty, rechecked 2026-10-19, because the $49 base and the $0.99 pricing-page package still disagree. The price note states both. Deactivate turns the four workflows off and keeps the mapping. Revoke deletes the workflows and the OAuth connection. Product Tours, Surveys, and Banners are not on this connector.

• Fin for HubSpot explained — checked 2026-10-18
• Fin for HubSpot tickets setup — checked 2026-10-18
• Intercom pricing — checked 2026-10-18

Object and field mapping

• A HubSpot ticket remains the system of record. Fin reads the thread after Assign New Tickets and writes the reply back onto that thread.
• Fin Status values are open, pending, and resolved. They are custom properties, not a replacement for your pipeline stages. The stage move is done by the four workflows using the map you set.
• Default stage names in the guide are New, Waiting on contact, Waiting on us, and Closed. A pipeline that uses different names has to be mapped. The words are not automatic.
• Fin Tags hold fin-involved, fin-soft-resolution, fin-hard-resolution, fin-resolved, fin-routed-to-team, and fin-failed. Those strings live in one property, not as six HubSpot properties.
• Fin Assignment is fin or human-teammate. Unassigning the Fin user by hand stops Fin from seeing later mail. The guide says to reply in HubSpot instead and let Fin back off.
• The knowledge-base CSV is title, language, and URL. It is not the body Fin syncs. Body sync uses the GraphQL collector scope and Content Hub Professional or Enterprise.
• Service Hub Professional is the ticket prerequisite in the setup guide. Content Hub Professional is a separate prerequisite and only for the article sync.
• A 30-day export link is an archive. Fin does not ingest that CSV.
• The $49 figure and the $0.99-only figure are on different Intercom pages. Neither was written into the empty Fin catalog price.

What will not carry over

• HubSpot workflows you already built. Fin adds four of its own and tells you not to delete them.
• Product Tours, Surveys, and Banners. The HubSpot explainer says those need the full Intercom suite.
• Dynamic ticket titles. The setup FAQ says titles stay static.
• Article HTML, if you only run the knowledge-base CSV export.
• Article sync on a Service Hub plan that lacks Content Hub Professional or Enterprise.
• More than one knowledge base in a single sync.
• A confirmed Service Hub dollar price. The pricing page failed to load its table.
• The catalog's $0 Service Hub starting price, which was not reconfirmed.
• A revoked OAuth connection. Revoke deletes the workflows. Deactivate does not.

Cutover checklist

1. Confirm Service Hub Professional if you want the ticket connector. The setup guide lists it as a prerequisite.
2. Create a dedicated user with a support seat. A personal login is what the guide says to avoid.
3. Connect with OAuth2. Do not paste a private app token. The guide does not describe one.
4. Map the real pipeline. Do not assume the default names New, Waiting on contact, Waiting on us, and Closed.
5. If you need article sync, confirm Content Hub Professional or Enterprise and the collector.graphql_query.execute scope. Otherwise leave knowledge sync off. The rest of the connector still runs.
6. Set the integration Live, then restrict Assign New Tickets to Description equals FIN test before you widen it.
7. Go live only when you intend Assign New Tickets to start routing.
8. Reply in the HubSpot thread if a human takes over. Do not unassign Fin first.
9. Use Deactivate for a pause. Use Revoke only if you accept a full rebuild.
10. If you archive tickets, download the email link before day 30, and remember the 300-export daily cap.
11. Quote Fin with both vendor sentences in view: the HubSpot article's $49 including 50 resolutions, and the pricing page's $0.99 with no $49. Quote Service Hub as unknown on this check.
12. Leave the catalog prices unchanged.

Common pitfalls

• Exporting knowledge-base CSV and expecting Fin to answer from titles and URLs.
• Testing before Live. The guide says Fin will not answer test tickets until the integration is Live.
• Deleting the four workflows. The guide says they are required.
• Editing them by hand. A later troubleshooting note says manual edits are overwritten.
• Using a user without a Service seat. Assign New Tickets then fails without an error.
• Treating the failed Service Hub price table as proof of the catalog's $0.
• Collapsing the $49 HubSpot-article price and the $0.99 pricing-page price into one number. They were both visible and they disagree.

Related catalog pages

• What should replace HubSpot Service Hub? — 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