Intercom to Salesforce Data Migration
Consolidating customer data into Salesforce? Mine 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
2–4 weeks
to production-ready mappings
40–50%
cost reduction vs. manual migration
90%+
average mapping confidence
Most enterprise migrations start 6+ 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. Mine 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 enterprise migration programs led by Mine's founding team
Last updated March 2026
How Mine automates your Intercom to Salesforce migration
Mine 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 — Mine 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.
Mine 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. Mine
Traditional approach
Timeline
2–4 months
Estimated cost
$80K–300K
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 Mine
Enterprise benchmarksTimeline
2–4 weeks
Team size
1–2 internal resources
Estimated cost
40–50% less
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. Mine 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. Mine 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. Mine 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. Mine 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. Mine handles profiling and mapping at any scale.
The cost of manual Intercom to Salesforce migration
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.
Frequently asked questions
In one enterprise migration, a single field mapping error in customer master data caused $100K in billing discrepancies that went undetected for 6 months.
Mine catches these issues before they reach production.
Built by a team that led SAP, Oracle, and Salesforce data migration programs for Fortune 500 companies at a Big 4 consulting firm. Currently in design partnership with enterprise clients running active migration programs.
Ready to migrate from Intercom to Salesforce?
Tell us about your migration and we'll show you how Mine can help.
No commitment required. We'll review your migration scope and share a preliminary assessment within 48 hours.
You'll receive a preliminary mapping analysis showing how your source objects map to your target schema, with confidence scores and flagged risk areas.