Importing from Help Scout

Updated Nov 20, 202617 min read
English
On this page

Bring your Help Scout conversations, customers, organizations, saved replies and Docs knowledge base into Deskwoot. You need the App ID and App Secret of an app you create in Help Scout, and a Docs API key for your Docs articles. Everything comes over by default, and you can choose to import less. The import runs in the background, keeps going through Deskwoot updates and can be started again safely. Nothing in your Help Scout account changes.

What comes over

  • Conversations come with every thread: the customer's messages, your team's replies, chat lines, private notes and Help Scout's activity lines (assigned, closed, a workflow ran and so on), with their attachments and images. Each keeps its subject, tags, custom field values, original dates and the teammate or team it was assigned to. A call a teammate logged and the note a conversation was forwarded with come as private notes.
  • Deskwoot tickets: if your workspace uses tickets (your plan includes them and they are switched on under Settings > Tickets), each imported conversation also gets a Deskwoot ticket. The ticket takes over the status, subject, team, assignee and labels, and holds the work from then on. The conversation keeps every message, is resolved as the handover and shows a private card Ticket #… imported from Help Scout. A reply in the ticket goes out through that conversation. Without tickets, the conversation keeps its Help Scout status.
  • Tags become labels. Every tag of your account comes, also one that no imported conversation carries (for example one that only a workflow adds), so you find it when you rebuild that workflow.
  • Satisfaction ratings become CSAT ratings with the customer's comment on the matching conversation: Great becomes 5, Okay 3 and Not Good 1 on Deskwoot's scale of 1 to 5. A conversation with several ratings keeps the newest.
  • Customers become contacts with every email address and phone number, job title, location, address, websites, social profiles, chat handles, the values of your customer properties and their profile picture. The Notes field of a customer becomes the contact's description.
  • Organizations come with their details and the values of your organization properties, and each contact keeps its organization.
  • Users are matched to your teammates by email, also by the alternate emails they have in Help Scout (see below). Teams become teams, with those of their members who are already in your workspace.
  • Saved Replies become canned responses with their images and files. The short code comes from the saved reply's name. A saved reply that also has a chat text brings a second canned response for it, whose short code ends in _chat. Saved replies of several inboxes with the same name and text become one canned response; with the same name and another text, they get _2, _3 and so on. If a canned response with the same short code already exists in Deskwoot, the imported one is left out, and Import History shows how many were left out.
  • Custom fields of your inboxes become conversation attributes (fields with the same name and type in several inboxes become one), customer properties become contact attributes and organization properties become organization attributes.
  • Workflows that are active in Help Scout become automation rules with the same name, switched off and without conditions or actions, because Help Scout's API does not share them. Each rule says in its description which Help Scout workflow and inbox it came from, so you can rebuild it.
  • Docs: with a Docs API key, each Docs site becomes a help center of its own, named after the site. Collections become top categories with their categories below them. Published articles stay published, all others arrive as drafts.

Files and images

