FreshdeskGorgias

Freshdesk to Gorgias migration

Migration specialists move your tickets, replies and private notes 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 · 10 object types mapped

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

Freshdesk to Gorgias at a glance

Gorgias has no built-in Freshdesk importer, so a Freshdesk to Gorgias migration is an API load from start to finish. The catch is on the Freshdesk side: a plain ticket list shows 30 days and ends at 30,000 tickets. We read your whole history in date windows, and Freshdesk stays live until the delta sync.

Objects mapped
10
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 at online stores leaving Freshdesk for Gorgias's ecommerce helpdesk.
What does not move
Freshdesk scenario automations, dispatch and supervisor rules, SLA policies and business hours stay behind, listed for your admin to rebuild in Gorgias.
What sets the scope
Years of history behind the 30-day list, ticket and attachment volume, pending and waiting tickets, canned responses with placeholders, and the solution articles.

What moves

What moves from Freshdesk to Gorgias

Contacts become Customers, tickets become Tickets with their original dates, replies become messages and private notes become internal notes, with attachments on the message they came from.

  • 10 included
FreshdeskGorgias
  • ContactsCustomers

    Matched by email, with the Freshdesk contact ID stored in external_id.

  • TicketsTickets

    Created, closed and updated dates are set, the imported flag is on, and the Freshdesk ticket ID goes in external_id.

  • RepliesTicket messages

    Posted with the agent flag, the original send time and the sender, in order.

  • Private notesTicket messages, internal-note channel

    Kept off the customer-facing thread by the internal-note channel.

  • StatusOpen or closed

    Open, pending, waiting, resolved and closed fold into two. Pending can be kept as a tag.

  • PriorityTicket priority

    Freshdesk's four levels line up with Gorgias's low, normal, high and critical.

  • Ticket and contact fieldsCustom fields

    Created as typed Gorgias fields before tickets load.

  • TagsTags

    Carried over by name.

  • Agents and groupsUsers and teams

    Created first, so each ticket lands with its assignee.

  • AttachmentsMessage attachments

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

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

What does not move

What does not move from Freshdesk to Gorgias as-is

Scenario automations, dispatch and supervisor rules, SLA policies and business hours are configuration that Gorgias cannot import, so they are rebuilt as rules and settings.

CompaniesOn request
In Gorgias: Customer fieldGorgias has no company object in its API, so the company name is written to the customer.
Solution articles, folders and categoriesOn request
In Gorgias: Help Center articles and categoriesLoaded from a CSV, because Gorgias imports articles directly only from Zendesk, HelpDocs, Re:amaze and Intercom.
Canned responsesOn request
In Gorgias: MacrosReply text moves. Placeholders are checked by hand.
Scenario automations, dispatch and supervisor rulesNot migrated
In Gorgias: RulesConfiguration, rebuilt as Gorgias rules by your admin from the list we hand over.
SLA policies and business hoursNot migrated
Settings, set up again in Gorgias.
Portal themes and marketplace appsNot migrated
No Gorgias counterpart.

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

Scope my migration

Timeline

