Importing from Gorgias

Updated Nov 20, 202616 min read
English
On this page

Bring your Gorgias tickets, customers, macros, tags, fields, rules and views into Deskwoot with your Gorgias subdomain, your email and an API key. The import reads every ticket with all of its messages and files. Everything comes over by default, and you can choose to import less. It runs in the background, keeps going through Deskwoot updates and can be started again safely. Nothing in your Gorgias account changes.

What comes over

  • Tickets become conversations with every message, internal notes (as private notes), attachments, status, priority, team, agent, tags and the values of your ticket fields. Each keeps its original dates and the channel it came in on (email, chat, phone and so on). An email comes as Gorgias keeps it for reading: without its signature and the earlier replies it quotes. Messages that a Gorgias rule or bot sent show as your team's, without an agent.
  • Deskwoot tickets: if your workspace uses tickets (they come with the Enterprise plan and the free trial, and an admin can switch them off under Settings > Tickets), each Gorgias ticket also becomes a Deskwoot ticket next to its conversation. The ticket takes over the status, priority, subject, team, agent and labels, and holds the work from then on. Its conversation is resolved as the handover and shows a private card that names the ticket as imported from Gorgias. Without tickets, the conversation keeps the Gorgias status.
  • Tags become labels with their color and description. Deleted tags stay out.
  • Satisfaction ratings become CSAT ratings with their score and comment on the matching conversation. Surveys the customer never answered stay out.
  • Customers become contacts with every email address and phone number (WhatsApp numbers included), their X handle, language, time zone, note (as a contact note), the values of your customer fields and the extra data stored on them in Gorgias. Their other channels, like Instagram or Facebook, are saved on the contact too.
  • Teams come with their description and with those of their members who are already in your workspace. Users (your Gorgias agents) are matched to your teammates by email (see below).
  • Macros that are not archived become canned responses with their reply text, images and attachments. Gorgias variables that Deskwoot also has become Deskwoot's, for example {{ticket.customer.firstname}} becomes {{contact.first_name}}. The short code comes from the macro's name. If a canned response with the same short code already exists in Deskwoot, the imported one is left out, and the import in Import History shows how many were left out. What a macro does besides its reply (add tags, set the status or priority, assign an agent or a team, add an internal note) becomes a Deskwoot macro of the same name for your whole team. A macro of that name that is already in Deskwoot stays as it is.
  • Ticket fields and customer fields become custom attributes with their type and the choices of a dropdown. Archived fields come too, so their old values come over.
  • Rules that are active in Gorgias become automation rules, and they arrive switched off. Gorgias writes a rule as code, which Deskwoot does not run: each imported rule keeps that code and lists the actions it took, so you can rebuild it with Deskwoot's conditions and actions. As it arrives, it never matches.
  • Ticket views that are active and that your team made become saved filters of the admin who started the import. Everything Deskwoot can filter by comes over (status, snooze, agent, team, tags, priority, field values, search words and sort order). The rest is left out, so a filter may show more conversations than the view did, never fewer. A view whose filter Deskwoot cannot read at all, such as one on Gorgias's AI fields only, is left out, since it would show every conversation.

Files and images

The import copies every file Gorgias hosts into Deskwoot: the attachments and images of every message, the images in your macros and the files your macros attach, which the canned responses offer as files the customer can open. Nothing stays a link to Gorgias, so your files keep working after you leave Gorgias. If your workspace has booked the Virus scan, every file is scanned before it is stored.

  • If a file cannot be copied right now (Gorgias does not answer even after several tries, or the virus scanner or Deskwoot's storage cannot be reached), the import ends with Imported partly. Start the import again to copy it. When 3 files in a row from the same server do not arrive, the run skips that server's files for 2 minutes and then tries one of them again. If that file arrives, the run carries on with the server's files. If not, it waits another 2 minutes. That way a server that does not answer cannot hold up the whole import, and the next run tries the skipped files again.
  • A file that no run can copy is left out, and the import still finishes. This includes a file that could not be reached in 3 runs, so a server that never answers cannot keep your import at Imported partly. Only runs in which the file could not be reached count, not runs in which the virus scanner or the storage was down. The count starts over when the last of those runs was more than 7 days ago, and deleting any import of your workspace clears it.
  • Each import in Import History lists these files under Files not imported with the reason, for example too large (over 25 MB), a file type that is not allowed, refused by the virus scan or no longer available at the source.
  • Images that a message or a macro loads from another website, such as your own, stay as they are.

What does not come over

  • Your Gorgias help center. Gorgias has no API for it, and its own help says articles cannot be exported.
  • Organizations, because Gorgias has no companies, and profile pictures, because Gorgias customers have none. Your teammates keep their Deskwoot profile.
  • Archived macros, and the parts of a macro that a Deskwoot macro has no action for: setting a ticket field, HTTP actions and store actions.
  • Rules and views that are switched off, Gorgias's own system views (Deskwoot's built in inbox folders cover them) and customer views.
  • Gorgias's AI fields and the guesses its AI makes on messages (intents). The contact reason comes over as a field value.
  • A customer's store data from Shopify and other apps. Deskwoot's own integrations read it from your store.
  • A ticket's history of events. Gorgias gives it only one ticket at a time and only for the last 12 months.
  • Call recordings and call details. A phone ticket comes with its messages.
  • The CC and BCC of emails.
  • Tickets in spam or in the trash, and deleted messages. A ticket Gorgias merged into another is already part of that one.
  • That Gorgias failed to send a reply: such a reply comes over as sent.

