Gorgias to Zendesk migration
We migrate Tickets, Customers, Macros, Conversations, and Knowledge Base from Gorgias into Zendesk with ticket status translation resolved upfront, comment-count splitting handled for threads exceeding 250 messages, and every Gorgias channel flag mapped to the equivalent Zendesk ticket form before cutover.
FlitStack AI migrates tickets, comments, users, agents and groups from Gorgias to Zendesk, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

What moves from Gorgias to Zendesk?
Moving from Gorgias to Zendesk is primarily a ticket and customer data migration with several non-obvious translation points.
Read the full summary
Gorgias uses billable-ticket-volume pricing with separate AI outcome fees, while Zendesk prices per agent seat, making the cost structure fundamentally different for teams evaluating the switch. We handle the bulk export from Gorgias within the 40-request-per-20-second API envelope using pagination with exponential backoff, and we translate the ticket status model carefully because Gorgias's Solved and Pending statuses map to Zendesk's closed-ticket states, meaning historical open-close transitions cannot be fully replicated. Knowledge Base articles, categories, and multi-locale translations migrate with separate API calls per locale as the Gorgias API requires. Zendesk workflows, automations, and triggers do not migrate; we deliver a written inventory of every Gorgias Rule requiring rebuild as a Zendesk Trigger or Automation. Voice channels, Skills-based routing, and the Zendesk Advanced AI add-on are add-on features on Zendesk Suite Enterprise and Suite Growth, not included at entry-level, so we flag these gaps during scoping so the customer's procurement team is not surprised post-migration.
Tickets → Tickets
Gorgias Tickets map to Zendesk Tickets.
How it maps
The channel field (email, chat, Facebook, Instagram, WhatsApp, SMS) maps to Zendesk's ticket_form_id, which we configure per channel type during migration. Priority (low, normal, high, urgent) maps to Zendesk Priority. The assignee, group, and status fields map directly. We flag that Gorgias Solved and Pending statuses both translate to Zendesk's Closed status on import; if a ticket was Solved then reopened in Gorgias, the most recent status wins and the transition history is not preserved in Zendesk's audit log.
Conversations → Comments
Gorgias Conversations (public replies and internal notes) map to Zendesk Comments.
How it maps
The public/private flag translates directly. Attachments on comments download from Gorgias and re-upload to Zendesk via the attachment API. Threads exceeding 250 comments are split into multiple closed tickets per Gorgias's own Zendesk import limitation; we apply the same 250-comment split logic during our migration to prevent orphaned child tickets.
Customers → Users (End Users)
Gorgias Customers (end shoppers) map to Zendesk End Users.
How it maps
The customer email is the dedupe key. Phone number, name, and address fields map to Zendesk user fields. Customer attributes from Shopify order context (total spend, order count, AOV) do not have native Zendesk equivalents; we map them to Zendesk user fields prefixed with gorgias_ or create custom user fields, and the customer's admin chooses the final field placement during scoping.
Agents → Agents (Staff)
Gorgias Agents map to Zendesk Agents.
How it maps
We map by email match against the Zendesk user table and set the role (admin, agent) based on the Gorgias permission level. Group membership from Gorgias maps to Zendesk Groups and the agent's group assignment. If a Gorgias agent was deactivated, we create them as inactive in Zendesk to preserve historical assignment.
Groups → Groups
Gorgias Groups (called Teams) map directly to Zendesk Groups.
How it maps
Group membership is preserved as agent-to-group assignments on the Agent record. Zendesk Groups are used for routing and assignment in combination with business rules, which we do not migrate as code.
Macros → Macros
Gorgias Macros map to Zendesk Macros.
How it maps
We export the macro body, conditions, and action sequence. Note that Gorgias supports dynamic action fields (refunds, order edits, shipping updates) that have no Zendesk equivalent without Shopify middleware or a Zendesk Shopify app integration. We flag every macro containing Gorgias-specific actions and document them in the inventory delivered post-migration for the admin to evaluate in context of the new Shopify integration.
- TicketsTickets1:1
- ConversationsComments1:1
- CustomersUsers1:1
- AgentsAgents1:1
- GroupsGroups1:1
- MacrosMacros1:1
+ 6 more in the mapping below
How Gorgias and Zendesk differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Gorgias | Zendesk |
|---|---|---|
| Pricing model | Per billable ticket volume with unlimited agent seats; overage at $0.40/ticket plus $1.50/AI Agent resolution | Per agent seat starting at $55/agent/month; AI resolutions at $1.50 committed or $2.00 pay-as-you-go as add-on |
| Channel support | Email, live chat, Facebook, Instagram, WhatsApp, SMS, voice (add-on) bundled at all tiers | Email and chat on Suite Team ($55/agent); voice, SMS, WhatsApp, Facebook, Twitter, Instagram as add-on bundles on Suite Growth and Enterprise |
| AI Agent model | Built-in Automate AI; $0.90-$1.00 per automated resolution on top of base subscription | Advanced AI add-on at $50/agent/month; $1.50-$2.00 per Automated Resolution on committed or pay-as-you-go plans |
| Ticket status model | Open, Pending, Solved, Closed; Pending and Solved both import as closed in Zendesk | New, Open, Pending, Hold, Solved, Closed; custom ticket statuses available on Suite Enterprise |
| Automation objects | Rules govern routing, assignment, and auto-response with conditions and actions | Triggers, Automations, Macros, and Views as separate objects with different condition syntax |
| Knowledge Base | Help Center with articles, categories, and multi-locale translations via separate API calls per locale | Help Center with articles and sections; community forums are standard on Suite Enterprise not Growth |
| Custom reporting | Built-in KPIs, CSAT, Revenue Dashboard; raw event-level data export limited | Explore with reporting workspace; custom report types available from Suite Enterprise upward |
What to watch for in a Gorgias to Zendesk migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Gorgias Solved and Pending both import as Zendesk Closed
Gorgias has five ticket statuses: Open, Pending, Solved, Closed, and Spam.
How we handle it
Zendesk's default ticket statuses are New, Open, Pending, Hold, Solved, and Closed. During import, Gorgias Solved and Pending both map to Zendesk Closed. The historical transition from Open to Solved to Pending (indicating a customer replied) cannot be replicated in Zendesk's audit trail. We flag this to the customer during scoping and recommend that if ticket status transition history is a compliance or audit requirement, the customer reviews whether Zendesk Custom Ticket Statuses on Suite Enterprise can approximate the original sequence.
Threads with 250+ comments split into multiple closed tickets
Gorgias's own Zendesk import documentation states that tickets with more than 250 comments are split into multiple closed tickets.
How we handle it
Our migration applies the same logic to prevent data loss. If your account has a significant number of high-comment-count threads, the split count is included in the scoping report so the customer can assess whether the split is operationally acceptable or whether archiving older resolved threads before migration is preferable.
Gorgias API rate limits restrict bulk export throughput
Gorgias API key integrations are limited to 40 requests per 20-second window; OAuth2 apps get 80 requests per 20 seconds.
How we handle it
Enterprise accounts have the same limits but in a 10-second window, making effective throughput lower. For accounts with hundreds of thousands of tickets, a naive sequential export will take days. We implement pagination with exponential backoff and parallelize across object types where the API permits, staying within the leaky bucket envelope. We request the customer increases their API rate limits before migration begins if the account supports it.
Gorgias Shopify order-context fields have no native Zendesk equivalent
Gorgias surfaces Shopify order data (order history, shipment status, return eligibility, customer lifetime value, AOV) directly inside the ticket view.
How we handle it
Zendesk does not offer this natively without a Shopify integration app from the Zendesk Marketplace and custom configuration. We map Gorgias customer attributes to Zendesk user fields, but order-level detail and in-ticket order actions (refunds, cancellations, edits) require the customer to install and configure a Zendesk Shopify app post-migration. We flag every Gorgias Rule that depends on Shopify order data so the admin knows which automations require the new integration before they can function.
Knowledge Base multi-locale translations require separate API calls per locale
Gorgias stores Knowledge Base article and category translations as separate field structures per locale, and the API does not return all locales in a single response.
How we handle it
We enumerate the enabled locales from account settings and issue one article fetch per locale. This adds API round trips proportional to the number of enabled locales. For accounts with 5+ locales, the Knowledge Base migration phase extends accordingly and we account for this in the timeline estimate during scoping.
How the migration runs
Discovery and API scoping
We audit the Gorgias account across plan tier, monthly billable ticket volume (including AI resolution count), enabled channels, active Rules, Macros, Views, Knowledge Base article and category count, enabled locales, and attachment storage volume.
What this step covers
We confirm API key access and test the 20-second rate-limit envelope with a trial export of 500 tickets to measure actual throughput. The discovery output is a written migration scope including object counts, estimated runtime per phase, and any account-level configuration (rate limit increase, additional admin credentials) required before migration begins.
Ticket status matrix and field mapping
We define the status translation matrix for all Gorgias ticket states (Open, Pending, Solved, Closed, Spam) into Zendesk ticket statuses, documenting that Solved and Pending both map to Closed.
What this step covers
We map priority, assignee, group, channel, and tags to their Zendesk equivalents. For high-comment-count threads (250+ comments), we document the split plan and confirm whether the customer prefers to archive resolved high-volume threads before migration or accept the split in Zendesk. We also map custom fields on tickets and customers to Zendesk field equivalents, flagging any Gorgias Shopify-specific fields that require a post-migration Zendesk Shopify app configuration.
Sandbox migration and reconciliation
We run a full migration into a Zendesk Sandbox (copy of production configuration) using a sample of production-like volume.
What this step covers
The customer reconciles record counts across all object types, spot-checks 25-50 tickets for accurate field mapping, reviews Knowledge Base article formatting in the Zendesk Help Center, and validates that tag names have not collided with reserved Zendesk system tags. Any mapping corrections and schema adjustments happen in the sandbox before production migration begins.
Agent and Group provisioning
We extract every distinct Gorgias Agent and map by email against the Zendesk user table.
What this step covers
Agents without a matching Zendesk user go to a reconciliation queue for the customer's Zendesk admin to provision. Group membership migrates as Zendesk Group assignments on each agent record. We cannot proceed past agent provisioning until all assignee references in the ticket migration can be resolved to an active Zendesk user.
Production migration in dependency order
We run production migration in dependency order: Zendesk Help Center Sections (prerequisite for article placement), Help Center Articles with multi-locale translations per locale, Users from Gorgias Customers, Agents, Groups, Tags, Macros, Views, Tickets with Conversations (with the 250-comment split applied), and CSAT ratings.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. Conversations with attachments download from Gorgias and re-upload to Zendesk with the parent comment reference resolved.
Cutover, validation, and Rules inventory handoff
We freeze writes in Gorgias during the cutover window, run a final delta migration of any tickets created or modified during the migration, then enable Zendesk as the system of record.
What this step covers
We deliver the Rules inventory document listing every Gorgias Rule with its trigger, conditions, and actions, noting which rules depend on Shopify order data and require a Zendesk Shopify app for full functionality. We support a one-week hypercare window where we resolve any record reconciliation issues. We do not rebuild Gorgias Rules as Zendesk Triggers or Automations inside the migration scope; that work is handled by the customer's Zendesk admin or a Zendesk partner.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with ticket volume, attachment storage size, Knowledge Base article count, and whether delta migration is required. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Gorgias to Zendesk →Why teams move from Gorgias to Zendesk
- Gorgias ticket-volume pricing with AI outcome fees compounds unpredictably during seasonal spikes. A Shopify brand with 5,000 billable tickets and a 40% AI resolution rate pays $0 base ticket cost (if on Enterprise) plus $1.50 times 2,000 AI resolutions, totaling $3,000 in AI fees alone. Zendesk's per-agent-seat model at $55 per agent for the same team costs $220 per month with no variable AI line. Teams with high ticket volume but small agent headcount migrate to Zendesk for cost predictability and explicit per-seat budgeting rather than billable-event billing.
- G2 reviews and comparison analyses document performance and glitch reports for Gorgias at higher ticket volumes. Teams running 3,000-5,000 tickets per month report the platform becomes unreliable, with ticket loading delays and UI lag. Zendesk's infrastructure handles higher volume with less UI degradation, which is a common reason cited by teams migrating out of Gorgias as their business scales through peak seasons.
- Gorgias Knowledge Base, Macros, and Rules do not export cleanly via native tooling, making competitive migrations complex without a specialist integration partner. Reviewers on G2 and Capterra cite this as a switching cost that outweighs the platform's Shopify-native benefits when teams decide to evaluate alternatives. Zendesk's Help Center import tooling and macro export functionality make the return migration path more straightforward.
- Teams needing skills-based routing, advanced SLA configuration, or enterprise reporting features find these locked behind Zendesk Suite Enterprise at comparable or lower total cost than Gorgias Advanced. Zendesk's Suite tiers bundle multiple channels and add-ons in a structured way that enterprise procurement teams find easier to negotiate and audit versus Gorgias's layered base-plus-overage-plus-AI model.
- Custom reporting depth and the ability to export raw event-level data for BI tooling is limited in Gorgias. Teams with evolving business intelligence needs that require data warehouse integration or complex multi-dimensional pipeline analysis move to Zendesk's Explore workspace or to an external BI tool fed by Zendesk's API, where raw event data is more accessible.
Questions, answered
Gorgias to Zendesk migration questions
How long does a Gorgias to Zendesk migration take?
Most migrations land between three and five weeks for accounts under 50,000 tickets and 10,000 customers with a clean Knowledge Base and no concurrent-write cutover window. Migrations with large attachment volumes, high-comment-count threads requiring the 250-comment split logic, multi-locale Knowledge Base content (5+ locales), or delta synchronization for a live-cutover approach move to seven to eleven weeks because of per-locale Knowledge Base API calls, delta migration time, and sandbox validation cycles.
Do Gorgias Rules, Macros, and Views migrate to Zendesk?
Macros and Views migrate as active objects. Rules do not migrate as code. Gorgias Rules use a condition-action model that differs from Zendesk Triggers and Automations in trigger syntax, action types, and execution context. We deliver a written inventory of every Gorgias Rule with its trigger event, conditions, and actions, including a flag for every rule that references Gorgias Shopify order data so the customer's admin knows which rules require a Zendesk Shopify app configuration to function post-migration. The admin rebuilds rules as Zendesk Triggers or Automations using this inventory. Voice routing rules, SLA-based assignment rules, and intent-detection triggers are documented with their Zendesk counterparts noted.
What happens to our Knowledge Base articles and translations?
We migrate Knowledge Base articles and categories from Gorgias to the Zendesk Help Center. Category hierarchy and ordering are preserved. Article status (draft, published, unlisted) translates directly. Multi-locale articles are fetched from Gorgias via separate API calls per enabled locale and mapped to Zendesk's locale-aware article structure. We do not migrate the Help Center appearance, custom scripts, or brand styling; these must be reapplied manually in Zendesk's Help Center theme editor post-migration. The total number of enabled locales is captured during scoping so the Knowledge Base migration timeline is accurately estimated.
Can we keep writing to Gorgias during migration and sync the changes to Zendesk?
Yes, we can configure a concurrent-write delta migration window. During the window, new tickets created in Gorgias after the initial export are captured and migrated in a delta pass at cutover. Note that Gorgias Rules that fire on new tickets during this window will not be recreated in Zendesk until the admin rebuilds them, so tickets created during the delta window may not receive the same routing and auto-response as tickets created before migration. We document this gap in the Rules inventory so the admin knows which Rules to prioritize.
Will our Zendesk admin need to rebuild automations from scratch?
Yes, for Rules. Gorgias Rules and Zendesk Triggers/Automations are different systems with incompatible condition syntax and action models. We deliver a complete written inventory of every Gorgias Rule (trigger, conditions, actions) and note which ones reference Gorgias Shopify data or other Gorgias-native actions. The Zendesk admin rebuilds these using the inventory as a specification. Macros and Views are migrated as active objects and do not require rebuild. SLA policies migrate as configuration records that the admin reviews and applies in Zendesk Admin Center post-import.
Do we lose ticket status transition history?
Gorgias Solved and Pending statuses both import as Zendesk Closed. The transition from Open to Solved to Pending (indicating a customer replied and the ticket reopened) cannot be replicated in Zendesk's native audit trail. The final status is preserved but the historical state transitions are not. If ticket status audit history is a compliance or SLA reporting requirement, we recommend Zendesk Suite Enterprise with Custom Ticket Statuses to approximate the original sequence, and we flag this during scoping so the customer's procurement team can evaluate the tier decision.
Related migrations
Sources: official documentation
- About ticket import — Zendesk help
- How can I bulk update users — Zendesk help
- About custom objects — Zendesk help
- Bulk importing user data with the data importer — Zendesk help
- Help Desk Migration — Gorgias Help Center
- Create a custom field — Gorgias documentation
- Import and export Macros — Gorgias Help Center
Get a quote
Moving from Gorgias to Zendesk?
Tell us roughly how many records and objects you have. We scope the mapping and the Zendesk setup with you, then send a quote.
Get a quote