ZendeskGorgias

Zendesk to Gorgias migration

Migration specialists move your tickets, public comments and private comments into Gorgias, check a sample with you first, and count every record on both sides.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.

Last updated November 2026 · 11 object types mapped

  • 1000+migrations
  • 15 yearsof collective experience
  • AICPA SOC 2 Type IISOC 2 Type IIGDPR compliantHIPAA compliant

Zendesk to Gorgias at a glance

A Zendesk to Gorgias migration has to go further than Gorgias's own Zendesk importer, which skips attachments and ratings, closes pending and solved tickets and stops at two years. We move the full Zendesk history through the API, and Zendesk stays your live inbox until the final delta sync.

Objects mapped
11
in this route's mapping
Typical timeline
About 10 business days end to end
3 phases
Free sample
100 records
checked by your team first
Quote
Fixed
within 24 hours
Who it is for
Support teams moving to Gorgias to see Shopify orders beside every ticket, and teams that tried Gorgias's importer and found gaps.
What does not move
Zendesk triggers, automations, SLA policies and views stay behind, each listed with what it does today for your admin to rebuild in Gorgias.
What sets the scope
Ticket count, attachment volume, the status rule, long threads, the Help Center, and how much of the two-year limit of Gorgias's importer you need to go past.

What moves

What moves from Zendesk to Gorgias

End users become Customers, tickets become Tickets, public comments become messages and private comments become internal notes, with the attachments Gorgias's own importer skips and ratings on request.

  • 11 included
ZendeskGorgias
  • End usersCustomers

    Matched by email, with the Zendesk user ID stored in external_id.

  • TicketsTickets

    Original created and closed dates are set and the imported flag is on. The Zendesk ticket ID goes in external_id.

  • Public commentsTicket messages

    Each carries its original send time so Gorgias does not email it again.

  • Private commentsTicket messages, internal-note channel

    Posted on the internal-note channel with their author and time.

  • Ticket statusOpen or closed

    Pending, hold, solved and closed all fold into the two Gorgias statuses by the rule signed off at mapping.

  • Ticket priorityTicket priority

    Carried across to Gorgias's priority levels.

  • Ticket fieldsTicket custom fields

    Mapped field by field, including the lookup fields Gorgias's own importer skips.

  • TagsTags

    Kept with their names, which Gorgias treats as case sensitive.

  • Agents and groupsUsers and teams

    Created before tickets so every assignee exists when the ticket loads.

  • AttachmentsMessage attachments

    Passed by URL with name and content type on the message they came from.

  • Help Center articles and categoriesHelp Center articles and categories

    Gorgias imports a Zendesk Help Center directly or from a CSV. The route is agreed at scoping.

Looking for another object?Field-level mapping is reviewed with you during scoping.

What does not move

What does not move from Zendesk to Gorgias as-is

Triggers, automations, SLA policies, views and Guide themes are configuration with no Gorgias import, so they are rebuilt as rules and views.

OrganizationsOn request
In Gorgias: Customer field or tagGorgias has no company object in its API, so the organization is flattened onto the customer.
MacrosOn request
Reply text and status-change actions move. Gorgias brings any other macro action in as an empty list, so those are rebuilt.
Satisfaction ratingsOn request
In Gorgias: Satisfaction surveysCreated through the API as surveys with the score and a null send time, so Gorgias never sends them. Gorgias's own importer skips ratings.
Side conversationsOn request
In Gorgias: Internal notesRead separately because Zendesk records their messages as events, and posted as internal notes.
Triggers and automationsNot migrated
In Gorgias: RulesConfiguration, rebuilt by your admin from the list we hand over.
SLA policies and viewsNot migrated
In Gorgias: Views and Gorgias SLAsSet up again in Gorgias on the migrated tags, statuses and fields.
Guide themes, Zendesk apps and Talk dataNot migrated
No Gorgias counterpart.

Free sample migration of 100 of your records. Fixed quote within 24 hours.

Scope my migration

Timeline

Zendesk to Gorgias migration timeline

Estimated total

About 10 business days

