Migrate from Pylon: what moves, permissions, limits
What Shuttio reads from Pylon, where it lands in Zendesk Support, Gorgias, Freshdesk and 6 more, which permissions it needs and why, and what does not move.
Last updated: 15 November 2026
An API token. You paste an admin-made token from Pylon under Settings, Integrations & dev, API tokens; the token belongs to one organization and Shuttio reads that organization only.
Object by object: What objects are supported for Pylon 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.
- Accounts: As Zendesk organizations, matched by name: one Zendesk already has is linked to, never changed. The name, domains, owner, type, tags, external ids, channel links and custom fields are read.
- Contacts: As Zendesk end-users, matched by email: one Zendesk already has is linked to, never changed. The name, emails, phone numbers, account, portal role, external ids and custom fields are read.
- Issues: Imported whole through Zendesk's ticket import with the original created time, state (closed stays solved, waiting on the customer is pending, on hold is on hold), requester, assignee, team, priority, source channel and tags. No customer is emailed and no trigger runs.
- Messages and notes: Every reply and internal note of the issue, in order, with its time and author (the customer or the matching agent).
- Attachments: Downloaded from Pylon through its signed links and uploaded to Zendesk with the comment. A file that cannot be copied is named in the run's warnings.
- Tags and custom fields: Tags as Zendesk tags. Each issue custom field is created in Zendesk when it has none of that name and type, and filled.
- Satisfaction answer, linked issues and incidents, external ids: Kept as lines in the ticket's internal note: Zendesk has no field for them.
Where each thing lands
| Pylon object | In Zendesk Support | In Gorgias | In Freshdesk | In Freshservice | In Kustomer | In Plain | In Pylon | In LiveAgent | In HubSpot Service Hub |
|---|---|---|---|---|---|---|---|---|---|
| Accounts | Organizations | A Company field on each customer | Companies | Departments | Companies | Accounts | Accounts | Companies | Companies |
| Contacts | End-users | Customers | Contacts | Requesters | Customers | Customers | Contacts | Contacts | Contacts |
| Issues | Tickets, with their replies, notes, files and original dates | Tickets, with their messages, notes, files and original dates | Tickets, with their messages as notes (an agent's are private), files, time entries and the original dates in custom fields | Tickets (incidents), with their messages as private notes, files and time entries; the original dates are in the notes | Conversations, with their messages, notes, files and the original dates and authors (when the key has the org.admin role) | Threads, with their messages as imported inbound and outbound messages, notes, files and the original dates and authors (an agent with no Plain user of that email is named in the first line) | Issues with the original created date, and every message as an internal note with its files and the original author and time in its first line (Pylon sets no time or author on a note) | Tickets, each with every message after the first as an internal note with its files and the original author and time in its first line (LiveAgent sets no time on a ticket or a note) | Tickets, with their emails, notes, files and original dates |
Notes, tasks, meetings, calls, files, owners and lists depend on the destination. This is the row for Pylon, generated from the same tables the runner uses:
Into Zendesk Support
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Pylon | Accounts, Contacts, Issues | No | No | No | No | No | Yes | Yes | No |
Into Gorgias
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Pylon | Accounts, Contacts, Issues | No | No | No | No | No | Yes | Yes | No |
Into Freshdesk
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Pylon | Accounts, Contacts, Issues | No | No | No | No | No | Yes | Yes | No |
Into Freshservice
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Pylon | Accounts, Contacts, Issues | No | No | No | No | No | Yes | Yes | No |
Into Kustomer
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Pylon | Accounts, Contacts, Issues | No | No | No | No | No | Yes | Yes | No |
Into Plain
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Pylon | Accounts, Contacts, Issues | No | No | No | No | No | Yes | Yes | No |
Into Pylon
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Pylon | Accounts, Contacts, Issues | No | No | No | No | No | Yes | Yes | No |
Into LiveAgent
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Pylon | Accounts, Contacts, Issues | No | No | No | No | No | Yes | Yes | No |
Into HubSpot Service Hub
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Pylon | Accounts, Contacts, Issues | No | No | No | No | No | Yes | Yes | No |
Each destination's own article says how its data is written: Zendesk Support, Gorgias, Freshdesk, Freshservice, Kustomer, Plain, Pylon, LiveAgent, HubSpot Service Hub.
Permissions and why
| What | Why Shuttio needs it |
|---|---|
| An API token made by an Admin | Create it in Pylon under Settings, Integrations & dev, API tokens, Create API Token. It is shown once. The token belongs to one organization and Shuttio sends it to Pylon's API host only (US or EU, read from the token). |
| A role that may read | Pylon has no scopes: a token's access is its role. Give it the Admin role (or a role that reads accounts, contacts, issues, users and custom fields). Shuttio checks each of those reads before it saves anything, and never writes to Pylon as a source. |
Pylon limits each endpoint to 30, 120 or 300 requests a minute for the whole organization, so a large workspace takes hours: the run spaces its calls and pauses when Pylon asks it to slow down, until you resume it. The token is stored encrypted and deleted 14 days after the migration finishes. You can delete it at any time in Pylon under Settings, Integrations & dev, API tokens.
Known limits
- Emoji reactions, followers and call recordings: The helpdesk model has no place for them. Reactions are counted in the run summary and stay in Pylon.
- SLA state, surveys beyond the answer on an issue, macros and knowledge base articles: They are Pylon settings or content, not records Zendesk's ticket import takes.
- Speed: Pylon limits each endpoint to 30, 120 or 300 requests a minute for the whole organization. Shuttio spaces its calls under the limit, waits when Pylon asks it to and pauses the run when the wait does not clear; Resume carries on.
- Emails: Shuttio reads no emails from this source.
Not answered here? Email help@shuttio.com.