HubSpot Service Hub
What Shuttio reads from HubSpot Service Hub, where it lands in Zendesk Support, which permissions it needs and why, and what does not move.
Last updated: 7 Nov 2026
The HubSpot sign-in you already use for the CRM. Service Hub needs the optional permissions for conversations and feedback; HubSpot shows them as unticked boxes, so tick every box.
Object by object: What objects are supported for HubSpot Service Hub migrations.
What Shuttio reads and moves
The list below describes the move into Attio. Where Clarify or Odoo differ, the destination's own article says so.
- Companies and contacts: Companies as organizations (with their domain), contacts as end-users with every email (the first is the login, the others are identities) and every phone. A match in Zendesk is linked to, never changed.
- Tickets: Subject, description, pipeline and stage (the stage's own Open or Closed state decides open or solved, the stage name is kept as a tag), priority, source channel, owner as assignee (matched by email), the owner's team as group, the contact as requester and your own ticket properties as ticket fields.
- Emails, notes, calls and meetings: Every email associated with the ticket is a reply (an incoming one is the customer's, an outgoing one the agent's), every note an internal note, every call and meeting an internal note, each at its own time.
- Conversations: The messages of the conversation threads tied to the ticket, as replies and internal comments, when HubSpot lets the connection read them.
- Files: Attachments on emails, notes, calls and meetings are read through the Files API and uploaded to Zendesk; one that cannot be copied is named in its message.
- Satisfaction answers: A CSAT feedback submission on a ticket, when the connection may read feedback submissions.
Where each thing lands
| HubSpot Service Hub object | In Zendesk Support |
|---|---|
| Companies | Organizations |
| Contacts | End-users |
| Tickets | Tickets, with their replies, notes, files and original dates |
Notes, tasks, meetings, calls, files, owners and lists depend on the destination. This is the row for HubSpot Service Hub, generated from the same tables the runner uses:
Into Zendesk Support
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| HubSpot Service Hub | Companies, Contacts, Tickets | No | No | No | No | No | Yes | Yes | No |
Each destination's own article says how its data is written: Zendesk Support.
Permissions and why
| Permission | Why Shuttio needs it |
|---|---|
| Read tickets, contacts, companies and their properties | The same permissions as a HubSpot CRM migration: tickets, their stages and pipelines, and the people and companies they belong to. |
| Read owners | To match a ticket's owner to a Zendesk agent by email, and to name the author of a note or an email. |
| Read conversations (optional) | The messages of the threads tied to a ticket. Without it only the emails, notes, calls and meetings move, and the run says so. |
| Read feedback submissions (optional) | A satisfaction (CSAT) answer on a ticket. Without it no rating moves. |
| Read emails and files (optional) | Email bodies need sales-email-read; attachments are read through the Files API. Without them those parts do not move, and the run says so. |
Shuttio never writes to the HubSpot portal it reads from. HubSpot shows the optional permissions as unticked boxes: tick every box. The access is deleted 14 days after the migration finishes, and you can remove the app in HubSpot at any time.
Known limits
- Other feedback surveys (NPS, CES) and knowledge base articles: A rating that maps to Zendesk's satisfaction scale is the only one carried; HubSpot's feedback API is read-only and its articles have no ticket link.
- Tickets' SLAs, automation history, merged and deleted tickets: HubSpot's ticket API does not list them with the ticket.
- Emails without the email permission: HubSpot hands over email bodies only with sales-email-read; without it no email moves and the run says so.
- Rate limits: HubSpot limits requests per app and per portal; Shuttio stays under them and pauses the run when HubSpot asks it to slow down.
- Emails: the emails HubSpot logged on a ticket are read as replies of that ticket (they need the sales-email-read permission); Shuttio reads no mailbox.
Not answered here? Email help@shuttio.com.