HubSpot Service Hub to Crisp is a data-model translation from CRM-centric tickets and fragmented engagements to Crisp's conversation-first model. No native import path exists — you need a custom API script or managed service.
Migrating from HubSpot Service Hub to Crisp requires translating a CRM-centric, ticket-and-engagement architecture into a conversation-first messaging platform with a fundamentally flatter data model. No native migration path exists — Crisp's open-source crisp-import-conversations tool supports Zendesk, Gorgias, Help Scout, and others, but has no HubSpot adapter. HubSpot fragments conversation content across 3–5 separate API endpoints (Tickets, Emails, Notes, Calls, Associations), all of which must be reconstructed into Crisp's single-threaded conversation model via custom extraction and transformation work. A custom API adapter, a purpose-built ETL pipeline, or a managed migration service is required for any migration that needs conversation history preserved.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
TL;DR — HubSpot Service Hub to Crisp Migration
A HubSpot Service Hub to Crisp migration is a data-model translation from a CRM-centric, ticket-and-engagement architecture to a conversation-first messaging platform. HubSpot tickets, pipelines, engagement objects (emails, notes, calls), contacts, companies, and custom objects do not map 1:1 to Crisp's flatter model of conversations, contacts, and key-value custom data. The biggest structural challenge: HubSpot fragments conversation content across 3–5 separate API endpoints (Tickets, Emails, Notes, Calls, Associations), while Crisp treats each conversation as a single threaded unit. Crisp has no native HubSpot import tool — their open-source crisp-import-conversations script supports Zendesk, Gorgias, Help Scout, Tidio, GrooveHQ, and WHMCS, but not HubSpot. You need a custom adapter or a managed migration service. Realistic timeline: 1–3 weeks for teams under 50K tickets (roughly 40% extraction, 25% transformation, 20% loading, 15% validation); 3–6 weeks for larger datasets with complex custom objects and attachment-heavy histories.
Custom Objects Warning
HubSpot Custom Objects (Enterprise-only) have no Crisp equivalent. You must either flatten them into key-value custom data on contacts/conversations or accept that this data won't migrate. Do not force HubSpot deals, custom objects, and deep associations into fake Crisp structures. Keep the system of record where it belongs, and migrate only the support context your agents actually need.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Establish why you are moving, what "done" means, and who signs off.
Objective A written scope with agreed success criteria, a named owner per workstream, and a budget approved by finance.
Keep these open
-
Pull the real numbers out of HubSpot Service Hub
Export counts for tickets (open and closed separately), contacts, organisations, attachments, macros, triggers, automations, views and SLA policies. Note the oldest ticket date — history depth drives the whole timeline. Estimating from memory is the single most common cause of a blown migration window.
Data Profiler Get real record counts instead of estimating from memory -
Decide what history actually moves
Agree a cut-off with the support lead: all history, last 24 months, or open tickets plus a read-only archive. Every extra year of closed tickets adds API time and cost without adding much agent value. Get this in writing — it is the decision people relitigate mid-cutover.
A "move everything" default is what turns a two-week migration into a two-month one.
COI & ROI Calculator Build the 36-month business case you will need for sign-off -
Confirm Crisp can hold your support model
Walk your current workflow through Crisp: multi-brand, business hours, SLA targets, CSAT, side conversations, public vs internal notes, and any channel you depend on (voice, chat, WhatsApp, social). List anything with no native equivalent — those are project risks, not configuration details.
-
Build the business case
Model licence delta, migration effort, agent retraining, and the cost of staying put (Cost of Inaction). Executives approve a number, not a plan, and you will be asked for it again at the go/no-go.
Helpdesk Migration Planner Turn ticket volume into a dated HubSpot Service Hub → Crisp timeline -
Name owners and set the go/no-go date
One named owner each for data, configuration, integrations, and agent enablement, plus a decision-maker who can call a rollback. Put the go/no-go meeting in calendars now, 48 hours before the freeze.
HubSpot Service Hub → Crisp specifics
- Simplicity
- Crisp's built-in CRM tracks contacts with conversation history, custom attributes, tags, and segments. It's not a replacement for HubSpot, Pipedrive, or Salesforce — it's a lightweight contact tracker that provides context during conversations. Teams that don't need HubSpot's full CRM gravity find it faster to resolve conversations in Crisp.
- Multichannel unification
- Crisp's all-in-one multichannel platform allows companies to centralize more than 10 channels in one inbox. WhatsApp, Messenger, Emails, Live chat, Phone calls, or even Viber or Line are available from one unified inbox.
- Hybrid setups and agency use cases
- The tradeoff is ecosystem dependency: Service Hub works best as part of the full HubSpot suite, and using it standalone feels incomplete compared to Crisp's self-contained platform. Teams that don't use HubSpot CRM, Marketing Hub, or Sales Hub alongside Service Hub see diminishing returns. For these teams, the cleanest architecture is often Crisp for the support inbox while retaining HubSpot as the CRM of record — Crisp's HubSpot integration supports two-way contact sync, can surface HubSpot deals and list memberships in the Crisp sidebar, and can report Crisp conversations back into HubSpot a
- Time window
- Decide how far back to migrate. Tickets older than 2 years rarely get referenced — consider archiving them to a data warehouse and only migrating recent history.
- Status filter
- Migrate only closed + open tickets, or include deleted?
Don't move on until
- Record counts confirmed for tickets, contacts, organisations and macros
- Success criteria signed off by the support lead
- Freeze window provisionally booked with the business
02 Data Audit Find out what is actually in the data before you try to move it.
Objective A profiled, cleaned export with every quality defect either fixed at source or explicitly accepted.
Keep these open
-
Take a full HubSpot Service Hub export and profile it
Export to CSV or JSON and profile every file: row counts, null rates per column, distinct values, and type consistency. Compare row counts against the API totals from Discovery — a gap here means your export is silently truncated, usually by pagination.
Data Profiler Profile the HubSpot Service Hub export for nulls, outliers and type drift -
Validate file structure before anyone writes a transform
Check delimiters, quoting, encoding (expect UTF-8, watch for BOMs and Latin-1), duplicate headers, and embedded newlines in ticket bodies. Ticket descriptions with raw newlines and commas break naive CSV parsers and silently shift columns.
A single unescaped quote in one ticket body can shift every subsequent column without any error.
CSV Validator Catch broken headers and ragged rows in the raw export -
Inventory PII and set retention
Scan for emails, phone numbers, payment card fragments, national IDs and anything else regulated in ticket bodies and custom fields — support tickets are where customers paste things they should not. Decide what gets migrated, masked, or dropped, and record the legal basis.
Ticket bodies and attachments routinely contain card and ID data that never appears in a structured field.
PII & Compliance Scanner Find regulated fields before they land in a new system -
Quantify duplicates, orphans and dead references
Count duplicate contacts (same email, different casing), tickets whose requester no longer exists, organisations with no members, and attachments whose parent ticket is gone. Fix these in HubSpot Service Hub where you can — migrating them just moves the mess.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Clean and normalise the export
Trim whitespace, drop empty rows and columns, normalise casing on emails and tags, and standardise every timestamp to UTC ISO 8601. Timezone drift is invisible at load time and shows up weeks later as SLA reports nobody can reconcile.
-
Produce a masked copy for sandbox work
Generate a realistic but fake version of the export for testing and for any vendor who needs sample data. Loading real customer PII into a sandbox is a breach in most jurisdictions, and sandboxes are rarely covered by your DPA.
PII Masker Generate a safe copy for sandbox and vendor testing
Don't move on until
- Export parses cleanly with no ragged rows or encoding errors
- PII inventory complete and retention decisions recorded
- Duplicate and orphan records quantified and triaged
03 Field Mapping Turn two schemas into one signed-off mapping spec.
Objective A reviewed field-level mapping covering every object, with an explicit decision for every field that has no target.
Keep these open
-
Generate the first-pass HubSpot Service Hub → Crisp field map
Start from an automated match on both schemas, then review every row by hand. Automated matching gets the obvious 70% right and is confidently wrong on the rest — especially anything named "type", "status" or "custom_field_1".
Schema Mapper Opens pre-loaded with the HubSpot Service Hub → Crisp field pair -
Map status, priority and channel values, not just field names
Enumerate every value in each picklist on both sides and map them explicitly. Value-level mismatches are the defect class that survives all the way to production because the field itself mapped fine — a ticket that should be "Pending" arriving as "Open" reopens SLA clocks.
Statuses with no target equivalent (on-hold, pending-customer) need a policy decision, not a best guess.
-
Decide how custom fields land
Create the target custom fields first, matching type exactly (a dropdown mapped to free text can never be mapped back). Where Crisp has no equivalent, decide between a new custom field, a tag, or a note appended to the ticket body — and record which.
-
Resolve identity and threading
Decide how source IDs are preserved — most platforms will not let you set the primary key, so keep the original ID in a custom field. Without it, reconciliation becomes fuzzy matching and every future support question about an old ticket is unanswerable.
Losing the original ticket ID makes reconciliation and rollback effectively impossible.
-
Plan attachments, inline images and threading order
Confirm size limits, allowed MIME types, and whether inline images survive as attachments or need rehosting. Decide the comment ordering and author attribution rules: comments loaded out of order, or all attributed to the API user, destroy the conversation history agents rely on.
-
Freeze and sign off the mapping spec
Version the spec, walk the support lead through it row by row, and get explicit sign-off. Any change after this point goes through change control — mid-flight mapping edits are how partial loads happen.
Don't move on until
- Every source field is mapped, deliberately dropped, or parked in a custom field
- Status, priority and channel value maps agreed with the support lead
- Mapping spec version-controlled and signed off
04 Test Migration Prove the pipeline on a small, representative slice.
Objective A pilot load into a Crisp sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a Crisp sandbox that matches production config
Create the custom fields, groups, brands, business hours and SLA policies first. A pilot into a default sandbox tests nothing, because the failures you care about are all configuration mismatches.
-
Pick a deliberately nasty pilot sample
Take 500-1000 records chosen for difficulty, not convenience: the longest ticket threads, tickets with the most attachments, non-Latin character sets, merged and split tickets, deleted requesters, and every status value. A clean random sample proves only that easy records are easy.
-
Run the load with masked data and instrument everything
Log every API request and response with its source record ID. When 40 records fail out of 10,000 you need to know exactly which ones and why, without re-running the whole batch.
PII Masker Never load real customer PII into a sandbox -
Measure real throughput against the rate limit
Record achieved records-per-hour under Crisp's actual rate limits, including retries and backoff. Extrapolate to the full volume: if the maths says the full load exceeds your freeze window, you fix that now, not on cutover night.
Published rate limits are ceilings, not throughput. Assume real-world rates are meaningfully lower once retries and backoff are counted.
-
Reconcile the pilot and triage every failure
Diff source against target on record counts and field-level values. Every discrepancy gets a root cause and a fix — "probably fine" at pilot scale becomes thousands of broken records at full scale.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Put real agents in front of the pilot data
Have two or three agents work sample tickets end to end in the sandbox. They find the things reconciliation cannot see: unreadable threading, missing context, macros that no longer make sense. Fix the mapping, then re-run.
Don't move on until
- Pilot batch reconciles to 100% on record counts
- Agents have reviewed sample tickets and confirmed they are workable
- Measured throughput extrapolates to a viable full-load window
05 Cutover Execute the switch inside a controlled, reversible window.
Objective All in-scope data live in Crisp, agents working in the new system, and a rollback path that stayed available throughout.
Keep these open
-
Pre-load history before the freeze
Load closed tickets and contacts days or weeks ahead while HubSpot Service Hub stays live. Only open tickets and the final delta need to move inside the freeze — this is the single biggest lever on window length.
Helpdesk Migration Planner Size the freeze window from Crisp's real API limits -
Publish the runbook with times, owners and abort criteria
A timed sequence: freeze start, final export, delta load, channel switch, smoke test, go/no-go, agent switch. Name who does each step and the explicit condition that triggers a rollback. Decide the abort criteria before the night, when nobody wants to be the one to call it.
-
Freeze HubSpot Service Hub and take the final delta
Stop new ticket creation, let agents finish in-flight replies, then export everything changed since the pre-load. Announce the freeze to the whole business, not just support — someone always tries to raise a ticket during it.
Tickets created during an unenforced freeze land in the old system and are the most common source of permanently lost data.
-
Load the delta and open tickets
Run the delta load, then reconcile counts before touching any channel. Do not repoint email until the delta has verified — an inbound ticket arriving mid-load is far harder to untangle than a few extra minutes of freeze.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint channels and verify with live traffic
Switch email forwarding and MX or connector settings, update chat widgets and web forms, and re-authorise integrations. Then send real test tickets through every channel and confirm each lands, routes and triggers the right automation.
Email forwarding changes can take up to a full DNS TTL to propagate — check the TTL days in advance and lower it if needed.
Cron Expression Builder Schedule the delta syncs that run through the freeze -
Run the go/no-go and switch the agents
Walk the exit criteria with the decision-maker, call it explicitly, then move agents over with a named person on hand for the first few hours. Keep HubSpot Service Hub read-only rather than cancelled — cancelling the old contract on day one removes your only fallback.
Don't move on until
- Full historical load complete and counts matched
- Inbound channels repointed and verified with live test tickets
- Rollback decision point passed explicitly, not by default
06 Validation Prove the migration is complete, then close it out.
Objective Documented evidence that data, workflow and reporting all survived, and a signed acceptance.
Keep these open
-
Run the full reconciliation
Compare source and target on every object: total counts, counts by status, counts by group, attachment counts, and field-level spot checks on a random sample. Produce one report you can hand to an auditor.
Migration Validation Tool Reconcile HubSpot Service Hub and Crisp record-for-record -
Verify field completeness, not just record counts
Re-profile the loaded data and compare null rates per field against the source profile. Matching record counts with a field that silently arrived empty is the failure mode counts alone will never catch.
Data Profiler Prove field completeness held up through the load -
Rebuild reporting and compare against baselines
Recreate your core dashboards — volume, first response time, resolution time, CSAT — and compare to pre-migration figures for the same period. Explain every variance; a changed SLA calculation is a real finding, not a rounding error.
SLA and first-response metrics are usually recalculated from the loaded timestamps, so they will differ if any timestamp mapping was approximate.
-
Test the workflow layer end to end
Fire every trigger, automation, SLA escalation, macro and notification with a live ticket. Workflow does not migrate — it gets rebuilt — so it is untested until someone has actually watched it run.
-
Confirm compliance and produce the audit trail
Re-scan the loaded data for regulated fields, confirm retention and deletion policies are configured in Crisp, and file the evidence with your PII decisions from the audit phase.
PII & Compliance Scanner Produce the compliance evidence your auditor will ask for -
Sign off, then decommission on a schedule
Get written acceptance against the Discovery success criteria. Keep HubSpot Service Hub read-only for an agreed period (30-90 days is typical), take a final archive export, and only then cancel. Diarise the decommission date so it does not quietly renew.
Don't move on until
- Full reconciliation report attached to the project record
- Reporting baselines match pre-migration figures within agreed tolerance
- Formal acceptance signed and archive retention scheduled
Field mapping reference
The field-by-field mapping for each object. Use this as the starting point for your mapping spec.
HubSpot Service Hub Equivalent
| HubSpot Service Hub field | Crisp field | Notes |
|---|---|---|
| Contact | Contact (Profile) | 1:1 mapping. Email is the primary key in both. |
| Company | Contact custom data (company_name, company_domain) | Crisp has no standalone Company object. Flatten to contact-level attributes. |
| Ticket | Conversation | Each ticket becomes a conversation. Status maps to conversation state (pending/resolved/unresolved). |
| Email (engagement) | Message (type: text, from: user/operator) | Reconstruct as messages inside the conversation. Preserve timestamps. |
| Note (engagement) | Message (type: note, from: operator) | Private notes. Requires Essentials or Plus plan. |
| Call (engagement) | Message (type: text or note) with call metadata | No native call object in Crisp. Log as a note with duration/outcome. |
| Deal | No equivalent | Crisp has no deal/opportunity object. Keep in HubSpot or store key fields as contact custom data. |
| Custom Object | Contact or conversation custom data (key-value) | No structured custom objects in Crisp. Flatten to key-value pairs. |
| Pipeline | Conversation segments/tags | Use Crisp segments and tags to replicate pipeline categorization. |
| Pipeline Stage | Conversation state + tags | Map stages to resolved/pending/unresolved + descriptive tags. |
| Workflow | No equivalent (rebuild manually) | Rebuild using Crisp chatbot builder, Hugo AI, or webhook triggers. |
| Knowledge Base Article | Knowledge Base Article | Separate import. Crisp KB supports locales and categories. |
HubSpot Crisp
| HubSpot Service Hub field | Crisp field | Notes |
|---|---|---|
| Contact Email | Contact Email | Primary key for deduplication |
| Contact First Name | Contact Nickname | Concatenate first + last |
| Contact Phone | Contact Phone | Normalize to E.164 format before load |
| Company Name | Contact Custom Data | Flattened — no separate Company object |
| Ticket Subject | Conversation Subject | Can also be inserted as the first message |
| Ticket Status | Conversation State | Map: closed → resolved, open → unresolved |
| Ticket Priority | Conversation Tag | No native priority field in Crisp |
| Ticket Pipeline | Conversation Segment | Use segment filters for operator workflow |
| Email Body | Message Content | Sanitize HTML; strip tracking pixels and inline CSS |
| Note Body | Note Content | Requires Essentials+ |
| Ticket Owner | Conversation Operator | ID mapping required |
| Custom Property | Custom Data | Key-value only; max key length 100 chars |
| HubSpot Object ID | Custom Data | Keep as canonical foreign key for validation and rollback |
| Country | Geolocation | Use ISO 3166-1 alpha-2 country codes, not free text |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Contacts | low | Contacts can be migrated via CSV import or API with standard fields and custom attributes mapping cleanly to Crisp's contact model. |
| Companies | medium | Crisp has no native company object, so company data must be denormalized into contact-level custom attributes or maintained in an external CRM. |
| Tickets | high | HubSpot tickets must be reconstructed from fragmented engagement objects across multiple API endpoints and transformed into Crisp's unified conversation format with no direct structural mapping. |
| Conversation History | high | Email bodies, notes, and call logs are stored as separate engagement objects in HubSpot and must be reassembled in chronological order into single Crisp conversation threads. |
| Custom Fields and Properties | medium | HubSpot's typed custom properties on multiple object types must be flattened into Crisp's simpler key-value custom data, losing data typing and cross-object relational structure. |
| Custom Objects | high | HubSpot Enterprise custom objects with associations have no equivalent in Crisp and must be either abandoned, flattened into metadata, or maintained in an external system. |
| Pipelines and Stages | high | Multi-pipeline ticket configurations with stages and SLA rules cannot be replicated in Crisp, which only supports three conversation statuses (open, pending, resolved). |
| Attachments | medium | File attachments referenced in HubSpot engagements must be downloaded, re-hosted, and linked within Crisp conversations, adding complexity and transfer time for attachment-heavy histories. |
| Tags and Segments | low | HubSpot tags and contact lists can be mapped to Crisp's tags and segment system with relatively straightforward value transformation. |
| Workflow Automations | high | HubSpot's workflow engine with branching logic, delays, and custom code actions cannot be automatically migrated and must be manually recreated using Crisp's more limited chatbot builder and AI routing. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Fragmented Engagement Object Reconstruction
HubSpot stores emails, notes, calls, and meetings as separate engagement objects at distinct API endpoints, requiring 3–5 API calls per ticket to reconstruct a single conversation thread for Crisp's unified model.
No Native Import Path
Crisp's official import script lacks a HubSpot adapter, meaning teams must write a custom adapter or pre-transform all HubSpot data into Crisp's expected JSON format before loading.
Pipeline and Stage Mapping
HubSpot's multi-pipeline ticket system with stages, SLAs, and automations has no direct equivalent in Crisp, which only supports simple conversation statuses (open, pending, resolved).
Custom Object Translation
HubSpot's structured custom properties and Enterprise-tier Custom Objects must be flattened into Crisp's key-value custom data fields at the conversation or contact level, losing relational structure.
Dual-Side API Rate Limiting
Both HubSpot (190 requests per 10 seconds burst limit) and Crisp (multi-level rate limits with daily plugin quotas) impose throttling that requires careful orchestration for bulk migrations.
Automation and Workflow Recreation
HubSpot's branching workflow engine with delays, custom code actions, and SLA enforcement must be manually rebuilt using Crisp's visual chatbot builder and Hugo AI routing, with significant feature gaps.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate HubSpot Service Hub ticket history to Crisp?
Yes, but not via CSV. HubSpot stores email, note, and call content as separate engagement objects across different API endpoints. You need an API-based script to extract engagements, reconstruct them into threaded messages, and import them as Crisp conversations using the Crisp REST API or the official crisp-import-conversations tool with a custom adapter.
Does Crisp have a built-in HubSpot migration tool?
No. Crisp's open-source crisp-import-conversations script supports Zendesk, Gorgias, Help Scout, Tidio, GrooveHQ, and WHMCS adapters, but not HubSpot. You need to write a custom adapter or use a managed migration service.
What data is lost when migrating from HubSpot Service Hub to Crisp?
Pipeline stage history, SLA metrics (first response time, resolution time), deal associations, workflow execution history, custom objects (Crisp has no equivalent — only key-value custom data), and NPS/CES survey data. Workflows must be rebuilt manually using Crisp's chatbot builder or webhook triggers.
How long does a HubSpot Service Hub to Crisp migration take?
For teams with under 50K tickets: 1–3 weeks including planning, test migration, and validation. Larger datasets with complex custom objects or heavy attachments take 3–6 weeks. The main bottleneck is API rate limits on both platforms and the engagement reconstruction step.
Can I keep HubSpot CRM after moving support to Crisp?
Yes. Crisp's HubSpot integration supports two-way contact sync, can surface deals and list memberships in the Crisp sidebar, and can report Crisp conversations back to HubSpot. This hybrid setup — Crisp for support, HubSpot for CRM — is often the cleanest architecture.