end to end

  • MigrateXwe run it
  • Youyour team acts
  • Bothon a call together
  1. Preparation

    Day 1-2

    • Scoping call

      Both0.5 day

      We settle the status rule, how Zendesk organizations land on customers, which macros move, and whether Gorgias's importer handles any part of the load.

    • Connect Zendesk and Gorgias

      You0.5 day

      You approve a Zendesk OAuth client. A Gorgias admin creates an API key or OAuth2 app, and the first loads go to a test account before production.

    • Field, tag and macro review

      Both1 day

      Ticket fields to Gorgias custom fields, tags to tags, agents and groups to users and teams. Lookup fields are checked, since Gorgias's importer skips them and brings integers in as decimals.

  2. Migration

    Day 3-7

    • Free sample

      MigrateX1 day

      100 of your records, picked for the longest threads, the most attachments and the oldest closed tickets, loaded into the test account.

    • You review the sample

      You1 day

      Your support lead opens the tickets as an agent and checks message order, internal notes, status, customer match and the Shopify panel.

    • Full load

      MigrateX2-3 days

      Customers and users first, then tickets with their messages, then attachments and surveys, paced to the request window of your Gorgias plan.

    • Delta sync

      MigrateX0.5 day

      Tickets changed in Zendesk since the full load are matched on the stored Zendesk ID and updated, never duplicated.

  3. Validation

    Day 8-10

    • Reconciliation report

      MigrateX1 day

      Zendesk tickets against Gorgias tickets by status and year, comments against messages, attachments against files, and every thread that was split.

    • Rules, email and sign-off

      You1-2 days

      Your admin switches on the rebuilt rules, the mailbox is connected to Gorgias in one window, and Zendesk stays read-only until you agree.

An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.

Known risks

Every known risk on this route, with how we handle it

  • 3 solved
  • 5 handled
  1. 01SolvedMost critical

    Gorgias's own Zendesk importer drops attachments and ratings

    The problem

    Run alone, Gorgias's importer leaves behind the screenshots, order photos and CSAT scores sitting on old tickets.

    How we handle it

    Files are read from Zendesk and passed to Gorgias by URL on each message, and ratings are created as satisfaction surveys with the send turned off. You choose on the scoping call whether MigrateX loads everything or only fills the gaps the importer leaves.

    Source: Gorgias Help Center, checked 15 Nov 2026

  2. 02Handled

    Pending, on hold and solved all have to become open or closed

    The problem

    Zendesk runs a longer status path and Gorgias keeps two statuses. Its own importer closes pending and solved tickets, which hides a pending ticket your team still owes a reply.

    How we handle it

    The rule is written in the mapping sign-off before any ticket loads. Open and pending can stay open, solved and closed become closed, and the original Zendesk status is kept in a ticket field or tag so a report can still split them.

    Source: Gorgias Help Center, checked 15 Nov 2026

  3. 03Handled

    A very long thread may not stay one ticket

    The problem

    Gorgias's importer cuts a ticket of more than 250 comments into several closed tickets. Zendesk lets a ticket hold 5,000. The Gorgias pages we read state no maximum number of messages for a ticket created through the API.

    How we handle it

    The longest Zendesk threads go into the free sample, so you see how they land through the API before the full load.

    Source: Gorgias Help Center, checked 15 Nov 2026

  4. 04Solved

    A reply loaded without its sent time goes out to the customer

    The problem

    A Zendesk public comment replayed without its sent time would become a fresh email to a customer whose order was closed years ago.

    How we handle it

    Every public comment carries its original send time, and private comments go in on the internal-note channel. The sample loads into a test account first, so you see that no mail leaves.

    Source: Gorgias developer documentation, checked 15 Nov 2026

  5. 05Handled

    Zendesk organizations have no Gorgias counterpart

    The problem

    Zendesk ties users to an organization with its own fields. Gorgias has a Customer object and no company object in its API, so the organization record and the link from a user to it cannot be carried as they are.

    How we handle it

    The organization name and the fields you choose are written to the Gorgias customer as a custom field or tag, agreed with you before the sample.

    Source: Gorgias developer documentation, checked 15 Nov 2026

  6. 06Handled

    Whether loaded tickets use up the plan's billable tickets is not published

    The problem

    Gorgias bills a ticket once a message is sent from its helpdesk, and its pages do not say whether tickets created through the API with closed history count. A brand on a small plan could meet an overage it did not plan for.

    How we handle it

    We confirm it with Gorgias before the production load, and we load history as closed tickets with no reply sent from the helpdesk. You see the answer before any ticket moves.

    Source: Gorgias Help Center, checked 15 Nov 2026

  7. 07Handled

    Zendesk triggers and automations do not convert to Gorgias rules

    The problem

    Gorgias's importer does not carry rules, and nothing converts a Zendesk trigger into one. Routing that depends on order data from Shopify also has no Zendesk equivalent to copy.

    How we handle it

    Each trigger and automation is listed with its conditions and actions. Your admin rebuilds them in Gorgias against the migrated tags and fields, and the load runs first so the new rules never see old tickets.

    Source: Gorgias Help Center, checked 15 Nov 2026

  8. 08Solved

    Connecting email before the history lands creates open and closed mismatches

    The problem

    Gorgias says to run the Zendesk import first and import emails after, to avoid inconsistencies. Pointing the same mailbox at both systems early also splits one conversation across two help desks.

    How we handle it

    The mailbox moves last, in one planned window after the delta sync. Zendesk stays your live inbox until then.

    Source: Gorgias Help Center, checked 15 Nov 2026

