Moving your test cases to CaseRun

Export a CSV from the tool you have now, drop it into CaseRun, and the columns are matched for you — including the awkward part where one test case spans several rows.

4.0 sto import 5,000 cases with 10,000 steps (measured)

5 toolsXray, Zephyr Scale, Zephyr Squad, TestRail, qTest recognised

0 lock-inexport back to the same format whenever you want

How it works Xray Zephyr Scale Zephyr Squad TestRail qTest What doesn't come across

How it works

Export your test cases from your current tool to CSV (include the step columns — see your tool below).
In Jira, open CaseRun → Test cases → Import CSV/Excel. Upload the file, or paste the cells straight from a spreadsheet.
CaseRun tells you which tool the file came from and fills in the column mapping. Change anything that looks wrong.
The preview shows exactly how many test cases and steps will be created. Import.

Two details that usually cause trouble elsewhere, and are handled here:

One case, many rows. Most tools write each step as its own row. CaseRun groups them back into one test case — by the case ID column when the file has one, otherwise by the convention that a blank title continues the previous case.
Repeated titles. Xray repeats the summary on every step row. Grouping by title alone would duplicate the case once per step; CaseRun uses the ID instead, so you get one case with three steps, not three cases.

From Xray

Export your tests to CSV from the Test Repository or from a Jira issue search that includes the test fields. These column names are recognised as they come:

Xray column	Becomes
`TCID` (or `Test Case ID`, `Key`, `Issue Key`)	Groups the rows of one test case
`Test Summary` / `Summary`	Title
`Test Repo`	Folder
`Action`	Step
`Data`	Test data
`Result`	Expected result
`Precondition` · `Test Priority` · `Labels`	Precondition · Priority · Labels

Xray priorities map to CaseRun's four levels: Blocker/Critical → Critical, Major → Normal, Minor/Trivial → Low. P1–P4 work too.

From Zephyr Scale (TM4J)

Zephyr Scale writes the step columns with a long prefix; they are matched anyway:

Zephyr Scale column	Becomes
`Name`	Title
`Folder` · `Objective` · `Precondition`	Folder · Objective · Precondition
`Test Script (Step-by-Step) - Step`	Step
`Test Script (Step-by-Step) - Test Data`	Test data
`Test Script (Step-by-Step) - Expected Result`	Expected result
`Key`	Groups the rows of one test case

From Zephyr Squad

Zephyr Squad column	Becomes
`Test Case ID`	Groups the rows of one test case
`Summary` · `Description`	Title · Objective
`Steps` · `Test Data` · `Expected Result`	Step · Test data · Expected result
`Component` · `Labels`	Folder · Labels

From TestRail

When you export, choose the format that writes steps in separate columns — CaseRun reads both shapes.

TestRail column	Becomes
`ID`	Groups the rows of one test case
`Title` · `Section` · `Preconditions`	Title · Folder · Precondition
`Steps Separated (Step)`	Step
`Steps Separated (Expected Result)`	Expected result
`Steps Separated (Additional Info)`	Test data

From qTest

qTest column	Becomes
`Id`	Groups the rows of one test case
`Name` · `Module` · `Precondition`	Title · Folder · Precondition
`Test Step Description`	Step
`Test Step Expected Result`	Expected result

What doesn't come across

Be realistic about this part. A CSV carries the catalogue, not the history. Coming in, you get test cases, their steps, folders, objectives, preconditions, priorities and labels.

You do not get: past execution history, attachments and screenshots, custom fields, test plans or cycles from the old tool, comments, or per-user permissions. If any of those matter, keep the old tool readable for a while rather than deleting it on day one — run new cycles in CaseRun and let the old history age out.

Requirement links are rebuilt in CaseRun by linking tests to Jira issues, which takes a moment per test but ends up cleaner than an imported mapping.

Coming from a spreadsheet instead?

That works the same way — and you can paste cells straight from Excel rather than saving a file. Any column named like Title, Step, Expected Result, Folder or Priority is picked up automatically, in English or Korean.

Leaving later

Press Export CSV on the test list and you get the same shape back — the file CaseRun writes is a file CaseRun reads. We would rather you stay because the app is fast than because your data is stuck.

Questions about a specific export? Send the header row of your file to support@caserun.dev and we'll tell you what it will map to — or add the columns if we don't recognise them yet.