Switch from Zendesk
Move in a day. Keep everything that matters.
Bring your full Zendesk history, run both side by side, and switch one group at a time. Your agents keep their way of working, your own scripts keep their API.
Animated demo of the ChaosDesk Migration center: a Zendesk import counts up tickets, users, organizations, attachments, help centre articles, macros, triggers and views, the counts are verified against Zendesk, and delta sync keeps importing changes until cutover.
What switching saves
83%
Lower list price per agent
Zendesk Suite Professional $115 vs ChaosDesk Pro $19, annual billing, checked 2026-11-06
$23,040
Less per year for 20 agents
($115 - $19) x 12 months x 20 agents, list prices
$0
Extra for the AI copilot
Included in every paid ChaosDesk plan (fair use). Zendesk Copilot is an add-on, see zendesk.com/pricing
What comes over
Your whole account, with its history.
The importer reads your Zendesk account through its API and rebuilds it in ChaosDesk in the right order. Run it as often as you like: it updates, it never duplicates.
Imported history does not fire triggers, notifications or webhooks, so customers hear nothing while you test.
- Tickets with every comment, attachment, tag, CC, follower and custom field
- The full audit history, replayed with the original time and actor
- Your ticket numbers: the Zendesk id becomes the ChaosDesk ticket number
- Users with identities, organizations with domains, user and organization fields
- Brands, support addresses, groups and custom roles
- Ticket fields (nested drop-downs included) and ticket forms with conditions
- Triggers, automations, macros and views, including personal ones
- Business schedules, holidays and SLA policies
- Webhooks, CSAT ratings and the help centre in every brand and language
Step by step
No big-bang weekend.
Five steps, one group at a time, with Zendesk running until the last group has moved.
-
Connect your Zendesk account
Create a read-only admin API token in Zendesk and paste it into the Migration center. Nothing changes on the Zendesk side.
-
Dry run and review
The first import shows counts per object and a report of anything it could not map. Rules with a condition we cannot translate are imported inactive and listed, never dropped silently.
-
Parallel run
Delta imports keep ChaosDesk up to date every few minutes. Team leads check their views, forms and SLAs against real tickets while Zendesk keeps running.
-
Go live, one group at a time
For each group: point the support addresses at ChaosDesk, run a final delta, turn off that group's Zendesk triggers, change your integrations' base URL, swap the messenger snippet. Agents move.
-
Keep a way back
Zendesk stays read-only for the moved groups during a fallback window. If something is wrong, roll the group back from the Migration center.
Keeps working
Same API. Same snippet. New address.
Your own scripts and services
Anything you wrote against the Zendesk API (internal tools, back-office jobs, services using the official PHP or C# SDKs, plain HTTP clients) calls /zd/api/v2 on your ChaosDesk address with a ChaosDesk API token. Same requests, same response shapes.
Your website messenger
The ChaosDesk messenger loads from the same kind of script tag, keeps the id="ze-snippet" and understands the same zE() calls. Change the script URL and the key.
Help-centre links
Imported articles answer on their old paths, so links in emails, macros and search results keep working.
Rules and reporting habits
Triggers, automations, SLA metrics and the search syntax behave the way your team is used to.
# base URL before
https://yourcompany.zendesk.com/api/v2/
# base URL after
https://yourcompany.chaosdesk.io/zd/api/v2/
# auth: {email}/token:{ChaosDesk API token}<!-- keep the id, change src and key -->
<script id="ze-snippet"
src="https://app.chaosdesk.io/messenger.js?key=YOUR_KEY">
</script>
// zE('messenger', 'open') keeps workingBe ready for this
What you will need to replace
We would rather tell you now. Third-party integrations that are hard-wired to *.zendesk.com cannot be pointed at a new address by you; they need a ChaosDesk version or a different route.
- The Zendesk app for Zapier
- Zaps that use the Zendesk app need the ChaosDesk webhooks or API instead.
- Fivetran and other data connectors
- Connectors built for zendesk.com need to point at the ChaosDesk API or a CSV and report export.
- Zendesk mobile SDKs
- Native Zendesk SDKs in iOS and Android apps are replaced by the ChaosDesk messenger in a web view today; native ChaosDesk SDKs are built and follow after app store review.
- Marketplace apps hard-wired to zendesk.com
- Sidebar apps built on the Zendesk App Framework can be installed; apps that call zendesk.com servers directly need their vendor's ChaosDesk version.
- Sunshine Conversations bots
- An external bot that runs through Sunshine Conversations needs a new messaging hub before the Zendesk contract ends.
Assisted migration
More than 20 agents? We migrate with you, for free.
A migration engineer plans the waves with you, watches the dry run and the parallel run, and is on call on go-live day.
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.
Zendesk is a trademark of Zendesk, Inc. ChaosDesk is not affiliated with, endorsed or sponsored by Zendesk, Inc. Product names are used only to describe compatibility and to compare publicly available information.