Technical profile

What makes this route technical

Zendesk paces the export through per-ticket comment reads, and Gorgias paces the load at 40 API requests every 20 seconds on an API key.

Exporting from Zendesk: comment bodies need their own pass
The incremental ticket export carries no comment bodies. Adding the comment_events sideload to the ticket events export returns full comment data, and Zendesk's comments endpoint lists at most 100 comments a page, oldest first.

Source: Zendesk developer documentation, checked 15 Nov 2026

Exporting from Zendesk: up to 5,000 comments on one ticket
A Zendesk ticket can hold 5,000 comments, public and private together, and a thread that long takes many calls to read.

Source: Zendesk developer documentation, checked 15 Nov 2026

Exporting from Zendesk: closed tickets leave the list calls
Zendesk archives most tickets 120 days after they are closed, and the Listing Tickets endpoint does not return archived ones. The incremental export does, so the inventory is taken from it.

Source: Zendesk Help Center, checked 15 Nov 2026

Gorgias's own importer: what it brings
Under Settings, Advanced, Historical Imports, an admin on any Helpdesk plan can import tickets, macros, users, tags and ticket fields from Zendesk, for the most recent two years.

Source: Gorgias Help Center, checked 15 Nov 2026

Gorgias's own importer: pace
Gorgias says its Zendesk importer averages around 720 tickets an hour, so a large account runs for days.

Source: Gorgias Help Center, checked 15 Nov 2026

Gorgias's own importer: what it skips
Gorgias's Zendesk importer brings no ticket attachments and no rating or satisfaction survey data.

Source: Gorgias Help Center, checked 15 Nov 2026

Gorgias's own importer: statuses and long threads
Pending and solved Zendesk tickets import as closed, and a ticket with more than 250 comments is split into several closed tickets.

Source: Gorgias Help Center, checked 15 Nov 2026

Importing into Gorgias: replies need a sent time
A message created without sent_datetime is sent by Gorgias to its recipients, so every reply already delivered in Zendesk carries the time it went out.

Source: Gorgias developer documentation, checked 15 Nov 2026

Importing into Gorgias: surveys without a send
A satisfaction survey can be created with a score and a null should_send_datetime, which stops Gorgias from sending it to the customer.

Source: Gorgias developer documentation, checked 15 Nov 2026

Importing into Gorgias: the API-key window
An API-key integration may make 40 requests in a 20-second window. An OAuth2 app may make 80.

Source: Gorgias developer documentation, checked 15 Nov 2026

Importing into Gorgias: older emails keep only stripped text
Since 8 September 2026, Gorgias archives the original body of an email 30 days after it is sent or received and keeps it at a body URL, when a stripped version exists.

Source: Gorgias developer documentation, checked 15 Nov 2026

Facts checked 15 Nov 2026 against Zendesk and Gorgias documentation. Each fact links its source.

Zendesk to Gorgias questions

Still unsure? Ask the engineer who would run this migration, not a sales rep.

How do I migrate from Zendesk to Gorgias?

Through Gorgias's built-in Zendesk importer, which covers two years and skips attachments and ratings, or through a managed API migration that keeps both. MigrateX writes the full Zendesk history to Gorgias with original dates and internal notes, after a free 100-record sample.

Can I use Gorgias's own Zendesk import, and what does it skip?

Yes, if two years of tickets, macros, users, tags and ticket fields is enough. It skips attachments, ratings and lookup fields, keeps only reply-text and status-change macro actions, and imports pending and solved tickets as closed.

Why were my imported tickets split into smaller tickets?

Gorgias's Zendesk importer splits any ticket of more than 250 comments into several closed tickets, while a Zendesk ticket can hold 5,000. Your longest threads go into the free sample, so you see how they land first.

Do attachments and CSAT survey results come across?

Yes, with an API load: attachments go by URL on the message they came from, and Zendesk ratings become satisfaction surveys that Gorgias never sends. Gorgias's own importer brings neither.

How are Zendesk statuses mapped to Gorgias's open and closed?

Gorgias has only open and closed. Our usual rule keeps new, open and pending tickets open and turns solved and closed into closed, with the original Zendesk status kept in a field or tag. You sign off the rule before the sample.

