Kustomer 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 Kustomer, 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 sources such as Zendesk, Salesforce Knowledge and Freshdesk but nothing for Kustomer, and no Kustomer 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.

Kustomer API: a per-organisation limit set by plan and shared by every API token, counted over 60-second intervals; searches by machine users have a separate 100 requests a minute, a single conversation or company can be updated 100 times in 10 minutes, and standard search only returns records updated in the past two years (older ones need Archive Search). 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.

Every Klass of custom objects needs a keep, flatten or link-back decision before the mapping can be signed off. Conversations older than two years are not returned by standard search, so the read plan has to use Archive Search or per-customer reads to cover the full history. Business rules, workflows and queue logic cannot be exported from Kustomer, so they are documented by hand before access 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.