Migrate from Intercom to Salesforce Service Cloud

MIGRATION OVERVIEW

Why teams migrate from Intercom to Salesforce Service Cloud

There is no native migration path from Intercom to Salesforce Service Cloud. Intercom's native Salesforce app supports live sync of ongoing conversations as Tasks, but it is not designed to replay historical support data into Salesforce's Account → Contact → Case hierarchy. The fundamental challenge is that Intercom's flat, conversation-centric data model—where Users, Leads, and conversation_parts exist as loosely related streams—must be restructured into Salesforce's strict relational schema with parent-child relationships across Accounts, Contacts, Cases, and CaseComments. Custom ETL work is required to extract full transcripts via the Intercom REST API (CSV exports omit message content), transform timestamps and custom attributes to Salesforce's strict schema, handle character limits on CaseComment fields, and rebuild Fin AI configurations, bot flows, and Product Tours from scratch.

KEY CHALLENGES

What makes this migration complex

These are the architectural mismatches and technical hurdles specific to a Intercom to Salesforce Service Cloud migration.

Most Critical

Conversation Transcript Export Gap

Intercom's CSV and S3 dataset exports omit actual message content entirely, requiring per-conversation REST API calls to retrieve full transcripts—meaning 100,000 conversations need over 100,000 individual API requests.

Hierarchical Data Model Mismatch

Intercom's flat identity model with loosely attached Companies must be restructured into Salesforce's strict Account → Contact → Case hierarchy where every Case requires a Contact and every Contact should belong to an Account.

CaseComment Character Truncation

Salesforce's CaseComment.CommentBody field is capped at 4,000 characters and silently truncates longer content, risking data loss for lengthy Intercom conversation parts without explicit handling or use of EmailMessage objects.

Non-Migratable AI and Automation

Intercom Fin AI configurations, Product Tours, Checklists, custom bot flows, and Series automation sequences have no equivalent in Salesforce Service Cloud and must be entirely rebuilt using Einstein, Agentforce, or Flows.

Strict Schema and Picklist Validation

Intercom allows flexible custom attributes as free-form strings, booleans, and numbers, while Salesforce picklists reject any values not matching predefined options, requiring thorough data auditing and cleansing before load.

Audit Field and Timestamp Preservation

Preserving original created dates requires the 'Set Audit Fields upon Record Creation' permission (Enterprise+ only, enabled by Salesforce Support), and all Intercom Unix epoch timestamps must be explicitly converted to ISO 8601 format.

COMPLETE COVERAGE

Intelligent Human-Verified Data Mapping

Our migration engineer precisely maps every data point from Intercom to Salesforce Service Cloud, ensuring perfect continuity for your customer support operations.

Contacts (Users)

Contact

Contacts (Leads)

Contact

Companies

Account

Conversations

Case

Conversation Parts

CaseComment

Conversation Parts

EmailMessage

Conversation Parts

FeedItem

Every migration risk, already solved

Migration between platforms is full of edge cases. Our engineers have identified every risk from Intercom to Salesforce Service Cloud and built proven solutions for each one.

Migration Challenge ClonePartner Status

High Complexity —

Solved

Cases (Conversations)

Mapping Intercom's flat conversation stream to Salesforce's structured Case lifecycle requires preserving original timestamps via audit field permissions, and the API caps conversation_parts retrieval at 500 per conversation.

Solved

Conversation Transcripts

Full message content is unavailable from CSV or S3 exports and must be extracted via individual API calls, with CaseComment's 4,000-character limit silently truncating long conversation parts.

Solved

Attachments

Attachments must be individually downloaded from Intercom's CDN, uploaded as Salesforce ContentVersion records, and linked to parent Cases via ContentDocumentLink, adding significant processing time and storage considerations.

Solved

Custom Engineering —

Handled

Contacts (Users)

Intercom Users often lack a last name (required by Salesforce) and may have incomplete profiles, requiring data enrichment and deduplication by email before import.

Handled

Accounts (Companies)

Intercom Companies are loosely attached to Users without strict hierarchy, so matching to Salesforce Accounts by company_id or domain requires careful deduplication to prevent duplicates.

Handled

Custom Attributes / Fields

Intercom's flexible string/boolean/number attributes must be mapped to Salesforce's strict field types and picklist values, with any non-matching data causing insert failures.

Handled

Knowledge Base Articles

Help Center Articles must be migrated to Knowledge__kav with Salesforce Knowledge enabled, requiring rich text transformation and re-hosting of embedded images to Salesforce-accessible URLs.

Handled

Macros and Saved Replies

Intercom saved replies and multi-step macros have no automated migration path to Salesforce Quick Text or Macros and must be manually recreated or scripted via Metadata API.

Handled

Clean Transfer

Fully customizable engineer-led migration

Tailor your migration from Intercom to Salesforce Service Cloud exactly to your needs with our flexible customization options. Our experts will configure the perfect migration plan for your business.

Migration Filters

Data Types

ZERO DOWNTIME