Will imported tickets count towards my billable ticket limit?

Gorgias does not say. It bills a ticket once a message is sent from its helpdesk, so we load history with no reply sent and confirm the answer with Gorgias before the production load.

Do Zendesk macros and triggers carry over?

Macros carry over with reply-text and status-change actions only. Triggers and automations do not convert: your admin gets a list of each with its conditions and actions, and the rebuilt rules go live after the history loads.

How long does a large Zendesk to Gorgias migration take?

About 10 business days end to end in our default plan. Gorgias's own importer runs at about 720 tickets an hour and an API-key load at 40 requests every 20 seconds, so a large account runs for days either way. The free sample measures your pace.

Do Zendesk Help Center articles move to Gorgias?

Yes. Gorgias imports a Zendesk Help Center directly or from a CSV, and the route is agreed with you. Article addresses change, and redirects from the old ones are scoped with you during the free sample.

What does a Zendesk to Gorgias migration cost?

The price is set by what moves: tickets with their comments and attachments, the Help Center, and how many macros and fields need mapping. You get a fixed quote within 24 hours of the scoping call, after a free sample migration of 100 of your records.

How it compares

Four ways to run Zendesk to Gorgias

The same data, moved four different ways. This is what changes between them.

Object coverage (cases, emails, comments, files, Knowledge)

  • MigrateX

    Every object in the mapping on this page, plus the ones you ask for during scoping.

  • Automated migration software

    Tickets and contacts are covered. Linked records, files and knowledge often are not.

  • Vendor CSV import

    One object per file, and only the fields the export template exposes.

  • In-house scripts

    Whatever you have time to build before the cutover date.

Public replies vs internal notes

  • MigrateX

    Each entry is posted separately, private stays private, public stays public.

  • Automated migration software

    Threads usually arrive, but per-entry author and visibility can be flattened.

  • Vendor CSV import

    Notes collapse into one field on the ticket, if they come across at all.

  • In-house scripts

    Possible, but it is the part teams most often run out of time for.

Attachments

  • MigrateX

    Uploaded against the right note, and re-hosted with a link when they exceed the Gorgias cap.

  • Automated migration software

    Supported up to the destination cap. Oversize files are skipped.

  • Vendor CSV import

    Not carried by a CSV import.

  • In-house scripts

    Needs its own download, retry and upload pipeline.

Original IDs cross-referenced

  • MigrateX

    Every source id is stored on the destination record and handed back as a map.

  • Automated migration software

    Often kept as a tag or a single text field.

  • Vendor CSV import

    Lost once the file is imported.

  • In-house scripts

    Only if you design the mapping table up front.

Delta sync before cutover

  • MigrateX

    Included. Anything created or changed during the bulk pass is synced at cutover.

  • Automated migration software

    Usually a paid upgrade on the top tier.

  • Vendor CSV import

    You would re-export and re-import by hand.

  • In-house scripts

    Requires change tracking and idempotent writes on both sides.

Rate-limit handling

  • MigrateX

    Paced to your plan limits, honours Retry-After, and resumes from a checkpoint.

  • Automated migration software

    Backs off, but a long run can still stall and leave partial records.

  • Vendor CSV import

    Not applicable, and the file size limits bite instead.

  • In-house scripts

    The most common reason a home-grown run dies overnight.

Validation report

  • MigrateX

    Counts per object and per status on both sides, with every default and placeholder listed.

  • Automated migration software

    A run log and an error list, rather than a reconciliation.

  • Vendor CSV import

    Row counts in a spreadsheet.

  • In-house scripts

    You write the reconciliation queries yourself.

Rollback plan

  • MigrateX

    Every write is tagged, so a batch can be reversed without touching your own records.

  • Automated migration software

    Some approaches can clear a migration, some cannot.

  • Vendor CSV import

    Manual cleanup of everything the import created.

  • In-house scripts

    Only if you built the tagging in from the start.

Who does the work

  • MigrateX

    A MigrateX engineer runs it and stays on the cutover call.

  • Automated migration software

    You run the software. Support answers tickets.

  • Vendor CSV import

    Your admins, one file at a time.

  • In-house scripts

    Your engineers, instead of your roadmap.

Guides

Guides for a Zendesk to Gorgias migration

Related routes

Built for your security review, from the first call.

Read how we handle your data
  • AICPA SOC 2 Type II

    SOC 2 Type II

    Independently audited controls over how we handle your data.

  • GDPR compliant

    Data processing agreement available.

  • HIPAA compliant

    Business associate agreement available.

Start your Gorgias move with 100 of your records.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.