Salesforce Service Cloud 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 Salesforce Service Cloud, so your team keeps working during the full run, and a delta sync at cut-over moves anything created or changed since.

No case importer. Intercom's Salesforce app syncs accounts with companies and leads or contacts from the moment it is set up, without importing historical records, and Intercom can sync Salesforce Knowledge as content for Fin and Copilot. A migration adds a written mapping, a sample run on your own data, a delta sync at cut-over and rollback.

Salesforce: a 24-hour allocation of 15,000 calls on Developer Edition; Enterprise and Professional (with API access) get 100,000 plus 1,000 per Salesforce licence, and Unlimited and Performance 100,000 plus 5,000 per licence. Requests over 20 seconds are limited to 25 concurrent in production. Bulk API calls count toward the same allocation. 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.

Case history spread across emails, comments and feed items has to be merged into one ordered thread with private comments kept internal. The 24-hour Salesforce allocation is shared with every other integration on the org, so extraction is paced around it. Teams often keep Salesforce as the account system of record, which shapes which fields are migrated and which are synced.

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.