Your timeline. Our engineers.

A dedicated engineer runs your migration, planned around your schedule and your data.

No babysitting a wizard. Avoid debugging errors yourself.

Looking for a more detailed migration timeline?

Contact our team

Speed

The migration timeline depends on both our turnaround time and yours.

We can complete a migration in under a day when the accounts are connected and the sample migration is approved promptly.

Background Sync

We also support migrating the newest records first, so you can go live faster while the rest of the data is synced in the background.

Data Volume Impact

Larger data volumes may require longer migration windows.

Continuous Operation

Weekend migrations minimize disruption to your customer service operations.

MIGRATION TIMELINE

Your Intercom to Salesforce Service Cloud migration, step by step

See how long your migration will take from start to finish. Drag the slider to estimate based on your data volume.

How many records are you migrating?

<10K 50K 100K 250K 500K 1M 2M 5M 10M+

Checklist ~3 days

Sample 1 day

Review ~2 days

Full 2 days

Delta 1 day

Your team ClonePartner

Estimated total

~9 business days

Migration Checklist

1 day · ClonePartner ~2 days · Your team

We prepare the optimal data mapping as a shareable spreadsheet. Your team reviews, approves, and adds any customizations.

Sample Migration

1 day · ClonePartner

We run a test migration with a representative sample of your data to verify mapping accuracy and identify any potential issues before the full run.

Review & Approve

~2 days · Your team

Your team reviews the sample migration results, confirms data accuracy and mapping, and gives the go-ahead for the full migration.

Full Migration

2 days · ClonePartner

We execute the complete migration of all your data to your new Salesforce Service Cloud, with real-time progress tracking and comprehensive logging.

Delta Migration

1 day · ClonePartner

We capture and transfer any new data that was added or updated during the main migration to ensure no data is lost. This final sync keeps everything current.

Pros and cons of different migration options

Choosing the right approach is key because migrating from Intercom to Salesforce Service Cloud isn't just about moving data – it's about protecting customer relationships.

Feature / Criteria	ClonePartner	Automated Tools	CSV Import	In-house migration
Custom Scripting for complex data	✓ Engineers build & maintain	✗ No	⚠ Manual	✓ Yes – but costly
Sandbox & Pilot Migrations	✓ Full sandbox + pilot plans	⚠ Limited	✗ No	⚠ Often Informal
Manual validation & reconciliation	✓ Automated + manual QA	✗ No	✓ Yes (Manual)	✓ Heavy manual effort
Backup & rollback plan	✓ Robust procedures	✗ No	✗ No	⚠ Often incomplete
Handles automation and integrations	✓ Full support	⚠ Partial	✗ No	⚠ Possible but fragmented
Post-migration engineer support	✓ Dedicated engineers	✗ No	✗ No	⚠ Limited SLA
Adaptable to API changes	✓ Proactive adaptation	✗ No	⚠ Manual fixes	⚠ Slower response
Turnaround / SLA predictability	✓ Predictable SLAs	⚠ Fast but brittle	⚠ Slow and manual	⚠ Often slower
Data Security & Compliance	✓ High – enterprise grade	⚠ Medium (depends)	⚠ Low (manual)	⚠ Hidden gaps common
Pricing predictability	✓ Transparent & fixed	⚠ Low (per-job)	⚠ Low (manual hours)	⚠ High/variable OPEX
End-to-end project management	✓ Full E2E delivery & PM	✗ No	✗ No	⚠ Often partial
Business impact & opportunity cost	✓ No diversion of staff	✗ No	✗ No	⚠ Diverts engineering

What does an Engineer-led migration mean anyway?

Speed & Accuracy: Our Blended Method

We blend automation (smart scripts, bulk APIs) with human expertise for speed without risk. Our engineers manually check every mapping, validation, and exception.

You get:

Speed of automation for bulk record migration
Precision of engineers verifying integrity and business logic
Pilot migrations and sandbox testing to catch issues early
Real-time validation reports and rollback readiness

Result: 50x faster migrations than manual imports — with near-zero error rates.

Handling the Tricky Tech and API Details

The Intercom and Salesforce Service Cloud APIs each behave differently, which is where our engineers shine. We build custom logic to handle the data quirks where generic tools typically break.

We handcraft API logic for:

Field mapping and transformation
Pagination, rate-limit handling, and throttling
Preserving conversation threads, attachments, and internal notes
Syncing custom fields, SLAs, and macros without breaking structure

Our scripts: Natively retry failed calls, re-queue large attachments, and ensure data parity.

No Guesswork

We don't just promise smooth migrations—we measure and prove them. Every client receives a Migration Validation Report with all metrics.

Typical results across projects:

100% record-count parity between your Intercom data and Salesforce Service Cloud
Zero downtime during staged cutovers
99.9% attachment integrity (verified via checksum)
Full automation and preservation of all business rules

Our standard: Includes full SLA preservation and 48 hours of engineer-assigned support post go-live.

We Adapt to Your Setup (Not the Other Way Around)