What stays internal

Deskwoot keeps private what only your team saw in Gorgias:

  • Internal notes arrive as private notes, and a customer's note becomes a contact note. Only your team sees them.
  • The card in a conversation that names its Deskwoot ticket is private too.
  • Saved filters made from Gorgias views belong to the admin who started the import.

Before you start

  1. In Gorgias, open Settings > REST API as an admin. Click Create API Key, or copy the key that is already there. The same page shows your Username, which is your email. Only an admin or the account owner can create a key, and a key reads with the rights of the person who made it, so use an admin's key: then the import can read every part of your helpdesk.
  2. Note your Gorgias subdomain: your-company from your-company.gorgias.com.
  3. Gorgias offers its REST API on all of its Helpdesk plans, so you need no particular Gorgias plan for the import.
  4. Invite your teammates to Deskwoot with the same email they use in Gorgias. You can also do this later.
  5. For imported tickets to land in an inbox, set up your email, Telegram, WhatsApp or SMS inboxes first.

How to import

  1. In Deskwoot, go to Settings > Import & Migration. Only admins can import.
  2. Under Where does your data come from?, pick Gorgias.
  3. Enter the Subdomain, the Email (the Username Gorgias shows next to your key) and the API Key.
  4. Under What should come along?, choose what comes over. Everything is on by default. To import only newer tickets, pick a day under Only tickets created on or after.
  5. Under Which inbox should the tickets go to?, pick an inbox for each kind of ticket (Email, Chat, Web forms and help center, Phone, WhatsApp, SMS, Everything else), or leave No inbox. Only email, Telegram, WhatsApp and SMS inboxes are offered. On your first Gorgias import, an email, WhatsApp or SMS inbox that is the only one of its kind in your workspace is already picked.
  6. Click Start Import. Deskwoot first checks the subdomain, the email and the key with Gorgias. If Gorgias refuses them, the panel says so and nothing starts.

While the import runs

  • The import runs in the background, so you can close the page. The import page shows the step it is on and how many records are done. After a few minutes of measuring, it also shows the speed. Under How fast the import goes, it shows how many API calls per minute your Gorgias account allows and how many of them the import uses at most.
  • Gorgias lets an API key make 40 calls every 20 seconds (every 10 seconds on its Enterprise plan). The import uses at most 85% of that, so your other apps keep working. When the limit is reached anyway, the import waits and then carries on.
  • Deskwoot updates and server restarts don't stop it. It continues where it stopped. If a run crashes or gets stuck 3 times in a row without getting any further, the import stops and says so. Start it again to continue.
  • One import runs per workspace at a time. Start the next one when the current one has finished.
  • To stop an import, click Cancel import on the import page and confirm with Cancel and delete. The import stops and what it imported so far is deleted. A conversation someone wrote in since then keeps those new messages.
  • If Gorgias stops answering, the import keeps what it already read, finishes the other steps and ends with Imported partly and the steps that stopped early. Start the import again to continue. If Gorgias no longer accepts the key, for example because someone deleted it, the run stops: start a new import with a valid key, and it skips what is already in Deskwoot.

Your agents' tickets and replies

A ticket assigned to a Gorgias agent goes to the teammate with the same email, and their replies show them as the sender. With tickets switched on, the Deskwoot ticket goes to that teammate too. If that person has no Deskwoot account yet, the ticket arrives unassigned and their replies show their name with (imported).

When they join your workspace later with the same email, Deskwoot hands them their work automatically: their unassigned imported conversations are assigned to them and they become the sender of their replies. Open, pending and snoozed conversations come with one notification for all of them. Resolved ones are assigned quietly. No status changes, and your customers see nothing. A conversation that someone in Deskwoot has already held stays as it is. The Deskwoot tickets the import made are not handed over this way: assign those by hand.

Imported conversations stay quiet

Imported conversations are history, so they stay quiet until the customer writes again or someone on your team replies in Deskwoot. Until then Deskwoot sends the customer nothing from them (no farewell message, no satisfaction survey), starts no SLA clock and does not resolve them automatically. Imported conversations never count toward your plan's monthly conversation limit and are never locked by it, also after the customer writes again. Resolving or reopening one by hand fires no webhook and no automation rule. From the first new message on, the conversation works like any other, except that Fynn, the AI bot, never answers in an imported conversation. The Deskwoot tickets the import made are history in the same way.

