Intercom → Pylon

Catalog plan outline

General guidance from the Afterstack catalog for Intercom → Pylon. Not Intercom or Pylon vendor documentation.

Migration friendliness

Intercom 5/10 · Pylon 5/10

Speed to live

Intercom 6/10 · Pylon 7/10

Data to export from Intercom

• 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

How the catalogs differ

• Neither product is flagged for custom objects. Keep the object list short.
• Pylon is not flagged for: campaign and automation records, installed marketplace apps.
• Intercom is flagged with an open API, which is the export path to test.
• Pylon is flagged with an open API for the load.
• Intercom is cataloged as a fit for: SaaS products with in-app chat.
• Pylon is cataloged as a fit for: B2B SaaS support.

Phases

1. Export

   Take Intercom as the source of truth for this pair. Export 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. Messenger-first support. Fin — listed separately as Fin / Intercom Fin — is the AI agent layer.

2. Map

   Load into Pylon only after the field map is written down. B2B support hub for Slack, Teams, and ticket-weary account teams. Neither product is flagged for custom objects. Keep the object list short.

3. Prove a sample

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

4. Cut over

   Intercom scores 5/10 on migration friendliness. Keep Intercom readable until the team is working in Pylon. Intercom started as an in-app messenger and is now a support platform. Fin is Intercom’s AI agent; Afterstack lists Fin / Intercom Fin as its own catalog entry because teams shop the agent, not a new desk. Intercom itself is still the incumbent workspace: strong when the customer is already in the product, heavier if you needed classic email ticketing and a BPO-friendly queue.

Intercom to Pylon: what the vendor docs actually cover

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

What to export from Intercom

An Intercom help article that actually describes exporting conversations, users, or companies was not found on 2026-10-12. URLs that were tried resolved to teammate-permission help, to a two-factor article, or to a 404. Those pages are not export documentation, and they are not listed as sources. This cutover therefore does not invent an Intercom download path, a column list, or a file-size cap. What was opened is the pricing page. Beside an annual-versus-monthly control that does not reveal a second price column, the cards show Essential at twenty-nine dollars per seat each month, Advanced at eighty-five, and Expert at one hundred thirty-two. The catalog's twenty-nine-dollar start matches the Essential card. Fin is an extra meter, from ninety-nine cents for an outcome. The page counts that outcome once in a conversation, when the customer says the issue is resolved, or when they stop asking for more help, or when Fin finishes a workflow, handoffs included. Advanced includes twenty Lite seats at no extra seat charge. Expert includes fifty. Expert is also where the page lists SSO, HIPAA, SLAs, and multibrand. Copilot is twenty-nine dollars per agent each month on annual billing or thirty-five on monthly billing, and each agent gets ten Copilot conversations and ten AI auto-translation conversations without an extra charge. A Pro add-on starts at one hundred dollars a month for five hundred conversations and six thousand credits, with extra credits at one cent. Proactive Support Plus is ninety-nine dollars a month and includes five hundred messages. The trial is fourteen days, no card, and the page says it includes all features. At least one full seat is required. An early-stage offer is printed on the page. It is an offer, not a result this site measured. Customer quotations and resolution-rate claims on the page are not used.

• Intercom pricing — checked 2026-10-12

How Pylon imports

Pylon does not, on the pages opened for this pair, document an Intercom inbox import. The pricing URL redirects to schedule-demo and prints no seat price, which matches the catalog's custom model and the note that there is no public list price. The docs introduction describes agentic support, connectors, an API navigation item, automations, and skills. It never names Intercom conversations, Fin outcomes, or a CSV of users. The same docs page was read for the Zendesk pair. The finding here is narrower: Intercom is also unnamed. A search query against the docs site is not an article, so it is not a source. Mapping lines are general guidance. The catalog sentences about Pylon's SOC 2 Type 2 report and a November 2022 founding date were not re-verified on a security page in this pass.

• Pylon pricing — checked 2026-10-12
• Pylon docs introduction — checked 2026-10-12

Object and field mapping

• Intercom people are the conceptual source for contacts. No export article was opened, so this line does not name a button.
• Intercom companies are the conceptual source for accounts. Same limit: no file format was read.
• Intercom conversations are the conceptual source for ticket history. Fin outcomes are a billing event on Intercom's price page, not a column in a file this check possesses.
• Teammate seats on Essential, Advanced, and Expert are a price fact. They are not a user export.
• Lite seats included on Advanced and Expert are a packaging fact. They do not describe a Pylon role.
• Copilot conversations and the Pro add-on's credit pool are usage meters. They are not records to migrate.

What will not carry over

• A documented Intercom export. The tried URLs were the wrong articles.
• Fin outcome history, unless a future article says otherwise. None was opened.
• Resolution-rate marketing figures. They were ignored on purpose.
• A Pylon price. The demo redirect has none.
• A Pylon importer for Intercom. The docs intro does not name one.
• The early-stage discount as a measured saving. It is the vendor's offer text only.

Cutover checklist

1. Stop citing permission or two-factor help pages as if they were an export manual.
2. Ask Intercom support for the current export article rather than guessing a URL.
3. Record Essential, Advanced, and Expert from the cards, and do not invent a second column the toggle did not show.
4. Treat Fin as usage on top of the seat. The catalog's twenty-nine dollars is the Essential seat, not Fin.
5. Read Pylon's docs intro and confirm Intercom is still unnamed before telling stakeholders there is a connector.
6. Keep the Intercom workspace online. There is no landing format to test.
7. Do not paste review quotes or resolution percentages into the cutover doc.
8. If a real export article appears later, replace this section. Do not extend it with rumors.

Common pitfalls

• Calling a 404 or a two-factor article an export guide.
• Adding Fin's ninety-nine cents into the seat and calling the sum the list price.
• Assuming Advanced's twenty Lite seats are a data migration.
• Using one Pylon docs search as proof of an Intercom connector.
• Updating the catalog's Pylon security sentences without opening the security page.

Related catalog pages

• Best AI-native Intercom alternatives (2026) — Which tool, compared
• What should replace Intercom? — Switch narrative
• Pylon product page — B2B support hub for Slack, Teams, and ticket-weary account teams.
• Pylon vs Intercom — Head-to-head already in the catalog
• Customer support category — Catalog hub for this category