Zendesk to HubSpot migration

Configuration such as automations, macros and views is not data, so it is set up again in HubSpot. Anything with no equivalent in HubSpot 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 Zendesk, so your team keeps working during the full run, and a delta sync at cut-over moves anything created or changed since.

Partly. HubSpot imports Zendesk knowledge base articles by Smart copy (Service Hub Professional or Enterprise, up to 400 articles per import, primary language only) and imports records and activities such as notes and emails from files, with associations between them. HubSpot's knowledge base documents no importer that reads Zendesk tickets directly, so the ticket history is prepared from the Zendesk API first. A migration adds a written mapping, a sample run on your own data, a delta sync at cut-over and rollback.

Zendesk Support API: 200 requests a minute on Team, 400 on Professional, 700 on Enterprise and 2,500 on Enterprise Plus or with the High Volume add-on; incremental export endpoints are limited to 10 requests a minute (30 with High Volume). 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 ticket needs a pipeline and status decided before it moves, because HubSpot references both by internal ID. Comment history lands as logged emails and notes on the ticket timeline, so a sample is reviewed with agents before the full run. HubSpot's daily API allowance is shared by every app on the account, so the write is paced around existing integrations.

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.