Migration Center (optional)
Move your test cases. Know exactly what moved.
Migration is optional. If you choose to move test cases and their steps from Xray, Zephyr Scale, AIO Tests or any spreadsheet, the Migration Center previews the mapping, validates every row, imports in the background and reconciles what moved, what was skipped and why. Past execution results stay in your old tool. You do not need to migrate to use The Warden: keep your tools and add it above them.
- Move from XrayTest Case Importer CSV
- Move from Zephyr ScaleZephyr Scale CSV
- Generic CSVSpreadsheet or AIO Tests export
Choose. Pick the source: Xray Test Case Importer CSV, Zephyr Scale CSV, or a generic CSV such as an AIO Tests export. Here, a 412-row export.
Read this scene as text
- Choose. Pick the source: Xray Test Case Importer CSV, Zephyr Scale CSV, or a generic CSV such as an AIO Tests export. Here, a 412-row export.
- Map. Source columns map to TestWarden fields. Known layouts are detected; anything unmapped is kept as a custom field, not dropped.
- Preview. A dry run validates every row before anything is written: what will import, what will skip, and the reason for each exception.
- Import. The import runs in the background in batches with checkpoints. It is resumable and idempotent, so closing the panel loses nothing.
- Reconcile. The report accounts for every row. Test cases and their steps are in TestWarden; past execution results stay in your old tool, so export them there before you retire it.
Be clear about history
Test cases move. Execution history stays where it is.
CSV migration brings test cases, their structured steps and mapped fields into the Shared Library. It does not bring past execution results, runs or attachments, in any adapter.
- Before you cancel the old tool, export or archive the execution history you need for audit or release records.
- From the first run in TestWarden, every attempt is version-pinned and kept, so your new history starts clean and complete.
- Runbooks: Xray, Zephyr Scale, AIO Tests.
Supported sources
What each source brings, stated plainly.
Each adapter runs on the same migration engine, and the product discloses what it imports and what it does not before you commit. Paths are verified on a development Jira site against documented export layouts, not every edition of another vendor's product, so always preview your own file first.
- Xray Test Case Importer CSV
Move from Xray
- Imports
- Manual test cases with grouped steps, priority, labels as tags and custom fields, from the Test Case Importer layout or a Jira/Xray CSV with the Manual Test Steps JSON field. Cucumber and Generic test definitions are kept as a script. Unknown columns are kept as custom fields.
- Not imported
- Test Sets, Test Plans, Test Executions, Precondition issues and attachments are disclosed as not imported.
- Note
- Ready. Verified end to end on a development Jira site using documented Importer-layout fixtures, not every Xray edition or export. Preview your own file before committing.
- Zephyr Scale CSV
Move from Zephyr Scale
- Imports
- Test cases, structured steps, priority, labels as tags and Zephyr metadata preserved as custom fields. Status “Approved” maps to Ready.
- Not imported
- Native folders, requirement links, attachments and execution history stay outside the adapter.
- Note
- Ready. Verified end to end on a development Jira site using a documented Zephyr Scale export layout, not every Zephyr edition or export. Mapping is detected automatically.
- Generic CSV, any spreadsheet export
Move from AIO Tests or a spreadsheet
- Imports
- Obvious columns are mapped automatically; map the rest to Title, Description, Priority, Status, Tags or Steps (multi-step paste format). Every unmapped column is preserved as a custom field.
- Not imported
- Columns you choose to ignore. Rows without a title are reported as skipped.
- Note
- Ready: live-verified end to end on a development Jira site. Up to 10 MB and 10,000 rows per job. AIO Tests data can only arrive this way: export to CSV and map the columns. There is no AIO-specific importer.
Imported tests carry the provenance label “Imported from migration” with their source reference.
Engine guarantees
Resumable. Idempotent. Nothing silently lost.
Preview before import
A dry run shows Will import, Will skip and Total rows, with per-row reasons, before anything is written.
Background processing
Imports run asynchronously in batches of 200 with checkpoints. Close the panel; it resumes exactly where it left off.
Duplicate handling
Re-previewing the same file and mapping reuses the job. Concurrent duplicate delivery produces exactly one set of rows.
Explicit reporting
Imported, imported with warnings, skipped and failed — filterable, with a reason for every non-imported row.
Migration and import are included in every TestWarden subscription. There is no separate migration edition.
Before you migrate
Migration is optional.
Integration: keep your original test-management platform and use its results as verification evidence for The Warden. No test case is moved. Migration: optionally import supported test cases into TestWarden’s native Jira repository. Execution history stays in the original tool. The Warden works above your current tools, so adopting it does not require moving a single test; see Integrations. If you do want one system, compare TestWarden with Xray, Zephyr Scale or AIO Tests, then read the migration documentation.
Now available on Atlassian Marketplace
Proof before progress.
TestWarden is listed on the Atlassian Marketplace for Jira Cloud. Keep your existing test-management and CI tools, and add The Warden's independent verification layer—or use TestWarden's built-in Jira test management. Visit the Marketplace to get started; we're here if you want guided setup or migration help.