What comes over when you import a Zendesk account

A walk through everything the ChaosDesk importer copies from Zendesk, in what order, and how it handles the things that do not map one to one.

A bright data centre with rows of server cabinets
Photo: Taylor Vick / Unsplash

“Can we keep our history?” is the first question every team asks. With ChaosDesk the answer is yes, all of it. Here is what the importer brings over and how.

In dependency order

The importer runs in the order records depend on each other, and every step can be repeated: a second run updates records, it never duplicates them.

  1. Brands and support addresses, with each address’s default group and form.
  2. Groups, private ones included, and their memberships.
  3. Custom roles, mapped to ChaosDesk permissions.
  4. Users and identities, then organizations with their domains, then user and organization fields.
  5. Ticket fields, including drop-downs with nested :: options, then ticket forms with their conditions.
  6. Business schedules, holidays and SLA policies.
  7. Rules: triggers with their categories and positions, automations, macros and views, personal ones included.
  8. Webhooks, each imported active, inactive or skipped according to a policy you choose.
  9. Tickets, with comments, attachments, tags, CCs, followers and custom fields.
  10. CSAT ratings and the help centre, for every brand and language.

Your ticket numbers stay

The Zendesk ticket id becomes the ChaosDesk ticket number. New tickets start above the highest imported id, so “ticket 48213” means the same ticket before and after.

History, replayed quietly

Each ticket’s audits are replayed with their original time and actor. That keeps reports and SLA history meaningful. The replay fires no triggers, notifications, webhooks or SLA side effects: customers hear nothing.

When something does not map

Some rules use a condition or action that has no ChaosDesk equivalent yet. Those rules are imported inactive and listed in the unmapped-rule report. Nothing is dropped silently. Rules that call a skipped webhook are handled the same way.

Bot conversations that no agent touched are imported as closed history, tagged bot_log, so they never appear in a queue or count against an SLA.

Imported help-centre articles answer on their old Zendesk paths. Links in macros, emails and search results still land on the right article.

Run it as often as you like

The importer streams in batches, respects Zendesk’s rate limits, and stores its progress, so a long import can pause and resume. Delta imports keep ChaosDesk in step during the parallel run.

See the whole switching process.

Zendesk is a trademark of Zendesk, Inc. ChaosDesk is not affiliated with Zendesk.

Bring your whole Zendesk history. Keep your way of working.

Import tickets, users, rules and the help centre, run both side by side, and switch when your team is ready.

Send us a line from your work address and we will add you to the early access list.