Migrate from HubSpot Service Hub to Intercom

MIGRATION OVERVIEW

Why teams migrate from HubSpot Service Hub to Intercom

There is no native migration path from HubSpot Service Hub to Intercom. The two platforms differ fundamentally: HubSpot uses a CRM-integrated service model where tickets are separate containers linked to engagements via an Associations API (requiring 3–5 API calls per ticket to reconstruct a thread), while Intercom uses a messenger-first conversation parts model with no dedicated bulk import API for conversations. Custom API-based extraction, engagement-to-conversation-part transformation, property pruning, and routing logic (Conversations vs. Intercom Tickets) are all required, making this one of the most technically demanding helpdesk migration paths available.

KEY CHALLENGES

What makes this migration complex

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

Most Critical

Multi-Endpoint Ticket Extraction

Reconstructing a complete HubSpot ticket thread requires 3–5 API calls per ticket across the Tickets, Associations, and legacy Engagements endpoints, each with separate rate limits and pagination.

No Bulk Conversation Import

Intercom lacks a dedicated bulk import API for conversations, forcing sequential API writes where each engagement must be transformed into a typed conversation part (reply, note) with individual calls.

Cross-Object Workflow Loss

HubSpot Workflows that span objects—such as triggering on a contact property change to update a ticket—have no equivalent in Intercom's conversation-scoped Workflow engine and must be decomposed or rebuilt with middleware.

CRM-to-CDP Data Model Translation

HubSpot's CRM-shaped contact model (lifecycle stages, deals, marketing attribution) must be translated into Intercom's engagement-shaped CDP model (roles, custom events, session data), requiring property pruning and paradigm remapping rather than a lift-and-shift.

Tickets vs. Conversations Routing

HubSpot tickets must be routed to either Intercom Conversations or Intercom Tickets based on pipeline and type, with Intercom Tickets requiring pre-created ticket type definitions as a prerequisite.

Multi-Contact Association Flattening

HubSpot tickets can be associated with multiple contacts, but Intercom conversations support only a single contact, requiring primary requester selection and documentation of additional contacts as internal notes.

MIGRATION RISK ASSESSMENT

Every migration risk, already solved

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

Migration Challenge ClonePartner Status

High Complexity —

Solved

Tickets

Each ticket requires multi-endpoint extraction (3–5 API calls) and a routing decision between Intercom Conversations and Tickets, with no bulk import path on the Intercom side.

Solved

Engagements (Emails, Notes, Calls)

Engagements must be individually transformed into typed conversation parts with correct timestamps and author mapping, and the create-conversation endpoint does not support HTML in the body.

Solved

Workflows/Automations

Cross-object HubSpot Workflows have no Intercom equivalent since Intercom Workflows are conversation-scoped, requiring full decomposition and partial rebuilds with potential middleware.

Solved

Custom Engineering —

Handled

Companies

Intercom's CSV import does not support company data, so companies must be loaded via API or the integration app, and CRM properties like revenue translate awkwardly to custom attributes.

Handled

Custom Fields/Properties

HubSpot instances often have 50–200+ custom properties that must be audited, pruned, and recreated as typed custom attributes in Intercom before data loading; calculated and score fields migrate as static values only.

Handled

Ticket Pipelines

Intercom has no pipeline Kanban view, so pipeline stages must be flattened into conversation states (open/closed/snoozed) plus custom attributes to preserve stage granularity.

Handled

Attachments

Intercom enforces a 20 MB per file limit and restricts certain file types, so oversized or disallowed attachments will silently fail unless pre-filtered and re-uploaded.

Handled

Clean Transfer

Contacts

Core identity fields map directly and contacts can be imported via CSV, though CRM-specific fields like lifecycle stage require classification as custom attributes or exclusion.

Clean

Knowledge Base Articles

Categories map to collections and articles map directly, though Intercom limits collection nesting to three levels which may require restructuring deep hierarchies.

Clean

Snippets/Macros

HubSpot Snippets map to Intercom Macros with added action capabilities, though Playbooks have no direct equivalent and must be recreated as Saved Replies or Workflow-based paths.

Clean

3 high-complexity solved

4 custom-engineered

3 clean transfers

CUSTOM MIGRATION

Fully customizable engineer-led migration

Tailor your migration from HubSpot Service Hub 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 Service Hub 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 Service Hub to Intercom 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 HubSpot Service Hub 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 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 HubSpot Service Hub 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 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 HubSpot Service Hub or Intercom 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 HubSpot Service Hub to Intercom. Can't find what you're looking for? Talk to our team.

How long does a HubSpot Service Hub to Intercom migration take?

Decoupled model with full history: 6–10 weeks. Full departure: 8–12 weeks. Clean-break: 4–7 weeks. The conversation history migration phase (5–15 days) is the longest and most variable.

Can I keep my full HubSpot ticket history in Intercom?

Yes, but only with an API-led migration. Intercom's Conversations API supports a created_at parameter for setting original timestamps on conversations, and reply/note endpoints also support it. Test this in week 1 to verify behavior on your plan.

What data is lost when migrating from HubSpot Service Hub to Intercom?

Cross-object Workflows, the unified CRM activity timeline, Playbooks, NPS/CES surveys (unless using Intercom's Surveys product), calculated/score properties (become static), Kanban pipeline views, deal associations on tickets, and HubSpot task objects.

Can I keep HubSpot CRM and just move service to Intercom?

Yes — this is the decoupled model and the most common approach. Install Intercom's HubSpot app to surface CRM context in the Inbox sidebar. The native app is one-way (Intercom to HubSpot) — bidirectional sync requires HubSpot Data Sync or middleware.

Why is HubSpot to Intercom migration harder than HubSpot to Zendesk?

Zendesk has a dedicated Ticket Import API with guaranteed timestamp preservation — Intercom does not. Intercom also has two interaction objects (Conversations and Tickets) requiring a routing decision that doesn't exist with Zendesk's single-object model.

How long does the HubSpot Service Hub 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 Service Hub 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 Service Hub 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 Service Hub→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 Service Hub to Intercom with precision & ease

Why teams migrate from HubSpot Service Hub to Intercom