Migrate from HubSpot to Intercom

MIGRATION OVERVIEW

Why teams migrate from HubSpot to Intercom

The core problem

Migrating from HubSpot to Intercom presents a fundamental architectural mismatch: HubSpot is a relational CRM where Contacts, Companies, Deals, and Tickets exist as associated objects within a deep object graph, while Intercom is a messenger-first communication platform where Conversations and Contacts are the primary entities. There is no native, point-and-click migration path between the two platforms, and attempting a direct field-level export/import will result in broken conversation threading, misaligned ticket statuses, and lost historical context. HubSpot constructs like Deals, multi-level Engagement objects, and relational Custom Objects have no direct Intercom equivalents and require substantial transformation logic — including object flattening, chronological sequencing of engagement records, and pre-creation of Intercom data structures — before any data can be imported. Custom development work is required to map HubSpot pipelines to Intercom Ticket Types, sequence Engagements into Conversation Parts, and handle entities like Deals that must be either discarded, flattened into Contact attributes, or mapped to Intercom Custom Objects.

Why this matters for your migration

KEY CHALLENGES

What makes this migration complex

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

Most Critical

Deal Object Has No Equivalent

HubSpot Deals have no native counterpart in Intercom and must be either mapped to Intercom Custom Objects via API, flattened into Contact-level attributes, or retained in HubSpot as a separate system of record, each option requiring deliberate architectural decisions before migration begins.

Blocks all downstream imports if mapped wrong

Engagement Threading Into Conversations

HubSpot stores activities — Emails, Notes, Calls, Tasks, and Meetings — as discrete Engagement objects that must be chronologically sorted and sequenced into Intercom Conversation Parts or Contact Notes, a multi-step transformation process with a high error rate due to ordering failures and missing associations.

Ticket Pipeline and Stage Remapping

HubSpot Ticket pipelines and stages do not map directly to Intercom's Ticket Types and Ticket States, requiring a pre-migration configuration step where Ticket Types are created in Intercom and each HubSpot stage is explicitly mapped to an Intercom state such as submitted, in_progress, waiting_on_customer, or resolved.

Custom Object Schema Incompatibility

HubSpot Custom Objects support full associations, pipelines, and nested sub-objects, whereas Intercom Custom Objects are API-populated, single-level structures with no support for nested objects or multi-level associations, requiring a complete schema redesign rather than a direct port.

Contact Role Classification Required

Intercom distinguishes between Users and Leads at the contact level, requiring each HubSpot Contact to be classified by its Lifecycle Stage before import — a transformation step that, if skipped, will result in incorrect role assignments and corrupted segmentation in Intercom.

Knowledge Base SEO Continuity Risk

HubSpot Knowledge Base articles use a different URL structure than Intercom's Help Center, meaning all article URLs change post-migration and 301 redirects must be explicitly mapped and implemented to prevent search ranking loss and broken Fin AI content references.

MIGRATION RISK ASSESSMENT

Every migration risk, already solved

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

High complexity

Conversations (Engagements)

HubSpot Engagements — Emails, Notes, Calls, Meetings, and Tasks — must be chronologically sequenced and individually mapped to Intercom Conversation Parts or Contact Notes, making this the highest-error-rate step in the migration due to ordering logic, missing associations, and attachment handling failures.

Solved
Deals

HubSpot Deals have no native Intercom equivalent and require a deliberate pre-migration decision to either map to Intercom Custom Objects via API, flatten key fields into Contact attributes, or retain the data outside Intercom entirely, with no option preserving full pipeline and association fidelity.

Solved
Custom Objects

HubSpot Custom Objects with nested sub-objects, pipelines, or multi-level associations cannot be ported directly into Intercom's single-level Custom Object schema and require a full schema redesign, object flattening, and API-based population through Intercom's Data Connectors.

Solved
Tasks

HubSpot Tasks have no equivalent object in Intercom and must either be discarded or rebuilt manually in an external project management tool, meaning task-based workflow history cannot be preserved within the Intercom platform post-migration.

Solved

Custom engineering

Tickets

HubSpot Tickets require a pre-migration configuration step to create matching Ticket Types and Ticket States in Intercom, and each pipeline-to-type and stage-to-state mapping must be explicitly defined before any ticket records are transferred.

Handled
Custom Fields (Data Attributes)

Custom properties from HubSpot Contacts and Companies must be manually pre-created as Data Attributes in Intercom before any records are imported, and any attribute not created in advance will cause import failures or silent data loss.

Handled
Knowledge Base Articles

