Run the Zendesk import

Before you start

Create an admin API token in Zendesk, under Admin Center, Apps and integrations, Zendesk API: turn token access on and add a token. Lower roles can't read admin-only setup such as custom roles, SLA policies, schedules and webhooks.

The importer only sends GET requests, so read access is enough. Endpoints your Zendesk plan does not have are skipped and listed in the report.

Import

1. Open Admin Center, Integrations, Import and pick Zendesk.
2. Enter the Zendesk subdomain (the part before .zendesk.com), the Admin email and the API token (or an OAuth access token instead), and choose Test connection. Optionally set Requests per minute to leave headroom for your team: 400 by default, at most 700.
3. Start a Dry run. It shows what would be imported without changing anything, reading the first 200 records of each entity.
4. Start the Full import. The Runs table shows progress per entity: created, updated, skipped and failed. A long import can be resumed.

You can limit a run to some entities, or to some Zendesk groups for one migration wave. Bot logs from Sunshine Conversations can be imported as closed history, or skipped.

The report

• Failed records and Warnings list what did not import and why.
• Rules that use something ChaosDesk can't map are imported inactive and listed under Untranslated rule items. Fix them in ChaosDesk, then run again.
• Reconcile counts compares the number of records in Zendesk and in ChaosDesk.

See What the Zendesk import brings over.

Related

• Parallel run and go-live
• Keep data in sync until go-live