In this section (13)
- Moving to ChaosDesk
- Run the Zendesk import
- Parallel run and go-live
- What the Zendesk import brings over
- Import from Freshdesk
- Import from Help Scout
- Import from a spreadsheet
- Keep data in sync until go-live
- Keep your Zendesk scripts working
- Switch the Zendesk widget to the ChaosDesk messenger
- Import from Intercom, Gorgias, Zoho Desk, Front, HubSpot or Jira
- Import from Salesforce, ServiceNow, Zammad, Kayako, LiveAgent or osTicket
- Import a help centre from a website or files
Run the Zendesk import
Connect your Zendesk account, run a dry run, import and read the report.
Before you start
Create an admin API token in Zendesk. Lower roles can’t read every view and macro, SLA policies, schedules or the incremental export.
Import
- Open Admin Center, Integrations, Import and pick Zendesk.
- 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. - Start a Dry run. It shows what would be imported without changing anything.
- 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
Was this article helpful?
Thanks for letting us know.
Sorry about that. Tell us what was missing and we will improve the article.