The import copies every file Help Scout hosts into Deskwoot: attachments of conversations, images pasted into messages and notes, images and file links in Docs articles and saved replies, and the profile pictures you uploaded for your customers. Nothing stays a link to Help Scout, so your files keep working after you leave Help Scout. If your workspace has booked the Virus scan, every file is scanned before it is stored.

  • Links between the pages of your Docs site, and links to them in saved replies and conversations, point at the matching page of your Deskwoot help center, also when that page is a draft or Team only. Customers can open such a page once you publish it for them. Without the knowledge base (no Docs API key, or Knowledge base switched off), these links stay links to your Docs site.
  • A profile picture that Help Scout shows from another service, such as Gravatar or a social network, is left out: the import never asks those services for it. So are the placeholder pictures Help Scout draws for customers without one.
  • An attachment that Help Scout's own virus scan blocked is left out.
  • If a file cannot be copied right now (Help Scout 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.
  • Import History lists these files under Files not imported with the reason, for example too large (over 25 MB, profile pictures over 2 MB), a file type that is not allowed, refused by a virus scan or no longer available at Help Scout.
  • Images that a message or an article loads from another website, such as your own, stay as they are.

What does not come over

Some things Help Scout's API does not give, and for some Deskwoot has no place:

  • The conditions and actions of a workflow (see above). Inactive workflows stay out.
  • Folders and views (Mine, Assigned, Closed and the views your team made), so no saved filters come.
  • Drafts, replies held for review, and spam and deleted conversations.
  • A priority, since Help Scout has none, and a snooze: Help Scout keeps a snoozed conversation active, so it comes in as open.
  • The To, CC and BCC addresses of conversations and replies, so reply all on an old conversation never mails them. The note a conversation was forwarded with comes without the address it went to.
  • The link between a forwarded conversation and the one the forward opened: both come, each with its own messages, but not linked to each other.
  • The messaging channel (WhatsApp, SMS, Messenger, Instagram) a conversation came through. Help Scout lists it as an email, chat or phone conversation, and it comes in as that.
  • The single messages of a Beacon chat that has ended: Help Scout keeps its transcript as one message, and it comes as one message.
  • In Docs: related articles, keywords, redirects, the site's logo and colors, and the unpublished draft of a published article (its published text comes). An article in several categories goes into the first of them. An empty category, such as the Uncategorized one every collection has, comes only once it holds an article.
  • Organization logos and brand colors, and the pictures of users and teams.
  • Help Scout's conversation numbers. Deskwoot numbers the conversations in the order Help Scout lists them, newest first.

What stays internal

Deskwoot keeps everything private that your Docs site did not show to everyone:

  • A private collection becomes a Team only category, together with every category in it. A category that is not public becomes Team only too.
  • Every category of a Docs site that has no public site, is switched off or uses Restricted Docs (only approved visitors, Plus and Pro plans) becomes Team only.

Team only categories and their articles are visible only to your team in the dashboard. They never show on the public help center, in the sitemap, in the chat widget or to Fynn, the AI bot.

Before you start

  1. Check your Help Scout plan. The import reads through Help Scout's API, which every paid plan and the trial include. Help Scout's Free plan has no API, so the import needs a paid plan or a trial.
  2. In Help Scout, click your avatar and open Your Profile > My Apps. Do this as the account owner, so the import sees every inbox. Click Create App, enter any name (for example "Deskwoot Migration") and any redirect URL (for example https://deskwoot.com), then save. Copy the App ID and the App Secret.
  3. For your Docs articles, also copy the key under Your Profile > Security & Access > Docs API.
  4. Invite your teammates to Deskwoot with the same email they use in Help Scout. You can also do this later.

How to import

  1. In Deskwoot, go to Settings > Import & Migration. Only admins can import.
  2. Pick Help Scout.
  3. Enter the App ID and the App Secret, and the Docs API key if you want your Docs articles. Without the key, your Docs articles stay out of the import. Deskwoot checks the keys with Help Scout when you start and tells you if Help Scout refuses them.
  4. Under What should come along?, choose what comes over. Everything is on by default. To import only newer conversations, pick a day under Only conversations created on or after.
  5. Under Which inbox should the conversations go to?, pick an inbox for each kind of conversation, or leave No inbox. Only email, Telegram, WhatsApp and SMS inboxes are offered, so set them up first.
  6. Click Start Import.

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. It also shows how many API calls per minute your Help Scout account allows and how many of them the import uses at most.
  • Help Scout gives each account a number of API calls per minute, depending on its plan, and counts the calls of all your apps and integrations together. The import uses at most 85% of that limit, so your other apps keep working while it runs. When the limit is reached, 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 Help Scout stops answering or refuses a list, 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. A list your Help Scout plan does not have (teams and inbox custom fields come with Plus and Pro) is skipped without a warning.

Your teammates' conversations and replies

A conversation assigned to a Help Scout user goes to the teammate with the same email, and their replies and notes show them as the sender. With tickets switched on, the Deskwoot ticket goes to that teammate too. A conversation assigned to a Help Scout team goes to the Deskwoot team of that name. If the user has no Deskwoot account yet, the conversation 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.

Inboxes for imported conversations

  • Help Scout notes whether each conversation is an email, a chat or a phone conversation, and whether it came through a Beacon or Docs contact form. The import puts each conversation into the inbox you picked for its kind (Email, Chat, Web forms and help center or Phone), so your team can answer it there. Help Scout lists WhatsApp, SMS and Messenger conversations as one of these kinds too, so the rows WhatsApp, SMS and Everything else get no Help Scout conversations.
  • A conversation 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 conversations come in without an inbox.
  • When you start the import again, earlier imported conversations go into the inboxes you pick too, if they have no inbox yet. A conversation 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.
  • A Deskwoot ticket has no inbox of its own: its replies go out through its conversation, so that conversation needs one.
  • Import History shows the inboxes you picked and how many conversations went into one.

After the import

  • A conversation 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. Import History shows under Still to do how many there are.
  • Rebuild your workflows: add the conditions and actions to each imported rule, then switch on the ones you want. Import History links to them with Check and turn on the rules.
  • Check the articles and categories of your new help center, and publish the ones your customers should see.

Frequently asked questions

Which Help Scout plan do I need?

A paid plan or a trial: Help Scout's Free plan has no API access. Teams, inbox custom fields and Restricted Docs exist in Help Scout only on Plus and Pro. On Standard, ratings are dated by the reply they rate, because Help Scout's reports, which give the time of each rating, are part of Plus and Pro only.

Can I import only part of my data?

Yes. Under What should come along?, everything is on by default, and you can switch off Conversations, Contacts and organizations, Knowledge base, Canned responses and Satisfaction ratings. With a day under Only conversations created on or after, only conversations created on or after that day come, and only the ratings given since then. Ratings come only with the conversations they rate, so that option is greyed out without the conversations. Tags come with the conversations too. Users, teams, workflows and the fields of conversations and contacts always come. If you leave out the contacts, each imported conversation still brings its own contact.

Import History shows under each import 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.

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 by each of their email addresses, whether written in upper or lower case. Their conversations then go to the contact you already have, and its name, details and fields stay as they are. If all of your contacts are in Deskwoot already, you can switch off Contacts and organizations: each conversation still goes to its contact, and one that Deskwoot does not have yet comes with the conversation.

Can I start the import again?

Yes, that is safe. A new run finds what is already in Deskwoot and skips it, so conversations, contacts and articles are not duplicated. It brings in what is new or was missing, for example after a run that ended with Imported partly. In a conversation it imported before, it adds new messages and tags, and it follows a new status, subject, assignee or team, as long as nobody worked on that conversation in Deskwoot. Custom field values changed in Help Scout and tags removed there are not followed.

If you merged two conversations in Help Scout after an earlier import, a new run brings the moved messages into the conversation Help Scout kept, and the merged one stays in Deskwoot as it was imported.

Help center articles your team edited in Deskwoot keep their new text, and a new run never publishes an article you unpublished or made Team only. If Help Scout has since made a collection or category private, a new run makes it Team only in Deskwoot too. If Help Scout has since unpublished an article, a new run unpublishes it in Deskwoot too, but only if your team has not edited it.

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

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

Help Scout 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.

How do I undo an import?

In Import History, click Delete next to the import, confirm and enter your password. This deletes the conversations, 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, labels, fields, automation rules, help center articles 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 Help Scout more than once, delete the imports from the newest to the oldest: while a newer Help Scout import exists, Deskwoot asks you to delete that one first.

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.