Gorgias to Intercom migration
DataGrine migrates Gorgias to Intercom: companies, contacts, tickets with their replies, notes and attachments, tags and knowledge base articles. Every field is mapped in writing and a sample of your own records is signed off before the full run. Run it yourself on the DataGrine platform or have the DataGrine team run it end to end, with 24/7 premium support either way.
What moves
From Gorgias into Intercom.
- CustomersContacts
- Shopify integration dataContact and conversation attributes
- TicketsConversations or tickets
- Public messagesConversation replies
- Internal notesInternal notes
- Social and channel ticketsConversations with a channel attribute
- AttachmentsPart attachments
- Custom ticket fieldsConversation attributes
- TagsTags
- Ticket statusesOpen or closed
Why teams make this move
Ecommerce teams moving from Gorgias often need support to cover more than order status, with Fin AI Agent on the front line.
Worth planning for
Gorgias tickets carry Shopify order context in the sidebar and pull in social comments and DMs as tickets. Intercom has neither natively - the order data becomes contact and conversation attributes, and every social channel needs a decision about where it lands.
Decided with you in the written mapping, before anything moves.
How it runs
Self-serve or fully managed. Same steps, same checks.
- 01
Connect and map
Read-only access to your old helpdesk. Every field and value mapped before anything moves.
- 02
Sample run
A sample of your own records lands in the new helpdesk for you to check and sign off.
- 03
Full migration
The full move at the fastest pace both platforms allow, while your team keeps working.
- 04
Delta at cut-over
Anything created or changed since the full run, moved on go-live day.
- 05
Reconcile
Counts checked object by object against the source, and every run can be rolled back.
- Read-only access to the source
- Rollback per run
- 24/7 premium support
Questions
Gorgias to Intercom, answered.
What does not carry across from Gorgias?
Configuration such as automations, macros and views is not data, so it is set up again in Intercom. Anything with no equivalent in Intercom is listed in the written mapping, and you choose what happens to it before anything moves.
Can we run it ourselves?
Yes. Run it self-serve on the DataGrine platform, or let our migration team handle it end to end. Either way you get 24/7 premium support until the migration is signed off.
Does our team have to stop working?
No. We only read from Gorgias, so your team keeps working during the full run, and a delta sync at cut-over moves anything created or changed since.
Can we use the built-in importer instead?
None documented. Intercom's Syncing and importing content collection has no Gorgias source, and no Gorgias ticket importer is documented in Intercom's help centre. A migration adds a written mapping, a sample run on your own data, a delta sync at cut-over and rollback.
How fast can data come out of Gorgias?
Gorgias REST API (leaky bucket): 40 requests per 20 seconds for API key integrations and 80 per 20 seconds for OAuth2 apps; Enterprise accounts get the same caps over a 10-second window. Runs are paced to stay inside that limit, which is why large accounts move in a full run first and a delta at cut-over.
What needs deciding before the move?
Gorgias's API allowance is small, so reading a large ticket history takes time and must be scheduled well before cut-over. Every social channel needs a decision about where its history lands and how the live channel is reconnected. Shopify order context needs a scoped list of fields worth keeping as Intercom attributes.
What does it cost?
It depends on how many records move and whether you run the migration yourself or have the DataGrine team run it. You get a quote once the records in scope are counted, before anything moves.
Other routes
Moving a different pair?
Teams move for Fin and the Messenger, then discover four years of ticket history has to come with them.
Teams moving from Freshdesk often need more flexible routing, workflows and AI-powered support.
Teams moving from Help Scout often need more advanced routing, SLAs and AI-powered support.
Plan your Gorgias to Intercom move.
Tell us where you are moving from and to. Run it yourself on the DataGrine platform or let our migration team handle it end to end, with 24/7 support either way.
- A written mapping document before anything moves
- A sample migration you review before the live run
- Delta sync at cut-over and rollback per run
- 24/7 premium support until you sign off