Zoho Desk 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 Zoho Desk, 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 Zoho Desk source, and no Zoho Desk ticket 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.

Zoho Desk API credits per 24 hours: 5,000 on Free or trial, 25,000 plus 100 per agent on Express, 50,000 plus 250 per agent on Standard, 75,000 plus 500 per agent on Professional and 100,000 plus 1,000 per agent on Enterprise; concurrency is 5, 10, 10, 15 and 25 calls respectively. 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.

Per-department fields and layouts need a merge-or-separate decision before they become workspace-wide attributes. Private threads, private comments and public comments each need a deliberate mapping so nothing internal reaches the customer. The daily credit allowance can stop extraction partway through a day, so the full run is spread across several days on large accounts.

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.