Intercom to Salesforce Service Cloud migration

Configuration such as automations, macros and views is not data, so it is set up again in Salesforce Service Cloud. Anything with no equivalent in Salesforce Service Cloud 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 Intercom, so your team keeps working during the full run, and a delta sync at cut-over moves anything created or changed since.

No helpdesk importer. Salesforce Data Loader is a client application for bulk import or export that works with every object type, so cases, contacts and accounts can be loaded from files, but each case's emails, comments and files have to be prepared and linked to it separately. Intercom's own Salesforce app syncs accounts with companies and leads or contacts from the moment it is set up, without moving conversation history. A migration adds a written mapping, a sample run on your own data, a delta sync at cut-over and rollback.

Intercom REST API: 10,000 calls a minute per app and 25,000 per workspace by default, spread over 10-second windows; the same limits apply on every plan as documented. 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.

Original created dates need Salesforce's permission to set audit fields enabled for the import, otherwise every case is dated the day it moves. Each conversation has to be split into email messages, case comments and files in time order, with notes kept unpublished. On this route Salesforce sets the pace: its 24-hour API allocation is shared by every integration on the org.

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.