Integrations & imports

Import from Help Scout

Bring over conversations and customer history with a small dry run before the full migration.

Owners and administrators can open Settings → Imports → Help Scout to bring over customer and conversation history. Supply authorized Help Scout credentials in the importer, not in a support message.

Choose the scope and mappings

The importer defaults to Conversations only (skip customers) and the current UTC conversation-creation year. Use this when you don’t need a full scan of the customer directory, especially if customers were already imported.

Map Help Scout users to existing OutcomeArc teammates and mailboxes to the intended inboxes. New inboxes can be created where configured. Mapping an imported author does not invite a new teammate or configure a live email sender.

The creation year selects conversations, not individual reply dates. A conversation created in one year includes its later replies too. Choose All years only when that is the intended scope.

Run a small sample

  1. Set one page and at most three conversations, with attachment downloads off initially.
  2. Run the dry run and inspect mappings, warnings, and the number of conversations actually found.
  3. Import the same small sample.
  4. Open the imported threads and check customers, authors, assignments, notes, drafts, tags, statuses, and dates.
  5. Test a small attachment-enabled sample if you need files migrated.

Dry-run counts describe potential writes, not imported records. Imported drafts remain unsent, and history does not trigger new automatic AI drafts or live playbooks.

Import the remaining history

Remove the small conversation limit and raise the page limit for the intended scope. For a full year, use 10,000 max pages and no max-conversation limit. Work one year at a time, waiting for completion and reviewing warnings before moving backward.

Save each job ID. Re-running an incomplete scope updates existing source-linked records rather than creating duplicates; review local edits before re-importing source-owned fields.

Check completion

Check conversation counts compares Help Scout’s totals with persisted imported totals, including per-inbox counts and separate native OutcomeArc conversations. It is read-only and doesn’t start an import.

Matching counts are a useful check, but also spot-check full threads and attachments. A completed job with warnings or a reached page/sample limit is not a complete migration.

If a run fails, review the error and saved scope, correct credentials or mappings as needed, and rerun a bounded sample before expanding again. Connect forwarding and sender verification separately before using imported inboxes for live support.

Browse all topics →

Still need a hand? Ask our team.