Help Scout to Intercom migration

Configuration such as automations, macros and views is not data, so it is set up again in Intercom. Anything with no equivalent in Intercom is listed in the written mapping, and you choose what happens to it before anything moves.

Yes. Run it self-serve on the DataGrine platform, or let our migration team handle it end to end. Either way you get 24/7 premium support until the migration is signed off.

No. We only read from Help Scout, so your team keeps working during the full run, and a delta sync at cut-over moves anything created or changed since.

None documented. Intercom's Syncing and importing content collection lists article importers for Zendesk, Salesforce Knowledge and Freshdesk but nothing for Help Scout, and no Help Scout conversation importer is documented. A migration adds a written mapping, a sample run on your own data, a delta sync at cut-over and rollback.

Help Scout Inbox API: 200 calls a minute on Standard (no reporting endpoints), 400 on Plus and 800 on Pro, no API on Free; write requests count as two, and the limit is shared by all users on the account. The Docs API allows 2,000 to 4,000 requests per 10 minutes depending on the number of Docs sites. Runs are paced to stay inside that limit, which is why large accounts move in a full run first and a delta at cut-over.

Mailbox-scoped custom fields need a merge-or-separate decision before they become workspace-wide Intercom attributes. Attachments must stay on the thread they came from, which is easy to get wrong at volume. Each mailbox needs an agreed Intercom team or inbox, and teammates must exist before assignment can be kept.

It depends on how many records move and whether you run the migration yourself or have the DataGrine team run it. You get a quote once the records in scope are counted, before anything moves.