Intercom to Salesforce Data Migration
Consolidating customer data into Salesforce? Settle automates the mapping between Intercom's conversation-centric model and Salesforce's Case and Account architecture — preserving conversation history, user attributes, and company data.
Working with enterprise teams on active migration programs
Days
to production-ready mappings
Roughly half
the cost of consulting-led delivery
Every row
validated before go-live
Enterprise migrations routinely run months behind schedule. Yours doesn't have to.
This guide is for VPs of IT, data architects, and migration leads at companies moving data from Intercom to Salesforce — whether you're scoping, planning, or mid-program.
Intercom stores customer interactions as conversations with user profiles, company records, and custom attributes in a product-usage-aware model. Salesforce uses Cases, Contacts, and Accounts with a CRM-centric structure. Settle translates Intercom's product-led support model to Salesforce's enterprise service architecture — connecting conversations to Cases and enriching Account records with Intercom's product usage data.
Based on the founding team's enterprise migration experience
Last updated July 2026
How Settle automates your Intercom to Salesforce migration
Settle converts Intercom conversations into Salesforce Cases with full thread history — each conversation part becomes a Case Comment or EmailMessage with timestamps, author attribution, and internal/external visibility preserved.
Intercom users are matched to existing Salesforce Contacts by email — Settle enriches existing records with Intercom's product usage attributes and creates new Contacts only for users that don't have Salesforce records.
Custom attributes from Intercom (plan type, feature usage, last login, sign-up date) are mapped to Salesforce custom fields on Contact and Account — giving the sales and service teams product context they didn't have before.
Settle generates the complete conversation-to-Case mapping with tag-to-picklist translation, team-to-Queue routing, and admin-to-User assignment mapping.
Get your Intercom to Salesforce mapping analysis — see results in under an hour
Migration timeline: manual vs. Settle
Traditional approach
Timeline
2–4 months
Estimated cost
$75K–$250K
Team size
2–4 consultants
Typically requires
×Manual field mapping in spreadsheets
×Custom ABAP/SQL extraction scripts
×3–5 mock migration cycles
×Dedicated source system consultants
×Manual reconciliation testing
With Settle
Enterprise benchmarksTimeline
Days
Estimated cost
A fraction of consulting cost
Team size
1–2 internal resources
Included
✓Schema profiling & analysis
✓AI-generated field mappings
✓Transformation SQL
✓Validation & readiness reports
✓Production-ready load files
Common challenges migrating from Intercom to Salesforce
Conversation-centric to Case-centric translation
Intercom conversations are real-time chat threads with multiple participant messages, notes, and snooze/close states. Salesforce Cases are structured records with status, priority, and entitlement tracking. Each Intercom conversation becomes a Salesforce Case, but the conversation thread must map to Case Comments or EmailMessage records. Settle generates the Case creation with full conversation history preserved as an activity timeline.
Explore related migrations →User profiles to Contact/Account matching
Intercom users have product-specific attributes (plan type, sign-up date, last active, custom events) tied to company records. Salesforce Contacts need Account associations with different attribute patterns. If Salesforce already has CRM data, Intercom users must deduplicate against existing Contacts. Settle matches Intercom users to Salesforce Contacts by email and enriches Account records with Intercom's product data.
Explore related migrations →Custom attributes and events
Intercom tracks custom user attributes (plan_type, feature_usage, last_login) and custom events (subscription_created, feature_activated). These have no standard Salesforce equivalent but are valuable for sales and service teams. Settle maps custom attributes to Salesforce custom fields on Contact or Account and documents event data for potential custom object creation.
Explore related migrations →Chatbot and automation data
Intercom's chatbot flows, custom bots, and automation rules contain routing logic and response templates. These don't migrate to Salesforce — they need Salesforce Flows or Einstein Bot equivalents. Settle documents which conversation topics and routing rules the Intercom bots handle so the Salesforce team can rebuild coverage.
Explore related migrations →Intercom to Salesforce field mapping — what data moves
10 data objects typically migrated
| Source Object | → | Target Object |
|---|---|---|
| Conversation | → | Case |
| Conversation Part (message) | → | Case Comment / EmailMessage |
| User | → | Contact |
| Company | → | Account |
| Custom Attributes | → | Custom Fields on Contact/Account |
| Tags | → | Case fields / Picklists |
| Admin (agent) | → | User |
| Team | → | Queue |
| Help Center Article | → | Knowledge Article |
| Notes (internal) | → | Case Comment (internal) |
Typical enterprise migrations include 500K–10M+ records across these objects. Settle handles profiling and mapping at enterprise scale.
The cost of manual Intercom to Salesforce migration
Intercom to Salesforce migrations happen when product-led growth companies mature into enterprise sales motions. Intercom excels at in-app messaging, chatbot automation, and product-aware support for SaaS companies. But as these companies scale — adding enterprise sales teams, multi-product lines, and formal support SLAs — they need Salesforce's CRM breadth. This migration is common during Series B/C scaling, when support teams formalize SLAs and entitlements, or when the company needs Salesforce's ecosystem for CPQ, billing, or marketing automation.
The fundamental challenge is translating Intercom's conversation-centric, product-aware model to Salesforce's Case-centric, relationship-aware model. Intercom conversations are real-time chat threads tied to user profiles with product usage data (pages visited, features used, plan type). Salesforce Cases are structured service records tied to Contacts and Accounts with entitlements and milestone tracking. The models solve different problems — Intercom optimizes for speed, Salesforce optimizes for accountability.
Companies typically build a Salesforce-Intercom integration for ongoing sync but need a one-time historical migration. The conversation-to-Case translation, user-to-Contact matching, and product attribute mapping are the most manual parts.
Consulting-led delivery for migrations in this class typically runs $75K–$250K. Settle prices it fixed and scoped — read the full cost breakdown.
Frequently asked questions
Exceptions surface before the first load, not after the third.
Built by the team that ran Fortune 500 migrations by hand. Currently onboarding enterprise design partners on active migration programs.
Ready to migrate from Intercom to Salesforce?
Tell us about your migration and we'll show you how Settle can help.
No commitment required. We'll review your migration scope and share a preliminary assessment within 48 hours.