Intercom to Freshdesk migration

Configuration such as automations, macros and views is not data, so it is set up again in Freshdesk. Anything with no equivalent in Freshdesk 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.

None documented for Intercom. Freshdesk's support site documents a built-in import app for Zendesk only, so Intercom data goes in through the Freshdesk API. 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. On this route the destination usually sets the pace: Freshdesk allows 100, 400 or 700 calls a minute by plan, with ticket create capped at 50, 160 and 280. 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.

Default status, type and group must be agreed for conversations that have none in Intercom. Freshdesk refuses values not on its choice lists and rejects the whole record, so lists must be checked before the run. Freshdesk's ticket-create allowance is a fraction of its total allowance, so large histories need a long, paced full run.

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.