Gorgias to Intercom migration
We migrate Tickets, Customers, Knowledge Base articles, and conversation history from Gorgias into Intercom with every conversation anchored to a valid Contact record, custom ticket fields mapped to Intercom Custom Attributes, and the Knowledge Base reconstructed in Intercom's article builder before go-live.
FlitStack AI migrates conversations, contacts, conversation parts, saved replies and inbox rules from Gorgias to Intercom, 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 Intercom?
Gorgias and Intercom both manage customer conversations, but the data models differ significantly.
Read the full summary
Gorgias treats a Ticket as the primary workflow unit with an embedded order context pulled from Shopify; Intercom treats a Conversation as the primary unit anchored to a Contact or Lead record. We resolve this structural difference by pre-importing all Gorgias Customers into Intercom Contacts before any ticket history moves, ensuring no orphaned conversations. Macros and Rules from Gorgias map to Intercom Saved Replies and Inbox Rules respectively, though the condition syntax differs. Knowledge Base articles migrate as Articles in Intercom's Help Center builder, preserving category hierarchy and publication status. We do not migrate Gorgias Rules as automated workflows; we deliver a written inventory of every active Rule for the customer's admin to rebuild in Intercom's automation builder. Active Outbound campaigns in Intercom consume API limits and must be paused during migration to avoid throttling the import pipeline.
Ticket → Conversation
Gorgias Tickets map to Intercom Conversations.
How it maps
The primary structural difference is anchoring: every Intercom Conversation must be associated with a Contact or Lead record, whereas Gorgias Tickets can exist without a strict contact requirement. We pre-import all Gorgias Customers into Intercom Contacts before any ticket import so that every Conversation has a valid user_id or lead_id. Ticket priority maps to Conversation priority. Closed ticket status maps to Intercom closed Conversation state. Open and pending statuses map to Intercom open and snoozed states respectively. If a Gorgias Ticket has no associated Customer, we create a minimal Intercom Contact using the ticket's from field email before importing the Conversation.
Customer → Contact
Gorgias Customers map directly to Intercom Contacts.
How it maps
The customer email is the dedupe key. Name, phone, and address fields map to the corresponding Intercom Contact standard attributes. Gorgias custom fields on Customers map to Intercom Custom Attributes on Contact. We preserve the customer's total ticket count, total spend, and last order date as attributes. If a Customer has multiple email addresses in Gorgias (aliases), we migrate the primary email and flag additional addresses for the customer's admin to reconcile post-migration.
Conversation (message) → Conversation Part
Individual messages within a Gorgias Ticket (public replies, internal notes, and customer messages) map to Intercom Conversation Parts.
How it maps
The author, timestamp, privacy flag, and message body transfer. Internal notes in Gorgias (marked private) map to Intercom internal Parts with the same visibility constraint. We handle attachments on messages by downloading from the Gorgias URL reference and uploading to Intercom's file attachment API, respecting file type restrictions (max 10MB per attachment in Intercom). The message-per-ticket density directly impacts API call volume: migrations with high-density tickets (10+ messages per ticket) can inflate total API calls 10-100x compared to simple ticket-count migrations.
Macro → Saved Reply
Gorgias Macros with dynamic action fields and variable substitution map to Intercom Saved Replies.
How it maps
We export the macro body, conditions, and action sequence. Intercom Saved Replies support liquid syntax for personalization variables; we convert Gorgias variable placeholders (e.g., {{customer.name}}) to Intercom liquid syntax during the export transform. Macro conditions (trigger based on channel, subject pattern, or customer attribute) do not migrate as active rules; we document each macro's trigger conditions as a recommended Saved Reply usage guide for the customer's admin to implement as an Inbox Rule or Fin automation post-migration.
Rule → Inbox Rule
Gorgias Rules (auto-assignment, auto-response, routing, and tag application) map conceptually to Intercom Inbox Rules and automation actions.
How it maps
The condition syntax differs: Gorgias uses field-operator-value conditions; Intercom uses step-based rule builders. We export every active Rule with its full condition tree and action sequence as a written inventory document that the customer's admin uses to rebuild in Intercom. We do not migrate Rules as executable code. We flag Rules that reference Shopify order context (e.g., order status triggers) because Intercom does not have a native Shopify order lookup; these Rules require either an Intercom Custom Object (Order) with Shopify integration or a third-party middleware connection.
View → Saved View
Gorgias Views (saved filter configurations with field conditions, operators, and sort order) map to Intercom Saved Views on the Inbox.
How it maps
We export the filter logic and recreate it as an Intercom inbox filter. Sort order and column configuration transfer as part of the saved view settings. Dynamic Views (using relative time conditions like 'created in the last 24 hours') convert to equivalent Intercom filter syntax.
- TicketConversation1:1
- CustomerContact1:1
- ConversationConversation Part1:1
- MacroSaved Reply1:1
- RuleInbox Ruletransformed
- ViewSaved View1:1
+ 8 more in the mapping below
How Gorgias and Intercom 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 | Intercom |
|---|---|---|
| Primary workflow unit | Ticket — linked to Shopify order context | Conversation — anchored to Contact or Lead |
| Knowledge Base | Gorgias Help Center with multi-locale support and article-customer linkage | Intercom Help Center with article builder, translations, and independent content model |
| Automation object | Rules (trigger-based routing, assignment, and auto-response) | Workflows (Inbox Rules, Operator Actions, and Fin AI) with different condition syntax |
| Template system | Macros with dynamic action fields and variable substitution | Saved Replies with liquid syntax for personalization |
| Ticket field types | Custom fields on Tickets and Customers: string, boolean, date, number, select, multi-select | Custom Attributes on Contact and Conversation: string, boolean, date, number, list, and Custom Objects |
| AI resolution billing | AI Agent at $1.50 per resolved interaction on top of ticket overage fees | Fin AI with per-resolution or subscription pricing depending on plan tier |
| Channel scope | Omnichannel inbox with deep Shopify and BigCommerce order context | Broad channel support with messenger-first UX and 250+ integrations |
What to watch for in a Gorgias to Intercom migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Every Intercom Conversation requires a Contact or Lead anchor
Intercom enforces that every Conversation is linked to an existing Contact or Lead record.
How we handle it
Gorgias Tickets can exist without a strict contact requirement (e.g., email-only tickets where the customer record was never created). We pre-import all Gorgias Customers into Intercom Contacts before any ticket import so that the foreign key constraint is satisfied at migration time. Any ticket without a resolvable customer email is flagged in the pre-migration audit; the customer can choose to create a placeholder Contact, skip the ticket, or map it to a default 'anonymous' Contact.
Active Intercom Outbound campaigns consume API limits during migration
Intercom's API enforces rate limits that are shared across all outbound campaign sends and migration import operations.
How we handle it
Active email campaigns, automation sequences, and product tour triggers run simultaneously with the migration and can throttle import throughput or cause 429 responses. We request that customers pause all active Intercom Outbound campaigns before migration begins. If campaigns cannot be paused, we schedule migration runs during off-peak hours and implement exponential backoff to stay within the leaky bucket envelope.
Message-per-ticket density can inflate API calls 10-100x
Intercom's documentation states that migrating conversation history message-by-message (as opposed to simple ticket-level records) inflates total API calls by 10-100x.
How we handle it
A Gorgias account with 5,000 tickets averaging 8 messages each requires approximately 40,000 API calls. We batch Conversation Part imports using Intercom's bulk endpoint where available and paginate remaining writes with rate-limit handling. High-density tickets (long email threads, internal note chains) are the primary driver of migration duration variance.
Intercom Custom Objects require schema pre-creation before migration
Gorgias custom fields on Tickets and Customers that reference external entities (e.g., an order ID from an external OMS) cannot map directly to Intercom standard Conversation attributes.
How we handle it
They require an Intercom Custom Object schema (e.g., an Order object) to be defined before migration. We design the Custom Object schema during scoping, create the object and its attributes in Intercom's Settings > Data > Custom Objects, and then map the migration data to the custom object records. Custom Object definitions are permanent once saved and cannot be renamed; we validate naming with the customer before creation.
Phone number validation in Intercom can block contact import
If phone number validation is enabled in Intercom workspace settings (Settings > Your Workspace > People Data > Phone), contacts with improperly formatted phone numbers will be rejected during import.
How we handle it
We request that customers disable phone number validation in the destination workspace before migration begins and re-enable it post-migration after data cleanup. Alternatively, we flag records with invalid phone numbers and fix them in a reconciliation batch before re-import.
How the migration runs
Discovery and data audit
We audit the source Gorgias account across ticket volume (last 6 months for overage analysis), customer count, Knowledge Base article and category count, active Macros, active Rules, custom field definitions on Tickets and Customers, agent and group count, CSAT history, and attachment volume.
What this step covers
We pair this with a review of the destination Intercom workspace settings: existing Contact schema, enabled channels, active Outbound campaigns, and Custom Object definitions. The discovery output is a written migration scope document with record counts, object dependency order, and a recommendation to pause Outbound campaigns before migration.
Contact pre-import and anchor resolution
We import all Gorgias Customers into Intercom Contacts before any Conversation import.
What this step covers
This step establishes the foreign key anchor required for every Conversation. We map Gorgias Customer custom fields to Intercom Custom Attributes on Contact. Any Gorgias Customer with a duplicate email (merged records) is reconciled to a single Intercom Contact. Customers without email addresses are flagged for the customer to resolve (create a placeholder contact, skip associated tickets, or supply missing email). This step completes with a row-count reconciliation before ticket migration begins.
Intercom schema preparation
We pre-create any missing Custom Attributes in Intercom to match Gorgias Ticket custom fields, pre-create any Custom Object schemas referenced by migrating data, and configure Saved Views in the Inbox matching the Gorgias View definitions.
What this step covers
Knowledge Base Collections are created with correct ordering. Tags are enumerated and conflict-checked against reserved Intercom labels. This step runs in the customer's staging or production Intercom workspace (customer choice) and completes before bulk data migration.
Bulk migration in dependency order
We run migration in record-dependency order: Contacts (validated), then Conversations (with each conversation anchored to a Contact by email lookup), then Conversation Parts (messages, internal notes, attachments), then Knowledge Base Articles, then CSAT ratings, then Tags.
What this step covers
Knowledge Base article translations are fetched per locale from Gorgias and imported to the corresponding Intercom article locale. Each phase emits a row-count and sample-record reconciliation report before the next phase begins. We use batch chunking and exponential backoff on 429 responses throughout.
Macro and Rule inventory document delivery
We deliver a written inventory of every active Gorgias Macro (body, conditions, actions, recommended Intercom Saved Reply usage) and every active Rule (full condition tree, routing logic, tag application, auto-response content) organized by business function.
What this step covers
Rules referencing Shopify order context are flagged separately because Intercom lacks a native Shopify order lookup and may require Custom Object configuration or a middleware connection. The customer's admin uses this document to rebuild automations in Intercom's Inbox Rules builder or Fin AI workflow editor.
Cutover, validation, and hypercare handoff
We freeze Gorgias writes during cutover, run a final delta migration of any tickets modified during the migration window, then enable Intercom as the system of record.
What this step covers
We perform a post-migration validation comparing total ticket count, conversation count, article count, and attachment count between source and destination, with a 25-record spot-check by the customer's team. We deliver a one-week hypercare window for reconciliation issues. We do not rebuild Gorgias Rules as Intercom automations within the migration scope; that is a separate engagement.
- 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, Knowledge Base article count, and the number of custom fields requiring attribute creation in Intercom. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Gorgias to Intercom →Why teams move from Gorgias to Intercom
- Gorgias ticket-volume pricing with AI Agent overage fees compounds unpredictably during seasonal demand spikes. Overage charges at $0.40 per ticket plus $1.50 per AI-resolved interaction can more than double the effective monthly cost in peak months. Intercom's pricing, while also complex, offers subscription tiers with more predictable per-seat and per-feature billing for teams that have outgrown volume-based overage models.
- Gorgias has approximately 30 native integrations versus Intercom's 250+. Teams with broader SaaS and product toolchains move to Intercom because the native integrations (CRM, product analytics, data warehouse, payments) are AppExchange-listed or first-party rather than requiring Zapier routing that introduces latency and failure points.
- Gorgias is built for reactive support with Shopify order context; Intercom offers more proactive engagement tooling including outbound campaigns, product tours, and behavioral triggers. Teams shifting from pure support to a customer communication model move to Intercom for the proactive messaging layer even when Gorgias handles the ticketing side adequately.
- Intercom's Fin chatbot supports complex multi-turn resolution flows and integrates natively with Custom Objects, allowing teams to build resolution workflows that reference order data without requiring the Shopify-deep integration that Gorgias provides. Teams that have outgrown Gorgias's prebuilt eCommerce actions move to Intercom for custom AI resolution design.
- Gorgias Knowledge Base, Macros, and Rules lack simple export tooling, making competitive migrations expensive without a specialist integration partner. Reviewers on Reddit and G2 cite the difficulty of extracting Knowledge Base content and rule logic as a barrier to leaving Gorgias. Moving to Intercom with professional migration support resolves this constraint and delivers a cleaner Help Center output.
Questions, answered
Gorgias to Intercom migration questions
How long does a Gorgias to Intercom migration take?
Most migrations land between three and five weeks for accounts under 20,000 tickets, 500 Knowledge Base articles, and a simple custom field set. Migrations with high message-per-ticket density (10+ messages per ticket averaging), multi-locale Knowledge Base content (requiring per-locale article fetches from Gorgias and per-locale imports to Intercom), or custom fields on both Tickets and Customers that require Intercom Custom Object schema design extend to eight to twelve weeks. The primary duration driver is API call volume on the Intercom side during Conversation Part import.
Do Gorgias Rules and Macros migrate to Intercom as active workflows?
No. Gorgias Rules use a condition-action syntax that does not map directly to Intercom Inbox Rules, which use a step-based builder. We do not migrate Rules as executable code. We deliver a written inventory of every active Rule with its full condition tree, routing logic, and recommended Intercom equivalent so that the customer's admin can rebuild them in Intercom. Macros migrate as Intercom Saved Replies with variable syntax converted from Gorgias liquid to Intercom liquid format. The macro trigger conditions are documented as recommended Saved Reply usage guidance rather than active automations.
What happens to my Gorgias Knowledge Base when migrating to Intercom?
Gorgias Help Center articles and categories migrate into Intercom's Help Center builder. Category hierarchy and ordering transfer as Intercom Collections. Article publication status (Draft, Public, Unlisted) maps to Intercom's article states. Multi-locale translations require a separate API call per locale from Gorgias; we fetch all enabled locales and import each into the corresponding Intercom article locale. The article appearance customization and any custom scripts from Gorgias do not transfer; the customer configures the Intercom Help Center appearance post-migration. The article-customer linkage (Gorgias showing related articles in ticket context) does not have a direct Intercom equivalent and is noted as a post-migration configuration option.
Will we lose our conversation history and internal notes?
No. We migrate the full conversation history including public replies, customer messages, and internal notes. Internal notes in Gorgias map to Intercom internal Parts with the same visibility constraint (visible to team but not the end customer). Attachments migrate by downloading from Gorgias URL references and re-uploading to Intercom's file API. The primary risk is API rate limit throttling on high-density tickets; we mitigate this with batch chunking and exponential backoff so that no records are silently dropped.
Can we migrate Gorgias customers who have no email address?
Gorgias allows tickets where the customer email is absent or anonymized. Intercom requires every Conversation to be associated with a Contact (which requires an email or a user_id). During scoping, we audit the proportion of Gorgias tickets with missing customer emails and present three options: create placeholder Intercom Contacts with a generated placeholder email and flag for post-migration cleanup; skip the orphaned tickets and document them for manual review; or supply missing emails from another system (CRM, order management) during migration. The customer selects the approach before migration begins.
How does the Intercom API rate limit affect migration speed?
Intercom enforces API rate limits that are shared across all operations in the workspace, including active Outbound campaigns. We implement batch chunking (grouping records in batches of 100-200 depending on object type), exponential backoff on 429 responses, and pagination on list endpoints. We also request that customers pause active Outbound campaigns before migration to maximize available throughput. For large migrations (over 50,000 tickets), we schedule migration runs during off-peak hours to minimize collision with live workspace activity.
What happens to our CSAT ratings and satisfaction survey data?
Gorgias CSAT ratings (score, free-text response, timestamp) migrate to Intercom Conversation ratings linked to the corresponding Conversation. The rating score transfers directly; if Gorgias used a non-5-star scale, we preserve the raw score and document the scale for reporting consistency. CSAT response text migrates as part of the Conversation Part history. Satisfaction survey configuration (questions, thank-you messages, survey channel) does not migrate; the customer configures Intercom's built-in CSAT survey or a third-party integration post-migration.
Related migrations
Sources: official documentation
- Import your user data into Intercom — Intercom Help
- Import your customers — Intercom Academy
- Create and track Custom Data Attributes (CDAs) — Intercom Help
- Events limits, troubleshooting and F.A.Q — Intercom 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 Intercom?
Tell us roughly how many records and objects you have. We scope the mapping and the Intercom setup with you, then send a quote.
Get a quote