↑↓ selectEnter openEsc close

    1. Elbuz

    How to move tickets from another support system

    8 min readUpdated

    Elbuz moves tickets with conversations and notes, customers, canned replies and articles from your old support system itself, so no history is lost and support never stops.

    When you need this:

    • A customer writes a year later — their old conversation is in “Tickets”, found by the old number.
    • The old system is still in use — a repeat run picks up new tickets without duplicates.
    • Years of canned replies — they become macros, articles become knowledge base drafts.
    • Hundreds of customers — Elbuz finds existing contacts by email or phone and creates the rest.

    Where to start: preparation, then the gear in “Tickets” → “Move from other systems”.

    What the move can do

    • Seven services — Zendesk, Freshdesk, HelpCrunch, Help Scout, Zoho Desk, Gorgias, Intercom; each has its own tab with a hint on where to get the key.
    • Tickets with conversations — messages, internal notes, statuses, priorities, tags, ratings, dates.
    • Customers — matched against your contacts with the same duplicate check that email and chats use; if not found, they are created.
    • Macros and articles — canned replies become macros, published articles become drafts.
    • In portions, in the background — close the window and the move continues from where it stopped.
    • Repeat runs without duplicates — a ticket that was already moved is skipped by service and number.

    In what order to move

    1. Add employees and set up SLAUsers; “Tickets” → “Support desk settings”
    2. Move everything you haveMove to Tickets
    3. Check what was movedTickets
    4. Work in parallel and pick up new ticketsMove to Tickets
    5. Final repeat run and turning off the old systemMove to Tickets

    Why work in parallel: while you check what was moved, customers keep writing to the old system. A repeat run with the same key picks up only new tickets. So turn off the old service not on moving day, but once your channels (email, chat, messengers) lead to Elbuz and nothing new appears there.

    What to do before you start

    Preparing for the move

    Why this matters before the start, not after:

    • Assignees. Elbuz looks for the ticket assignee among active Elbuz employees by email. If none is found, the ticket is moved unassigned and won't be reassigned automatically once the employee is added.
    • SLA. Deadlines for open tickets (“New”, “Open”, “Pending”, “On hold”) are counted from the moment of the move, based on priority and your current settings. Old tickets won't become overdue right away and won't flood managers with escalations. But deadlines are set at the moment a ticket is written.
    • Assignment. If ticket assignment is on, new and open moved tickets without an assignee are handed out to employees of the “Customer service” department — all moved tickets go to this department. How assignment works: ticket assignment.

    How the move runs

    After “Check and move”, Elbuz first contacts the service with your key. If it's refused, the move doesn't start and the window shows one of three messages:

    • “Fill in all connection fields” — an empty field, an invalid email, or an address in the wrong format;
    • “The service refused: check the address and the key” — with the service's response text below;
    • “Use an agent or admin key, not an end user” — the key belongs to an end user.

    Then three stages run in turn. You can follow them in the progress line: “Canned replies…”, “Knowledge base articles…”, “Tickets with conversations…”, then “Done.” and the counter “Moved: N tickets, N messages, N new customers, N macros, N articles”.

    • Portions. Elbuz works in portions of about 20 seconds and saves where it stopped after each page of the service's list.
    • Window closed. The move continues in the background: the “Tickets” background task runs one portion (up to 20 seconds of work) every 5 minutes. With the window open, portions run back to back, so a large account moves faster with the window open. When you reopen the window, progress is shown from where it stopped.
    • Rate limits. If the service replies “too many requests”, Elbuz waits once for as long as it asks (up to 30 seconds) and tries again.
    • Error. The move stops with the message “The move stopped: ‹reason›. Run it again — we continue from the same place.” Click “Check and move” again; you can leave the key fields empty.
    • No knowledge base or canned replies in the plan. If the service refuses the list of canned replies or articles right away, the stage is skipped silently and the move goes on to tickets. If it returns the list but denies a folder (Zoho department templates, Help Scout mailbox saved replies, a Freshdesk article folder) — access denied or “not found” — that folder is skipped and the move continues. To get it, grant the key the needed permissions and run again.

    After saving, the key fields in the window are empty with the hint “saved — leave empty”: an empty field means “the same key”. Keys are never shown in the window.

    Zendesk tab with the green progress block showing the finished move
    1Result counter
    2Last move date
    1. The progress block reads Done with the counts of moved tickets, messages, customers, macros and articles.
    2. The last-move line shows when the previous run finished and reminds you that a rerun picks up new tickets.

    What happens when you run it again

    What happens if you run it again
    SituationWhat happens
    Same fields, move not finished (error, stop)It continues from where it stopped
    Same fields, move already “Done”Canned replies and articles aren't reread; Elbuz goes straight to tickets and picks up those created since then. The window reminds you: “Last move: ‹date›. Tickets created since then — run it again.”
    A different key or addressEverything from the start: canned replies, articles, tickets. There will be no duplicates: Elbuz skips a macro with the same name, an article with the same name and language, and a ticket already moved

    In Freshdesk and Intercom, every repeat run goes through the ticket list from the start. Tickets already moved are skipped quickly, without loading conversations, but for a large account this takes time. In other services, a run continues from where the previous one ended.

    Elbuz filters out duplicates by service and ticket number, without regard to the account: in some services the account is visible only through the key, and keys get replaced, so tying to the key would create duplicates after every replacement. So if you move from two accounts of the same service (two Zendesk, two Freshdesk), tickets of the second account whose numbers already exist in the first won't be moved.

    What is moved and how

    What becomes of the old system's data
    In the old systemIn Elbuz
    TicketA ticket with the number from the old system; the channel (email, chat, phone, messenger) stays as it was, if the service reports it
    ConversationThe ticket timeline: customer messages, employee replies and internal notes — separately, with author and date
    AttachmentsA link with the file name; the file itself stays in the old system
    CustomerA contact: searched by email, or by phone if there's no email, with the same duplicate check as email, chat and calls. If two match, the ticket stays without a customer. If none is found, one is created in the “Customers” group with the service name in the “Source” field; the customer's history gets a “Record created” entry on behalf of the service. The owner is the ticket assignee if their email matches an employee's, otherwise the least busy sales manager
    AssigneeThe active Elbuz employee with the same email; if there is none — unassigned
    Status“New”, “Open”, “Pending”, “On hold”, “Solved”, “Closed”; an unknown status becomes “Open”
    Priority“Low”, “Normal”, “High”, “Urgent”; if missing — “Normal”
    Tags, dates, customer ratingTicket tags; created and modified dates; a “Good” / “Bad” rating with a comment
    Ticket without a subjectThe customer's first message becomes the subject
    Canned repliesPublic macros; if a macro with the same name already exists, the reply is skipped
    Knowledge base articles (published)Drafts in the “Articles” window, in the article's language if the store has that language; otherwise in the storefront's main language

    All moved tickets go to the “Customer service” department, are marked as read and have no AI analysis: reason, summary and tone are empty. Articles are moved as drafts on purpose: review them before publishing, because AI uses published articles to answer customers (AI in tickets).

    What stays in the old system

    • Views, groups, triggers, automations and SLA policies. Elbuz has its own queues, assignment and deadlines — set them up before the move.
    • Organizations and custom ticket and customer fields. Only the customer's name, email and phone are moved.
    • Agent accounts. Elbuz doesn't create employees, it only matches existing ones by email.
    • Attachment files. Only links to the old service remain. Once the old system is turned off, the files behind them may become unavailable — save the ones you need in advance.
    • Deleted tickets and spam. Zendesk — deleted, Help Scout — spam, Gorgias — spam and trash, HelpCrunch — empty chats.
    • AI analysis. Moved tickets get no automatic analysis. “AI draft” and “Create an article from the reply” do read the moved conversation — click the button when you need it.

    Where to get the key in each service

    The menu paths below are the same as in the hints on the tabs. Services rename menu items from time to time; if an item is called something else, look for the section in the service's settings.

    Zendesk

    Key: Zendesk Admin Center → Apps and integrations → APIs → Zendesk API → enable Token access → Add API token. The window has three fields: “Account address” (acme.zendesk.com or just acme), “Agent or admin email” and “API token”.

    A custom help center domain (for example, support.acme.com) won't work — you need the ….zendesk.com address. The email must belong to an agent or admin, otherwise you get “Use an agent or admin key, not an end user”.

    Moved: tickets with conversations and internal notes, statuses (“hold” becomes “On hold”), priorities, tags, “good” / “bad” ratings with a comment, dates, channel; customers; macros together with their actions: changing status, priority, tags and “assign to me”.

    Placeholders in macro text are replaced with ours: customer name → {CUSTOMER_NAME}, ticket number → {TICKET_ID}, agent name → {AGENT_NAME}. Published Help Center articles become drafts.

    Not moved: deleted tickets, Help Center article drafts.

    Freshdesk

    Key: Freshdesk → avatar at top right → Profile settings → View API Key. Fields: “Account address” (acme.freshdesk.com) and “API Key”.

    Moved: tickets with conversations and private notes; the first message is the ticket description. Statuses: the standard ones, while custom “waiting on customer / third party” statuses (codes 6 and 7) become “On hold”. Also priorities, tags, dates, customers, canned responses as macros without actions, and published Solutions articles as drafts.

    Not moved: customer ratings, unpublished articles.

    Elbuz takes Freshdesk tickets oldest first, 30 per page. The Freshdesk API returns the list only up to page 300, so after that Elbuz continues from the date of the last ticket received. There is no limit on the number of tickets; after “Done.” compare the “Moved: N tickets” counter with the count in Freshdesk.

    HelpCrunch

    Key: HelpCrunch → Settings → Developers → Public API → create an API key (not Legacy). There is one field — “API key”.

    Moved: chats with conversations and private notes, statuses (“no communication” becomes “Closed”), “great” / “poor” ratings, dates, customers. The channel of all tickets is chat, the priority is “Normal”. The subject is the customer's first message.

    Not moved: canned replies and the knowledge base — the HelpCrunch public API doesn't have them, move them by hand. Also empty chats, system messages, tags and attachments.

    Help Scout

    Key: Help Scout → your profile → My Apps → Create My App. Redirect URL can be any address, it isn't used. Copy the App and App Secret into the “App ID” and “App Secret” fields. Elbuz gets the access token itself and renews it when it expires.

    Moved: conversations from all mailboxes with threads and notes, statuses, tags, dates, channel (email, chat, phone), customers, and each mailbox's saved replies as macros. Priority is “Normal”.

    Not moved: Help Scout Docs articles (they have a separate API with its own key), spam, system entries in a conversation (forwarding, assignee change), ratings.

    Zoho Desk

    Zoho doesn't issue a ready-made key — you get one in the developer console. Fields: “Your Zoho Desk address”, “Client ID”, “Client Secret”, “Refresh token”.

    1. Open api-console.zoho.eu or api-console.zoho.com — the same domain as your Desk address in the browser (desk.zoho.eu → .eu).
    2. Add Client → Self Client → Create. Copy the Client ID and Client Secret.
    3. Open the Generate Code tab. In the Scope field, paste:
      Desk.tickets.READ,Desk.contacts.READ,Desk.basic.READ,Desk.articles.READ,Desk.templates.READ
      Choose a time duration, enter any description, click Create. Copy the code: it is valid only for the chosen duration.
    4. Exchange the code for a refresh token with a request to the same domain (example for .eu; on Windows, run it in PowerShell as curl.exe):
      curl -X POST https://accounts.zoho.eu/oauth/v2/token -d grant_type=authorization_code -d client_id=YOUR_CLIENT_ID -d client_secret=YOUR_CLIENT_SECRET -d code=CODE_FROM_STEP_3
    5. In the response, find "refresh_token":"1000.…" and paste that value into the “Refresh token” field.
    6. In the “Your Zoho Desk address” field, enter the address from your browser, for example desk.zoho.eu.

    Elbuz supports Zoho domains .com, .eu, .in, .com.au, .jp, .ca, .sa, .uk, .com.cn. Any other address gives “Fill in all connection fields”. If the token sees several Zoho Desk portals, the first one is moved.

    Moved: tickets with threads (private threads as notes) and comments (as notes), statuses (Open, On Hold, Closed), priorities, tags, dates, channel, customers, email templates from all departments as macros, published knowledge base articles as drafts.

    Not moved: archived tickets, ratings.

    Gorgias

    Key: Gorgias → Settings → Account → API → Create API Key. The section is visible to the owner and admins, and the key is shown only once. Fields: “Account address” (acme.gorgias.com), “Your Gorgias email”, “API key”.

    Moved: tickets with conversations and internal notes, tags, dates, channel, customers, macros with tags and status. Priority: “critical” becomes “Urgent”. Ratings: 4–5 become “Good”, 1–2 “Bad”, 3 — no rating.

    Not moved: the knowledge base (the Gorgias REST API doesn't have it), spam and trash. Statuses are simplified: a closed ticket becomes “Closed”, anything else “Open”.

    Intercom

    Key: Intercom → Developer Hub → New app → Configure → Authentication → Access token. Fields: “Workspace region” (US, EU or AU — where your Intercom is hosted; the wrong region gives “The service refused…”) and “Access token”. The token must belong to an admin.

    Moved: conversations with messages and notes, statuses (“snoozed” becomes “On hold”), priorities, tags, 1–5 ratings with a comment (4–5 — “Good”, 1–2 — “Bad”), dates, channel, customers, macros, published Help Center articles as drafts.

    Not moved: for very long conversations, Intercom returns only the last 500 messages — the beginning of such a conversation won't come through. System events without text (assignment, open/close) are skipped; an event with text appears in the timeline as a message.

    What to check after the move

    In a moved ticket's card, “‹Service› #N” appears next to the number, for example “Zendesk #N”, and the timeline has the event “Moved from Zendesk (ticket #N)”.

    Searching “Tickets” by number (“N” or “#N”) finds both the moved ticket with that number and the Elbuz ticket with the same number. The number is searched across all tickets that “Data scope” opens to you, whatever queue is selected — including closed ones.

    Checking after the move

    The move for each of the seven services was tested on simulators of their APIs built from the services' documentation, not on live accounts. If a service changes its response format or a field name, the move may stop with an error or skip part of the data. That's why the check after the move is mandatory, not a formality.

    What to expect from moved tickets:

    • “Solved” become “Closed”. Elbuz closes tickets in “Solved” status 4 days after they were solved. For moved tickets, the solved date is the modified date in the old system, so at the very first sync almost all of them become “Closed”.
    • A reply to a moved email goes as a new email. Elbuz “Mail” doesn't have the email from the old system, so “Send” sends the customer a new email to the address from the customer card or the ticket contact, with the subject “Ticket #N: …” — like “Email to …”. The customer's reply to it comes into the same ticket. A moved call has no “Reply” button at all, only a note. A moved chat or call with a known customer email has an “Email to ‹address›” button: it sends a new email with the subject “Ticket #N: …”.
    • New messages in the old system won't appear on their own. Only a repeat run brings them. A repeat run doesn't pick up extra messages in a ticket that was already moved: it skips the whole ticket.

    When to turn off the old system

    1. Support email, website chat and messengers already lead to Elbuz (where tickets come from), and no new tickets have appeared in the old system for a few days.
    2. Replies to tickets that stayed open in the old system were finished there, not in Elbuz.
    3. The final repeat run is done and the counter stopped growing.
    4. The attachments you need are saved: after the old system is turned off, file links may stop working.
    Moved ticket #110 with the Zendesk number in the header and the conversation thread
    1Zendesk #4812 in the header
    2Internal note
    1. The header shows the original Zendesk ticket number next to the ticket.
    2. The thread keeps the customer message, the agent reply and the internal note.

    Scenarios

    Moving without a day of downtime

    What to do. Move everything, connect email, chat and messengers to Elbuz, and pick up new tickets with repeat runs for a few days. Result. Customers write as before; when new tickets stop appearing in the old system, do the final run and turn it off (when to turn off).

    A large account with tens of thousands of tickets

    What to do. Start the move and keep the window open. Result. Portions run back to back; if you close the window, the move continues in the background, one portion every 5 minutes. After “Done.” compare the “Moved: N tickets” counter with the old system.

    A service without a knowledge base (HelpCrunch, Gorgias)

    What to do. Move the tickets, and move articles and canned replies by hand. Result. The articles stage is skipped without an error; replies from the moved conversations can be turned into articles with the “Create an article from the reply” button.

    What to do when the move doesn't run

    What you seeWhyWhat to do
    “Fill in all connection fields” An empty field, an invalid email, a custom domain instead of the service address, or a Zoho domain not on the list Enter an address like acme.zendesk.com (services)
    “The service refused: check the address and the key” The key was revoked or copied incompletely, the wrong Intercom region, an expired Zoho code Create the key again; for Zoho — a new code and a new refresh token (Zoho Desk)
    “Use an agent or admin key, not an end user” The email or token belongs to an end user (Zendesk) or not to an admin (Intercom) Get the key under an admin account
    “The move stopped: … Run it again — we continue from the same place.” The service returned an error or hit the rate limit twice in a row Click “Check and move” with the key fields empty (how the move runs)
    “0 articles” or “0 macros”, although the service has them The service didn't give access to the knowledge base or canned replies, and the stage was skipped; or they all already exist under the same names Check the key's permissions and the service plan; HelpCrunch and Gorgias don't return a knowledge base at all
    Moved tickets without an assignee Elbuz has no active employee with the same email as in the old system Assign by hand; for future runs, add the employee in advance (before you start)
    “Could not send” in a moved ticket The reply goes as a new email, and the customer's address is missing from both the customer card and the ticket contact, or the mailbox didn't send the email Link a customer with an email or check the mailbox in “Mail” (after the move)
    After closing the window, the counter grows slowly In the background, one portion runs every 5 minutes Open the window and keep it open until “Done.” — portions will run back to back

    FAQ

    Will there be duplicates if I run the move twice?

    No: a ticket already moved, and a macro or article with the same name, are skipped. The exception is two accounts of the same service (repeat runs).

    Can I close the window during the move?

    Yes, no data is lost: the move continues in the background, but more slowly (how the move runs).

    Are attachments moved?

    As links with the file name. The files themselves stay in the old system — save the ones you need before turning it off.

    Why aren't old tickets overdue under SLA?

    Deadlines for open moved tickets are counted from the moment of the move, not from the date in the old system — otherwise managers would get an avalanche of escalations.

    How do I find a ticket by its number from the old system?

    Enter the number in the search above the list, with or without “#”, in any queue. A moved ticket's card shows “‹Service› #N”.

    Can I move from CSV or Excel?

    No, the move works only through the API of the seven listed services (services).

    Where it is and who has access

    From the “Tickets” window
    the gear icon in the header of the left queue panel → “Move from other systems”
    Window search
    “Move to Tickets”
    Access right
    “Management” only: other departments don't see the window or the menu item
    Prepare
    an agent or admin key for the old system; employees with the same email addresses

    This window has no main menu item or desktop shortcut: moving is a one-time operation. The window has one tab per service. Each tab has a hint on where to get the key, a “What is moved:” line, the connection fields and the “Check and move” button.

    The “Move to Tickets” window with the Zendesk tab open
    1Service tabs
    2Where to get the key
    3What is moved
    4Account address field
    5Check and move button
    1. Service tabs — one tab per system, from Zendesk to Intercom.
    2. Where to get the key — the hint shows the path to the API token in the source service.
    3. What is moved — tickets with conversations, notes, customers, macros and articles.
    4. Account address, email and token — the three fields for the connection (fake values here, token left empty).
    5. Check and move — starts the move; it runs in the background in portions.

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free