In this section (13)

What the Zendesk import brings over

The Zendesk data ChaosDesk imports, what stays the same and what you rebuild by hand.

1 min read

Imported

  • Account setup: brands and support addresses, groups, custom roles, ticket fields, user and organization fields, ticket forms with conditions, custom statuses, schedules and holidays, SLA policies.
  • People: agents, light agents and admins, end users with their emails and phones, organizations.
  • Rules: triggers and their categories, automations, macros and views, shared and personal, with their usage.
  • Tickets: every ticket with its comments, attachments, events, CCs, followers, tags, fields, satisfaction ratings and time spent.
  • Help centre: categories, sections and articles with their translations.
  • Webhooks.

What stays the same

  • Ticket numbers: an imported ticket keeps its Zendesk id, so links and references still work.
  • Help centre links: imported articles answer on their old Zendesk paths.
  • Placeholders and conditions: rules use the same names, so most work unchanged.

What you rebuild by hand

  • Rules that use something ChaosDesk can’t map. They come over inactive and are listed in the report.
  • Legacy targets: they show as Notify target (legacy, inactive). Replace them with webhooks.
  • Zendesk apps and marketplace integrations. Look for ChaosDesk apps, or call the Zendesk-compatible API.
  • Answer bots and Flow Builder flows. Rebuild them as answer flows.
  • Secrets such as the messaging JWT secret: always create new ones.

Was this article helpful?