Intercom → Help Scout
Import Intercom conversations into Help Scout with Import2 after users and inboxes exist. Snoozed conversations do not stay snoozed, and Help Scout's own docs say chat volume can drop because Beacon only chats when someone is available.
Should you make this move?
Both platforms have a case. Compare what you gain with what you give up before scheduling the cutover.
Intercom
- Messenger, inbox, automation, help center, and customer context create a strong conversational support experience
- Tickets, customer context, knowledge, automation, and service reporting share one operating system
- Seat and usage pricing, proprietary conversations, and automation complexity raise switching costs
- Conversation visibility, routing logic, SLAs, and reporting history are hard to reproduce exactly
Help Scout
- Shared inboxes, Docs, and Beacon keep email support and self-service in one desk
- Tickets, customer context, knowledge, automation, and service reporting share one operating system
- Import2 skips users, workflows, and the knowledge base, and a full archive leaves through the API
- Conversation visibility, routing logic, SLAs, and reporting history are hard to reproduce exactly
Help Scout: Shared inboxes, Docs, and Beacon keep email support and self-service in one desk. This removes a major source-side concern: Seat and usage pricing, proprietary conversations, and automation complexity raise switching costs.
What you lose: Messenger, inbox, automation, help center, and customer context create a strong conversational support experience. What you inherit: Import2 skips users, workflows, and the knowledge base, and a full archive leaves through the API.
Jump to a section
Know the shape of the move.
This timeline assumes
- An Account Owner or Admin on Standard, Plus, or Pro starts Import2 inside Help Scout. Intercom is on the provider list. Users and inboxes exist before the sample.
- You accept Help Scout's product difference on chat. They say people can start a Beacon chat only when someone is available. Otherwise Beacon asks for an email.
- Snoozed Intercom conversations will not import as snoozed. You will snooze again in Help Scout if you still need that.
- The site already documents Intercom → Zendesk and Intercom → Freshdesk if you are comparing desks.
What survives the move.
“Partial” and “manual” are not footnotes. They are work that must be scheduled and verified.
| Item | Outcome | Impact | What happens | Mitigation |
|---|---|---|---|---|
| Chat availability | partial | high | Help Scout says Intercom lets a customer start a conversation whether or not someone is available. Beacon starts a chat only when someone is available, and otherwise asks the customer to email. Help Scout says it is not uncommon to see up to a 50 percent reduction in conversations and chats after a switch. That figure is their statement about the product difference, not a result measured on your account. | Tell the team before cutover. Turn Beacon more toward contact if you want more messages than the default. |
| Snooze | lost | high | Help Scout says both products snooze, and an Intercom snooze does not import. The conversation comes in without that snoozed status. You snooze it again in Help Scout and pick the time it should return to Active. | Export or list snoozed conversations before the full import and snooze them again after. |
| Statuses | partial | medium | Intercom has Open and Closed. Help Scout adds Pending, for work where you are waiting and not ready to close. The switching guide says Open elsewhere becomes Active, and Resolved elsewhere becomes Closed. | Expect Open to land as Active and Closed to land as Closed. Use Pending only for new work. |
| Tags on people and messages | partial | medium | Help Scout says Intercom tags People and Messages, while Help Scout tags Conversations. Tags and labels that the import brings across become Tags on those conversations. | Check a tagged person and a tagged message in the sample. Recreate anything that did not land on the conversation. |
| Star priority | manual | low | Help Scout says it has no star priority. A custom field is the replacement they name. | Create the field before the sample if you hope to map it. The general import article says custom fields are not included, so confirm the mapping screen. |
| Users, inboxes, and rules | manual | critical | Import2 does not bring users, inbox settings, saved replies, or rules. Create users and inboxes before the sample. Recreate replies and workflows after. | Copy the reply text out of Intercom first. |
| Help center | manual | high | The import tool does not import knowledge base articles. Help Scout points at the Docs API for a custom transfer. The older article importer they mention is for Zendesk, not for Intercom. | Plan Docs as a separate project if you need the articles. |
| Workspaces versus inboxes | partial | medium | Help Scout says one inbox has an email address, and you can alias several addresses onto it. Intercom would often use a separate workspace for another brand or team. | Decide which Intercom workspaces become inboxes and which become aliases before you map mailboxes. |
| Messenger identify data | manual | medium | Help Scout says Beacon identify can log custom fields such as role or plan, and Secure Mode is what saves those details and shows previous conversations. Intercom sidebar data does not move because you installed Beacon. | Re-implement identify and Secure Mode in the app. Test with one known user. |
| Import price and live edits | manual | high | Imports of 500,000 records or fewer are free when started inside Help Scout. Larger imports are billed at $500 per 500,000 records, including the first block. Help Scout's example is $1,000 for 1 million. During the full import, stop working in Intercom and avoid working in Help Scout until it finishes. Switch forwarding first so new conversations are not stranded. | Count records, switch sources, then start the full migration on a quiet day. |
Where each thing goes.
| Source | Destination | Method | Notes |
|---|---|---|---|
| Intercom conversation | Help Scout conversation | automatic | Import2 from Settings, Import Data. |
| Open | Active | transform | Help Scout's switching guide. |
| Closed | Closed | transform | Pending is new. It is not an Intercom status. |
| Snoozed | Unsnoozed conversation | manual | Snooze again after import. |
| Tag on a conversation | Tag | automatic | People and message tags may not have a conversation to sit on. |
| User | Help Scout user | manual | Create users before the sample. |
| Workspace | Inbox or alias | manual | Several addresses can share one inbox. |
| Saved reply | Saved Reply | manual | Not imported. |
| Article | Docs | manual | Not part of Import2. Docs API if you build it. |
Make the move recoverable.
Create the source-of-truth backup
Keep a list of snoozed conversations and the reply text you must recreate.
- List snoozed conversations and when they should wake.
- Copy saved replies out of Intercom.
- List workspaces, addresses, and the Messenger install.
- Leave Intercom readable until the sample is accepted.
Proof to capture: The snooze list, the reply archive, and the address map are stored outside Intercom.
Sample, then snooze list
See what Import2 actually maps before you rely on it.
- Create users and inboxes.
- Start the sample from Settings, Import Data, and choose Intercom.
- Check an open conversation, a closed one, and a tagged one.
- Compare the snooze list with Help Scout. Snooze again after the full import.
Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.
Beacon instead of Messenger
Replace identify data and set the chat expectation.
- Install Beacon where Messenger ran.
- Call identify for the fields you still need, with Secure Mode on.
- Decide whether chat should stay available-only.
- Send one test as a known user and as a logged-out visitor.
Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.
The things most likely to hurt.
These are operating limits. Treat every “Stop if” condition as a blocked migration, not a suggestion.
Snoozes are forgotten
The full import finishes and nobody re-snoozes.
- Consequence
- Waiting conversations sit Active, or they never come back on the date you promised.
- Mitigation
- Keep the snooze list and apply it after import.
Stop if: You have snoozed work and no list of it.
The 50 percent line is treated as your forecast
Staffing is cut because Help Scout mentioned a reduction.
- Consequence
- That sentence is their general claim. Your volume can differ.
- Mitigation
- Measure your own first week. Do not staff from their sentence.
Stop if: A schedule change depends on that 50 percent figure.
Messenger is removed before Beacon works
The widget is swapped and identify is not tested.
- Consequence
- Agents lose the sidebar context, and customers lose the contact path.
- Mitigation
- Test Beacon with Secure Mode before you remove Messenger.
Stop if: A known user does not show the fields you need.
Do the work in this order.
- Days 1 to 3 · inventory
Workspaces, snoozes, and replies
4 to 8 hours active2 to 3 days elapsedExports you can get from Intercom waiting- List workspaces and addresses.
- List snoozed conversations.
- Copy saved replies.
Depends on: Help Scout admin and Intercom admin
Stop / go checkpointSample?
Go when: Users and inboxes exist and the snooze list is saved.
Stop when: You cannot name the conversations that are snoozed.
- Days 3 to 4 · backup
Keep Intercom readable
1 to 3 hours active1 day elapsedNone waiting- Confirm you can still open Intercom history.
- Store the reply text.
Depends on: Inventory
Stop / go checkpointIs the archive enough?
Go when: Replies and snoozes exist outside Intercom.
Stop when: A day-one reply exists only in Intercom.
- Days 4 to 8 · pilot
Sample import and Beacon
4 to 8 hours active2 to 4 days elapsedImport2 waiting- Run the sample.
- Check statuses and tags.
- Test Beacon identify.
Depends on: Users and inboxes
Stop / go checkpointFull import?
Go when: Open and closed samples look right, and a test user shows Beacon fields.
Stop when: Secure Mode is off and previous conversations are part of the test.
- Days 8 to 10 · cutover
Forwarding and full import
2 to 4 hours active1 to 2 days elapsedFull migration waiting- Switch addresses.
- Start the full import.
- Pause Intercom edits.
- Re-snooze from the list when it finishes.
Depends on: Passed sample
Stop / go checkpointRemove Messenger?
Go when: New mail is in Help Scout and the snooze list is applied.
Stop when: Snoozed work is still only a list.
- Days 10 to 17 · observe
A week of volume
3 to 5 hours active5 to 7 days elapsedLive traffic waiting- Count conversations against the previous week.
- Watch chat-available hours.
- Keep Intercom readable.
Depends on: Cutover
Stop / go checkpointClose Intercom replies?
Go when: You can explain the volume change from your own counts.
Stop when: Customers have no email path when chat is offline.
Cut over with a way back.
Cutover
Receive new Intercom-bound messages in Help Scout, with snoozes reapplied and Beacon tested.
- Finish the sample and the Beacon test.
- Switch forwarding and other sources.
- Start the full import and stop Intercom edits.
- When it finishes, snooze the conversations on your list.
- Remove Messenger only after a known user sees the right sidebar.
Proof to capture: A new message is in Help Scout, snoozed items have a Help Scout snooze, and Beacon identify works for a test user.
Rollback
Put Messenger and mail back on Intercom if Help Scout is not ready.
- Point addresses back at Intercom.
- Turn Messenger back on if you removed it.
- Export Help Scout replies that are not in Intercom.
- Review those replies before you paste them into Intercom.
- Keep the snooze list. The import will not have preserved it.
Proof to capture: New messages arrive in Intercom, and Help Scout-only replies are listed.
- Snoozed work has no list
- Beacon identify fails for a known user
- Mail still arrives in Intercom after the switch
- A tag you needed did not land on the conversation
- The team is staffing from the 50 percent sentence
Prove the migration worked.
Every blocking check must pass. Capture the evidence before cleanup begins.
| Pass | ID | Check | Method | Expected result | Evidence |
|---|---|---|---|---|---|
V-01Blocking | Import Data | Confirm Owner or Admin on Standard, Plus, or Pro. | Intercom is selectable. | Import screen. | |
V-02Blocking | Users and inboxes | Compare Intercom teammates and workspaces with Help Scout. | Users exist, and each workspace has an inbox or an alias decision. | Inbox list. | |
V-03Blocking | Open and closed | Open one of each in the sample. | Active and Closed. Pending is unused unless you set it. | Sample. | |
V-04Blocking | List versus Help Scout | Search the snooze list after import. | Each one is snoozed again or explicitly dropped. | Snooze list. | |
V-05 | Conversation tags | Open a tagged sample. | The tag is on the conversation, or you have recreated it. | Conversation. | |
V-06Blocking | identify | Load the app as a known user with Secure Mode on. | The fields you send appear, and previous conversations show for that user. | Test notes. | |
V-07Blocking | New message | Send to the public address after the forward change. | It arrives in Help Scout. | Test email. | |
V-08 | Your counts | Compare a week of Help Scout conversations with the previous Intercom week. | You have your own numbers. The 50 percent line is not the report. | Weekly count. |
Remove the scaffolding safely.
Safe after: New mail is in Help Scout, snoozes are reapplied, and Beacon works for a test user.
- Remove Messenger after that test.
- Rebuild saved replies and workflows from the copy you saved.
- Keep Intercom readable until rollback closes.
- Store the snooze list with the Import2 email.
- Leave Docs as a separate project if articles did not move.
- Review chat-available hours after the first week.
When the plan met reality.
First-hand accounts are preferred. Vendor case studies are labeled, and every note below is an editorial paraphrase—follow the link for the full context.
This is a Help Desk Migration case study, so it is a vendor account of their own project. Rood Fluweel, a Belgian software company founded in 2012 with 1 to 10 people, moved from Intercom to Help Scout. The page lists tickets, contacts, agents, groups, and companies as the data migrated. Damiaan Peeters, named as an Umbarco and .Net developer at Umbrace, says the migration had no hiccups and was faster than they expected. He says the vendor used the API and reached conversations further back than Intercom's front-end export, which he describes as limited in the data set and limited to two years. That two-year line is his description, not an Intercom policy page. They had looked at the market for almost six months and delayed because they could lose history. He did not want two systems running for months. His tip is to plan where new data arrives while the migration is in progress. The page does not show a clear publication date.
- Plan where new conversations arrive during the import. Damiaan calls that out because history and live mail move at the same time.
- If a front-end export stops at a date, say so as the exporter's limit. Do not upgrade one customer's two-year remark into a current Intercom rule.
- The reason they waited was the risk of losing long-running conversations, and the API path is what they say recovered older history.
- The published result is a completed vendor migration of tickets, contacts, agents, groups, and companies, described as faster than they expected.
Verify against the primary material.
Platform behavior changes. Check these sources and the review dates above before executing a production migration.
- Help Scout: move from IntercomAccessed 2026-11-04
- Help Scout: import emails or ticketsAccessed 2026-11-04
- Help Scout: switching help desksAccessed 2026-11-04