No two teams configure Intercom or Salesforce Service Cloud exactly the same way—with unique automations and data. We customize every migration script to fit your exact workflow, tags, and triggers.

Our engineers adapt for:

Custom fields, ticket forms, and workflows
Multi-brand or multi-language setups
Historical imports and partial (date-based) migrations
Integration re-mapping for CRMs, chat, or feedback tools

The promise: If your data doesn't fit a standard template, we build one just for you.

Enterprise-Grade Security & Compliance

Your customer data is precious. Our migration process maintains the highest standards of security and regulatory compliance.

SOC 2 Type II

Independently audited compliance with rigorous security standards

ISO 27001

Certified information security management system

GDPR

Full compliance with EU data protection regulations

HIPAA

Certified for handling protected health information

AES-256 Encryption

Bank-grade encryption for all stored credentials

Latest TLS

Secure transfer protocol for all data in transit

Role-Based Access

We follow role-based access control for every migration project

Scheduled Deletion

Automatic data purging after migration completion

FAQ

Frequently Asked Questions

Everything you need to know about migrating from Intercom to Salesforce Service Cloud. Can't find what you're looking for? Talk to our team.

Can Intercom conversation history be preserved in Salesforce Service Cloud?

Yes. Every Intercom conversation part — customer messages, agent replies, internal notes, and bot interactions — can be migrated to Salesforce as CaseComments or EmailMessages on the corresponding Case. The key constraint is the 4,000-character limit on CaseComment.CommentBody; use EmailMessage objects to preserve full HTML content and avoid truncation. Also plan explicit exceptions for threads longer than 500 conversation parts, since the Intercom API caps retrieval at 500.

How much does an Intercom to Salesforce Service Cloud migration cost?

Cost depends on volume and complexity. A managed migration for 10,000–50,000 conversations typically costs $5,000–$15,000. Enterprise migrations (100,000+ conversations with attachments and zero-downtime requirements) range from $15,000–$40,000. DIY costs 120–200 engineer-hours plus the opportunity cost of pulling developers off product work.

What data cannot be migrated from Intercom to Salesforce Service Cloud?

Intercom Fin AI training and configuration, Product Tours, Checklists, Series (automated sequences), custom bot flows, and Messenger styling cannot be migrated. These must be rebuilt natively in Salesforce using Einstein, Agentforce, or Flows. Conversation ratings can be migrated as custom fields but don't map to Salesforce's native CSAT mechanism.

Does the native Intercom Salesforce integration handle historical migration?

No. Intercom's native Salesforce app is designed for ongoing sync of new conversations, not bulk historical migration. It creates Cases or Tasks from active conversations going forward and does not back-fill historical conversation data into Salesforce.

Can I migrate Intercom to Salesforce Service Cloud without downtime?

Yes, with a delta sync strategy. Run the full historical migration while agents continue working in Intercom. Before cutover, run a final delta sync to capture conversations created or updated during the migration window. This ensures zero missed tickets and no agent downtime.

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

Most migrations complete within 1–5 business days, depending on data volume and complexity. We provide a detailed timeline after the initial assessment and can often complete small migrations in under 24 hours.

Will my team lose access to Intercom during the migration?

No. Your source system remains fully operational throughout the entire migration. We run the migration in the background with zero downtime to your current operations.

Will there be downtime when migrating from Intercom to Salesforce Service Cloud?

No. Our migration process is designed for zero downtime. We use a staged approach with background sync and a fast cutover, ensuring no disruption to your live business operations.

How do I validate that everything migrated correctly?

Every client receives a Migration Validation Report with comprehensive metrics including record-count parity, attachment integrity verification via checksum, and full audit logs. We also offer unlimited sample migrations so you can verify before committing.

Do I need professional help for this migration?

While simple migrations can sometimes be handled in-house, professional help ensures zero data loss, proper field mapping, and preservation of relationships between records. Our engineer-led approach catches edge cases that automated tools miss.

Does ClonePartner provide guidance before committing?

Yes. We provide a free consultation and assessment. We'll review your data structure, discuss your requirements, and provide a detailed migration plan and fixed-price quote before you commit to anything.

Still have questions?

Book a free 30-minute consultation with our migration engineers. We'll walk you through the exact approach for your Intercom→Salesforce Service Cloud migration.

Contact our team

Ready to start your
Salesforce Service Cloud Migration?

Join hundreds of businesses who have successfully migrated with ClonePartner. Let's discuss your migration needs and build a plan that works for you.

Book free consultation

Attention to Detail

We meticulously handle every aspect of your migration, ensuring no data is lost during transfer and mapping every field correctly between platforms.

Custom Solutions

Every business is unique. We tailor your migration strategy to match your specific requirements, workflows, and data structures.

Security & Compliance

Your customer data is handled with enterprise-grade security protocols, ensuring compliance with GDPR, HIPAA, and industry standards.

Migrate from Intercom to Salesforce Service Cloud with precision & ease

Why teams migrate from Intercom to Salesforce Service Cloud