The Complete Guide to Migrating from Intercom to Help Scout

Switching from Intercom to Help Scout is a significant step for any support team.

You are moving from a platform focused on customer engagement and messenger-style interactions to a platform, which excels at shared inbox management and structured support.

While Intercom and Help Scout share many similarities, their underlying data structures differ in ways that require careful attention during a migration.

This guide walks you through the steps to ensure your customer history, knowledge base, and team data are safely migrated to your new helpdesk.

Define your migration scope

The first step is identifying exactly what fits into the migration pipeline. Based on the API capabilities of both platforms, your migration will fall into three distinct buckets.

• Migrated via API: The vast majority of your data can be moved programmatically.

This includes your Knowledge Base, which consists of Articles and Collections. It also covers your core customer data, specifically Companies, Contacts, and Visitors.

Finally, your communication history. Conversations, Messages, Notes, and Tickets, along with their associated Tags and Data Attributes, are all eligible for API migration.

• Configured Manually: Not everything has a direct API equivalent for creation.

Your team members, referred to as Admins or Teammates in Intercom, must be set up manually in Help Scout.

Intercom Segments cannot be migrated directly via API and will need to be rebuilt using Help Scout's workflow or search features.

• Does Not Migrate: Several Intercom features have no equivalent in Help Scout and are out of scope for any migration. This includes Intercom Bots, Custom Actions, Product Tours, Outbound Messages, Series, and Banners. Plan to rebuild any critical workflows these features support using Help Scout's native tools.

Here is a canonical mapping of every migratable object:

Pre-migration checklist

Before you move a single byte of customer data, walk through this checklist:

• Create a Help Scout user account for every Intercom Admin/Teammate who has history in the source system. The Help Scout API does not support a "Create User" endpoint, so this must be done manually through the Help Scout UI.
• Record the Help Scout User ID for each agent — you will need these when assigning migrated conversations.
• Create all Custom Fields in Help Scout that correspond to your Intercom Data Attributes.
• Set up your Help Scout Mailbox(es) and Docs Site(s).
• Back up your Intercom data using Intercom's CSV export as a validation reference and fallback.
• Document which Intercom Segments, Workflows, and Bots you rely on so you can plan to rebuild them post-migration.
• Decide how to handle conversation status mapping: Intercom's open/closed/snoozed states need to map to Help Scout's active/closed/pending states.

If you skip the user creation step, you will be unable to assign migrated conversations to the correct agent, losing the historical context of who said what.

Migrate objects

This is the core of the operation. To maintain data integrity, you must follow a specific logical sequence. You cannot import a conversation for a customer who does not exist, and you cannot add an article to a category that has not been created.

1. The Knowledge Base: Start with your self-service content. Intercom organizes this into Collections and Sections.

You should map these to Help Scout's Sites, Collections, and Categories using the Docs API.

Once the structure is built, you can migrate your Articles into their respective collections. Pay attention to inline images and file attachments within articles — these often reference Intercom-hosted URLs that may break after migration. Re-host media assets to a stable location before or during the migration.

2. People and Companies: Next, you need to establish the entities you support.

Begin by migrating Intercom Companies to Help Scout Organizations. Once the organizations are established, migrate your Contacts and Visitors.

These will become Customers in Help Scout. It is vital to link these Customers to their corresponding Organization ID during creation to maintain the relationship.

During this step, you should also map your Intercom Data Attributes to Help Scout Custom Fields to ensure you don't lose key customer details.

Handle duplicate contacts during this phase. If the same email address exists multiple times in Intercom, decide on a merge strategy before importing — Help Scout will reject duplicate customer creation attempts.

3. Conversations and Tickets: With your users and customers in place, you can move the communication history. Intercom distinguishes between Conversations and Tickets, but Help Scout models everything as a Conversation (with types like email, chat, and phone that affect thread behavior).

• Conversations: Migrate these directly using the Create Conversation functionality. Map Intercom conversation states (open, closed, snoozed) to Help Scout's equivalent statuses (active, closed, pending).