Freshdesk 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 agree the date windows for history, how pending and waiting tickets are placed, and how Freshdesk companies are kept on customers.

    • Connect Freshdesk and Gorgias

      You0.5 day

      You share a Freshdesk API key with read access. A Gorgias admin creates an OAuth2 app or API key, and the first loads go to a test account.

    • Field, tag and canned response review

      Both1 day

      Ticket and contact fields to Gorgias custom fields, tags to tags, agents and groups to users and teams. Canned responses with placeholders are marked for hand checks.

  2. Migration

    Day 3-7

    • Free sample

      MigrateX1 day

      100 of your records, taken from different years so the date windows are tested, with long threads and private notes included.

    • You review the sample

      You1 day

      Your team opens the tickets in Gorgias and checks the original dates, status, customer and company, and where the private notes sit.

    • Full load by date window

      MigrateX2-3 days

      Customers and users first, then each window of tickets with its messages and attachments, paced to your Gorgias request limit.

    • Delta sync

      MigrateX0.5 day

      Tickets updated in Freshdesk since the full load are matched on the stored Freshdesk ID and brought up to date.

  3. Validation

    Day 8-10

    • Count reconciliation

      MigrateX1 day

      Ticket counts per date window in Freshdesk against Gorgias, replies against messages, and attachments against files.

    • Rules on and sign-off

      You1-2 days

      Your admin turns on the rebuilt rules, connects the store and the mailbox, and Freshdesk 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

  • 2 solved
  • 6 handled
  1. 01SolvedMost critical

    A quick Freshdesk export puts one month in Gorgias and leaves the rest

    The problem

    Freshdesk's ticket list shows 30 days by default and ends at 30,000 tickets. A load built on that list gives Gorgias a month of tickets, while years of order disputes, refunds and returns stay behind in Freshdesk.

    How we handle it

    We read history in date windows, count tickets per window against Freshdesk, and only then write to Gorgias. The counts are in the reconciliation report you sign off.

    Source: Freshdesk API documentation, checked 13 Nov 2026

  2. 02Solved

    Gorgias offers no Freshdesk importer

    The problem

    Teams expecting to press a button in Gorgias find an importer for Zendesk and nothing for Freshdesk.

    How we handle it

    MigrateX runs the whole move as an API load, tried first on a free sample of 100 of your records.

    Source: Gorgias Help Center, checked 15 Nov 2026

  3. 03Handled

    Reading Freshdesk is the slower half of the job

    The problem

    Freshdesk lists tickets at 40 calls a minute on Growth, then needs more calls to read each conversation. Gorgias takes about 2 requests a second on a self-serve plan, so the writer waits for the reader.

    How we handle it

    Reading starts on day one and runs ahead of the writing, in date windows. The free sample measures the real rate on your Freshdesk plan and your Gorgias plan before the schedule is fixed.

    Source: Freshdesk support documentation, checked 13 Nov 2026

  4. 04Handled

    Five Freshdesk statuses become two

    The problem

    Freshdesk tickets can be open, pending, waiting, resolved or closed. Gorgias accepts only open and closed, so a ticket waiting on a customer has to be placed in one of them.

    How we handle it

    Resolved and closed tickets go in as closed. Open tickets stay open. Pending and waiting are decided with you at mapping, and the original status can be kept as a tag so a view can still find them.

    Source: Gorgias developer documentation, checked 15 Nov 2026

  5. 05Handled

    Rebuilt rules still run on tickets loaded through the API

    The problem

    Freshdesk scenario automations, dispatch rules and supervisor rules are not copied, and they are rebuilt as Gorgias rules. On the API channel, only auto-reply rules are skipped, so a rebuilt tagging rule can touch every loaded ticket.

    How we handle it

    History loads before the rebuilt rules are switched on, and your admin turns them on after the delta sync.

    Source: Gorgias developer documentation, checked 15 Nov 2026

  6. 06Handled

    Canned responses become macros that need checking

    The problem

    A Gorgias macro is a list of actions that can change and reply to tickets, while a Freshdesk canned response is reply text. The text arrives as a macro, and any placeholder in it has to be checked in Gorgias before agents use it.

    How we handle it

    We list every canned response that contains a placeholder, and your team checks them on the sample before the full load.

    Source: Gorgias developer documentation, checked 15 Nov 2026

  7. 07Handled

    Freshdesk's three-level article tree goes in by CSV

    The problem

    Freshdesk keeps solution articles in categories and folders. Gorgias has no direct importer for them from Freshdesk, so articles go in from a CSV, and images inside them need to be checked after import.

    How we handle it

    We write the CSV from the Freshdesk hierarchy, load it into the Gorgias Help Center, and open a sample of articles for image and link checks.

    Source: Gorgias Help Center, checked 15 Nov 2026

  8. 08Handled

    Loaded history could meet the plan's ticket allowance

    The problem

    Each Gorgias plan has a baseline of billable tickets and charges overage beyond it. Whether tickets created through the API with closed history count towards that baseline is not documented.

    How we handle it

    We put the question to Gorgias before the production load and load history without sending a reply from the helpdesk, so you have the answer before the first ticket moves.

    Source: Gorgias Help Center, checked 15 Nov 2026

Technical profile

What makes this route technical

Freshdesk paces the export with a 30-day default list and a lower call budget for listing, and Gorgias paces the load at 40 to 80 requests every 20 seconds.

Exporting from Freshdesk: a plain list reaches back one month
A Freshdesk ticket list returns only tickets created in the past 30 days unless a date filter is set, and it stops at 300 pages, which is 30,000 tickets. Longer history is read in date windows.

Source: Freshdesk API documentation, checked 13 Nov 2026

Exporting from Freshdesk: listing has its own call budget
Freshdesk allows 100, 400 and 700 calls a minute by plan, and lowers the budget for ticket listing to 40, 100 and 200 a minute. Each ticket's conversation is then read in further calls.

