Done-for-you migrations are open: our consultants run yours. See the migration service

Migrate into Gorgias: where data lands, setup, limits

What Shuttio writes into Gorgias, how it keeps the original dates and sends no email, how to connect, what the Gorgias API cannot do, how its request limits shape a run, and what a rollback leaves.

Last updated: 15 November 2026

Helpdesks that can move into Gorgias: 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. Gorgias to Gorgias is not offered.

Object by object: What objects are supported for Gorgias migrations.

Source by source: Gorgias support matrix.

Connect

  • Shuttio asks for your Gorgias subdomain (the acme in acme.gorgias.com) and you sign in as an admin on Gorgias's own screen. It asks to read and create customers, tickets, tags and custom fields, and it never invites a user.
  • Without the sign-in you can paste an email and an API key instead (Settings, REST API). Gorgias limits an API key to 40 requests per 20 seconds, half of what the sign-in gets, so a large account moves slower.
  • The access is stored encrypted and deleted 14 days after the migration finishes. Gorgias documents no way for Shuttio to revoke it: remove Shuttio in Gorgias under Settings, App Store, My apps. A migration is pinned to the account it first wrote to: access to another account is refused.
  • Turn off any Gorgias rule that sends a reply or an email while the import runs: the Gorgias docs do not say whether rules run on tickets created through the API.

What Shuttio writes

  • Contacts as customers, matched by email first, with every email and phone as a channel. Gorgias has no organizations, so a company becomes the value of a customer field called Company.
  • A ticket with its created and closed times, status, priority, assignee, team and tags, flagged as imported. Every message keeps its own time, author and visibility (public reply or internal note) and carries its sent time, so Gorgias sends no email to anyone.
  • A ticket with more than 500 messages is created with the first 500, and the rest are added to the same ticket one by one. If Gorgias refuses one, the rest go into one internal note as text.
  • Attachments and inline images are downloaded from the source and uploaded to Gorgias, and an inline image points at its copy. A file that cannot be copied is named in the message and in the run's warnings.
  • Your own ticket fields, customer fields, tags and teams are created in Gorgias when it has none of that name (an existing field is filled, never retyped). Assignees are matched to Gorgias users by email; one with no user leaves the ticket unassigned and is named in its internal note.
  • A satisfaction answer becomes the ticket's survey, already answered and not sent. The data Gorgias has no field for (the source's channel, type, due date, time entries, CC) goes into one internal note per ticket. Messages show the channel API.
  • Every imported ticket carries the tags imported_from_helpdesk and one for this migration, so you can report on them apart.

Where each thing lands

FromObjectLands in Gorgias as
FreshdeskCompaniesA Company field on each customer
FreshdeskContactsCustomers
FreshdeskTicketsTickets, with their messages, notes, files and original dates
HubSpot Service HubCompaniesA Company field on each customer
HubSpot Service HubContactsCustomers
HubSpot Service HubTicketsTickets, with their messages, notes, files and original dates
GorgiasCustomersCustomers
GorgiasTicketsTickets, with their messages, notes, files and original dates
FreshserviceDepartmentsA Company field on each customer
FreshserviceRequestersCustomers
FreshserviceTicketsTickets, with their messages, notes, files and original dates
KustomerCompaniesA Company field on each customer
KustomerCustomersCustomers
KustomerConversationsTickets, with their messages, notes, files and original dates
PlainAccountsA Company field on each customer
PlainCustomersCustomers
PlainThreadsTickets, with their messages, notes, files and original dates
PylonAccountsA Company field on each customer
PylonContactsCustomers
PylonIssuesTickets, with their messages, notes, files and original dates
LiveAgentCompaniesA Company field on each customer
LiveAgentContactsCustomers
LiveAgentTicketsTickets, with their messages, notes, files and original dates

Matching, and what is never changed

  • A customer whose email Gorgias already has is linked to and never written or removed. A rollback does not remove it.
  • Every ticket and message carries an external id derived from the migration and the source id. A ticket created but not finished is looked up by that id and only its missing messages are added, so nothing is created twice.

Gorgias's request limits

Gorgias allows 80 requests per 20 seconds for an app sign-in and 40 for an API key (10-second windows on Enterprise accounts). Shuttio paces itself, waits out a 429 as Gorgias asks and pauses the run if the limit does not clear; press Resume a few minutes later. A ticket costs several requests, so a large account takes hours, not minutes.

What the Gorgias API cannot do

  • It has no delete for a custom field: a rollback deactivates the fields Shuttio created, and you delete them in Gorgias settings.
  • Its ticket list cannot be filtered by tag, so a ticket whose creation answer was lost and never recorded cannot be found by a sweep; it carries the tag shuttio_ in Gorgias.
  • It does not say whether deleting a ticket empties it for good or sends it to the trash, or whether a tag used in a rule can be deleted (the docs say it cannot).
  • Gorgias keeps no SLA or reply-time metrics for imported tickets. Macros and Help Center articles are not moved.

Not answered here? Email help@shuttio.com.