
Gorgias migration
Gorgias migration
Gorgias is a help desk for ecommerce brands: it puts Shopify and other store customer and order data beside each ticket. Its data model is small and strict. A Ticket holds messages, belongs to one Customer, and has only two statuses. We move Zendesk and Freshdesk history into Gorgias, and scope a move out of Gorgias on a call.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.
- 1000+migrations
- 15 yearsof collective experience
SOC 2 Type IIGDPR compliantHIPAA compliant
Gorgias migration at a glance
- Who it is for
- Store support teams on Shopify, BigCommerce, Magento or WooCommerce who are moving ticket history into Gorgias or out of it, and the agencies that run those moves.
- What moves
- Tickets with their emails, chats, comments and internal notes, attachments, customers, users, teams, tags, macros, custom fields and satisfaction surveys.
- What does not move as-is
- Rules, views, SLAs, reports and widgets are set up again in Gorgias. Shopify customer and order data comes from reconnecting the store, not from ticket history.
- What sets the scope
- Ticket count, attachments, how many source statuses must fold into open and closed, macros with placeholders, and how old the emails are, because Gorgias archives original email bodies.
What moves
What moves from Gorgias?
MigrateX moves Gorgias tickets with their messages, internal notes and attachments, plus customers, users, teams, tags, macros, custom fields and satisfaction surveys.
- Tickets
- Ticket messages
- Customers
- Tags
- Custom fields
- Attachments
- Help Center articles
What does not move
What does not move from Gorgias as-is
Configuration, not data. We list each item in scope so your team can rebuild it in the target.
- Rules
- What we do: Rebuilt in Gorgias. The Zendesk importer brings tickets, macros, users, tags and ticket fields only, and no source's automations convert one to one, so each is listed with what it does today.
Source: Gorgias Help Center, checked 15 Nov 2026
- Views, SLAs, reports and widgets
- What we do: Set up again in Gorgias on the migrated tags, statuses and fields.
Source: Gorgias Help Center, checked 15 Nov 2026
- Shopify customer and order data
- What we do: Comes from connecting the store, which Gorgias imports in the background. We match migrated tickets to those profiles by email.
Source: Gorgias Help Center, checked 15 Nov 2026
- Macros with conditions, placeholders or integrations
- What we do: Gorgias imports only reply-text and status-change macro actions and brings any other action in as an empty list, so these macros move as reply text and are checked line by line.
Source: Gorgias Help Center, checked 15 Nov 2026
- Ticket event history older than a year
- What we do: Gorgias keeps audit-log events for 12 months, so older events cannot be read. The final state of each ticket moves.
Source: Gorgias developer documentation, checked 15 Nov 2026
- Help Center articles
- What we do: Imported from a CSV, or directly from Zendesk, HelpDocs, Re:amaze or Intercom. Leaving Gorgias, support supplies the copy because you cannot export articles yourself.
Source: Gorgias Help Center, checked 15 Nov 2026
- Email connection
- What we do: Switched on after the history is in, in one planned window, so the same mailbox never feeds two help desks at once.
What does a Gorgias migration have to handle?
A Gorgias migration has to give every ticket at least one message, fold each source status into open or closed, mark old replies as already sent so no customer is emailed, and leave Shopify data to the store connection. Each point is settled with your Gorgias admin before the free sample.
- A ticket cannot exist without a message
- Gorgias refuses a ticket that has no message, and messages are the only required property when a ticket is created. A source ticket with an empty thread needs a placeholder message, which we agree with you.
Source: Gorgias developer documentation, checked 15 Nov 2026
- Two statuses, open and closed
- The API accepts only open and closed. Anything richer in the source, such as pending, on hold or solved, has to fold into one of the two, and the rule is written down and signed off before the load.
Source: Gorgias developer documentation, checked 15 Nov 2026
- An old reply must say it was already sent
- A message loaded without a sent_datetime is sent by Gorgias to its recipients. Every historical reply carries the original sent time, so the load emails nobody.
Source: Gorgias developer documentation, checked 15 Nov 2026
- The source ID rides in external_id
- Gorgias does not use a ticket's external_id itself, so the source system's ticket ID is stored there. That keeps the delta sync from creating a second copy of any ticket.
Source: Gorgias developer documentation, checked 15 Nov 2026
- API-created tickets skip auto-reply rules, not every rule
- On the API channel, auto-reply rules do not fire, but other rule actions such as auto-tag still do, and keyword rules need stripped_text to match. We list your active rules before the load.
Source: Gorgias developer documentation, checked 15 Nov 2026
- Shopify data comes from the store, not the ticket
- Order history and Shopify customer profiles appear on tickets once the store is connected, and Gorgias imports them in the background. A migration carries the conversation and matches customers by email.
Source: Gorgias Help Center, checked 15 Nov 2026
- Internal notes are messages on their own channel
- A Gorgias internal note is a message sent on the internal-note channel. Private comments from the source land there, so the customer never sees them.
Source: Gorgias developer documentation, checked 15 Nov 2026
Free sample migration of 100 of your records. Fixed quote within 24 hours.
Scope my migrationMigration paths
Where can I move to or from Gorgias?
Routes we run from and into Gorgias. Open a route to see what migrates, or ask us about one that is not listed yet.
Into Gorgias
191 connectors, all live
Every connector is live, so Gorgias can be paired with any of them. Some of the help desk platforms:
- Salesforce Service Cloud
- HubSpot Service Hub
- Intercom
- Zoho Desk
- Dynamics 365 Customer Service
- Help Scout
- Kustomer
- Front
- HappyFox
Platform not listed?
We build new connectors in 2 to 3 days. Tell us what you run and we scope the route with you.
Timeline
Your Gorgias migration, step by step
Estimated total
About 10 business days
end to end
- MigrateXwe run it
- Youyour team acts
- Bothon a call together
Preparation
Day 1-2
Scoping call
Both0.5 dayA 30 minute call with the engineer who will run the migration, to agree the objects, date ranges and volumes in scope.
Connect both platforms
You0.5 dayYou create scoped API credentials on the source and the destination. Nothing is written until you sign off the mapping.
Field mapping review
Both1 dayWe walk through every field, status and group mapping with your team and note the ones that need a decision.
Migration
Day 3-7
Free sample migration of 100 records
MigrateX1 dayA sample of your real records is migrated end to end so you can see the result before the full run.
You review the sample
You1 dayYour team opens the migrated records and tells us what to adjust. We rerun the sample until it is right.
Full migration
MigrateX2-3 daysThe bulk pass runs in dependency order, paced to the destination rate limit. Your team keeps working normally.
Delta sync
MigrateX0.5 dayEverything created or changed during the bulk pass is synced at cutover so nothing falls between the two systems.
Validation
Day 8-10
Validation report
MigrateX1 dayRecord counts per object and per status on both sides, plus every record that needed a default or a placeholder.
Spot checks and sign-off
You1-2 daysYour leads check a random sample and sign off. We stay available for two weeks after go-live.
An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.
See how it works in detailData model
Gorgias data model and limits
How Gorgias holds the records that move, and the vendor limits that set the pace of the migration.
How does Gorgias store support data?
Gorgias stores a conversation as a Ticket that holds TicketMessage records, one for each email, chat, SMS, comment or internal note. A Customer sits on every ticket and carries the Shopify data, while tags, macros, rules and views surround it. A migration reads or writes these objects in that order.
| Object | What it holds | How it links |
|---|---|---|
| Ticket | One conversation with one customer: subject, status, priority, channel, tags, custom fields, language and spam flag, plus created, opened, closed, updated and trashed times. | Contains the messages, points to a Customer and an assignee user or team. Status is open or closed. The external_id field is free for a migration, and an imported flag marks historical tickets. Source: Gorgias developer documentation |
| TicketMessage | One email, chat, SMS, comment or internal note, with HTML and text bodies, sender, receiver, source, attachments and a sent time. | Child of a Ticket. The public flag is false for an internal note, and each message carries the ID of its integration. Source: Gorgias developer documentation |
| Customer | The person who writes in: name, email and other channels, language, time zone, a note and an external_id. | Linked to their tickets. Shopify, Recharge and HTTP integration data hangs off the customer. The API has no separate company object. Source: Gorgias developer documentation |
| Shopify and other store data | Customer profiles and order history from the connected Shopify store, shown beside each ticket. | Arrives when the store is connected, and Gorgias imports it in the background. It is not part of a ticket. Source: Gorgias Help Center |
| User and Team | Agents and admins, and the groups they belong to. | Referenced as the assignee user and assignee team of a ticket, and as the sender of a reply. Source: Gorgias developer documentation |
| Macro | A canned reply plus a list of actions that change or answer a ticket, with a language, an intent and a usage count. | Applied to tickets by agents or by rules. Can be archived. Source: Gorgias developer documentation |
| Rule | An automation: a trigger and the actions it takes on tickets. | Exposed through list, create and update endpoints, but not carried by Gorgias's own Zendesk importer. Source: Gorgias Help Center |
| View | A saved ticket filter. | Shared with users or teams. A ticket can sit in one or more views at once. Source: Gorgias developer documentation |
| Satisfaction survey | A score from 1 to 5, a comment, and the times it was sent and scored. | Child of a Ticket, and only one survey can exist for each ticket. A null send time means Gorgias will not send it. Source: Gorgias developer documentation |
| Custom field | Typed field definitions and values, for tickets and for customers. | Set on a ticket in the custom_fields property when it is created. Source: Gorgias developer documentation |
| Help Center article and category | Self-service content for shoppers. | Sits outside the REST API reference. Gorgias does not let you export it yourself, and support can supply a copy. Source: Gorgias Help Center |
Ticket
- What it holds
- One conversation with one customer: subject, status, priority, channel, tags, custom fields, language and spam flag, plus created, opened, closed, updated and trashed times.
- How it links
- Contains the messages, points to a Customer and an assignee user or team. Status is open or closed. The external_id field is free for a migration, and an imported flag marks historical tickets.
Source: Gorgias developer documentation
TicketMessage
- What it holds
- One email, chat, SMS, comment or internal note, with HTML and text bodies, sender, receiver, source, attachments and a sent time.
- How it links
- Child of a Ticket. The public flag is false for an internal note, and each message carries the ID of its integration.
Source: Gorgias developer documentation
Customer
- What it holds
- The person who writes in: name, email and other channels, language, time zone, a note and an external_id.
- How it links
- Linked to their tickets. Shopify, Recharge and HTTP integration data hangs off the customer. The API has no separate company object.
Source: Gorgias developer documentation
Shopify and other store data
- What it holds
- Customer profiles and order history from the connected Shopify store, shown beside each ticket.
- How it links
- Arrives when the store is connected, and Gorgias imports it in the background. It is not part of a ticket.
Source: Gorgias Help Center
User and Team
- What it holds
- Agents and admins, and the groups they belong to.
- How it links
- Referenced as the assignee user and assignee team of a ticket, and as the sender of a reply.
Source: Gorgias developer documentation
Macro
- What it holds
- A canned reply plus a list of actions that change or answer a ticket, with a language, an intent and a usage count.
- How it links
- Applied to tickets by agents or by rules. Can be archived.
Source: Gorgias developer documentation
Rule
- What it holds
- An automation: a trigger and the actions it takes on tickets.
- How it links
- Exposed through list, create and update endpoints, but not carried by Gorgias's own Zendesk importer.
Source: Gorgias Help Center
View
- What it holds
- A saved ticket filter.
- How it links
- Shared with users or teams. A ticket can sit in one or more views at once.
Source: Gorgias developer documentation
Satisfaction survey
- What it holds
- A score from 1 to 5, a comment, and the times it was sent and scored.
- How it links
- Child of a Ticket, and only one survey can exist for each ticket. A null send time means Gorgias will not send it.
Source: Gorgias developer documentation
Custom field
- What it holds
- Typed field definitions and values, for tickets and for customers.
- How it links
- Set on a ticket in the custom_fields property when it is created.
Source: Gorgias developer documentation
Help Center article and category
- What it holds
- Self-service content for shoppers.
- How it links
- Sits outside the REST API reference. Gorgias does not let you export it yourself, and support can supply a copy.
Source: Gorgias Help Center
Gorgias objects that hold support data, as of 15 November 2026. Source: Gorgias developer reference and help centre.
Which Gorgias limits set the pace?
Gorgias sets request windows per integration type and keeps only part of the history in each export route. These are the limits that decide how fast tickets, messages and files move into or out of Gorgias, and which of its own export and import routes can carry a full support history.
| Limit | Allowance |
|---|---|
| API request windows | API-key integrations: 40 requests in a 20-second window. OAuth2 apps: 80 in 20 seconds. Going over returns HTTP 429 with a Retry-after header. Source: Gorgias developer documentation |
| Enterprise window | Enterprise accounts get the same request counts in a smaller 10-second window. Source: Gorgias developer documentation |
| Rate on the plan table | The pricing page lists an API rate of 2 requests a second on self-serve plans and 4 a second on Enterprise. Source: Gorgias website |
| Ticket list paging | Cursor pagination, 30 tickets a page by default and 100 at most. Gorgias replaced offset pagination with it. Source: Gorgias developer documentation |
| Plans and billable tickets | Helpdesk plans are Starter, Basic, Pro, Advanced and a custom Enterprise plan. They are sized by billable tickets, not agents, from 50 a month on Starter to 5,000 on Advanced. Source: Gorgias website |
| What makes a ticket billable | A ticket is billable when at least one message in it is sent from the Gorgias helpdesk by an agent, the AI Agent or a rule. It counts once, however many messages it holds. Source: Gorgias Help Center |
| Ticket export from a view | A CSV emailed as a link that works for 14 days, up to 1 million tickets, about an hour for 100,000. It holds ticket metadata and a link, not message text. Owner, admins and leads only. Source: Gorgias Help Center |
| Export from an analytics drill-down | Can include message text, but only for the most recent 30 days of the chosen period, up to 100,000 tickets, public messages only. Internal notes and ticket events are left out. Source: Gorgias Help Center |
| Original email bodies | From 8 September 2026, 30 days after an email is sent or received, Gorgias removes its headers and archives the original HTML and text at a body URL when a stripped version exists. Older mail was processed through September and October 2026. Source: Gorgias developer documentation |
| Ticket event history | Audit-log events are kept for at most 12 months, since 25 February 2026. Source: Gorgias developer documentation |
| Attachment downloads | Attachment URLs returned by the API are not directly reachable. Files are fetched through the Downloads API. Source: Gorgias developer documentation |
| Ticket subject length | 998 characters at most, since 1 September 2024. Source: Gorgias developer documentation |
API request windows
- Allowance
- API-key integrations: 40 requests in a 20-second window. OAuth2 apps: 80 in 20 seconds. Going over returns HTTP 429 with a Retry-after header.
Source: Gorgias developer documentation
Enterprise window
- Allowance
- Enterprise accounts get the same request counts in a smaller 10-second window.
Source: Gorgias developer documentation
Rate on the plan table
- Allowance
- The pricing page lists an API rate of 2 requests a second on self-serve plans and 4 a second on Enterprise.
Source: Gorgias website
Ticket list paging
- Allowance
- Cursor pagination, 30 tickets a page by default and 100 at most. Gorgias replaced offset pagination with it.
Source: Gorgias developer documentation
Plans and billable tickets
- Allowance
- Helpdesk plans are Starter, Basic, Pro, Advanced and a custom Enterprise plan. They are sized by billable tickets, not agents, from 50 a month on Starter to 5,000 on Advanced.
Source: Gorgias website
What makes a ticket billable
- Allowance
- A ticket is billable when at least one message in it is sent from the Gorgias helpdesk by an agent, the AI Agent or a rule. It counts once, however many messages it holds.
Source: Gorgias Help Center
Ticket export from a view
- Allowance
- A CSV emailed as a link that works for 14 days, up to 1 million tickets, about an hour for 100,000. It holds ticket metadata and a link, not message text. Owner, admins and leads only.
Source: Gorgias Help Center
Export from an analytics drill-down
- Allowance
- Can include message text, but only for the most recent 30 days of the chosen period, up to 100,000 tickets, public messages only. Internal notes and ticket events are left out.
Source: Gorgias Help Center
Original email bodies
- Allowance
- From 8 September 2026, 30 days after an email is sent or received, Gorgias removes its headers and archives the original HTML and text at a body URL when a stripped version exists. Older mail was processed through September and October 2026.
Source: Gorgias developer documentation
Ticket event history
- Allowance
- Audit-log events are kept for at most 12 months, since 25 February 2026.
Source: Gorgias developer documentation
Attachment downloads
- Allowance
- Attachment URLs returned by the API are not directly reachable. Files are fetched through the Downloads API.
Source: Gorgias developer documentation
Ticket subject length
- Allowance
- 998 characters at most, since 1 September 2024.
Source: Gorgias developer documentation
Gorgias limits that shape a migration, as of 15 November 2026. Source: Gorgias developer reference, changelog and help centre, linked per row.
Facts checked 15 Nov 2026. Sources: Gorgias developer documentation, Gorgias Help Center and Gorgias website.
Gorgias migration questions
Still unsure? Ask us on the scoping call.
What does a Gorgias migration cost?
The cost of a Gorgias migration follows the tickets in scope and what hangs off them: messages, internal notes, attachments and customers. Macros with placeholders and the number of source statuses to fold add mapping work. We first migrate 100 of your records free of charge, then send a fixed quote within 24 hours.
How long does a Gorgias migration take?
The default plan is about 10 business days end to end. On Gorgias the load is paced by the request window: 40 requests every 20 seconds on an API key and 80 on an OAuth2 app. Gorgias's own Zendesk importer runs at about 720 tickets an hour. The free sample measures the pace on your own data.
How do I export tickets from Gorgias?
Export from a view gives a CSV link with ticket metadata for up to 1 million tickets, but no message text. An analytics drill-down adds public message text for the most recent 30 days only. MigrateX reads every message, internal note and attachment through the API instead, and Gorgias support can build a custom export on request.
Can I export Help Center articles from Gorgias?
Not yourself. Gorgias states that exporting articles is not supported in the product, and its support team can supply a copy of your data on request. Going the other way, articles import from a CSV or directly from Zendesk, HelpDocs, Re:amaze and Intercom. We plan the article move with you on the scoping call.
Do imported tickets count as billable tickets in Gorgias?
Gorgias counts a ticket as billable when at least one message in it is sent from the helpdesk by an agent, the AI Agent or a rule. Whether tickets loaded through the API count is not stated in the documentation, so we confirm it with Gorgias before the load. Accounts opened before 28 May 2025 may be on legacy pricing.
Will my Shopify customer and order data appear on migrated tickets?
Yes, once the store is connected. Gorgias imports Shopify customer profiles and order history in the background after you connect it, and that data sits beside the ticket, not inside it. MigrateX loads the conversation, matches each ticket to its customer by email, and you reconnect the store before cutover.
Do Gorgias rules and macros carry over?
Macros move as reply text, and the ones with conditions, placeholders or integrations are checked line by line, since Gorgias imports only reply-text and status-change actions. Rules do not convert. We hand you a list of each rule in scope with what it does today, and your admin rebuilds them in Gorgias.
What access do you need to our Gorgias account?
A Gorgias admin sets up an API key or an OAuth2 app, because Gorgias limits ticket export to the account owner, admins and leads. An API key gets 40 requests per 20-second window and an OAuth2 app gets 80, so the choice is agreed on the scoping call. MigrateX is SOC 2 Type II, GDPR and HIPAA compliant.
Guides
Guides for a Gorgias migration

Start with 100 of your records.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.

