Overview
Vansah Test Management for Jira supports seamless migration from Zephyr Essentials.
This guide explains:
What information is migrated
What is partially migrated
What cannot be migrated
How Vansah interprets Zephyr fields
Key differences between both systems
Migrated Test Artefacts
Vansah migrates all major Zephyr test case fields with equivalent support in Vansah.
1.1 Test Case Details
Zephyr Field | Migrated | Vansah Field | Notes |
Name | ✅ Yes | Headline |
|
Objective | ✅ Yes | Description |
|
Precondition | ✅ Yes | Precondition |
|
Status | ✅ Yes | Status |
|
Priority | ✅ Yes | Priority |
|
Component | ✅ Yes | Component |
|
Owner | ✅ Yes | Owner |
|
Estimated Run Time | ✅ Yes | Estimated Time |
|
Folder | ✅ Yes | Linked Test Folders |
|
Labels | ✅ Yes | Labels |
|
Traceability Issues | ✅ Yes | Linked work items |
|
Embedded Screenshots | ✅ Yes | Test Case and Test Script Editor |
|
Test Case Attachments | ❌ Not migrated | Attachments | Future consideration |
1.2 Custom Fields
We currently do not migrate custom fields from Zephyr.
However, Vansah supports Jira custom fields.
Additionally, Vansah provides a Bulk Update feature that makes it easy to update Jira custom fields to the Test Cases directly within Vansah.
Test Script Migration
Vansah supports all Zephyr script types.
Test Script Type (Zephyr) | Migrated | Notes |
Step-by-step | ✅ Yes | Embedded attachments allowed |
Plain Text | ✅ Yes | Embedded attachments allowed |
BDD / Gherkin | ✅ Yes |
|
Traceability Migration
Zephyr Field | Migrated | Notes |
Linked Issues | ✅ Yes | Supported as Linked work items |
Web Links | ❌ Not supported |
|
Test Execution Migration
Execution Data | Migrated | Notes |
Execution Key | ❗ No | Vansah generates new Test Run keys |
Status | ⚠️ Partial | Only Overall Results gets migrated as Test Run Result |
Actual End Date | ❌ Not supported | Vansah Test Plan supports (Start Date and End Date) |
Estimated Time | ✅ Yes | If provided |
Actual Time | ❌ Not supported |
|
Assigned To | ❌ Not migrated |
|
Executed By | ✅ Yes |
|
Release Version | ✅ Yes |
|
Iteration | ❌ Not migrated | Zephyr “Iterations” belong to Test Plans (not migrated) |
Environment | ✅ Yes | Support 50 environments per project |
Test Cycle | ⚠️ Yes | Structured differently, Migrated as Vansah Test Folder + Vansah Test Plan |
Version | ⚠️ Only Major Version | Only latest OR major version of Test Case is migrated |
Issues | ❌ Not migrated |
|
Execution Type (Manual/Automation) | ❌ Not supported | Vansah does not use Zephyr’s Manual/Automation type |
Test Case History / Versioning
Zephyr Feature | Migrated | Notes |
Test Case Version History | ❌ Not migrated |
|
Summary — What You Get After Migration
✔ All your test cases
✔ Test steps (step-by-step / BDD / plain text)
✔ Labels, components, owner
✔ Traceability with linked Jira issues
✔ Last execution status
✔ Execution cycle mapping into Vansah Test Plans
✔ Only Major version of test cases
What Is Not Migrated
❌ Zephyr Iterations (Test Plans)
❌ Zephyr Custom fields
❌ Web links
❌ Non-major test case versions
❌ Execution type (Manual/Automation)
❌ Exact Test Run keys
❌ Full execution history (only last execution imported)
❌ Attachments (Future consideration)
FAQ – Zephyr Essentials to Vansah Migration
Do we support Test Case Attachments?
Do we support Test Case Attachments?
Currently, Vansah does not migrate Test Case attachments from Zephyr. Only embedded screenshots are migrated.
However, attachment migration is on our roadmap and may be included in a future enhancement.
How does Vansah manage Zephyr Test Plans and Test Cycles?
How does Vansah manage Zephyr Test Plans and Test Cycles?
Vansah structures Test Plans and Cycles differently from Zephyr.
To maintain consistency and usability, we translate Zephyr artefacts into Vansah’s equivalent structure:
Zephyr Test Cycle → Vansah Test Folder + Standard Test Plan
The Test Cycle becomes a Vansah Test Folder.
A Standard Test Plan is created to manage the executions from that Cycle.
How does Vansah manage Iterations?
How does Vansah manage Iterations?
Vansah Test Plans include their own native Iteration support.
However, Zephyr Iterations are not migrated because their structure does not align with Vansah’s Iteration model.
Why are Test Execution keys different after migration?
Why are Test Execution keys different after migration?
When migrating test executions, Vansah creates new Test Run records.
Because of differences in database structure and system identifiers, retaining the same Zephyr execution key is not possible.
Therefore, Vansah generates new unique Test Run keys for all migrated executions.