Migrate into Freshservice: where data lands, setup, limits
What Shuttio writes into Freshservice, how it keeps the original dates and authors where the API allows, what can still email a requester and how to switch it off first, how to connect, what the Freshservice API cannot do, and what a rollback leaves.
Last updated: 15 November 2026
Helpdesks that can move into Freshservice: 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. Freshservice to Freshservice is not offered.
Object by object: What objects are supported for Freshservice migrations.
Source by source: Freshservice support matrix.
Before you start
- Freshservice has no switch that stops a single API call from emailing the requester. In Admin turn off the requester notifications (new ticket created, ticket resolved, ticket closed, requester activation) and pause any workflow automator that fires when a ticket is created. Shuttio never uses the reply call, writes every note as private, sets no CC address and moves a ticket to its final status last, but the new-ticket email is Freshservice's own.
- A ticket assigned to an agent notifies that agent: expect those emails.
- If your account marks a field as required to close a ticket, turn that off while the import runs: otherwise the ticket stays Open and the run names it.
- Create the agents you want to be assignees and note authors first, and any custom fields you want filled: the Freshservice API cannot create an agent or a custom field, so Shuttio never does.
Connect
- Paste your Freshservice address (acme.freshservice.com) and an administrator's API key from Profile Settings, View API Key. There is no OAuth and no app to install. The key is stored encrypted and deleted 14 days after the migration finishes. A migration is pinned to the account it first wrote to.
- Time tracking depends on your Freshservice plan. What your plan refuses is written into the ticket's closing note instead of being lost.
What Shuttio writes
- A ticket through the tickets API as an incident, with its subject, description (the first customer message), priority, channel, requester, assignee (matched by email), group, department, tags and custom values.
- Every later message as a private note that opens with its original time and author, written as the matching agent. Time entries are written with the original agent and date when the agent matches by email.
- Attachments are downloaded from the source and sent with the ticket or the note, up to 40 MB for one request. A file that cannot be copied is named in its note.
- Freshservice takes no created or closed time: the original time is the first line of every note, and the custom date fields Original created at and Original closed at are filled when your account already has fields with those labels.
- Every imported ticket carries the tags imported_from_helpdesk, one for this migration and one that identifies the source ticket, so a retry never makes a second ticket.
Where each thing lands
| From | Object | Lands in Freshservice as |
|---|---|---|
| Freshdesk | Companies | Departments |
| Freshdesk | Contacts | Requesters |
| Freshdesk | Tickets | Tickets (incidents), with their messages as private notes, files and time entries; the original dates are in the notes |
| HubSpot Service Hub | Companies | Departments |
| HubSpot Service Hub | Contacts | Requesters |
| HubSpot Service Hub | Tickets | Tickets (incidents), with their messages as private notes, files and time entries; the original dates are in the notes |
| Gorgias | Customers | Requesters |
| Gorgias | Tickets | Tickets (incidents), with their messages as private notes, files and time entries; the original dates are in the notes |
| Freshservice | Departments | Departments |
| Freshservice | Requesters | Requesters |
| Freshservice | Tickets | Tickets (incidents), with their messages as private notes, files and time entries; the original dates are in the notes |
| Kustomer | Companies | Departments |
| Kustomer | Customers | Requesters |
| Kustomer | Conversations | Tickets (incidents), with their messages as private notes, files and time entries; the original dates are in the notes |
| Plain | Accounts | Departments |
| Plain | Customers | Requesters |
| Plain | Threads | Tickets (incidents), with their messages as private notes, files and time entries; the original dates are in the notes |
| Pylon | Accounts | Departments |
| Pylon | Contacts | Requesters |
| Pylon | Issues | Tickets (incidents), with their messages as private notes, files and time entries; the original dates are in the notes |
| LiveAgent | Companies | Departments |
| LiveAgent | Contacts | Requesters |
| LiveAgent | Tickets | Tickets (incidents), with their messages as private notes, files and time entries; the original dates are in the notes |
Matching, and what is never changed
- A requester whose email, or a department whose name, Freshservice already has is linked to and never written or removed. A rollback does not remove it.
What the Freshservice API cannot do
- It cannot write the original created, updated or closed time of a ticket or a note, or a due date in the past.
- A reply call exists, but it emails the requester, so every message is a private note.
- It cannot create an agent without a licence and an invitation, a custom field, or a service request (a ticket is created as an incident).
- It writes no satisfaction answer: the rating is a line in the ticket's closing note.
- It has no call that deletes a tag, and a deleted requester is only deactivated: both are cleaned up in Freshservice by an admin.
Not answered here? Email help@shuttio.com.