Inboxes for imported tickets

  • Gorgias notes the channel of each ticket. The import puts each ticket into the inbox you picked for its kind, so your team can answer it there. Chat is live chat on your website and in your app, Web forms and help center covers contact forms and your Gorgias help center, Phone covers calls and voicemails, and Everything else covers Facebook, Instagram, X, tickets made through the API and every other channel.
  • A ticket only goes into an inbox where Deskwoot can reach the customer: an email inbox needs their email address, a Telegram inbox their Telegram chat, and a WhatsApp or SMS inbox their phone number. Other tickets come in without an inbox.
  • With tickets switched on, the inbox goes to the conversation, and a reply from the Deskwoot ticket reaches the customer through it (see Reply to the customer from a ticket).
  • When you start the import again, tickets you imported from this Gorgias account before go into the inboxes you pick too, if they have no inbox yet. A ticket that already has an inbox, or that someone on your team wrote in, stays where it is. The next import starts from the inboxes of the last one.
  • Each import in Import History shows the inboxes you picked and how many tickets went into one.

After the import

  • A ticket without an inbox (because you picked none for its kind, or Deskwoot can't reach the customer there) needs one before you reply: open it and pick an inbox in the This conversation has no inbox notice. For an email, WhatsApp or SMS inbox, you can also add the missing email address or phone number to the contact and run the import again.
  • Rebuild the rules you need. Open the import in Import History: under Still to do, Check and turn on the rules takes you to them. Give each one Deskwoot conditions and actions, then switch it on.
  • Check the saved filters and the macros: a Gorgias view can filter by more than Deskwoot reads, and a macro action that Deskwoot has no match for was left out.

Frequently asked questions

Can I start the import again?

Yes, that is safe. A new run finds what is already in Deskwoot and skips it, so tickets, contacts, labels and canned responses are not duplicated. It brings in what is new or was missing, for example after a run that ended with Imported partly. A ticket that changed in Gorgias since gets its new messages, and while nobody on your team has worked on it in Deskwoot, it takes over the new status, subject, priority, team and agent (on its Deskwoot ticket, if it has one). A contact the import made gets what it still lacks, and nothing your team entered is written over.

Canned responses and macros your team changed in Deskwoot stay as you left them. A rule you rebuilt stays too, but the new run no longer finds the original and brings Gorgias's version in again, switched off: delete that copy if you don't need it.

Keep in mind that conversations, contacts and notes you deleted or erased in Deskwoot since the last import come back if Gorgias still has them, and so do contacts you merged.

The import ended with "Imported partly". What now?

Gorgias stopped answering during one or more steps, for example because its API limit stayed used up for a long time. Everything read so far is in Deskwoot. Start the import again: it skips what is there and continues.

My contacts are already in Deskwoot. Does the import use them?

Yes. Before the import adds a contact, it looks for that person in Deskwoot: first by the Gorgias ID, then by the email address, whether it is written in upper or lower case. Their tickets then go to the contact you already have, and its name, details and fields stay as they are. To match by ID, give each contact its Gorgias ID when you add or update it through the API, in the externalId field: gorgias:, your Gorgias subdomain in lower case, a colon and the Gorgias customer ID, for example gorgias:acme:4711 for customer 4711 at acme.gorgias.com. If all of your contacts are in Deskwoot already, you can switch off Contacts: each ticket still goes to its contact, and one that Deskwoot does not have yet comes with the ticket.

Can I import only part of my data?

Yes. Under What should come along?, everything is on by default, and you can switch off Tickets, Contacts, Canned responses (your macros, with the Deskwoot macros made from them) and Satisfaction ratings. With a day under Only tickets created on or after, only tickets created on or after that day come. Ratings come only with the tickets they rate, so that option is greyed out without the tickets. Teams, agents, tags, fields, rules and views always come. If you leave out the contacts, each imported ticket still brings its own contact.

Each import in Import History shows under Your choice what was not selected and the start date. To get the rest later, start an import with everything selected: it skips what is already in Deskwoot and brings in what was left out.

How do I undo an import?

In Import History, click Delete next to the import, confirm and enter your password. This deletes the conversations, Deskwoot tickets and contacts it created, together with the files it copied for them. A conversation someone wrote in since then stays with those new messages, without the imported ones, and a contact who still has a conversation stays too. Teams, canned responses, macros, labels, custom attributes, automation rules, saved filters and other settings stay. Deleting continues after a restart, and you can start a new import once it is done. While another import runs, an import cannot be deleted. If you imported from Gorgias more than once, delete the imports from the newest to the oldest: while a newer Gorgias import exists, Deskwoot asks you to delete that one first.

Does Deskwoot keep my API key?

Only while the import runs, stored encrypted, so it can continue after a restart. It is removed when the import ends.

Was this guide helpful?

Keep reading

Ask Fynn about this guide

Get a short answer from this guide and the rest of the help center.

Still need help?

Fynn answers from these guides in the chat, and you can reach the team there too.