Migrate from Intercom to HubSpot Service Hub with precision & ease

A seamless, customizable migration solution for moving your Intercom data with perfect fidelity and minimal disruption.

Book free consultation
Intercom
HubSpot Service Hub
MIGRATION OVERVIEW

Why teams migrate from Intercom to HubSpot Service Hub

Migrating from Intercom to HubSpot Service Hub has no native migration path and requires significant custom work due to fundamental architectural differences between the two platforms. Intercom uses a messenger-first, conversation-centric model where interactions are stored as threaded Conversation Parts, while HubSpot organizes support around CRM-integrated Tickets with separate Engagement records (notes, emails) linked via the Associations API. Each Intercom Conversation must be decomposed into one HubSpot Ticket plus multiple Engagement records, flat tags must be translated into structured pipeline stages or custom properties, and Intercom's API cap of 500 conversation parts per thread introduces potential data truncation for long histories.
KEY CHALLENGES

What makes this migration complex

These are the architectural mismatches and technical hurdles specific to a Intercom to HubSpot Service Hub migration.

Most Critical

Conversation Parts Decomposition

Every Intercom Conversation must be split into one HubSpot Ticket plus N individual Engagement records (notes or emails), as HubSpot has no single threaded-conversation object equivalent.

Tags to Pipeline Mapping

Intercom's flat tag-based categorization has no automatic mapping to HubSpot's structured Ticket Pipelines, Stages, and custom properties, requiring manual translation of every tag.

Timestamp Format Mismatch

Intercom timestamps use Unix epoch in seconds while HubSpot expects milliseconds, and failing to convert causes silent date corruption that places records in January 1970.

Conversation History Truncation

Intercom's API returns only the 500 most recent conversation parts per conversation, requiring a fallback archival strategy for long-running threads.

Knowledge Base Rebuilding

HubSpot lacks a bulk API import for Knowledge Base articles, so Intercom Help Center content must be recreated via custom scripts with deep HTML cleaning to handle proprietary block elements.

Note Body Character Limits

HubSpot's note body field caps at 65,536 characters, so long Intercom conversation parts must be chunked across multiple note engagements to avoid silent data loss.

COMPLETE COVERAGE

Intelligent Human-Verified Data Mapping

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

Intercom
HubSpot Service Hub
Contacts (Users)
Contacts
Contacts (Leads)
Contacts
Companies
Companies
Conversations
Tickets
Conversation Parts
Engagements (Notes)
Tags
Properties (Fields)
Segments
Lists (Contact/Company)
Notes
Engagements (Notes)
Tickets
Tickets
Ticket Types
Ticket Pipelines
Conversation Attachments
Files (Attachments)
Subscription Types
Communication Preferences

Looking for more entity mappings?

Contact our team
MIGRATION RISK ASSESSMENT

Every migration risk, already solved

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

Migration Challenge ClonePartner Status
High Complexity —
Solved
Conversations (Tickets)
Decomposing each conversation into a ticket plus individual engagement records is complex, rate-limit-sensitive, and subject to the 500-part API cap that may truncate long threads.
Solved
Conversation Parts (Engagements)
Each message part must be created as a separate Note or Email engagement with correct timestamp conversion and association, and internal notes must be carefully mapped to prevent accidental customer exposure.
Solved
Knowledge Base Articles
No bulk import API exists for HubSpot Knowledge Base articles, Intercom's proprietary HTML blocks break in HubSpot's editor, and each article must be recreated via custom CMS API scripts.
Solved
Custom Engineering —
Handled
Tags
Tags have no native equivalent on HubSpot tickets and must be mapped to custom multi-select or single-select properties, requiring upfront property creation and value alignment.
Handled
Custom Attributes
Custom attributes require pre-creation of matching HubSpot properties with explicit type definitions, and any picklist value not in the predefined option list will be silently rejected.
Handled
Attachments
Files must be uploaded to HubSpot's File Manager individually (no multi-file requests), then linked to notes via attachment IDs, with async processing adding complexity.
Handled
CSAT Scores
Intercom's native CSAT ratings do not map to any standard HubSpot object and must be stored in a custom ticket property, losing native reporting integration.
Handled
Clean Transfer
Contacts
Contacts map well between platforms using email as the dedup key, though contacts without email addresses will create orphaned records requiring a skip-or-placeholder decision.
Clean
Companies
Companies can be matched on domain or company ID, and HubSpot supports Intercom's multi-company-per-contact model via Associations, though CSV exports only include the most recent company.
Clean
Admins / Teammates
Admins map to HubSpot Users by email, but all target users must be created and active before migration so historical tickets can be properly assigned.
Clean
3 high-complexity solved
4 custom-engineered
3 clean transfers
CUSTOM MIGRATION