Source: Freshdesk support documentation, checked 13 Nov 2026

Exporting from Freshdesk: the list-view export is partial
Exporting from a Freshdesk list view leaves out full conversations and archived tickets, so it cannot stand in for a migration source.

Source: Freshdesk support documentation, checked 13 Nov 2026

Importing into Gorgias: no Freshdesk importer
Gorgias documents a built-in Historical Imports importer for Zendesk, and none for Freshdesk. Its Help Center import offers a direct route only from Zendesk, HelpDocs, Re:amaze and Intercom.

Source: Gorgias Help Center, checked 15 Nov 2026

Importing into Gorgias: history keeps its dates
Creating a ticket accepts created, opened, closed, updated and trashed times. An imported flag on the ticket marks the ticket and every message in it as a historical import.

Source: Gorgias developer documentation, checked 15 Nov 2026

Importing into Gorgias: customers can arrive with the ticket
A customer is created from an email, a name, channels and an external_id, and can also be supplied inline when a ticket is created.

Source: Gorgias developer documentation, checked 15 Nov 2026

Importing into Gorgias: external IDs and sent times
A message that was already delivered must carry its sent_datetime, or Gorgias sends it again. Each message also takes an external_id, which holds the Freshdesk reply ID.

Source: Gorgias developer documentation, checked 15 Nov 2026

Importing into Gorgias: the OAuth2 window
OAuth2 apps may make 80 requests in a 20-second window and API-key integrations 40. Enterprise accounts keep the counts but use a 10-second window.

Source: Gorgias developer documentation, checked 15 Nov 2026

Importing into Gorgias: the rate on the plan table
Gorgias's pricing page lists an API rate of 2 requests a second on self-serve plans and 4 on Enterprise.

Source: Gorgias website, checked 15 Nov 2026

Importing into Gorgias: the API channel and rules
Tickets created on the API channel do not trigger auto-reply rules, but other rule actions, such as auto-tag, still run, and keyword rules need stripped_text to match.

Source: Gorgias developer documentation, checked 15 Nov 2026

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

Freshdesk to Gorgias questions

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

How do I migrate from Freshdesk to Gorgias?

Gorgias has no built-in Freshdesk import, so the move is an API load: MigrateX reads your Freshdesk history in date windows and writes tickets, customers and notes to Gorgias with their original dates, after a free 100-record sample.

Does Gorgias import from Freshdesk on its own?

No. Gorgias's built-in importer is for Zendesk only. Its Gmail or Outlook email import brings mailbox history, not your Freshdesk tickets, notes or fields.

Why is my Freshdesk export missing older tickets?

Freshdesk's ticket list returns only the last 30 days by default and stops at 300 pages, and the list-view export leaves out full conversations and archived tickets. We page through the whole history by date and reconcile counts before writing to Gorgias.

How are Freshdesk statuses mapped to open and closed?

Resolved and closed become closed, and open stays open. Pending and waiting are decided with you at mapping, usually as open with a tag that keeps the original Freshdesk status.

Do canned responses become Gorgias macros?

Yes, as macros with their reply text. Each canned response with a placeholder is flagged for your team to check on the sample, and Freshdesk scenario automations are rebuilt as Gorgias rules.

Do Freshdesk solution articles move to the Gorgias Help Center?

Yes, from a CSV, because Gorgias imports articles directly only from Zendesk, HelpDocs, Re:amaze and Intercom. Images are checked after import, and redirects from the old addresses are scoped with you during the free sample.

Will Shopify orders show on the tickets after the move?

Yes, once you connect the store. Gorgias fills its customer panel from Shopify, not from the Freshdesk ticket, so each migrated ticket is matched to its customer by email, and Gorgias then imports customer profiles and order history in the background.

Will the move use up my Gorgias ticket allowance?

Gorgias does not say. A ticket is billable once a message is sent from the helpdesk, and plans charge overage beyond their baseline, so we load history with no reply sent and confirm with Gorgias before the production load.

How long does a Freshdesk to Gorgias migration take?

About 10 business days end to end. The Freshdesk read is the slower half, with ticket listing capped at 40 to 200 calls a minute by plan, against Gorgias's 40 to 80 requests every 20 seconds. The free sample measures the pace on your accounts.

What does a Freshdesk to Gorgias migration cost?

The price is set by what moves: the tickets behind the 30-day list, their notes and attachments, the canned responses and the solution articles. 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 Freshdesk 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.

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.