• Tickets: Since Help Scout does not have a separate Ticket object, you must migrate these as Conversations. The best approach is to apply a specific Tag (like "Ticket") or a Custom Field to these entries so you can easily identify them later.

• Attachments: File attachments on conversations need separate handling. Extract attachment URLs from Intercom, download the files, and re-upload them as part of the Help Scout thread creation. Don't assume Intercom-hosted attachment URLs will remain accessible after you leave the platform.

4. Message History and Notes: For every conversation created, you must populate the history. Intercom Messages (the actual back-and-forth) should be migrated as Threads within the Help Scout conversation. You can differentiate these as replies or chat threads.

Similarly, Intercom Notes (internal comments) map perfectly to Help Scout Notes, allowing you to preserve private team context.

5. Tags: Finally, ensure that Tags from Intercom are applied to the newly created conversations and customers in Help Scout.

This preserves your categorization and helps with organization post-migration.

Post-migration validation

Once the data transfer is complete, validate the results before going live:

• Spot-check a sample of conversations across different agents, date ranges, and tags to confirm threads, notes, and attachments migrated correctly.
• Verify customer-to-organization links are intact.
• Confirm Custom Field values transferred accurately by comparing against your Intercom CSV export.
• Check that your Knowledge Base articles render correctly — look for broken images, malformed HTML, and missing formatting.
• Validate conversation counts: total conversations in Intercom vs. total conversations in Help Scout.
• Confirm conversation status mapping: verify that closed conversations didn't reopen and active ones didn't close.

Post-migration configuration

With validated data in place, rebuild the logic that powers your support operations. The primary focus here is Segments.

Intercom uses Segments to group people based on criteria. Help Scout does not have a direct "Create Segment" API endpoint.

To replicate this, you will need to manually set up Workflows or "Saved Searches" in Help Scout. You can configure these workflows to tag customers or conversations automatically based on the data you just imported, effectively recreating the logic you had in Intercom.

Also audit any third-party integrations that were connected to Intercom (CRM syncs, analytics tools, Slack notifications) and reconfigure them to point at Help Scout.

Insider secrets

Having mapped these objects out, there are a few technical nuances that can make or break your migration experience.

Respect the Speed Limit: The Help Scout Docs API has strict rate limiting that varies by your account setup. If you write a migration script that blasts the API as fast as possible, you will hit a 429 error code very quickly. Implement exponential backoff in your script — start with a short delay on 429 responses and increase it with each retry, capping at a sensible maximum. This is more reliable than a fixed sleep interval.

The Correlation ID: If things go wrong, and in complex migrations, they sometimes do. The API provides a Correlation-Id in the header of every response. If you receive an error and need to contact Help Scout support, having this specific ID allows their developers to trace the exact interaction. Log these IDs in your migration database so you have a trail if a specific batch fails.

Order is Everything: You might be tempted to run imports in parallel to save time. Do not do this. If you try to create a conversation before the customer exists, or attach a thread to a conversation that hasn't finished creating, the API will reject it. Stick rigidly to the order.

Plan for Partial Failures: In any large migration, some records will fail — malformed HTML in articles, encoding issues in message bodies, or intermittent API errors. Build your migration script to be idempotent: track which records have been successfully created so you can re-run the script without creating duplicates. Store a mapping of Intercom IDs to Help Scout IDs as you go.

Quick recap

Migrating from Intercom to Help Scout is a structured process of moving data from one container to another.

By understanding that Intercom's Tickets become Help Scout Conversations, that Users must be created manually before you begin, and that certain features like Bots and Product Tours simply don't migrate, you avoid the most common pitfalls.

Follow the sequence, respect the API limits, validate your results, and you will find your data ready and waiting for you in your new help desk.

If you'd rather focus on your revenue instead of wrestling with mapping sheets and pagination loops, ClonePartner can handle the full migration for you. Every migration is assigned a dedicated engineer who understands the nuances of both APIs and ensures zero downtime.

Further Reading:

• Help Scout Mailbox API Documentation
• Help Scout Docs API Documentation
• Intercom API Reference
• Help Scout Knowledge Base
• Intercom Data Export Guide