SquidSupport
Product reference / Settings

Data Migration

In the app: Settings → Data Migration

Needs the 'Manage Migrations' permission.

Data Migration copies your ticket history and customers from another helpdesk into Squid, so past tickets can be found in the inbox. It is a wizard with five steps: "Platform", "Credentials", "Configure", "Import" and "Summary". One import runs at a time for the organization.

Select Platform

Pick the helpdesk you are moving from:

  • "Gorgias": needs your subdomain, email address and API key.
  • "Zendesk": needs your subdomain, email address and API token.
  • "Re:amaze": needs your brand slug, email address and API token.
  • "Richpanel": needs an API key, or a CSV export.
  • "Help Scout": needs an App ID and App Secret.

The cards for Gorgias and Zendesk mention macros. Macros are not imported from any platform; see "Configure Import" for what is.

There is no import from a shared Google Workspace or Microsoft 365 mailbox, and no IMAP or mailbox-file upload. Keep the old mailbox for reference. New mail arrives in Squid once forwarding is set up under Settings → Email, and a customer who replies to an old thread can start a new ticket. Squid can also match a recent ticket for the same customer and subject.

Connect to the platform

Step 2 asks for the credentials of the platform you picked. "How to find your credentials" opens the steps for that platform, with a link to its own documentation.

  • For Gorgias, Zendesk and Re:amaze: the subdomain or brand slug (letters, numbers and hyphens only), the email address of an admin account, and the API key or token.
  • For Help Scout: "App ID (Client ID)" and "App Secret (Client Secret)" of an app you create in your Help Scout profile.
  • For Richpanel, "Import Method" offers two ways. "CSV Upload" needs no special Richpanel plan: export conversations from the Richpanel inbox and drop the CSV files on the upload area. Several files can be uploaded; they are merged, and a conversation that appears twice is kept once. "API Key (Enterprise)" needs a Richpanel Enterprise plan with API access.

Richpanel starts with "CSV Upload" selected.

"Default Store" is required and initially selects the first available store: imported data is put in this store unless the next step maps it elsewhere.

"Test Connection & Discover" (or "Upload & Discover" for CSV) checks the credentials and then counts what the account holds. That can take a minute. Wrong credentials give "Authentication failed"; an unreachable platform gives a connection message. "Back" returns to the platform choice.

Configure Import

Step 3 shows what was found and lets you choose what to bring over.

"Discovered Data" shows the number of tickets and customers, an estimate of the number of messages, and the date range of the tickets. If no tickets were found, the import cannot be started; check that the credentials may read tickets.

"What will be imported":

  • imported: tickets with their message history, customer profiles (name, email address, phone number), tags, and available email details. Subjects are limited to 500 characters and each message to 49,900 characters. Original email identifiers are retained for reference, but replies are not guaranteed to attach to imported tickets;
  • not imported: who a ticket was assigned to (every imported ticket is unassigned), custom fields, automation rules and macros.

What an imported ticket looks like in Squid:

  • It keeps its original creation and closing dates, its subject, its priority and its channel (email, chat or WhatsApp; any other channel becomes email). It gets a new Squid ticket number.
  • Its status is "Closed" when it was closed on the old platform. Every other status becomes "Open".
  • Each message keeps its date, its sender and whether it was from the customer or from your team. Internal notes from Gorgias, Zendesk, Re:amaze, Help Scout and Richpanel CSV exports come over as internal notes.
  • A ticket without any message is skipped. A ticket is also skipped if its customer could not be matched to an imported customer. So is a ticket that Squid already holds from an earlier import of the same platform, which makes it safe to run a second import for other addresses or dates.

Customers are imported first, all of them, whatever channels, addresses or dates you choose for the tickets. A customer whose email address already exists in Squid is not created again; the imported tickets are attached to the existing customer. A customer without an email address cannot be matched and is created as a new customer on every import.

"Channels": tick the channels to import. All discovered channels start selected. At least one is required.

"Email Addresses to Import": tick the support addresses to import. All discovered addresses start selected. If addresses were found, keep at least one selected. You can run another migration later for the rest.

"Email-to-Store Mapping": choose a store for each address that was found. Tickets of that address go to that store instead of the default store.

