Moving from Zendesk
The Zendesk import tool allows you to import your entire ticket history (including customer profiles) from Zendesk into Help Scout. Your Zendesk data will remain untouched! Help Scout will only import a copy of each ticket and customer profile.
In this article
Things you should know
Here are a couple of key points to remember before flipping the switch on the import tool:
You'll likely use the same support email address as you do in Zendesk.
For example, messages sent to firstname.lastname@example.org will no longer be forwarded to email@example.com, but rather to your unique mailbox alias that looks something like this: firstname.lastname@example.org.
Help Scout does not have a web portal.
This is more of a transition for your customers, but be prepared to direct them to your dedicated support address. Since Help Scout is entirely email-based, you'll be providing top-notch email support going forward. You can always connect a custom contact form if another ticket channel is needed.
There are some tiny differences between status options.
Here's how they line up post-import:
- Open tickets will be marked as Active in Help Scout.
- On-Hold tickets will be marked as Pending in Help Scout.
- Solved tickets will be marked as Closed in Help Scout.
- Closed tickets will be marked as Closed in Help Scout.
Zendesk tags will be imported to Help Scout.
You'll see the same tags on the same tickets, of course. You can clean up or merge tags after the import if needed.
Help Scout does not have a ticket "type" field.
We're unable to maintain the problem-incident ticket relationship seen in Zendesk. Although those tickets will be imported, they will not be linked together in Help Scout via the ticket type.
We can import your Zendesk knowledge base and help center articles.
Both forum articles and help center articles created by Admins or Agents in Zendesk can be imported. Ownership of articles created by deleted Zendesk Agents will be re-assigned to the Help Scout Account Owner.
The import process may take time to finish.
You're looking at roughly one hour per 1,000 tickets, so large accounts can take a few days or more. However, your tickets are imported newest to oldest so, within a couple of hours, you'll have the most recent data.
Pre-import check list
- Create a new mailbox using your catch-all support email address.
- Set up your mailbox signature or change mailbox settings.
- Create new User accounts for your team.
- Disable ticket channels as you see fit. For example, turn off the Chat, Twitter, and Facebook integrations so that new requests are no longer funneled into Zendesk.
- Sort through your Macros and Trigger-based emails. Those bits of text will not be imported, so you might want to save them for later to use as Saved Replies in Help Scout.
- Make sure you're able to log in to your email provider's control panel. You should know where your mail forwarding options are located, and how to create or change forwarding rules. For provider specific instructions, check out these helpful articles.
- If you're using third-party integrations with Zendesk, such as Olark or SnapEngage, be prepared to change external integration settings after you've made the move to Help Scout. You can always install Help Scout integrations at a later time.
- Make coffee.
Starting the import
Grab your Zendesk API key from
API. You'll need to generate a new token, and copy it your clipboard.
Bounce back to Help Scout and navigate to Manage → Company → Import data to configure the importer, and select Zendesk from the list. Insert your Zendesk sub-domain, an administrator's email address, and your Zendesk API key. Select which mailbox to import tickets to, then press the Next Step button.
Note: In your browser's address bar, the sub-domain is the text preceding .zendesk.com. For example, in the URL mycompany.zendesk.com, the sub-domain would be mycompany.
- On the next screen, choose to import all of your Zendesk tickets, or only tickets created after a specific date. If you already have User accounts created, make sure to select the appropriate matching User from the dropdown menu. You might want to tag imported tickets just so you know what's what. We'd also recommend importing attachments, so you have a complete record of each ticket.
Remember: if you're importing a bunch of tickets, the import process could be lengthy. Once you've started the import, you can close the page and get back to
Note: If you run a second import at any stage, only new conversations will be imported, rather than new replies on previously imported tickets. We recommend having a team member work in Zendesk to manage incoming replies after you set up your forwarder and before your second import. Replies to those emails will get looped back to Help Scout courtesy of the forwarder.
When should I update my forwarding rule to send mail to Help Scout?
Before or after the import has finished will both work fine. You can change it before starting the import tool, and then work out of Help Scout going forward. If you wait to switch your forwarding rule to Help Scout until after the import has finished, you'll want to be sure to re-run your import to catch anything that came in since you started the original import.
After my testing, I deleted all of the imported tickets and knowledge base articles in Help Scout so I can re-import them in. Is that possible?
Unfortunately, no. We'd recommend only importing the tickets and articles in only once you're ready to start working within Help Scout, since we don't support re-importing in all the same data again.
How do I know which tickets were imported?
Imported tickets contain a tiny bit of text that looks something like this: Conversation imported from Zendesk ticket #723.