Freshchat 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 Freshchat, 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 has no Freshchat source, and no Freshchat conversation importer is documented in Intercom's help centre. A migration adds a written mapping, a sample run on your own data, a delta sync at cut-over and rollback.

Freshchat API: an hourly allowance specific to each business account and Freshchat plan, reported in the X-RateLimit-Limit and X-RateLimit-Remaining headers; Freshchat publishes no fixed numbers, so the read is paced on those headers. Messages come at most 50 a page. 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.

There is no single list of every conversation, so the user base is walked first and each user's conversation IDs collected before history can be read. Private messages must be written as Intercom notes and bot buttons flattened to text, which is checked on a sample before the full run. Raw reports only reach back 15 months, so historical metrics are exported early, before access to the Freshchat account ends.

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.