HubSpot Knowledge Base articles can be mapped to Intercom Help Center Articles with matching collection and section structures, but unsupported HTML tags must be stripped, URL slugs change and require 301 redirects, and incomplete migration directly degrades Fin AI resolution quality.

Handled
Agent and Owner Assignments

HubSpot owner IDs referenced on Tickets and Engagements do not carry over to Intercom and require a pre-built mapping table that translates each HubSpot owner ID to the corresponding Intercom admin ID before ticket and conversation assignment data can be accurately transferred.

Handled

Clean transfer

Contacts

HubSpot Contacts map directly to Intercom Contacts with well-defined field equivalents, though lifecycle stage classification into User or Lead roles and pre-creation of custom attributes as Data Attributes in Intercom are required before import.

Clean
Companies

HubSpot Companies map to Intercom Companies with most native fields having direct equivalents, though the import order matters — Companies must be created before Contacts and associations established afterward, or Companies may not appear in the Intercom UI.

Clean

What Our Customers Say

Real migration stories

Direct Review

“One of the easiest migrations I've ever been through. The team took care of everything — all our data, customer interactions and macros. The process was clear, straightforward and we felt supported all the way. An absolutely seamless experience for our support team and our customers.”

Direct Review

“Fantastic at both guiding us through the process and helping us fix things as they come up and dial them in.”

Reviewed on G2

“The ease of the process and that ClonePartner was informing me what was going on at every step. If you're on the fence, do it. ClonePartner are great!”

Direct Review

“They were SO helpful. We had a few hiccups because our migration was in the middle of the process, but they were really flexible and did multiple delta migrations for us. We were able to map a lot of our old ticket data so it's usable for comparisons in the future.”

Direct Review

“Overall a great experience. We had to go back a few times to get everything just right, which was totally expected. The transition was smooth, and there was no data loss.”

See all customer stories →

CUSTOM MIGRATION

Fully customizable engineer-led migration

Tailor your migration from HubSpot to Intercom 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 HubSpot to Intercom 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 Intercom, 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 HubSpot to Intercom isn't just about moving data – it's about protecting your content and search visibility.

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 content support
Adaptable to API changes	✓ Proactive adaptation	✗ No	⚠ Manual fixes	⚠ Slower response
Turnaround / publish predictability	✓ Predictable publish timelines	⚠ 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 HubSpot and Intercom 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 article history, media, and author metadata
Syncing custom fields, categories, and tags 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 HubSpot data and Intercom
Zero downtime during staged cutovers
99.9% attachment integrity (verified via checksum)
Full automation and preservation of all business rules

Our standard: Includes full SEO and category-structure 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 HubSpot or Intercom exactly the same way—with unique content structures and data. We customize every migration script to fit your exact workflow, categories, and tags.

Our engineers adapt for:

Custom fields, categories, and workflows
Multi-brand or multi-language setups
Historical imports and partial (date-based) migrations
Integration re-mapping for search, 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 HubSpot to Intercom. Can't find what you're looking for? Talk to our team.

Can I migrate HubSpot tickets to Intercom using a CSV?

No. Intercom's CSV import covers Users and Leads only — not Companies, Conversations, or Tickets. You must use the Intercom REST API to migrate historical support data, creating each record individually since there is no bulk import endpoint.

Can I migrate HubSpot Deals to Intercom?

Not 1:1. Intercom has no native Deal/Opportunity object. You can map operationally useful deal data to Intercom Custom Objects or Ticket attributes, flatten key data into Contact custom attributes, or keep Deals in HubSpot CRM and use Intercom only for support.

Does Intercom have a bulk import API?

No. Intercom does not offer a bulk create or update endpoint for Contacts, Companies, or Tickets. Every record requires a separate API call. For large migrations, request elevated rate limits from Intercom support before starting.

How long does a HubSpot to Intercom migration take?

A small migration (<10K contacts, no custom objects) can be completed in 1–3 days. Enterprise migrations with 100K+ records, custom objects, and relationship rebuilding typically take 2–4 weeks including validation and testing.

Will I lose HubSpot property change history when migrating to Intercom?

Yes. HubSpot tracks property change history on records. Intercom does not have an equivalent feature. You migrate the current state of each record only. If you need historical data, export and archive it separately before migration.

How long does the HubSpot to Intercom 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 HubSpot 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 HubSpot to Intercom?

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 HubSpot→Intercom migration.

Contact our team

Ready to start your
Intercom 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 HubSpot to Intercom with precision & ease

Why teams migrate from HubSpot to Intercom