Migrate into Pylon: where data lands, setup, limits
What Shuttio writes into Pylon, why every message is an internal note with the original author and time in its first line, what Pylon's own automations can still do, how to connect with an API token, what the Pylon API cannot do, and what a rollback leaves.
Last updated: 15 November 2026
Helpdesks that can move into Pylon: Freshdesk, HubSpot Service Hub, Gorgias, Freshservice, Kustomer, Plain, Pylon, LiveAgent. A migration is free under 20,000 records in total: contacts, companies, deals, notes, activities and files together; otherwise it is priced by record count. The sample is free. See pricing. Pylon to Pylon is not offered.
Object by object: What objects are supported for Pylon migrations.
Source by source: Pylon support matrix.
Before you start
- Shuttio contacts no customer. An issue is created with no delivery destination, so its first message is an internal note; every other message is an internal note too, because Pylon's only customer-facing call is delivered to the customer's channel. Contacts are created with no portal access and no invitation.
- Pylon's own triggers and workflows are outside Shuttio's reach. Pause every one that fires on a new issue, an assignment or a closed issue (a survey when an issue closes, a Slack message to the assignee) before the run, because they run on imported issues too.
- Invite the agents in Pylon first and Shuttio matches them by email for assignees, account owners and the authors of notes. A note whose author has no Pylon user is written as the API token's own identity, and its first line names the original author. Shuttio never invites anyone.
- Pylon limits creates and notes to 30 a minute, so a large history is slow (about 360 issues an hour with five notes each). The run waits and pauses when Pylon tells it to; Resume carries on.
- Custom fields and tags are created on the way.
Connect
- In Pylon, an Admin opens Settings, Integrations & dev, API tokens, Create API Token, gives the token the Admin role and copies it when it is shown (once). The token belongs to one organization, so there is no address to type, and there is no OAuth and no app to install. The token is stored encrypted and deleted 14 days after the migration finishes. A migration is pinned to the organization it first wrote to.
- Pylon has no scopes: a write cannot be tested before it is made. Shuttio checks that the token can read accounts, contacts, issues, users and custom fields; a refused write is named on its record.
What Shuttio writes
- An issue with its title, original created time, priority, assignee (matched by email), team (matched by name), account, tags and custom fields; then its state (closed when solved or closed, waiting on the customer when pending, on hold). A text over 20,000 characters continues in a further note.
- Every message after the first as an internal note, in order, with the original author and time in its first line. The text is plain: HTML formatting is lost. Attachments are downloaded from the source and uploaded to Pylon (up to 25 MB a message; Pylon refuses executables and scripts); a file that cannot be copied is named in its message.
- Source fields as issue custom fields, named from the label and typed by the field (text, number, decimal, date, checkbox); the original updated and solved times as custom date fields; owners as a user custom field or the owner's email in a text field.
- Every contact and account carries an external id, every issue a source id field and every note a reference, so a retry never makes a second one.
Where each thing lands
| From | Object | Lands in Pylon as |
|---|---|---|
| Freshdesk | Companies | Accounts |
| Freshdesk | Contacts | Contacts |
| Freshdesk | Tickets | 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) |
| HubSpot Service Hub | Companies | Accounts |
| HubSpot Service Hub | Contacts | Contacts |
| HubSpot Service Hub | Tickets | 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) |
| Gorgias | Customers | Contacts |
| Gorgias | Tickets | 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) |
| Freshservice | Departments | Accounts |
| Freshservice | Requesters | Contacts |
| Freshservice | Tickets | 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) |
| Kustomer | Companies | Accounts |
| Kustomer | Customers | Contacts |
| Kustomer | Conversations | 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) |
| Plain | Accounts | Accounts |
| Plain | Customers | Contacts |
| Plain | Threads | 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) |
| Pylon | Accounts | Accounts |
| Pylon | Contacts | Contacts |
| Pylon | Issues | 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) |
| LiveAgent | Companies | Accounts |
| LiveAgent | Contacts | Contacts |
| LiveAgent | Tickets | 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) |
Matching, and what is never changed
- A contact whose email, or an account whose external id, domain or name, Pylon already has is linked to and never written or removed. A rollback does not remove it.
What the Pylon API cannot do
- It sets no time or author on a message or a note: the original ones are the first line of each note. Only an issue's created time is set. Contacts and accounts have no created time to set: it is a custom field.
- It writes no satisfaction answer, no time entry and no SLA state: they are lines in the issue's closing note.
- A contact belongs to one account and has no tags, address or job title: they are custom fields.
- It cannot delete a custom field, and Shuttio deletes no tag: after a rollback the ones Shuttio created stay.
Not answered here? Email help@shuttio.com.