---
title: "Gorgias to Freshdesk Migration: Field Mapping & Rollback"
description: "Migrate Gorgias to Freshdesk with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/helpdesk/gorgias/to/freshdesk"
---

# Gorgias to Freshdesk migration

We migrate Tickets, Customers, Conversations, and Knowledge Base content from Gorgias into Freshdesk with the billing model shift addressed up front, macro and rule logic preserved as written inventory, and every custom field type mapped to the correct Freshdesk field definition before cutover.

Short answer

FlitStack AI migrates tickets, contact and organizations, agents, agent groups and macros from Gorgias to Freshdesk, 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.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/helpdesk/gorgias/to/freshdesk#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Gorgias ![](https://flitstack.ai/platforms-trim/gorgias.webp)

Destination Freshdesk ![](https://flitstack.ai/platforms-trim/freshdesk.webp)

Ticket Contact and Organization Agent Agent Group Macro

Mapped field by field · sample run · one-click rollback

## What moves from Gorgias to Freshdesk?

Moving from Gorgias to Freshdesk is a migration from a ticket-volume-priced e-commerce helpdesk to a per-seat-priced multi-channel support platform with a broader industry focus.

Read the full summary

The structural shift is from Gorgias's Shopify-centric ticket model (where order context is native to every ticket) to Freshdesk's agent-based licensing with company and contact hierarchy. We handle the per-ticket overage cost exposure that drove the switch by scoping peak monthly ticket volume during discovery and recommending a Freshdesk plan with sufficient agent headroom. Macros, Rules, and Views export as written configuration documents rather than executable code because neither platform has a native macro export that survives the cross-system import intact. Knowledge Base articles and categories migrate in full with translation content. Workflows, automations, and AI Agent configurations do not migrate; we deliver a written handoff inventory for the customer's admin team to rebuild.

1:1

### Ticket → Ticket

Gorgias Tickets map directly to Freshdesk Tickets with status, priority, assignee, and channel preserved.

How it maps

The Gorgias channel field (email, chat, Facebook, Instagram, WhatsApp, SMS, voice) maps to Freshdesk's type field. We preserve the original ticket ID as a custom field for cross-reference during reconciliation. Customer lookup resolves to Freshdesk Contact by email match.

N:1 merge

### Customer → Contact and Organization

Gorgias Customers (end shoppers) map to Freshdesk Contacts.

How it maps

When a Gorgias Customer has a company\_name field populated, we create or match a Freshdesk Organization and link the Contact to it. This creates a two-record structure (Contact plus Organization) versus Gorgias's single Customer record, which requires admin review of the Organization assignment logic post-migration.

1:1

### Agent → Agent

Gorgias Agents map to Freshdesk Agents by email match.

How it maps

Group membership in Gorgias maps to Freshdesk Agent Groups, which control ticket assignment routing. We preserve agent status (active/inactive) and flag any Gorgias agent without a matching Freshdesk user for the customer's admin to provision before production migration.

1:1

### Group → Agent Group

Gorgias Groups (also called Teams) map to Freshdesk Agent Groups.

How it maps

Group membership and routing rules are preserved in a written configuration document for the admin to reapply in Freshdesk's group settings, since routing logic is defined differently in each platform's automation layer.

configuration

### Macro → Macro

Gorgias Macros (saved reply templates with variable substitution and dynamic action fields) are exported as written configuration documents listing the macro body, conditions, and action sequence.

How it maps

Freshdesk supports macros natively, but we do not import them as executable code because Gorgias's variable substitution syntax differs from Freshdesk's. The customer's admin rebuilds each macro in Freshdesk's macro editor using our written macro inventory as the specification.

configuration

### Rule → Automations

Gorgias Rules (ticket routing, assignment, and auto-responses) are exported as written inventory documents describing trigger conditions, filters, and actions.

How it maps

Freshdesk Automations use a different configuration model (time-based and event-based triggers with different action types). We do not migrate Rules as executable code; the written inventory is the handoff for the customer's admin to rebuild in Freshdesk Automations.

******What moves 12 objects

Gorgias Freshdesk

- Ticket Ticket 1:1
- Customer Contact and Organization merged
- Agent Agent 1:1
- Group Agent Group 1:1
- Macro Macro transformed
- Rule Automations transformed

\+ 6 more in the mapping below

## How Gorgias and Freshdesk 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                                                                               | Freshdesk                                                                                                |
| --------------------------- | ------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| Pricing model               | Ticket-volume based; overage at $0.40/ticket plus $1.50/AI Agent resolution           | Per-agent seats; no ticket-volume overage; starting at $19/agent/month                                   |
| eCommerce integration depth | Shopify and BigCommerce native; order and shipment data in every ticket view          | Broader channel support (email, chat, phone, social); e-commerce integrations via third-party connectors |
| Knowledge Base export       | No native export tooling; macro and rule export requires specialist tooling           | Native import from multiple platforms; Knowledge Base API supports article and category creation         |
| AI Agent billing            | Outcome-based fees layered on top of ticket volume; $1.50 per AI-resolved interaction | Freddy AI pricing integrated at plan level; no separate outcome-based fee                                |
| Customer data model         | Customer records linked to ticket history with order context                          | Contacts and Organizations as separate objects with hierarchy; no native order linkage                   |
| GDPR agent visibility       | No field-level or record-level data hiding per agent role                             | Role-based access controls and agent group permissions for PII restriction                               |
| API rate limits             | 40-80 requests per 20-second window depending on auth method                          | 100-700 calls per minute depending on plan tier                                                          |

## What to watch for in a Gorgias to Freshdesk migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Ticket-volume pricing shift requires peak-volume scoping

Gorgias pricing scales on billable ticket volume with overage at $0.40 per ticket plus $1.50 per AI Agent resolution.

How we handle it

Freshdesk pricing is per-agent with no ticket overage. We track the customer's trailing six-month peak monthly ticket volume during discovery and recommend a Freshdesk plan with sufficient agent seats to handle the same peak load without overage exposure. Skipping this step results in a Freshdesk plan that appears cheaper on average but leaves the customer paying overage-style costs for high-volume months under a different name.

high

### Macros, Rules, and Views do not migrate as executable code

Gorgias Macros use variable substitution syntax that differs from Freshdesk's macro format, and Rules use routing logic with different trigger and action models.

How we handle it

We do not import them as executable code. We deliver a written configuration inventory for each Macro, Rule, and View with its full specification (body content, conditions, operators, actions, sort order) so the customer's admin rebuilds them in Freshdesk. This is the standard scope for helpdesk migrations and is disclosed upfront.

medium

### Multi-locale Knowledge Base requires per-locale API calls

Gorgias stores Knowledge Base translations as separate field structures per locale.

How we handle it

The API does not return all translations in a single response; each locale must be fetched individually. We enumerate enabled locales from the Gorgias account settings and issue a separate article fetch per locale to capture complete translation coverage. For accounts with many locales and thousands of articles, this adds meaningful API time to the migration scope.

medium

### API pagination limits create long export windows for high-volume accounts

Gorgias API rate limits are 40 requests per 20 seconds for API key auth and 80 requests per 20 seconds for OAuth2, with page sizes capped below 100 records per response.

How we handle it

For accounts with hundreds of thousands of tickets, a naive sequential export takes days. We implement pagination with exponential backoff and parallelize across object types where the API permits, staying within the rate limit envelope. Freshdesk's import API has its own rate limits (100-700 calls per minute by plan tier) which we coordinate with during import.

low

### Customer-to-Organization restructuring may require admin review

Gorgias stores customer records as flat Customer objects, some with a company\_name field.

How we handle it

Freshdesk uses a two-object model: Contacts attached to Organizations. We create or match a Freshdesk Organization for each customer with a company\_name and link the Contact to it. For customers without a company\_name, we create a personal Organization or link directly to the Contact. The Organization assignment logic requires admin review before production migration to ensure the customer-facing account structure matches the support team's workflow.

## How the migration runs

1. ### Discovery and plan recommendation

   We audit the source Gorgias account: monthly ticket volume (trailing six months, identifying peak), active agents, Macros, Rules, Views, Knowledge Base article count and locale count, custom field schemas on Tickets and Customers, attachment volume, and CSAT survey configuration.

   What this step covers

   We pair this with a Freshdesk plan recommendation based on agent seat count needed for peak volume and the plan tier required for the customer's required API rate limit. The discovery output is a written migration scope and a Freshdesk plan recommendation.

2. ### Object inventory and field mapping specification

   We produce a field-level mapping document for each object: Tickets to Tickets (with channel type mapping), Customers to Contacts with Organization merge logic, Agents to Agents, Groups to Agent Groups, Knowledge Base Categories to Categories, and Knowledge Base Articles to Articles with per-locale fetch instructions.

   What this step covers

   Custom field types are mapped (string, boolean, date, number, select, multi-select) to Freshdesk equivalent field types. Macros, Rules, and Views are documented as written configuration specifications for admin rebuild.

3. ### Sandbox migration and reconciliation

   We run a full migration into a Freshdesk trial or sandbox environment using production-like data volume.

   What this step covers

   The customer's support operations lead reconciles record counts (Tickets in, Contacts in, Organizations in, Agents in, Articles in), spot-checks 25-50 random ticket threads against the Gorgias source, and reviews Knowledge Base article rendering. Any mapping corrections happen here, not in production.

4. ### Knowledge Base translation enumeration

   For accounts with multi-locale Knowledge Base, we enumerate enabled locales from Gorgias account settings and issue a separate article fetch per locale before the main migration pass.

   What this step covers

   Each locale's articles are tagged with locale metadata for Freshdesk import. This step runs in parallel with other export work to reduce total migration wall time.

5. ### Production migration in dependency order

   We run production migration in record-dependency order: Agents (validated for matching), Organizations (from Gorgias customers with company\_name), Contacts (with OrganizationId resolved), Tickets (with ContactId resolved by email match and custom field values populated), Knowledge Base Categories, Knowledge Base Articles (with per-locale tagging), Conversations (linked to Tickets), Attachments (downloaded and re-uploaded), and CSAT responses.

   What this step covers

   Each phase emits a row-count reconciliation report before the next phase begins.

6. ### Cutover, validation, and configuration handoff

   We freeze Gorgias writes during cutover, run a final delta migration of any records modified during the migration window, then enable Freshdesk as the system of record.

   What this step covers

   We deliver the Macro, Rule, and View configuration inventory to the customer's admin team with a rebuild guide. We support a one-week hypercare window where we resolve any reconciliation issues. We do not rebuild Macros, Rules, or Automations in Freshdesk inside the migration scope; that is a separate engagement or an internal admin task.

![](https://flitstack.ai/platforms/gorgias.svg) Gorgias ![](https://flitstack.ai/platforms/freshdesk.svg) Freshdesk

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Freshdesk Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**3-5 weeks** Typical, smaller accounts

**6-10 weeks** Large or heavily customised accounts

A quote scales with ticket volume, custom field count, and whether Knowledge Base articles with translations are included. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Gorgias to Freshdesk →](https://flitstack.ai/contact)

## Why teams move from Gorgias to Freshdesk

- Ticket-volume pricing with AI Agent overage fees create unpredictable monthly costs. Reddit reviewers and G2 users document Gorgias bills compounding during seasonal spikes ($0.40 overage per ticket plus $1.50 per AI Agent resolution). One Shopify merchant estimated $500-$700 per month just for AI Agent at moderate resolution volumes, prompting evaluation of per-seat alternatives. Freshdesk's per-agent model with no ticket overage is more predictable for teams with variable ticket loads.
- Custom reporting is shallow in Gorgias and raw event-level data export for BI tooling is not natively supported. Teams with evolving business intelligence needs cite G2 reviews and Software Advice comparisons as finding Gorgias built-in analytics insufficient, particularly for cross-channel support performance reporting. Freshdesk offers deeper built-in reporting with the ability to export to BI tools without Gorgias's export limitations.
- Knowledge Base, Macros, and Rules lack simple export tooling, making competitive migrations expensive without a specialist integration partner. This friction keeps teams on Gorgias even when pricing is no longer favorable. Freshdesk provides native import tooling from multiple platforms and a documented Knowledge Base API, lowering the barrier to exit and the cost of entry for teams migrating away from Gorgias.
- Gorgias is e-commerce-focused and becomes less relevant for teams expanding beyond Shopify and BigCommerce. G2 reviewers and Software Advice note that Gorgias's feature set is largely tied to order and shipment context, which is less relevant for SaaS companies, agencies, service providers, and manufacturing businesses migrating their support stack. Freshdesk supports a broader range of industries with multi-channel and self-service capabilities not tied to a transactional data model.
- Freshdesk's Freddy AI pricing integrates at the plan level without a separate outcome-based fee. While Freshdesk's AI features differ architecturally from Gorgias's AI Agent, teams migrating specifically to reduce AI automation costs find Freshdesk's bundled approach more transparent and easier to budget than Gorgias's layered outcome-based billing.

Questions, answered

## Gorgias to Freshdesk migration questions

How long does a Gorgias to Freshdesk migration take?

Most migrations land between three and five weeks for accounts under 50,000 tickets, 5,000 customers, and a single-locale Knowledge Base. Migrations with high ticket counts (over 200,000), multi-locale Knowledge Base content, complex custom field schemas, or customer records requiring Organization restructuring move to six to ten weeks because of API pagination time, translation enumeration per locale, and custom field type mapping work.

Do Gorgias Macros, Rules, and Automations migrate to Freshdesk?

No. We do not migrate Macros, Rules, or Automations as executable code because Gorgias and Freshdesk use different macro syntax, different rule trigger models, and different automation action types. We deliver a written configuration inventory for every Macro, Rule, and View with its full specification (body content, conditions, operators, actions, sort order) so the customer's admin rebuilds them in Freshdesk. This is standard scope for helpdesk migrations. Automations, workflows, and AI Agent configurations similarly do not migrate; the inventory documents the current automation logic for admin rebuild.

Will we lose ticket conversation history and attachments?

No. We migrate the full conversation history within every ticket, including internal notes and public replies, with author attribution, timestamp, and privacy flag preserved. Attachments referenced by URL in Gorgias are downloaded during migration and re-uploaded to Freshdesk, handling file type restrictions and size limits. CSAT ratings and survey responses migrate with rating score, free-text response, and ticket linkage preserved.

Can we keep Gorgias Knowledge Base while migrating tickets to Freshdesk?

This is technically possible but creates a split-knowledge situation where agents must reference two systems. We do not recommend a split-stack approach for Knowledge Base. Our standard scope migrates the full Knowledge Base (articles, categories, translations) to Freshdesk's Helpspot or Portal product. If the customer needs a period of parallel operation, we can migrate the Knowledge Base first and keep it read-only in Freshdesk while ticket migration runs, then switch ticket operations over and retire Gorgias.

What happens to our Gorgias AI Agent configurations during migration?

Gorgias AI Agent configurations (automation rules, resolution intents, knowledge base training data) do not migrate to Freshdesk's Freddy AI because they use different AI models and training approaches. We document the current AI Agent configuration as a written specification describing which ticket intents are automated, what resolution paths exist, and what escalation triggers are set. The customer's admin uses this specification to configure Freshdesk Freddy AI post-migration or to decide which automation functions to handle through Freshdesk's rule-based Automations instead.

Do you migrate our Gorgias Shopify and e-commerce integrations?

No. Gorgias Shopify and BigCommerce integrations pull order, shipment, and return data into the ticket view. Freshdesk does not have native Shopify or BigCommerce integration at the same depth. We flag any Gorgias integrations active on the account during discovery and note them in the handoff documentation. The customer's admin evaluates Freshdesk's app marketplace or third-party integration tools (such as Zapier, Make, or a custom API connector) to restore order-context capability in Freshdesk. This is outside migration scope.

## Related migrations

[![](https://flitstack.ai/platforms-trim/freshdesk.webp) Migrate to **Freshdesk** Every source we move into Freshdesk, native options and the checklist. Guide, checklist & sources ](https://flitstack.ai/migrations/helpdesk/freshdesk) [**Salesforce Service Cloud to Freshdesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/salesforce-service-cloud/to/freshdesk) [**Jira Service Management to Freshdesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/jira-service-management/to/freshdesk) [**Zoho Desk to Freshdesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/zoho-desk/to/freshdesk) [**Kayako to Freshdesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/kayako/to/freshdesk) [**Intercom to Freshdesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/intercom/to/freshdesk) [**Zendesk to Freshdesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/zendesk/to/freshdesk) [**Gorgias to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/gorgias/to/zendesk) [**Gorgias to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/gorgias/to/intercom)

## Sources: official documentation

1. [Import to Freshdesk — Freshworks Marketplace](https://www.freshworks.com/apps/import_to_freshdesk/)
2. [Import and export customers and company information — Freshdesk](https://support.freshdesk.com/support/solutions/articles/196491-importing-and-exporting-customer-data)
3. [Throughput and plan-tier limits — Freshdesk](https://support.freshdesk.com/support/solutions/articles/225439)
4. [Associating different object types in Freshdesk](https://support.freshdesk.com/support/solutions/articles/50000004226-understanding-associations-in-custom-objects)
5. [Help Desk Migration — Gorgias Help Center](https://docs.gorgias.com/en-US/help-desk-migration-398565)
6. [Create a custom field — Gorgias documentation](https://docs.gorgias.com/)
7. [Import and export Macros — Gorgias Help Center](https://docs.gorgias.com/en-US/import-and-export-macros-207786)

Get a quote

## Moving from Gorgias to Freshdesk?

Tell us roughly how many records and objects you have. We scope the mapping and the Freshdesk setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
