Test Case ExportGuide

How to verify a test case migration didn't lose cases or steps

Updated 2026-10-10 · by Hieu Tran, written with AI agents and checked against the sources below

Migrations between Zephyr and Xray, or from Data Center to Cloud, usually move the cases but quietly drop things: steps, folders, attachments, run history. A before/after comparison catches the losses while the source still exists.

Before you switch anything off

1. Export all test cases from the source project as CSV, with steps (one row per step is fine).
2. Export the same from the target after the migration.
3. Match cases by name, not key: keys change in a migration.
4. Count steps per case on both sides; a lower count after means lost steps.
5. Compare the folder of each case; cases often land in a default folder.
6. List cases that exist only in the target: renamed cases show up here and in the missing list.

What CSV exports usually miss

• Execution history (runs, results, defects linked to runs) is often in separate reports or not exported at all.
• Attachments and embedded images in steps.
• Links between test cases, requirements and plans.
• Keep the source read-only until those are checked or archived.

Duplicates

If two cases share a name in the source, name matching treats them as one. Add the folder to the name, or compare folder by folder.