Migrating HubSpot to Help Scout requires API extraction. Help Scout caps conversations at 100 threads and 10 custom fields per inbox. Plan for data model flattening, attachment re-encoding, and workflow rebuilds.
Migrating from HubSpot Service Hub to Help Scout requires moving data from a relational CRM-native ticketing architecture—with pipelines, multi-object associations, and unlimited custom properties—into Help Scout's flat, mailbox-centric conversation model. There is no native import path for conversation history; tickets and their associated engagements must be extracted via HubSpot's CRM APIs and written into Help Scout's Mailbox API 2.0 one conversation at a time. Critical constraints include Help Scout's limit of 10 custom fields per inbox and 100 threads per conversation, meaning significant custom transformation logic is required to avoid data loss. HubSpot features such as SLAs, pipelines, workflows, and multi-object association graphs have no direct equivalents in Help Scout and must be rebuilt, flattened, or accepted as losses.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
Critical constraint
Each inbox can have up to 10 custom fields. There are 5 supported field types: Dropdown (with a limit of 100 options), Single line, Multi-line, Number, and Date. If your HubSpot ticket object has 30+ custom properties, you will need to decide which 10 matter most per inbox, or flatten the rest into notes or tags.
Always include the associations parameter when reading tickets to pull linked records in
Always include the associations parameter when reading tickets to pull linked records in a single call, reducing your rate-limit consumption. Example: GET /crm/v3/objects/tickets/{id}?associations=contacts,emails,notes
Set "imported"
true on conversation creation. Without this flag, Help Scout sends real email notifications to customers for every imported conversation. This is the single most common catastrophic mistake in DIY migrations.
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 Help Scout can hold your support model
Walk your current workflow through Help Scout: 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 → Help Scout 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 → Help Scout specifics
- Simplicity
- Teams that only need shared inboxes and a knowledge base find HubSpot's CRM architecture — objects, associations, pipelines, custom properties — over-engineered for their workflow. Help Scout was built around a shared email inbox model, and the experience reflects that strength.
- Separation of concerns
- Many teams want to keep HubSpot for marketing or CRM while moving frontline support into a dedicated shared inbox. Help Scout's native HubSpot app supports this split by showing HubSpot contact and company properties, latest activity, list memberships, workflows, and deals in the Help Scout sidebar. (docs.helpscout.com)
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
HubSpot Service Hub → Help Scout specifics
- Contacts
- Count total, identify duplicates by email. Note contacts with no associated tickets (decide whether to migrate).
- Companies
- Count total. Decide if these map to Help Scout organizations.
- Custom properties
- List every ticket custom property. Identify which 10 (per inbox) you need in Help Scout. Plan where the rest will go (notes, tags, or dropped).
- Attachments
- Estimate total size. Identify any files over 10 MB (Help Scout's per-attachment limit).
- Knowledge Base
- Count articles, categories, and collections. These use Help Scout's Docs API v1 — a separate API from the Mailbox API with its own endpoints for categories (/v1/collections/{id}/categories), collections (/v1/collections), and articles (/v1/articles).
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 → Help Scout 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 → Help Scout 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 Help Scout 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.
-
Map to tags
Convert single-select picklists to Help Scout tags (e.g., priority:high, category:billing)
Data Format Converter Reshape the export into the format Help Scout's importer expects
HubSpot Service Hub → Help Scout specifics
- Thread ordering
- Sort HubSpot engagements by hs_timestamp to reconstruct the chronological conversation. If hs_timestamp is null (rare but possible on older records), fall back to hs_createdate.
- HTML sanitization
- HubSpot email bodies may contain tracking pixels (<img> tags with track.hubspot.com URLs) and HubSpot-specific hs-cta div wrappers. Strip these before importing. Use a library like bleach (Python) or sanitize-html (Node.js) with an allowlist of safe tags.
- Attachment encoding
- Help Scout's Create Reply endpoint expects attachments as base64-encoded data fields with fileName and mimeType parameters. Download from HubSpot's file API, base64-encode, and embed. For attachments over 10 MB, link to an external URL in the thread body instead.
- Agent matching
- Map HubSpot owner IDs to Help Scout user IDs. Agents must already exist in Help Scout before import. Build this lookup table during pre-migration.
- Custom field compression
- Reduce HubSpot's unlimited properties to Help Scout's 10-field-per-inbox limit. Overflow goes into notes or tags.
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 Help Scout sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a Help Scout 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 Help Scout'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 Help Scout, 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 Help Scout'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.
HubSpot Service Hub → Help Scout specifics
- Webhooks
- Configure a HubSpot webhook subscription for ticket.creation events during the migration window. Queue new ticket IDs and process them in a final batch after the main migration completes. This requires a running webhook receiver (e.g., a simple Flask/Express endpoint writing to a queue).
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 Help Scout 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 Help Scout, 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 Help Scout
| HubSpot Service Hub field | Help Scout field | Notes |
|---|---|---|
| Tickets | Conversations | Tickets become conversations in a target mailbox |
| Ticket pipeline / stages | Status (active, pending, closed) | No pipeline equivalent; status is a flat enum |
| Contacts | Customers | 1:1 mapping; match on email |
| Companies | Organizations | Basic mapping; no deep association graph |
| Engagements (emails, notes, calls) | Threads (customer, reply, note, chat, phone) | Each engagement becomes a thread |
| Custom properties (unlimited) | Custom fields (max 10 per inbox) | Major constraint — data loss risk |
| Associations (ticket↔contact↔company↔deal) | Conversation↔Customer (single link) | Multi-object relationships lost |
| Knowledge Base articles | Docs articles | Separate API (Docs API v1); manual structure rebuild |
| Workflows / Automations | Workflows | Must be rebuilt manually |
| SLAs | No native SLA engine | Lost in migration |
HubSpot Ticket Property Help Scout
| HubSpot Service Hub field | Help Scout field | Notes |
|---|---|---|
| subject | subject | Direct |
| hs_pipeline | mailboxId | Map pipeline → mailbox via lookup table |
| hs_pipeline_stage | status | Map stage label to active/pending/closed |
| hs_ticket_priority | Tag or custom field | priority:{value} |
| hs_ticket_category | Tag or custom field | category:{value} |
| hubspot_owner_id | assignee.id | Owner → agent lookup |
| createdate | createdAt | Direct (HubSpot stores UTC; Help Scout expects ISO 8601 with timezone) |
| closed_date | closedAt | Direct |
| content (engagement body) | Thread text | Sanitize tracking pixels, rewrite inline image URLs |
| Associated contact email | customer.email | Direct |
| Associated company name | Organization name | Create org, link to customer |
HubSpot KB Docs
| HubSpot Service Hub field | Help Scout field | Notes |
|---|---|---|
| Knowledge Base | Site (Docs site) | Create via Docs API or UI |
| Category | Collection | POST /v1/collections |
| Subcategory | Category (within collection) | POST /v1/categories |
| Article | Article | POST /v1/articles |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Tickets / Conversations | high | No native import path exists; each ticket must be individually reconstructed as a conversation via API, with thread ordering, timestamps, and author attribution carefully preserved. |
| Contacts / Customers | low | Contacts map 1:1 to Help Scout customers matched on email address, making this a straightforward data transfer with minimal transformation. |
| Companies / Organizations | low | Basic mapping is supported between HubSpot companies and Help Scout organizations, though the deep association graph is not preserved. |
| Custom Fields / Properties | high | HubSpot supports unlimited custom properties while Help Scout caps custom fields at 10 per inbox with only 5 field types, creating significant data loss risk for property-heavy accounts. |
| Engagements / Threads | high | Each HubSpot engagement (email, note, call) must be individually mapped to the correct Help Scout thread type, and conversations exceeding 100 threads will fail with an API error. |
| Attachments | medium | Attachments and inline images can be migrated via the API but require re-encoding and careful handling, with failures commonly occurring around large files and embedded content. |
| Multi-Object Associations | high | HubSpot's rich association chains (ticket↔contact↔company↔deal) collapse to a single conversation↔customer link in Help Scout, resulting in permanent loss of relational context. |
| Knowledge Base Articles | medium | Articles must be migrated via Help Scout's separate Docs API v1 with manual structure rebuilding, as there is no automated category or site mapping between platforms. |
| Workflows / Automations | medium | All HubSpot workflows and automation rules must be manually rebuilt in Help Scout's workflow system, as there is no migration path for automation logic. |
| SLAs | high | Help Scout has no native SLA engine, so all HubSpot SLA configurations, tracking data, and compliance history are permanently lost in the migration. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
No Native Conversation Import
Help Scout provides no CSV or bulk import mechanism for conversations, requiring all ticket history to be written programmatically via the Mailbox API 2.0 one conversation and thread at a time.
Custom Field Limit Constraint
Help Scout allows a maximum of 10 custom fields per inbox with only 5 field types, forcing teams with dozens of HubSpot custom ticket properties to compress, prioritize, or flatten remaining data into tags or notes.
Relational-to-Flat Data Model Conversion
HubSpot's multi-object association graph (ticket↔contact↔company↔deal) must be flattened into Help Scout's single conversation↔customer link, losing rich relational context in the process.
Pipeline and SLA Feature Gaps
HubSpot's ticket pipelines, stages, and SLA engine have no equivalent in Help Scout, which uses only a flat status enum (active, pending, closed) and lacks native SLA tracking.
Thread Count Ceiling Per Conversation
Help Scout enforces a hard limit of 100 threads per conversation, returning an HTTP 412 error if exceeded, which requires special handling for high-volume HubSpot tickets with more than 100 associated engagements.
User Provisioning Cannot Be Automated
Help Scout's API does not support user creation via REST—agents must be provisioned through the UI invite flow or SCIM (Pro plan only)—complicating automated agent matching during migration.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate HubSpot Service Hub tickets to Help Scout using CSV?
No. Help Scout has no native CSV import for conversations. You can export contacts via CSV, but ticket history, thread content, attachments, and notes require the Help Scout Mailbox API 2.0. HubSpot's CSV export only gives you ticket metadata — not the full thread content or engagement bodies needed for a complete migration.
What are Help Scout's API rate limits for migration?
Help Scout allows 400 API requests per minute per access token. Each ticket migration requires roughly 12–15 API calls (conversation creation plus threads, custom fields, tags, and status update). That means approximately 26–33 tickets per minute, making a 10K-ticket migration take about 5–6 hours of pure API time.
How many custom fields does Help Scout support per inbox?
Help Scout supports a maximum of 10 custom fields per inbox, available on Plus and Pro plans only. There are 5 field types: Dropdown, Single line, Multi-line, Number, and Date. Custom fields are inbox-specific and do not carry over if a conversation is moved between inboxes.
What happens to HubSpot deals and custom objects in Help Scout?
Help Scout has no native deal pipeline or custom object layer. Most teams keep deals and custom objects in HubSpot and surface the needed context in Help Scout through the native HubSpot app, which shows contact properties, activity, and deals in the sidebar.
Will my customers receive old emails during the migration?
Not if executed correctly. When creating conversations via the Help Scout API, you must set the imported flag to true. This suppresses all outbound customer notifications and workflow triggers, and preserves original timestamps.