Migrate your help desk to EvenTier
Bring your ticket history and knowledge base with you. Connect Zendesk, Freshdesk or Jira Service Management, import a Confluence space, or upload a CSV export from any other tool. Tickets keep their original dates, requesters, assignees, tags and conversation, and internal notes stay internal.
What you can bring
Tickets
The subject, description, status, priority, requester, assignee, team, tags, created and resolved dates, and every reply and internal note with its author and time.
Knowledge base articles
Titles and bodies, converted to Markdown, with their category and tags. Articles stay drafts unless the person importing them can approve knowledge base articles.
People
Import users from a CSV or provision them with SCIM. Requesters and comment authors who are not in your workspace yet are added as inactive placeholders, matched by email.
Supported sources
Zendesk, Freshdesk, Jira Service Management and Confluence connect through their APIs, and the import only reads from them. Any other tool imports from a CSV export.
Zendesk
Direct connector
- Connect with
- Your Zendesk subdomain and an OAuth access token, which Zendesk recommends. An API token with an admin email still works while token access is on in Zendesk.
- Tickets
- Every ticket in Zendesk's incremental export: subject, description, status, priority, requester, assignee, group as the team, tags, created and solved dates, and each comment with its author, time and public or internal flag.
- Knowledge base
- Published Zendesk Guide articles, with their category, and labels as tags.
- At cutover
- Sync new & updated pulls only the tickets created or changed since the last import.
Freshdesk
Direct connector
- Connect with
- Your Freshdesk domain and API key.
- Tickets
- Subject, description, status, priority, requester, agent, group as the team, tags, created and resolved dates, and each conversation entry, with private notes kept internal.
- Knowledge base
- Published Solutions articles, with their category and tags.
- At cutover
- Run the import again. Tickets already imported are updated in place, and new ones are added.
Jira Service Management
Direct connector
- Connect with
- Your Atlassian Cloud site, the account email and an API token. An optional JQL filter limits the import to one project or any set of issues.
- Tickets
- Summary, description, status, priority, reporter as the requester, assignee, the first component as the team, labels as tags, created and resolved dates, and each comment, with internal comments kept internal.
- Knowledge base
- Jira Service Management keeps its knowledge base in Confluence. Import it with the Confluence connector.
- At cutover
- Run the import again. Issues already imported are updated in place, and new ones are added.
Confluence
Direct connector, knowledge base only
- Connect with
- Your Atlassian Cloud site, the account email, an API token and the key of the space that holds your knowledge base.
- Knowledge base
- The space's current pages, with bodies converted from Confluence's storage format to Markdown and the space key as the category.
- At cutover
- Run the import again. Articles already imported are updated in place.
CSV from any tool
File upload
- Upload
- A CSV export of tickets, up to 50,000 rows per file, or of articles, up to 20,000 rows. Column presets match ticket exports from Zendesk, Freshdesk, Freshservice and Jira Service Management, and you can download a template.
- Tickets
- The same fields as the connectors, plus a request type. A ticket's conversation goes in one column as a JSON list of comments, each with its author email, text, time and internal flag.
- Knowledge base
- Title, summary, body, category, status, tags, slug and language.
- At cutover
- Upload a new export. Rows matched by their source id are updated in place, and new rows are added.
How a migration runs
Tickets and knowledge base articles import separately, from the same settings page. Import your people first, then tickets, then articles.
- 01
Connect a tool or upload a CSV
In Admin → Settings → Import & migration, open the Tickets or Knowledge base tab. To connect a tool, enter its site and credentials and test the connection. To upload a file, choose the file and the tool it came from, and the wizard starts from that tool's column names.
- 02
Map fields, people and teams
For a CSV, EvenTier matches columns to its fields and shows sample values, and you map each status and priority value. Connectors map each tool's standard statuses and priorities for you. People are matched by email address, and teams and tags by name. Missing teams and tags can be created during the import, as can request types named in a CSV. Add your agents first: a ticket whose assignee is not in the workspace is imported unassigned.
- 03
Preview and try a sample
For a CSV, the preview shows whether each row will be created, updated, skipped or rejected, and why. Next, import a sample of ten tickets and open them. If they look right, continue. If not, discard the sample and adjust the mapping. Discarding removes the sample's tickets and any placeholder people it added. Connector imports have no sample step. After the connection test, they import everything the account can read.
- 04
Run the full import
The import runs in the background, one page at a time, and pauses whenever the source asks it to slow down. The page shows progress and the result for each row, with the reason any row failed. Imported tickets do not start automations, notifications, webhooks or SLA timers.
- 05
Cut over
Keep the old tool open while your team starts working in EvenTier. When you switch over, import again to bring across what changed in the meantime. Records already imported are matched by their source id and updated in place, and new ones are added. For Zendesk, Sync new & updated fetches only the tickets that changed.
What is kept
Each imported ticket keeps the people, dates and conversation it had in the old tool.
- Original created and resolved dates on every ticket
- The requester and assignee, matched by email address
- Each reply and note with its author and time
- Internal notes, kept internal
- Tags, and the source's group or component as the team
- Status and priority, mapped to EvenTier's values
- The source id of every record, so a later run updates the record in place
- Replies and tags your team added in EvenTier, when you import again
- An audit log entry when each import starts and when it finishes
What is not imported
Check these against your current setup before you plan the cutover.
Attachments
Files attached to tickets, replies and articles are not copied into EvenTier.
Custom fields and forms
Only the fields listed on this page are imported. A connector files every ticket under your default request type, while a CSV can name a request type for each row.
Formatting in conversations
Replies and notes are imported as plain text, so formatting and inline images are dropped.
Replies without a known author
A Zendesk or Freshdesk reply whose author cannot be matched to an email address is skipped. Freshdesk replies are matched to agents and the requester, so a reply from a CC'd contact is skipped.
Ticket numbers
Imported tickets get EvenTier request numbers. The source id is stored with each one and used to match later runs.
Custom Freshdesk statuses
The connector maps Freshdesk's standard statuses, and a ticket in a custom status is reported as a failed row. Import those tickets from a CSV, where you map every status yourself.
Desk configuration
Automations, macros, views, SLA policies and satisfaction ratings stay in the old tool. Set them up again in EvenTier.
Knowledge base history
Connectors import published articles only. Each article is recorded as created by the person who runs the import, images are not copied, and links between Confluence pages become plain text.
Self-managed Atlassian products
The Jira and Confluence connectors work with Atlassian Cloud sites. For Jira Data Center or Server, import a CSV export.
Questions about migrating
How long does a migration take?
It depends on how many tickets you have and on the source's API rate limits, so a large account can take a while. The import runs in the background, so you can leave the page and check progress later under Recent imports.
Will importing old tickets notify anyone?
No. Imported tickets do not start automations, notifications, webhooks or SLA timers, so nobody is emailed about an old request and no imported ticket shows as breached.
Can we run an import more than once?
Yes. Each imported record keeps its source and original id, so running the same file or connector again updates it in place. Replies and tags your team added in EvenTier are kept. You can also choose to skip records already imported, or to update existing records only.
What happens to the API token we enter?
It is stored encrypted while the import runs and deleted when the run finishes, so a later Zendesk sync asks for it again. The connectors only read from the source, and they call only that source's own address.
Do our people need accounts before we import?
Agents do, because a ticket whose assignee is not in the workspace is imported unassigned. Requesters and comment authors do not. They are added as inactive placeholders, matched by email, so the record of who asked is kept. To add agents first, import users from a CSV or set up SCIM provisioning.
Who can run an import?
Admins. Ticket imports need permission to manage users and requests, and knowledge base imports need permission to edit the knowledge base. Imported articles stay drafts unless the person importing them holds the Approve knowledge base permission.
Can we import from a tool that is not listed?
Yes, from a CSV export. The wizard matches your columns to EvenTier's fields, or you can start from the downloadable template. Freshservice exports use the Freshdesk / Freshservice preset.
Guides and comparisons
- Importing & migratingBring ticket history and knowledge base articles over from Zendesk, Freshdesk, Jira Service Management, Confluence, or any CSV export. Timestamps, authors, and internal notes are kept.
- Migrating from Zendesk without losing ticket historyA migration plan: field and status mapping, the parallel run, the sync at cutover, and what requesters see.
- EvenTier vs ZendeskWhich plans include SSO, audit, and approvals, where Zendesk is stronger, and what migrating involves.
- EvenTier vs FreshdeskWhich plans include SSO, custom roles, and audit, where each tool fits, and what migrating involves.
- EvenTier vs Jira Service ManagementConfiguration options, plan tiers, and what migrating involves.
- EvenTier vs FreshserviceThe ITSM feature checklist by plan tier, the AI add-on, and what migrating involves.
Get notified when signup opens.
EvenTier is in private early access. Leave your work email and we will let you know when you can create a workspace.
No card. We use your email only for your early-access invite and launch news. Privacy Policy