"Options":

  • "Include trashed tickets" and "Include spam tickets". Both switches start off. Trashed tickets can be brought over from Gorgias, Zendesk and Help Scout when the source returns them, and spam tickets from Gorgias, Re:amaze and Help Scout. For the other platforms the switches change nothing;
  • "Import tags" starts on. It creates the tags of the imported tickets under Settings → Tags when they do not exist yet. The tags are put on the imported tickets whether this is on or off;
  • "Import attachments" starts on. It copies the files attached to messages into Squid. A file larger than 25 MB is not copied. When the option is off, messages come over without their files;
  • "Date Filter": import only "Tickets created after" or "Tickets with last message after" a date you pick. The date cannot be in the future. Leave it empty to import everything.

Billing. Imported tickets count toward your ticket allowance.

  • Each ticket is counted at the moment it is imported, one by one. Customers, messages and attachments are not counted, and no AI messages are used.
  • On a trial, a "Trial Limit" box warns when the import would go over the trial's ticket allowance. The figure estimates the saved import scope, excluding trash and spam by default. Changes you are making on this screen are not reflected until saved. Address and date choices and duplicate tickets are not included in the estimate. If the trial allowance is already used up, the import cannot start until you upgrade. If it runs out during the import, the import pauses itself at that ticket; after you upgrade, "Resume" continues from there.
  • These billing boxes are available only with the "Billing" permission.
  • On a paid plan, a "Billing Impact" box shows your plan's allowance, your usage so far, the price per ticket over the allowance, and an estimated extra cost. Tickets over the allowance are billed as overage, like any other ticket.
  • Imported tickets count toward billing even if you undo or cancel the import afterwards, or if it fails. A ticket that was moved to the trash that way and is imported again in a new import is counted again.

"Start Import" begins the import. "Back" returns to the credentials.

Importing Data

Step 4 shows progress in two parts: "Step 1 of 2: Importing customer profiles..." and "Step 2 of 2: Importing conversations and messages...". Counters show customers, tickets, messages and attachments so far, with a time estimate. The attachment counters are not updated during import today and can remain zero even when files are copied.

The import runs on Squid's servers, not in your browser. You can leave the page, close the tab or sign out; it keeps running, and the page picks it up when you return. When it completes, the person who started it gets a notification. Import failures normally notify that person too; an initial credential-validation failure does not.

  • "Pause" requests a pause after you confirm. The import finishes its current batch before stopping and saves its progress.
  • "Resume" continues a paused import from where it stopped. Tickets that were already imported are not imported or counted twice.
  • "Cancel Import" stops the import for good after you confirm. Squid attempts to move the tickets imported so far to the trash, as with "Undo Import"; the confirmation says they will remain, which is not what happens. Imported customers stay. A cancelled import cannot be resumed.

If the page shows "Failed to load migrations", use "Check again", or "Cancel this import and start over" when an import is stuck.

Import summary and undo

Step 5 shows the outcome: "Import Complete", "Import Failed" or "Import Cancelled", with the numbers of customers, tickets, messages and attachments imported and, where it happened, how many failed.

For a failed import the page names the kind of problem: "Connection lost", "Rate limited", "Authentication error" or "Import error". If no error message was saved, it says "Unknown error". When an import fails, Squid attempts to move the tickets it had imported to the trash automatically, and imported customers stay. Cleanup failures can leave imported tickets in the inbox. For a lost connection or a rate limit the page says the import can be resumed, but a failed import cannot be resumed: only a paused one can. Start a new import instead.

"What's next?" reminds you that the imported tickets are in the inbox and that none of them is assigned to anyone.

"Undo Import" moves every imported ticket to the trash after you confirm. From the trash they can be deleted for good or restored. The "Undo Import" button appears only for a completed import. Failed and cancelled imports use automatic cleanup instead. It does not lower your billed ticket count. It does not remove the imported customers, and it skips an imported ticket that was merged into another ticket since.

"Done" closes the summary so a new import can be started.

"View Errors" appears when failures are recorded and opens their details. "Load more" fetches another 20 errors.

Migration History

Under the wizard, "Migration History" lists finished imports: the platform, the status ("completed", "failed" or "cancelled"), the numbers of customers and tickets imported, and the date. It only appears once an import has finished.