Skip to content

Documentation

Importing & migrating

Bring 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.

Where
Admin → Settings → Import & migration
Permission
MANAGE_USERS · EDIT_REQUESTS (tickets) · EDIT_KNOWLEDGE_BASE (KB)
Updated
October 2026

Overview

Import tickets and knowledge base articles from Admin → Settings → Import & migration. It has a Tickets tab and a Knowledge base tab.

Each tab offers two ways in: upload a CSV file exported from any tool, or connect a source tool and pull records from its API.

Imported tickets keep their original created and resolved dates, tags, and full conversation. Internal notes stay internal.

The original requester and assignee are kept, matched by email.

Imported tickets do not fire automations, notifications, or service level agreement (SLA) timers. Nobody is paged about old requests, and live reporting is not affected.

You can safely run an import again. Each record stores its source system and original id, so a rerun of the same file or pull updates records in place instead of duplicating them.

The CSV import is a guided wizard. Large files are processed by a resumable background worker.

Step by step

  1. 01

    Choose what to import

    Open the import page, pick the tab for what you are bringing over, and choose how to bring it in.

    • Upload a CSV: a file exported from any tool
    • Connect a tool: pull records from the source's API
    1. Admin → Settings → Import & migration
    2. Tickets or Knowledge base
    3. Upload a CSV or Connect a tool
  2. 02

    Map fields and values (CSV)

    After you upload the file, the wizard matches your columns to EvenTier fields and shows sample values. A wrongly mapped column is caught before anything is imported.

    • Columns are detected automatically
    • Tickets: also map the source's status and priority values to EvenTier's
    • Required fields must be mapped before you can continue
  3. 03

    Preview, then try a sample

    Check the result before the full import. The preview shows what will happen to each row, and why.

    • Each row is marked created, updated, skipped, or rejected, with the reason
    • Tickets: import a sample of ten, then open them to check the subject, requester, timestamps, and conversation
    • Looks right: continue, and the full import runs in the background
    • Not right: discard the sample and adjust your mapping
    • Discarding removes the sample tickets and any placeholder requesters, so no duplicates are left behind
  4. 04

    Connect a source tool

    Pull records straight from a source tool instead of exporting a file. The Connectors table below lists what each source supports.

    • On Connect a tool, enter the source's credentials: an admin API token or API key
    • Zendesk: an OAuth access token with the email left blank, which Zendesk recommends, or an API token with the admin's email
    • Test the connection, then start the import
    • The pull runs in the background and shows live progress
    • It pages through every record within the source's rate limits
    • Article bodies (HTML, or Confluence storage format) are converted to Markdown
  5. 05

    Sync new & updated (delta)

    After a Zendesk import completes, pull only what changed since the last run, and cut over without downtime.

    • Find Sync new & updated in the recent-imports list
    • Enter your token again
    • Only tickets created or changed since the last run are pulled
    • Matching tickets are updated in place, and new ones are added

Connectors

Direct API connectors by source and record type. Any source not listed, and the Jira Service Management knowledge base, can be imported from a CSV export.

SourceTicketsKnowledge baseDelta sync
ZendeskYes (incremental export)Yes (Guide articles)Yes
FreshdeskYesYes (Solutions)No
Jira Service ManagementYes (JQL search)NoNo
ConfluenceNoYes (space pages → Markdown)No
Any CSV exportYesYesn/a

Good to know

  • Requesters and authors not yet in your workspace are created as placeholder users, matched by email, so the original requester is kept.
  • When a source hides the email address, as Jira often does, a stable placeholder is made from the account id instead.
  • Publishing an imported knowledge base article needs the Approve knowledge base permission. Without it, imported articles are saved as Draft, so a bulk import cannot publish without review.
  • Custom statuses with no known match show as unmapped in the preview instead of getting a wrong status. Map them and run the preview again.
  • Every import writes audit events when it starts and when it completes. Discarding a sample or running a delta sync also writes a rolled-back or re-synced record.