Migrating off Zendesk: what transfers, and what you rebuild
Relay ships real Zendesk importers for tickets, conversations, customers and organizations. It does not pretend to import your triggers — nobody can, and this page explains why that is the single biggest cost of any help desk migration.
Start your 14-day trialFrom $9/user/month · AI included · No credit card
The short answer
Tickets, ticket comments, end users, agents and organizations import from Zendesk into Relay through Relay's Zendesk connector. Triggers, automations, macros, SLA policies, views and routing rules do not transfer to any help desk, including Relay, because they are platform-specific logic that has to be rebuilt. Relay starts at $9 per user per month with AI included.
What moves, and what you rebuild by hand
Relay ships real Zendesk importers. They are honest about their scope: ticket and customer data moves, and platform-specific automation logic does not — not into Relay, and not into any other help desk either. Anyone promising a lossless migration of Zendesk automation is overclaiming.
Relay's importer moves this
- TicketsSubject, status, priority, requester, assignee and timestamps, imported into Relay tickets with an ID mapping back to the Zendesk ticket.
- Ticket commentsEvery public reply and internal note, imported as conversation messages in order, so the thread history survives the move.
- End usersZendesk end users become Relay customers, deduplicated on email.
- AgentsImported as mappings so historical assignee references still resolve, rather than showing as unassigned.
- OrganizationsImported as organization metadata attached to the import mapping.
- Custom field definitionsZendesk ticket field definitions are imported for reference, so you can see what shape your data was in before you rebuild it.
You rebuild this by hand
- Triggers and automationsPlatform-specific logic. There is no import path into Relay or into any competitor. Budget real time for rebuilding these — on a mature Zendesk instance this is most of the migration.
- MacrosRelay ships macros with variables, but the macro bodies have to be recreated. Exporting your Zendesk macro list first makes this an afternoon rather than a week.
- SLA policiesRelay ships SLA policies and breach tracking, but the policy definitions are rebuilt from scratch.
- Views and routing rulesRebuilt as Relay saved views and automations. Take the opportunity to delete the ones nobody has opened in a year.
- Business hours and schedulesReconfigured in Relay. Usually 15 minutes of work, not a project.
Zendesk data export is switched off by default
This is the step that surprises people. Full account export to JSON, CSV or XML is not enabled on a Zendesk account out of the box — the account owner has to contact Zendesk Customer Support and ask for it to be turned on. Once the export finishes, Zendesk emails a download link that is valid for about three days, so do not request it on a Friday before a holiday. Processing time scales with your data: minutes under 10,000 tickets, up to a few hours in the 10,000 to 500,000 range, and as long as 24 hours above a million. JSON is the most complete format. Start this request before you do anything else, because the wait is the long pole.
Verified 2026-08-25 against Zendesk's own documentation.
The migration, step by step
- 1
Request the export enablement first
Have the Zendesk account owner open a ticket with Zendesk Customer Support asking to enable data exports. Do this on day one; everything else can happen while you wait.
- 2
Inventory the logic that will not move
Export or screenshot your triggers, automations, macros, SLA policies and views. Count them. This number, not your ticket count, is what determines how long the migration takes.
- 3
Connect Zendesk to Relay
Create your Relay workspace and connect the Zendesk account. Relay authenticates against the Zendesk API and enumerates what it can import before it writes anything.
- 4
Run the import
Relay imports users and organizations first, then tickets, then comments, keeping an ID mapping so relationships and assignees survive. Progress and per-record errors are tracked on the import record.
- 5
Rebuild the six artifact types that did not move
Recreate triggers as Relay automations, macros as Relay macros with variables, SLA policies in Relay SLA, and views as saved views. Rebuild the ones you actually use, not all of them.
- 6
Cut the email over, and keep Zendesk read-only for a month
Point your support address at Relay. Leave the Zendesk account alive but read-only until you are confident, then cancel. The overlap month is cheap insurance.
Should you migrate at all?
Two honest cases against. If your Zendesk instance is a light one — a shared inbox with a handful of macros and no serious automation — the migration is genuinely easy and the savings are real. If it is a mature instance with hundreds of triggers wired into other systems, the rebuild is the cost, and no vendor's importer changes that. The case for is the arithmetic: Zendesk Suite Team is $55/agent/mo once you need more than ticketing, Copilot is another $50 per agent per month, and AI agents bill per automated resolution at a rate Zendesk quotes per contract rather than publishing. Relay is $9 per user per month with AI reply drafts included and no usage meter. The moment you are already being forced to rebuild automation for some other reason is the cheapest possible moment to leave, because that work has to be redone either way.
Migration questions
Does Relay import Zendesk triggers and automations?
No. Triggers, automations, macros, SLA policies, views and routing rules are platform-specific and do not transfer to any help desk. Relay imports tickets, comments, users, agents, organizations and custom field definitions. Anyone claiming a lossless automation migration is overclaiming.
How do I export my data from Zendesk?
Full account export is disabled by default. The account owner must contact Zendesk Customer Support to enable it. Once enabled, you export to JSON, CSV or XML and Zendesk emails a download link valid for about three days. JSON is the most complete format.
How long does a Zendesk migration take?
The data import is hours, not days — Zendesk processes exports in minutes under 10,000 tickets and up to 24 hours above a million. The real timeline is rebuilding triggers, macros, SLAs and views, which scales with how much automation you built, not how many tickets you have.
Will I lose ticket history?
No. Relay imports ticket comments as conversation messages in order, so the full thread history moves with the ticket, along with requester, assignee and timestamps.
What does Relay cost compared to Zendesk?
Relay is $9 per user per month on Starter, $19 on Growth and $39 on Scale, with AI included. Zendesk Support Team is $19 per agent per month for ticketing only, Suite Team is $55, and Suite Professional is $115, with Copilot a further $50 per agent per month. Verified 25 August 2026.
Move your Zendesk data into Relay
Connect your Zendesk account, import tickets and customers, and start answering in Relay the same day.