Does EvaCore write anything to the Zendesk account?

No. Every request to Zendesk is read-only, and nothing in your account is edited or deleted. The token is stored encrypted, you can disconnect to delete it, and imported leads stay as they are.

What exactly moves from each ticket?

The requester arrives as a lead and the ticket is added to their record with its subject, Zendesk status, project, description and first 5 replies. Nothing else moves.

What if the customer is already one of ours?

The ticket entry is added to the existing lead with the same number and no second lead is created; it keeps its status. When there is no phone, the email address serves as the key.

What if the import is interrupted or I run it again?

It resumes where it stopped and duplicates no lead, because every imported or skipped ticket is recorded in a ledger per Zendesk account. The counters come from that same ledger.

Does the import slow my team's work in Zendesk?

It throttles itself: when less than 20 percent of the account's request allowance for the minute is left, it waits, and when Zendesk asks it to wait, it waits that long and continues automatically.

No. It is paid once per migration and does not renew.

Last updated 2026-10-04

Zendesk import: move your customers and their tickets into EvaCore

CRM import is an Enterprise module that moves your customers and their tickets from Zendesk into EvaCore, so each ticket's requester becomes a lead and the ticket appears in their record. It reads from Zendesk and never writes to it. It is paid once per migration, not monthly, and it is for the owner only.

SAR 4,000 one-time per migration

Request a quote Start with a plan

What is it?

You connect your Zendesk account with its subdomain, an admin email and an API token, then preview the first 1,000 tickets and map fields, projects and statuses before anything is written. On start, the import runs in the background to the last ticket, and you can pause and resume it. Each requester becomes a lead, or the ticket is added to your existing lead with the same number, and no message is sent.

Who is it for?

A developer or large office managing customers and tickets in Zendesk that wants to move to EvaCore without losing the record.
A sales team that wants to see each former customer's history in their file at the first new conversation.
An account owner who wants a safe migration under their own supervision, since the API token can read the whole Zendesk account.

What problem does it solve?

Moving customers by export and manual copy takes time and creates duplicates between the new and the old customer.
Ticket history stays in Zendesk, so the salesperson never sees it in the customer's file.
The fear that old customers get a welcome or notification the moment they enter the system.
An import that breaks halfway leaves data incomplete or duplicated.

How it works, step by step

In Zendesk open Admin Center, then Apps and integrations, APIs, Zendesk API; turn on Token access, create a token named EvaCore and copy it.
In EvaCore open Import from Zendesk (owner only), enter the account subdomain and an admin email, paste the token, and press Save & test.
Press Preview the account: we read the first 1,000 tickets and show how many requesters there are, who has a mobile, who has email only and who would merge into your existing leads.
Choose where the mobile number comes from, map Zendesk projects (a field, a tag or a linked record) to your projects, and adjust the status mapping.
Review the sample tickets and what happens to each: new lead, added to an existing one, already imported, or skipped.
Press Start the import, then close the page if you like. It continues in the background, and you can Pause, Resume or Cancel.
When it completes, check the counters: new leads, added to existing leads, skipped, and download the skipped tickets as CSV.
Open Open leads and review any record: its ticket with subject, status and first replies, then assign the leads to your team by hand.

What is included

A connection to your Zendesk account with an API token stored encrypted and never shown again, a connection test, and a disconnect that deletes the token.
A preview of the first 1,000 tickets before anything is written, and a sample showing what happens to each ticket.
One lead per person: the mobile number is the key, email when there is none, and a merge into your existing lead with the same number.
A ticket entry in the lead's record: subject, its Zendesk status, project, description and the first 5 replies.
Status mapping: new becomes New, open, pending and on hold become Contacted, solved and closed become Closed, all editable.
Pause, resume and cancel, and a CSV download of skipped tickets.
No lead duplicated on a re-run, even after an interruption.

Limits and fair use

The supported source today is Zendesk only. A separate feature imports a customer list from an Excel or CSV file.
The import is for the owner alone, because the token reads the whole Zendesk account and the write covers every customer in the office, whatever the team.
An admin email is required in Zendesk; ticket export does not work with an agent account.
The import moves ticket requesters and ticket text: subject, description and the first 5 replies of each ticket, and nothing beyond that.
Tickets with no valid Saudi or international phone and no email, staff requesters and deleted tickets are skipped, and a CSV lists them.
Zendesk internal notes are imported but only the owner and team leads can read them; the rest of the team sees only how many there are.
The mapped status applies to new leads only, and your existing leads keep theirs.
No welcome or notification is sent to any customer and no one is auto-assigned; your staff handles distribution and follow-up.

Price and what others bill you

Item	Price	Billed by
CRM import	SAR 4,000 one-time per migration	EvaCore

Annual billing is ten months' money for twelve months of service. Pricing

Frequently asked questions

Does EvaCore write anything to the Zendesk account?: No. Every request to Zendesk is read-only, and nothing in your account is edited or deleted. The token is stored encrypted, you can disconnect to delete it, and imported leads stay as they are.
What exactly moves from each ticket?: The requester arrives as a lead and the ticket is added to their record with its subject, Zendesk status, project, description and first 5 replies. Nothing else moves.
What if the customer is already one of ours?: The ticket entry is added to the existing lead with the same number and no second lead is created; it keeps its status. When there is no phone, the email address serves as the key.
What if the import is interrupted or I run it again?: It resumes where it stopped and duplicates no lead, because every imported or skipped ticket is recorded in a ledger per Zendesk account. The counters come from that same ledger.
Does the import slow my team's work in Zendesk?: It throttles itself: when less than 20 percent of the account's request allowance for the minute is left, it waits, and when Zendesk asks it to wait, it waits that long and continues automatically.
Is the fee monthly?: No. It is paid once per migration and does not renew.

Related products

CSV lead importUpload your existing leads in one go.Leads, pipeline and recyclingEvery lead in its stage, with dormant ones sent back for follow-up.Shared inbox, takeover and AI copilotEvery conversation in one place; step in any time with Eva's suggestions.Roles and permissionsEach employee sees only what is theirs.Audit history with CSVWho did what and when, exportable on demand.