To migrate from Gorgias without losing your ticket history, connect Gorgias to REP AI, open Settings > Integrations in the REP AI Console and click Migrate to Rep Inbox on the Gorgias integration card. Migration copies all of your open tickets with full conversation history, your customers and their details, and, if you choose, your closed tickets and macros into Rep Inbox, with nothing to rebuild by hand.
The same steps work for Zendesk, Kustomer, Freshdesk and Richpanel. Your old helpdesk stays connected and fully working until the migration succeeds.
What does migration do?
If you are already using another helpdesk, Rep Inbox can bring your history with you. Migration copies your open tickets (with full conversation history), your customers and their details, and optionally your closed tickets and macros, so your team can pick up right where they left off, inside REP AI.
Supported helpdesks: Gorgias, Zendesk, Kustomer, Freshdesk, and Richpanel.
What do I need before I start?
- You need to be an Admin. Migrating requires activating the Rep Inbox add-on, and only an Admin can do that. If you are on another role, ask your Admin to set it up. (Once it is live, Support Managers, Agents, and Agencies can all use the Inbox.)
- Your current helpdesk must be connected to REP AI as an integration. If REP AI already hands off conversations to your helpdesk, you are ready.
- A plan is required. If you do not have one yet, you will be asked to choose a plan first, then you will land on the migration screen.
How do I run a migration?
- In the REP AI Console, open Settings > Integrations and find your connected helpdesk. You can also start from the Rep Inbox menu.
- Click Migrate to Rep Inbox on the integration card.
- In the migration window, review what will be moved and choose your options (see below).
- Confirm. If prompted, approve the Rep Inbox add-on in Shopify, then the migration begins.
- That is it. The migration runs in the background. You can close the window and check back anytime.
Migrating from Richpanel? There is one extra step and a few differences. See How do I migrate from Richpanel? below.
Which options can I set?
- Migrate macros? Choose whether to bring your response templates across.
- Migrate closed tickets? Choose whether to include closed tickets, and if so, set a lookback window (in days). A closed ticket is migrated only if it was created within that window. Open tickets always migrate in full.
- Add teammates. If people who handle tickets in your current helpdesk are not yet part of your REP AI team, you can add them right from this window. Anyone you do not add will still have their tickets migrated. Those tickets simply arrive Unassigned.
What gets migrated?
- Tickets: all open tickets with full conversation history, including tags, priority, assignee, and attachments. Internal notes come across from Gorgias, Zendesk, Kustomer, and Freshdesk. Closed tickets come across based on your lookback setting.
- Customers: all of your customer records and their details that are available to us. (Richpanel works differently. See the Richpanel section below.)
- Macros: your response templates, if you chose to include them.
Which customer details come across from each helpdesk?
Rep Inbox brings over the customer information each helpdesk makes available. Here is what transfers from each:
| Helpdesk | Details migrated |
|---|---|
| Gorgias | Name, email, and the customer note. Additional details such as time zone and language are saved as custom fields. Phone number is added from the ticket details when available. |
| Zendesk | Name, email, phone, and agent notes. Additional details (your custom user fields, the "details" field, time zone, language, and tags) are saved as custom fields. |
| Kustomer | Name, email, and phone. Additional details such as company, time zone, language, gender, tags, location, social profiles, and other custom attributes are saved as custom fields. (Customer-profile notes are not migrated.) |
| Freshdesk | Name, email, phone, and the contact description (as notes). Your custom contact fields and job title are saved as custom fields. |
| Richpanel | Name, email, and phone, taken from each ticket's customer details. |
How do I migrate from Richpanel?
Richpanel migration works the same way, with two differences worth knowing before you start.
Why do I add a second Richpanel key?
Richpanel issues two different credentials. The one you used to connect Richpanel to REP AI powers live conversations. Reading your ticket history needs a separate API key, so the migration window asks for it.
When you start the migration, you will see a step called Add your Richpanel API key:
- In Richpanel, open Settings > Integrations > API Keys.
- Create a key, or copy one you already have.
- Paste it into the migration window and continue.
Your existing Richpanel connection stays exactly as it is. The new key is stored separately and only used to read your history.
What comes across from Richpanel?
Your tickets arrive with their full conversation history, tags, priority, assignee, and attachments. Customers come across for the tickets that migrate.
A few Richpanel-specific things to expect:
- Your Richpanel customers come from the tickets that migrate. Richpanel makes a customer record reachable only through their conversations, so the customers you get are the ones attached to the tickets in your migration. If you choose to leave closed tickets out, a customer whose only tickets are closed stays in Richpanel.
- Internal notes stay in Richpanel. Their API does not make private notes available to other systems.
- Macros stay in Richpanel. Richpanel does not offer a way for other systems to read saved replies, so there is nothing to bring across. The macro option does not appear when you migrate from Richpanel.
-
Snoozed tickets arrive open, tagged
snoozed-in-richpanel. Richpanel records that a conversation is snoozed but not when it should return, so the tickets stay visible and you can filter by that tag to re-snooze whichever ones you want. - Some older messages may show "Message size is too big" instead of their text, and a few attachments may not arrive. Both reflect what Richpanel stored. Where the original content is not kept on their side, there is nothing to transfer.
What does not migrate?
- Macros with built-in actions will not come across. Rep Inbox macros are text templates, so any automated actions attached to a macro are not supported. The text of the macro still migrates.
- Placeholders inside macros (like a customer-name or order-number token) migrate as plain text. They will not be automatically replaced with live data in Rep Inbox.
- Customers with no way to identify them are skipped. Rep Inbox identifies a customer by email address, and falls back to their ID in your old helpdesk, or their name or phone number. A record with none of these is skipped.
- Very large tickets (an unusually big conversation with a lot of data or attachments) may be skipped.
- Closed tickets outside your lookback window are not migrated.
Anything that is skipped is reported to you in the summary email when the migration finishes, so you always know what came across and what did not.
How long does migration take?
Migration time depends on how much data is in your current helpdesk, and it might take a few hours.
The migration runs in the background, so you do not have to keep the window open. You can check its status anytime from the Rep Inbox menu or the integration card. Only choosing Cancel stops it.
Heads up: You cannot open Rep Inbox until the migration finishes. As soon as it is done, the Inbox is ready to use.
What happens when the migration finishes?
If it succeeds
- Rep Inbox automatically disconnects your old helpdesk and connects the Inbox.
- Your team gets an email summary confirming what was migrated and listing anything that was skipped.
- You can now open Rep Inbox and work as normal.
If it fails
- You will get an email letting you know it failed. Nothing changes. Your old helpdesk stays connected and no data is lost.
- You can simply try again. If the migration had already reached the ticket stage, it usually resumes from where it stopped. Otherwise it starts over.
Where can I learn more about Rep Inbox?
- Getting Started with Rep Inbox
- Rep Inbox: General Information and Billing
- Connecting Your Email to Rep Inbox
Frequently asked questions
Will my customers notice anything during the migration?
No. Migration copies your data in the background and does not change how customers reach you while it runs.
Can I keep using my old helpdesk until I am ready?
Yes. Your old helpdesk stays connected and fully working until the migration succeeds. Only then does Rep Inbox switch over.
What happens to tickets that were assigned to someone not on my REP AI team?
Those tickets still migrate. They just arrive Unassigned. To keep assignments, add those teammates in the migration window before you start.
Do I have to migrate closed tickets and macros?
No. Both are optional. You choose whether to include them, and for closed tickets you set how far back to go.
Why does Richpanel need a second API key?
Richpanel issues one credential for live conversations and a separate one for reading your history. The migration window asks for the second key so it can read your tickets, and your existing connection stays untouched.
How much does Rep Inbox cost after migrating?
Rep Inbox is billed per seat per month, and one seat is one Console user. On a monthly plan a seat is $20 per month. Check the billing article above for annual pricing, trial details and any current migration offer.