---
title: "Salesforce Service Cloud to Intercom Migration"
description: "Migrate Salesforce Service Cloud to Intercom with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/helpdesk/salesforce-service-cloud/to/intercom"
---

# Salesforce Service Cloud to Intercom migration

We migrate Cases, Contacts, Accounts, and engagement history from Salesforce Service Cloud into Intercom, transforming the case-centric schema into Intercom's conversation-first model with SLA translation, picklist value remapping, and milestone preservation handled before any record is written to the destination.

Short answer

FlitStack AI migrates conversations, conversation parts, users, leads and companies from Salesforce Service Cloud to Intercom, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-6 weeks.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/helpdesk/salesforce-service-cloud/to/intercom#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Salesforce Service Cloud ![](https://flitstack.ai/platforms-trim/salesforce-service-cloud.webp)

Destination Intercom ![](https://flitstack.ai/platforms-trim/intercom.webp)

Conversation Conversation Part User Lead Company

Mapped field by field · sample run · one-click rollback

## What moves from Salesforce Service Cloud to Intercom?

Moving from Salesforce Service Cloud to Intercom is a schema rethink, not a record copy.

Read the full summary

Service Cloud centers on the Case object with entitlements, milestones, case teams, and a picklist dependency tree; Intercom centers on Conversations threaded through Leads and Users attached to Companies. We extract Cases and their full object graph via Bulk API, split multi-record-type Cases into Intercom Conversations, translate picklist values against a value map built during scoping, and resolve Intercom User IDs from Salesforce Contact emails before linking any conversation. Entitlements and SLA milestone objects have no native Intercom equivalent — we carry these as custom attributes on the conversation record so supervisors retain visibility. We do not migrate Salesforce Flow workflows, entitlement processes, or Service Cloud reports; we deliver a written inventory of these for the customer's admin to rebuild in Intercom's operator rules and reporting suite.

1:1

### Case → Conversation

Salesforce Cases map to Intercom Conversations.

How it maps

Case Number becomes a custom 'Legacy Case ID' attribute on the Conversation for cross-reference. Case Status maps to Conversation State (open, closed, snoozed); case priority maps to a custom priority attribute. The Case Origin (Email, Phone, Chat, Web) determines the initial channel assignment in Intercom. If the destination has multiple Inboxes, we map Record Type to Inbox assignment during migration. Multi-record-type orgs require separate Conversation import batches per Record Type.

1:N

### Case Comment → Conversation Part

Case Comments — both public (IsPublished=true) and private (IsPublished=false) — map to Intercom Conversation Parts.

How it maps

Public comments become user-visible conversation parts; private comments are stored as internal notes in Intercom. We preserve the comment author (Salesforce Contact or User) mapped to an Intercom User or Teammate. Comment body and HTML formatting are sanitized and stored as part.body. The created date of each comment becomes the Conversation Part timestamp, preserving the chronological thread.

1:1

### EmailMessage → Conversation Part (email channel)

Salesforce Email Messages attached to a Case become Intercom Conversation Parts on the email channel.

How it maps

From, To, Cc, Subject, and HTML body migrate. Inline images require URL extraction and re-attachment as publicly accessible URLs per Intercom's image hosting requirement. Attachments migrate as file attachments on the Conversation Part. We detect inbound vs outbound on EmailMessage.Incoming and set the conversation part author accordingly (customer vs agent).

1:1

### Contact → User

Salesforce Contacts with cases attached map to Intercom Users.

How it maps

We resolve the Contact email as the dedupe key. Any Contact without an email address is held in a reconciliation queue and migrated as a User with an admin-generated placeholder address pending customer admin resolution. Custom contact fields migrate as custom attributes on the Intercom User. Contacts without cases migrate as Users only if specified in scope.

1:1

### Contact (unqualified / no case activity) → Lead

Salesforce Contacts that have never been associated with a Case map to Intercom Leads.

How it maps

This preserves the distinction between active support contacts and marketing-originated prospects without creating duplicate User records. We flag the original Contact ID as a custom attribute for future merge if the Lead becomes a User through a new conversation.

1:1

### Account → Company

Salesforce Accounts map to Intercom Companies.

How it maps

Account Name becomes Company name, and the Account's domain field maps to Company domain for workspace identification. We resolve all Contacts linked to the Account and attach them as contacts within the Company record. Account hierarchy (Parent Account) is not natively represented in Intercom; we store the parent account ID as a custom attribute if the hierarchy is material to the customer's operations.

******What moves 14 objects

Salesforce Service Cloud Intercom

- Case Conversation 1:1
- Case Comment Conversation Part transformed
- EmailMessage Conversation Part 1:1
- Contact User 1:1
- Contact Lead 1:1
- Account Company 1:1

\+ 8 more in the mapping below

## How Salesforce Service Cloud and Intercom differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension                     | Salesforce Service Cloud                                                                        | Intercom                                                                                                |
| ----------------------------- | ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Primary ticket object         | Case — a record-centric object with Status, Priority, Origin, Type, and Record Type             | Conversation — a message-thread object attached to a User or Lead, with a State (open, closed, snoozed) |
| SLA and entitlement tracking  | Entitlement and Milestone objects with breach timers, business hours, and supervisor dashboards | Service Level Agreement rules as a configuration; no milestone object or breach timer native equivalent |
| Contact model                 | Contact object attached to Account with a separate Lead object for unqualified prospects        | Single people object (Lead or User) with a role attribute, no separate Account-to-Contact hierarchy     |
| Channel routing               | Omnichannel routing across email, chat, phone, messaging, and social via Case Origin            | Inboxes with routing rules and team assignments; channels differentiated by source (email, chat, push)  |
| Workflow automation           | Salesforce Flow (record-triggered, scheduled, screen) with Apex triggers on Case events         | Operator rules and workflows scoped to conversation state, assignment, and team inbox rules             |
| Pricing model                 | Per-seat at $75-$500/user/month with storage overages, add-ons, and 8-10% annual uplift         | Seat-based or conversation-based plans from $39/seat/month; no storage overage charges                  |
| Picklist and dependency model | Dependent picklists enforcing Country/State/City hierarchies and Record Type field gating       | Flat custom attributes with no cross-field dependency enforcement                                       |

## What to watch for in a Salesforce Service Cloud to Intercom migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Entitlements and SLA milestones have no native Intercom equivalent

Salesforce Entitlement and Milestone objects enforce SLA compliance with breach timers, business hours, and supervisor alerts.

How we handle it

Intercom has SLA rules but no milestone tracking object. We store entitlement name, SLA terms, and milestone target dates as custom attributes on the Intercom Conversation and Company at migration time, which lets supervisors see the legacy SLA window. Customers must rebuild SLA escalation logic in Intercom's SLA rules using the migrated data as reference. If the customer relies on milestone breach notifications in Salesforce, those alerts do not transfer and the admin must configure equivalent Intercom operator rules post-migration.

high

### Dependent picklist values require explicit value translation tables

Salesforce enforces dependent picklists (e.g., a State picklist gated by a Country picklist) at the database level.

How we handle it

Intercom has flat custom attributes with no cross-field dependency enforcement. Before migrating any Case, Contact, or Account record with picklist fields, we generate a picklist value translation table mapping every Salesforce picklist value to an Intercom custom attribute option or free-text value. Naive imports that skip this step land records with mismatched country/state combinations or silently skip records with unrecognized picklist values. This step adds two to four days to the scoping phase depending on the number of dependent picklist fields.

medium

### Case Record Types split across Intercom Inboxes require separate batch loads

Salesforce orgs with multiple Case Record Types (e.g., Technical Support, Billing, Onboarding) often use separate page layouts and business processes per type.

How we handle it

Intercom uses Inboxes for channel segregation. When the destination has multiple Inboxes mapped to different Record Types, we run separate batch loads per Record Type to set the correct Inbox assignment at import time. Running a single bulk import across Record Types without Inbox routing logic causes all conversations to land in the default Inbox, requiring manual reassignment.

medium

### Salesforce Flow workflows and Apex triggers do not migrate to Intercom

Active Salesforce Flow workflows and Apex triggers respond to Case insert and update events.

How we handle it

A bulk import without disabling these can flood users with unwanted email notifications, create spurious follow-up tasks, or update entitlement fields based on Case status changes that Intercom cannot process. We include a Flow and trigger audit checklist in pre-migration planning, and we recommend deactivating trigger-based flows before production migration and re-enabling after validation. The rebuilt logic in Intercom's operator rules is out of scope and delivered as a written handoff document.

medium

### Knowledge Articles lack a native Salesforce-to-Intercom migration path

There is no out-of-the-box tool or native connector for moving Salesforce Knowledge Articles into Intercom's Help Center.

How we handle it

We use the Intercom REST API Articles endpoint in batches to create articles, which requires re-formatting article body HTML, re-hosting inline images with publicly accessible URLs, and mapping Salesforce article categories to Intercom Collections. This is a manual-heavy step that adds scope to migrations with large knowledge bases (over 500 articles). We include article count in scoping to surface this cost impact early.

## How the migration runs

1. ### Discovery and scoping

   We audit the source Salesforce org across edition tier, Case Record Types and business processes, active picklist dependencies, active Flow and trigger registrations, engagement volume (emails, case comments), entitlement and milestone count, and knowledge base article count.

   What this step covers

   We pair this with a review of the target Intercom workspace: inbox count, existing Teammate provisioning, custom attributes, and Help Center collections. The discovery output is a written migration scope document covering record counts per object, picklist translation table size, and a recommended ingestion batch strategy.

2. ### Picklist value mapping and schema design

   We build the picklist translation table from every Salesforce picklist field in scope, mapping each value to an Intercom custom attribute option or free-text equivalent.

   What this step covers

   We design the Intercom custom attributes and configure Inbox routing rules aligned to the Case Record Type mapping. We create the Help Center Collections in Intercom for Knowledge Article ingestion. All design is validated against the customer's Intercom workspace in a staging environment before production schema is finalized.

3. ### Bulk API extraction and sandbox migration

   We extract Salesforce data via Bulk API in batches split by Record Type and date range to respect API daily request limits.

   What this step covers

   Data is staged in a secure migration workspace. We run a sandbox migration into the customer's Intercom staging environment to validate mapping, verify conversation threading, spot-check custom attribute values, and confirm that Picklist translation is accurate. The customer reviews and signs off the sandbox migration before production migration begins.

4. ### Teammate and User provisioning reconciliation

   We extract every Salesforce User referenced as a Case owner or Case team member and match by email against the Intercom workspace's Teammate table.

   What this step covers

   Any Salesforce User without a matching Intercom Teammate is listed in a reconciliation report with the customer's Intercom admin responsible for provisioning before production migration. Migration cannot proceed past TeamMember resolution because Intercom conversation parts and assignments require valid Teammate IDs.

5. ### Production migration in dependency order

   We run production migration in this sequence: Companies (from Accounts), Users and Leads (from Contacts), then Conversations (from Cases) with case comments and email messages as related conversation parts, followed by Knowledge Articles and Solutions as Help Center articles.

   What this step covers

   Entitlement and milestone data loads as custom attributes on Conversations after the conversation records are created. Each phase emits a row-count reconciliation report. We pause writes to Salesforce Service Cloud during the production migration window to prevent record drift.

6. ### Cutover, validation, and automation handoff

   We run a final delta migration capturing any Cases or emails created or updated during the cutover window, then enable Intercom as the system of record.

   What this step covers

   We deliver a written inventory of every active Salesforce Flow and Apex trigger with its object, trigger event, conditions, and recommended Intercom operator rule equivalent. We do not rebuild workflows in Intercom; that work is a separate engagement. Reports and dashboards from Salesforce Analytics do not migrate; we recommend a BI connector or Intercom's native reporting suite as the replacement. We offer a one-week hypercare window for reconciliation issues raised during initial agent use.

![](https://flitstack.ai/platforms/salesforce-service-cloud.svg) Salesforce Service Cloud ![](https://flitstack.ai/platforms/intercom.svg) Intercom

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Intercom Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**4-6 weeks** Typical, smaller accounts

**10-14 weeks** Large or heavily customised accounts

A quote scales with record volume, picklist complexity, custom object count, and the number of Case Record Types requiring individual conversation mapping. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Salesforce Service Cloud to Intercom →](https://flitstack.ai/contact)

## Why teams move from Salesforce Service Cloud to Intercom

- Service Cloud total cost of ownership远超 sticker price. License costs at $75-$500/seat/month compound with Agentforce conversation charges ($2/conversation), storage overages ($125/GB), and 8-10% annual contract uplifts, creating a 30-40% true-cost premium that surprises teams during renewal. Intercom's seat-based pricing at $39-$74/seat/month eliminates storage overage billing and offers more predictable cost scaling for growing support teams, which reviewers on Capterra and G2 cite as a primary driver for switching.
- Agentforce AI has underdelivered for mid-market support teams. Multiple Capterra reviews note that the AI implementation felt buggy, escalated too aggressively without agent context, and failed to reduce Tier-1 volume as marketed. Intercom's Fin AI agent has a higher reported satisfaction rate for automated resolution on routine queries, and its conversation-first design gives agents more control over escalation decisions.
- Self-service portals reduce agent workload in ways Service Cloud's implementation does not for SMB and mid-market teams. Capterra reviewers highlight that Salesforce's customer portal requires significant configuration and licensing overhead to deliver comparable self-service, while Intercom's Help Center and Article delivery is native to the product and agent-facing without added complexity.
- Agent adoption on Service Cloud is consistently low for non-power users. Reviewers cite the steep learning curve and unintuitive navigation as reasons support reps fall back on spreadsheets and shadow IT. Intercom's conversation inbox and chat-first interface reduces training time and increases agent adoption, which directly impacts first-response quality and customer satisfaction scores.
- Configuration overhead makes Service Cloud unsuitable for teams without dedicated Salesforce admins. Research.com and SoftwareAdvice comparison guides consistently note that most Salesforce Service Cloud alternatives offer simpler setup with minimal disruption, which is especially relevant for companies with fewer than 50 agents who cannot justify a full-time Salesforce administrator.

Questions, answered

## Salesforce Service Cloud to Intercom migration questions

How long does a Salesforce Service Cloud to Intercom migration take?

Migrations under 20,000 Cases, 10,000 Contacts, and a single Case Record Type with no complex picklist dependencies typically complete in four to six weeks. Migrations with multiple Case Record Types, large engagement histories (over 300,000 email and comment records), entitlement translation, and Knowledge Article migration of over 500 articles move to ten to fourteen weeks. The picklist translation table build adds two to four days to scoping before any data extraction begins.

Do Salesforce Flow workflows, entitlement processes, and SLA milestones migrate to Intercom?

No. Salesforce Flow workflows, Apex triggers, entitlement processes, and SLA milestone configurations are structurally incompatible with Intercom's operator rules and SLA configuration. We do not migrate them as code. We deliver a written inventory of every active Flow, trigger, and entitlement process with its object, trigger event, conditions, and recommended Intercom equivalent. Your admin or an Intercom implementation partner rebuilds these post-migration. SLA milestone data is carried as custom attributes on conversations at migration time so the SLA context is available for rebuild.

Can we keep Salesforce Sales Cloud while moving Service to Intercom?

Yes. A hybrid stack where Salesforce Sales Cloud handles the sales pipeline and Intercom handles customer support is a common pattern. Intercom offers a native two-way Salesforce integration that syncs Leads, Contacts, Accounts, and Cases between the platforms. If you choose this path, we configure the Intercom-Salesforce sync during migration so that new customer contacts from Intercom conversations flow into Salesforce and Salesforce Account updates sync back to Intercom Companies.

Do historical case comments, emails, and SLA milestone data transfer?

Yes. Case Comments (public and private) transfer as conversation parts, preserving the author, timestamp, and body. Email Messages transfer as conversation parts on the email channel with from, to, cc, subject, and HTML body intact. SLA milestone names, target dates, and breach status transfer as custom attributes on the Conversation. However, Intercom has no native milestone breach timer equivalent — the milestone data is available as reference for rebuilding SLA rules in Intercom, but the breach notification logic requires manual configuration post-migration.

What happens to Salesforce Knowledge Articles and Solutions?

Salesforce Knowledge Articles and Solutions migrate to Intercom Articles via the Intercom REST API. There is no native migration path, so this step requires re-formatting article HTML, re-hosting inline images with publicly accessible URLs, and mapping Salesforce article categories to Intercom Collections. Publishing states (Draft, Published, Archived) are preserved so archived source articles do not go live unintentionally. Migrations with large knowledge bases (over 500 articles) add two to four weeks to the timeline because of the manual formatting work.

What about Salesforce reports, dashboards, and analytics from Service Cloud?

Salesforce Analytics (Einstein Analytics / Tableau) reports and Service Cloud dashboards are built on a proprietary data model that does not export to Intercom's reporting format. We do not migrate them. We deliver a written report inventory listing every active Salesforce report and dashboard in scope, with a recommended mapping to Intercom's conversation reporting suite (conversation volume, first response time, CSAT, resolution time) and any gaps that require a third-party BI tool to fill.

How do you handle Salesforce API rate limits during extraction?

Salesforce Enterprise Edition limits are 100,000 API requests per 24-hour rolling window, shared with any active integrations. We audit API consumption during scoping and schedule bulk extraction passes during off-peak hours. Large-volume extractions (over 500,000 records) are split into date-range batches with staggered start times to avoid REQUEST\_LIMIT\_EXCEEDED failures mid-job. We use Bulk API rather than REST API for record extraction to maximize throughput within the daily limit. If Salesforce Starter or Professional editions are in scope with lower API limits, we adjust the batch size accordingly and extend the extraction window.

## Related migrations

[![](https://flitstack.ai/platforms-trim/intercom.webp) Migrate to **Intercom** Every source we move into Intercom, native options and the checklist. Guide, checklist & sources ](https://flitstack.ai/migrations/helpdesk/intercom) [**Jira Service Management to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/jira-service-management/to/intercom) [**Freshservice to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/freshservice/to/intercom) [**Kustomer to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/kustomer/to/intercom) [**Gorgias to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/gorgias/to/intercom) [**Freshdesk to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/freshdesk/to/intercom) [**Zendesk to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/zendesk/to/intercom) [**Salesforce Service Cloud to HubSpot Service Hub** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/salesforce-service-cloud/to/hubspot-service-hub) [**Salesforce Service Cloud to Freshdesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/salesforce-service-cloud/to/freshdesk)

## Sources: official documentation

1. [Import your user data into Intercom — Intercom Help](https://www.intercom.com/help/en/articles/177-import-your-user-data-into-intercom)
2. [Import your customers — Intercom Academy](https://academy.intercom.com/import-your-customers)
3. [Create and track Custom Data Attributes (CDAs) — Intercom Help](https://www.intercom.com/help/en/articles/179-create-and-track-custom-data-attributes-cdas)
4. [Events limits, troubleshooting and F.A.Q — Intercom Help](https://www.intercom.com/help/en/articles/5245634-event-limits-troubleshooting-and-f-a-q)
5. [Custom Field Attributes — Salesforce Help (External ID)](https://help.salesforce.com/s/articleView?id=platform.custom_field_attributes.htm)
6. [Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help](https://help.salesforce.com/s/articleView?id=000380434\&type=1)
7. [Sandboxes — Staging Environments for Customizing and Testing](https://help.salesforce.com/s/articleView?id=platform.deploy_sandboxes_parent.htm)

Get a quote

## Moving from Salesforce Service Cloud to Intercom?

Tell us roughly how many records and objects you have. We scope the mapping and the Intercom setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
