How to Export Intercom Data
Converge Team
Export Intercom data in 2026: CSV row caps, the 200-300 bulk transcript limit, JSON to S3/GCS/Azure, and the old export's deprecation. Checked 6 Sept 2026.
How do you export Intercom data?
There is no single "export everything" button in Intercom. Six separate routes cover different data, and each one is missing something the others have: single-conversation transcript downloads from the Inbox, bulk transcript downloads from the Inbox, CSV dataset exports from Reports (metadata only), the Conversations REST API (the only programmatic route to full transcripts), scheduled JSON exports to cloud storage, and the Contacts CSV for your customer list. Every figure below carries the date it was verified against Intercom's own help centre and developer docs. The conversation, cloud-storage and contact routes were re-opened on 6 September 2026, and two of the six had changed since our August pass.
Download a single conversation or ticket (text or PDF)
Open the conversation or ticket in your Inbox, click the three dots in the top-right corner, and choose Export conversation as text or Export conversation as PDF (Export ticket as text / PDF for tickets). Both formats carry the complete message chronology with timestamps, all participant information, and AI summaries where they exist. Two limits matter for a migration: internal notes are stripped from conversation transcript exports, and payment card numbers are redacted at the point of entry, so a transcript is never a complete audit record. Tickets are the exception — tick the include-attributes-and-notes box and the .txt file carries notes plus non-customer-visible attributes. The PDF never does (Intercom's tickets export article, checked 6 August 2026).
Bulk-download transcripts from the Inbox (no API needed)
Most third-party guides still say the UI can only export one conversation at a time. That is out of date. Filter your Inbox to the conversations you want, tick their checkboxes (or use the select-all control), open ... (More actions) in the bulk-actions bar, type "export", and pick Export as text or Export as PDF. Each conversation downloads as its own file. Intercom caps this at 200–300 conversations per operation and directs you to the Conversations API for anything larger (Export your conversations data, checked 6 September 2026). For a team with a few thousand historical threads, running this in filtered batches by date range or tag is usually faster than writing an API script.
Export conversation metadata as CSV (Reports > Dataset export)
Go to Reports > Dataset export, pick one of the 13 reporting datasets, set a time range, optionally filter by attribute, choose your columns, preview, then Export CSV. Browser downloads cap at 10,000 rows; anything larger is emailed instead and can take up to an hour to arrive. Two documented gaps break migrations here. The CSV carries reporting metadata only — conversation IDs, timestamps, assignees, tags, status, response times — and never the message text. And user details such as name and email are not available as attributes at all, so the file cannot be joined to a person without a workaround (bulk-tag the conversations, filter by that tag in Contacts, export from there). Two permissions gate the page: Can access Chart drill-in and Can export CSV (Intercom teammate permissions, checked 6 August 2026).
Schedule recurring CSV exports
From the same Reports > Dataset export screen, build your dataset, columns, filters and preset time range, then open the Schedule dropdown and select New schedule to have the file delivered on a recurring frequency. One constraint catches people mid-migration: an existing schedule only lets you edit its name and frequency. Changing which columns or filters it exports means building a new schedule and cancelling the old one from Manage schedules. Data is retained for roughly two years for both CSV and JSON exports, so a schedule is a rolling feed rather than an archive — it will not backfill anything older than that window. Every dataset attribute available to a schedule is listed in Intercom's reporting metrics and attributes reference.
Pull full transcripts with the Conversations API
The Conversations API is the only route that returns complete transcripts programmatically. List conversations to collect their IDs, then issue a GET on each ID to retrieve its parts. Intercom's export endpoint accepts a maximum 90-day window per request but sets no volume cap inside that window, so a two-year archive is roughly eight sequential passes. Rate limits are not plan-based, which is the single most common misconception about this route: every app gets 10,000 API calls per minute, a workspace is capped at 25,000 per minute across all installed apps, and the allowance is spread evenly into 10-second buckets (Intercom REST API rate limiting, checked 6 August 2026). Read X-RateLimit-Remaining and back off on it rather than guessing a sleep interval.
Export contacts, users and companies as CSV
Open Contacts, select the users you want, click More, then Export users, and choose whether to ship the currently displayed columns or all columns. The file arrives by email and the download link expires one hour later, so start it when someone is at a keyboard. It covers names, email addresses, phone numbers, custom attributes and tags — but only the name and ID of the most recent company each user was tracked with, and no other company data (Intercom's user export article, checked 6 September 2026). There is no separate GDPR packaging tool, despite it being widely described as one: Intercom's own GDPR data-portability article routes you back to these same CSV, REST API and cloud-storage exports.
What changed in Intercom's exports in 2026?
Three changes since mid-2026 alter the order you should run these in. Teammate records and teammate activity logs became exportable data objects on the cloud-storage feed at the end of August 2026, and they carry no historical backfill — whatever you do not switch on today is unrecoverable without an Intercom Support request. Intercom also put the old conversation data export on a deprecation notice whose stated window has already elapsed, and the replacement renamed some attributes, so a schedule built on the old export has to be rebuilt rather than remapped. And the Conversations dataset gained two attributes, Has user reply and First contacted by, that make it far easier to work out how much of your archive is worth carrying over.
New: teammate and activity-log exports (switch these on first)
The cloud-storage export now has a Data objects section with three checkboxes: Conversations, Teammates, and Teammate activity logs. Teammates writes a full roster snapshot every run to <folder>/admins/; activity logs write only new activity since the previous run to <folder>/admin_activity_logs/, covering logins, permission changes and SSO changes. The detail that decides your sequencing: there is no two-year backfill for teammate data. It starts at the next scheduled run, and filling an earlier gap means asking Intercom Support to run a historical export for you. You need both the Manage teammates and See all teammates and team details permissions or the checkboxes are not offered at all, and the objects are unavailable on Snowflake Data Share destinations (Export teammate and activity log data to cloud storage, checked 6 September 2026).
The old conversation data export is condemned, not yet gone
Intercom's export article, timestamped 1 July 2026, states that the old conversation data export "will be deprecated in the next 60 days" and that the legacy version stays reachable from a banner at the top of Reports > Dataset export until then. That 60 days ran out at the end of August. Re-reading the article on 6 September 2026, the sentence is unchanged and no replacement date has been published, so plan around a removal that could land any week. The part that costs real work is that the replacement is not a drop-in: attribute names differ between the two exports, and the old "Inbound/Outbound" is "Started by" in the new one. Any schedule, dashboard or downstream script keyed on the old column names gets rebuilt (Export your conversations data, checked 6 September 2026).
Two new Conversations attributes worth exporting
The Conversations dataset gained Has user reply (did the customer ever answer, Yes or No) and First contacted by (Customer, Teammate, Fin AI Agent, or Workflow), both available as filters and as columns. Neither is cosmetic when you are deciding what to carry into a new platform. Filtering on First contacted by = Fin AI Agent sizes how much of your archive is bot-originated, and Has user reply = No isolates the outbound threads that inflate every volume number you are about to quote a new vendor.
Which Intercom export method should you use?
Pick the Intercom export method by what you need the data for, not by which one sounds most complete. Reporting and analytics want the CSV dataset export. A compliance archive of what was actually said wants the Conversations API or a bulk Inbox transcript download. A structured warehouse feed wants cloud storage. A single customer dispute wants one PDF. The mismatch that costs teams the most is assuming the cloud-storage export contains the conversation text — it does not.
| Your goal | Use this method | What you get / what's missing |
|---|---|---|
| Reporting, SLA analysis, volume trends | Reports > Dataset export (CSV) | All metadata and metrics. No message text, no customer name or email. |
| Compliance archive of what was said | Conversations API | Full transcripts including parts. 90-day window per request; needs a script. |
| Readable archive without writing code | Bulk Inbox export (text or PDF) | Readable transcripts, one file each. 200–300 conversations per operation. |
| One conversation for a dispute or escalation | Three-dots > Export as PDF | Single shareable file. Internal notes excluded on conversations. |
| Warehouse or BI feed, ongoing | Cloud storage export (S3 / GCS / Azure) | Structured JSON or JSONL, hourly or daily, plus attachments. No transcript. |
| Customer list for a new platform | Contacts > Export users (CSV) | Names, emails, phones, attributes, tags. Only the most recent company. |
| Access review or audit evidence | Cloud storage: Teammates + activity log objects | Full roster snapshot per run, activity deltas. No historical backfill. |
| Automation config for rebuild reference | Workflows / Macros / Articles APIs | JSON definitions. Product Tours and Fin training have no export. |
Most migrations need three of these, not one: the CSV for reporting continuity, a transcript route for the archive, and the Contacts CSV to seed the new platform's customer records. Budget for running all three rather than hunting for a route that does everything.
What does an Intercom export quietly get wrong?
Four documented behaviours make an Intercom export disagree with what you see on screen, and all four are cheaper to handle before you pull the file than after. Contact details in a conversation export are frozen at the moment the conversation opened, outbound threads the customer never answered are counted as conversations, company-level filtering does not exist in the Conversations Search API, and stopped or deleted in-app messages still appear in the file. All four are stated in Intercom's own Export your conversations data article, checked 6 September 2026.
- Contact data is a snapshot, not a lookup. Intercom captures user details at the start of the conversation, so the export reflects the email address, plan and custom attributes as they were then. A customer who changed address last year appears in your archive under the old one. When the export is seeding a new platform's contact records, treat the Contacts CSV as the source of truth for identity and the conversation export as history only.
- Outbound conversations with no reply are in the count. The dataset export includes every conversation whose Conversation created at timestamp falls in the range, outbound messages the customer never answered included. A row count therefore overstates real inbound support load, which matters when you are sizing seats on the platform you are moving to. The new Has user reply filter is the cheap correction.
- You cannot filter conversations by company. The Conversations Search API does not support
company_id. Pulling one account's threads is a two-hop: retrieve every contact for the company, then search conversations bycontact_ids. B2B teams modelling support cost per account repeat that on every extract. - Stopped and deleted in-app messages still export. In-app messages surface only once delivered, but messages you deleted or stopped are included in the file. Filter them on the way in rather than explaining them to someone six months later.
How do you export Intercom conversations to JSON?
Intercom produces JSON two ways, and the two files do not contain the same thing. The Conversations REST API returns JSON that includes the full transcript. The scheduled cloud-storage export writes JSON or JSONL to Amazon S3, Google Cloud Storage or Azure Blob Storage — and Intercom explicitly documents that this data does not contain a transcript. Choose the wrong one and you end up with a two-year archive containing every field except the words your customers wrote.
JSON from the Conversations API (contains the transcript)
Call the list-conversations endpoint to page through IDs, then GET each conversation by ID. The response is a JSON object per conversation containing its conversation parts — every reply, every note, with author, type and timestamp. This is the shape you want if the destination is anything that stores message history. Practical notes from running it: paginate on the cursor rather than on offsets, persist each conversation to disk as you go so a 429 does not cost you the run, and remember the 90-day ceiling applies to the export endpoint's timeframe parameter, not to how many conversations come back inside it. Contact name and email are not on the conversation object — join them from the Contacts CSV on contact ID.
JSON or JSONL to S3, GCS or Azure Blob (no transcript)
Go to Settings > Data > Imports & exports > Export data and select New data export. You choose the data API version, the output format (JSON or JSONL — both are offered, it is not JSONL-only), whether to include conversation-part attachments, and the destination bucket. Azure Blob Storage joined S3 and Google Cloud Storage as a destination in Intercom's December 2025 documentation update. The critical caveat, in Intercom's own words: conversation and ticket data exported this way will not contain a transcript — you have to use the UI export or the REST API for that (Export conversations data to cloud storage, checked 6 September 2026). Choose JSONL over JSON when the destination is a warehouse: one conversation per line, 200 per file, loads straight through Redshift's COPY … FORMAT AS JSON, BigQuery's newline-delimited JSON loader or Snowflake's COPY INTO, where a single JSON array has to be split first. Intercom also offers a Snowflake Data Share destination, though the teammate and activity-log objects are not available on it.
What the cloud-storage export actually writes
Setup takes an email confirmation step: Intercom sends a verification message you must click before the first export starts. Historical mode backfills up to two years; Periodic mode then runs hourly or daily, and each periodic file contains the entire conversation object rather than a delta. Files are named in ISO time format from the batch start and end (for example 2025-01-01T00-00-00Z-2025-01-02T00-00-00Z-19.jsonl), capped at 200 conversations per file, and optionally organised into date-named folders. Attachments land at folder/attachments/conversation_id/part_id/name and are referenced from the JSON. Two options on the setup screen are worth getting right first time, because most of the configuration becomes read-only afterwards — only Data API version, Output format and Attachments stay editable, and changing anything else means deleting the export and recreating it. Export data dated folders nests files under 2026-09-06/-style folders, and Skip empty exports when no data has changed suppresses runs with nothing in them. Clicking Test writes intercom-data-export-test-file.json to the bucket root, which proves the IAM policy works before you spend a day waiting on a two-year backfill. Intercom can write to your bucket but cannot read or delete from it, and one bucket cannot receive two workspaces. Deleting the export config leaves already-written files in place.
What can't you export from Intercom?
Three things people expect to export from Intercom genuinely cannot be exported: Product Tours, Fin AI training and guidance, and Messenger customisation. Three more that older migration checklists list as unexportable now have documented API routes — Workflows, Macros and Help Center articles. And one constraint applies to all of it: an Intercom export cannot be re-imported into a new Intercom workspace.
Now exportable via API: Workflows, Macros, Help Center articles
Guides written before 2026 tell you to screenshot your automation config. Three of those items no longer need it. Workflows have a dedicated export endpoint, GET /export/workflows/{id}, added for EU Data Act compliance, which returns the complete definition including steps, targeting rules, embedded rules and attributes — one workflow per call, so list your workflow IDs first. Macros are listable through GET /macros with cursor pagination, and the API helpfully rewrites Intercom's {{user.name | fallback: 'there'}} placeholder syntax into a standard XML-like form, which makes mapping to a new platform's variable format far less manual. Help Center articles come out of GET /articles, newest-updated first, with version-history endpoints if you need prior revisions (Intercom REST API reference v2.16, checked 6 August 2026).
Still no export at all: Product Tours, Fin training, Messenger settings
Product Tour sequences, Checklists, Fin AI guidance and its trained content configuration, Custom Bot branching logic, and Messenger appearance and targeting settings have no documented export endpoint and no UI download. These have to be captured by hand before you cancel. The cheapest reliable method is a screen recording per item rather than screenshots — a Product Tour is a sequence of steps with conditions, and a still image loses the branching. For Fin, record which content sources are enabled, which audiences each is scoped to, and your guidance text, because that configuration is the accumulated tuning work, not the model. Note your installed marketplace apps and their settings at the same time.
Export is not import: the two-year wall and the re-import ban
Two hard limits shape what an Intercom export can ever be worth. First, data is retained for roughly two years for both CSV and JSON exports — anything older is already gone, so an export run today cannot recover a conversation from three years ago no matter which method you use. Second, Intercom states plainly that exported conversation data cannot be re-imported into a new Intercom workspace. That rules out the "export, spin up a fresh workspace, import" pattern people assume is available, and it means your export's only realistic destinations are cold storage, a warehouse, or a different vendor's platform. Treat the export as an archive, not as a portable copy of your helpdesk.
How do you move exported Intercom data into monday.com or another tool?
There is no native Intercom-to-monday.com export path. Intercom emits CSV, JSON, JSONL and text or PDF files; monday.com imports .xlsx, .xls and .csv, so the CSV route is the one that works — but what lands is the ticket ledger, not the conversations. The same shape applies to any destination that ingests a spreadsheet: Airtable, Notion, Sheets, a CRM. Plan for a two-file join rather than a single clean import.
The CSV route into monday.com and its limits
Export the Conversations dataset from Reports > Dataset export, then import it in monday.com via Import Data for a new board, or the arrow next to New item > Import items for an existing one. monday.com's documented limits are the ones that bite: a file may carry up to 100 columns and 8,000 rows, but importing to a new board only brings across the first 50 columns; the sheet needs at least two columns; dates must be ISO-formatted (2026-08-06); only the first tab of a multi-tab workbook imports; and a column with more than 40 unique labels fails the import outright (monday.com import documentation, checked 6 August 2026). Split exports by quarter to stay under the row cap.
Getting the actual conversations across, not just the metadata
The Intercom CSV has no message text and no customer name or email, so a straight import gives you rows of IDs and timestamps that nobody can read. Two fixes, depending on effort. The low-effort one: run the Contacts CSV export as a second file and join it to the dataset export in a spreadsheet before importing, which at least restores who each row belongs to. The higher-effort one: pull transcripts from the Conversations API, flatten each conversation into a single text column (author, timestamp, body per line), and add that column to the CSV before import — monday.com will accept it as a Text column. If you only need the archive readable rather than queryable, skip both and keep the bulk PDF export as a folder alongside the board.
Opening the export in Excel or Google Sheets
Two Intercom behaviours decide whether the file reaches your spreadsheet at all. Anything over 10,000 rows is never downloaded in the browser — it is emailed instead, and can take up to an hour — and the Contacts CSV is always emailed, with a link that expires one hour later. Start both when someone is at a keyboard. Once the file is open, what corrupts an Intercom CSV is the import default rather than anything Intercom did: conversation and contact IDs are long integers that a double-click import converts to scientific notation and rounds, and non-Latin customer names need the file read as UTF-8. Import through Data > From Text/CSV in Excel or File > Import in Sheets, and set the ID columns to Text before the first parse. Re-typing the column afterwards does not bring the lost digits back.
What order should you run Intercom exports in?
Run the Intercom exports in dependency order, and start the slow ones first. The sequence that avoids rework: kick off cloud storage, then pull transcripts via API or bulk Inbox export, then take the CSVs, then capture the config that has no export, and only cancel your subscription once every file has been opened and spot-checked. The failure this prevents is the common one — discovering after cancellation that the CSV had no message text and the S3 archive had no transcript.
- Start the cloud-storage export first, with every data object ticked. Tick Conversations, Teammates and Teammate activity logs before you press start: conversations backfill up to two years, but teammate data only begins at the next scheduled run, so a day's delay is a day of audit history you cannot get back without a Support request. The export needs an email confirmation click and then runs unattended, so starting it on day one means it is finished by the time you need it.
- Pull transcripts while that runs. Bulk Inbox export in 200-conversation batches if you want readable files without code; the Conversations API in 90-day windows if you need structured JSON. This is the step that actually preserves what your customers said.
- Take the CSVs. Conversations and Tickets datasets from Reports > Dataset export for reporting continuity, plus Contacts > Export users for the customer list. Download the emailed contact file within the hour before its link expires.
- Export the config that has an API. Workflows, Macros and Help Center articles, so you have their definitions as reference when rebuilding.
- Record the config that has none. Screen-record Product Tours and Checklists, write down Fin guidance and content scoping, note Messenger settings and installed marketplace apps.
- Set up and connect the destination platform. Create the account, invite the team, connect channels, and rebuild automations from your exported definitions. Converge is $49/month flat rate for up to 15 agents with WhatsApp, Telegram, Messenger, Instagram, Discord and Zalo included, which is where messaging-first teams tend to land coming off per-seat pricing.
- Run both platforms in parallel for one to two weeks. New conversations route to the destination; open Intercom threads get finished in Intercom.
- Open every export file before you cancel. Confirm the transcripts contain messages, the contact CSV contains emails, and the cloud-storage bucket contains files. Only then decommission Intercom — retention is roughly two years and the export cannot be re-imported, so a gap found later cannot be filled.
The full cutover sequence, including channel reconnection and team training, is in the complete Intercom migration guide. If Intercom's per-seat plus per-outcome pricing is what triggered the move, the Intercom pricing breakdown has the current seat and Fin figures.
Frequently Asked Questions
You cannot export everything in one action — Intercom has no single "export all" button, and each of its five routes is missing something the others carry. To cover the whole account you run several: Reports > Dataset export for conversation and ticket metadata as CSV (10,000 rows per browser download, larger files emailed), the Conversations REST API or a bulk Inbox transcript download for the actual message content, Contacts > Export users for your customer list, and Settings > Data > Imports & exports > Export data for a scheduled JSON or JSONL feed to Amazon S3, Google Cloud Storage or Azure Blob Storage. Two limits shape all of it: data is retained for roughly two years, and exported conversation data cannot be re-imported into a new Intercom workspace (Intercom help centre, checked 6 August 2026).
No. Intercom's CSV dataset export contains reporting metadata only — conversation IDs, timestamps, assignees, tags, status and response-time metrics — and never the text of the messages. Intercom's own documentation states that conversation and message content is not included and points you to the Conversations API or the Amazon S3 export for transcripts. A second gap catches people out: user details such as name and email are not available as CSV attributes either, so the export cannot be joined to a person without a workaround (bulk-tag the conversations, filter by that tag in Contacts, then export from there). If you need a readable record of what was said, use the Conversations API or a bulk Inbox export as text or PDF instead.
Two routes produce JSON, and they contain different things. The Conversations REST API returns JSON that includes the full transcript — list conversations to get their IDs, then GET each ID to retrieve its conversation parts. The cloud-storage export at Settings > Data > Imports & exports > Export data writes JSON or JSONL to Amazon S3, Google Cloud Storage or Azure Blob Storage on an hourly or daily schedule, with a historical backfill of up to two years, files capped at 200 conversations each, and optional attachment export. Intercom documents that this cloud-storage data does not contain a transcript. So use the API when you need the words, and cloud storage when you need a structured warehouse feed (checked 6 August 2026).
Yes, and this changed recently enough that most third-party guides still say otherwise. From the Inbox, filter to the conversations you want, tick their checkboxes or use the select-all control, open ... (More actions) in the bulk-actions bar, type "export", and choose Export as text or Export as PDF. Each conversation downloads as its own file. Intercom caps this at 200–300 conversations per operation and directs you to the Conversations API above that volume. For a few thousand historical threads, running batches filtered by date range or tag is usually quicker than writing a script. Note that internal notes are excluded from conversation transcript exports; ticket exports can include notes, but only in the .txt format, never the PDF.
Intercom's REST API rate limits are not tied to your plan, which is the most common misconception about bulk exports. Every app — private or public — gets 10,000 API calls per minute, and a workspace is capped at 25,000 calls per minute across all installed apps. The allowance is spread evenly into 10-second windows rather than released as one per-minute burst, so sustained throughput matters more than peak. Exceeding it returns HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers; read X-RateLimit-Remaining and back off on it rather than guessing a sleep interval. Separately, the export endpoint accepts a maximum 90-day timeframe per request, with no volume restriction inside that window (Intercom developer docs, checked 6 August 2026).
Yes, and the announced window has already lapsed without a replacement date. Intercom's "Export your conversations data" article, timestamped 1 July 2026, states that the old conversation data export "will be deprecated in the next 60 days" and that you can still reach it from a banner at the top of Reports > Dataset export until then. Those 60 days ended at the end of August 2026; re-reading the article on 6 September 2026, the sentence is unchanged and no firm removal date has been published. Treat the legacy export as condemned and rebuild on the new Dataset export now. The migration is not a rename-and-go: attribute names differ between the two, so the old export's "Inbound/Outbound" is "Started by" in the new one, and any scheduled export, dashboard or script keyed on the old column names has to be rebuilt rather than remapped. If you have a live schedule on the old export, that schedule is the thing most likely to fail silently.
Yes, since the end of August 2026, but only through the cloud-storage export and only going forward. Your scheduled export at Settings > Data > Imports & exports > Export data now has a Data objects section with three checkboxes — Conversations, Teammates, and Teammate activity logs. Teammates writes a full roster snapshot (name, email, role) every run to a <folder>/admins/ subfolder; activity logs write only new activity since the last run to <folder>/admin_activity_logs/, covering logins, permission changes and SSO changes. Three constraints matter: there is no two-year historical backfill for teammate data, so it starts at the next scheduled run and an earlier gap has to be filled by Intercom Support; you need both the Manage teammates and See all teammates and team details permissions or the checkboxes never appear; and the objects are not available on Snowflake Data Share destinations. Activity performed by someone who has since left your workspace is exported without an actor ID or IP address (Intercom help centre, checked 6 September 2026).
Product Tours, Checklists, Fin AI guidance and its trained content configuration, Custom Bot branching logic, and Messenger appearance and targeting settings have no export route at all — capture them by hand before cancelling, ideally as screen recordings rather than screenshots so branching logic survives. Three items that older migration checklists list as unexportable now do have API routes: Workflows via GET /export/workflows/{id} (added for EU Data Act compliance, returning steps, targeting and embedded rules), Macros via GET /macros, and Help Center articles via GET /articles. The Macros API also rewrites Intercom's placeholder syntax into a standard XML-like form, which makes remapping variables to a new platform considerably less manual.
There is no native Intercom-to-monday.com path, so the route is a CSV handoff. Export the Conversations dataset from Reports > Dataset export, then in monday.com use Import Data for a new board or New item > Import items for an existing one. monday.com accepts .xlsx, .xls and .csv, up to 100 columns and 8,000 rows — though a new board only imports the first 50 columns — and requires ISO-formatted dates, at least two columns, and no more than 40 unique labels in any column being mapped to a Status column. The catch is content, not format: the Intercom CSV carries no message text and no customer name or email, so join the Contacts CSV to it first, or flatten API-pulled transcripts into a text column before importing (monday.com import docs, checked 6 August 2026).
Keep reading
See our breakdown of Intercom's pricing model for more.
Ready to try Converge?
$49/month flat. Up to 15 agents. 7-day free trial, no credit card required.
Start Free Trial