Fully customizable engineer-led migration

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

Migration Filters

Conversation Type

Filter by chat, email, or social media conversations

Tag-Based Selection

Migrate tickets with specific tags only

User Selection

Migrate tickets for specific users or agents

Time Range

Migrate tickets from a specific time period

Data Types

Tickets & Conversations

Full conversation history with all metadata

Automations & Macros

Workflows, templates, and automation rules

Knowledge Base

Articles, categories, and help center content

Customer Profiles

Customer information and interaction history

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 HubSpot Service Hub 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

1

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.

2

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.

3

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.

4

Full Migration

2 days · ClonePartner

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

5

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.

Timeline is an estimate. Actual duration depends on API rate limits, data complexity, and your team's availability.

Get an exact timeline

Complete Technical Guide

How to Migrate Intercom to HubSpot Service Hub (2026 Guide)

Migrating Intercom to HubSpot Service Hub takes 3–8 weeks via API, not CSV. The biggest risks are broken inline images and multi-object association mapping.

24 min read

Read the guide

Pros and cons of different migration options

Choosing the right approach is key because migrating from Intercom to HubSpot Service Hub 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:

  1. Speed of automation for bulk record migration
  2. Precision of engineers verifying integrity and business logic
  3. Pilot migrations and sandbox testing to catch issues early
  4. 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 HubSpot Service Hub 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:

  1. Field mapping and transformation
  2. Pagination, rate-limit handling, and throttling
  3. Preserving conversation threads, attachments, and internal notes
  4. 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:

  1. 100% record-count parity between your Intercom data and HubSpot Service Hub
  2. Zero downtime during staged cutovers
  3. 99.9% attachment integrity (verified via checksum)
  4. 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 HubSpot Service Hub 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:

  1. Custom fields, ticket forms, and workflows
  2. Multi-brand or multi-language setups
  3. Historical imports and partial (date-based) migrations
  4. 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 HubSpot Service Hub. Can't find what you're looking for? Talk to our team.

How long does an Intercom to HubSpot Service Hub migration take?
A typical migration takes 3–8 weeks end-to-end, including scoping, field mapping, script development, test migration, and production run. The actual data transfer for 100K conversations takes 1–2 days of API processing time. Calendar time is driven by mapping decisions and validation, not data volume.
Can I migrate Intercom conversations to HubSpot without losing data?
Yes, but only via the API — not CSV imports. Native CSV imports cannot carry conversation content or multi-object associations. API-based migration preserves conversation parts as engagement records with timestamps and author attribution. Inline images require explicit download and re-hosting to avoid permanent breakage when Intercom is deactivated.
What data cannot be migrated from Intercom to HubSpot Service Hub?
Intercom Workflows, Fin AI configuration, Product Tours, Series, Messenger Apps, and behavioral events cannot be migrated programmatically. These must be manually rebuilt using HubSpot Workflows, Chatflows, and Breeze Customer Agent. Conversation ratings also have no direct equivalent and should be stored as custom properties.
Will my HubSpot Workflows fire during migration?
Yes. Any active Workflow with enrollment triggers like 'Ticket is created' or 'Contact property is updated' will fire on every migrated record, potentially sending thousands of unwanted emails. Always disable enrollment-based Workflows before starting the migration and re-enable them after validation.
Do I need HubSpot Enterprise to migrate from Intercom?
No. HubSpot Service Hub Professional is sufficient for most migrations. Enterprise is only required if you need Custom Objects (to map Intercom Custom Objects) or Custom Behavioral Events (to map Intercom Events). The ticket, contact, company, and engagement APIs are available on Professional and above.
How long does the Intercom to HubSpot Service Hub 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 HubSpot Service Hub?
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→HubSpot Service Hub migration.

Contact our team

Ready to start your
HubSpot Service Hub 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.