Zephyr Essentials migration brings supported test cases, test scripts, folders, and the latest execution results into Vansah. Some information is mapped to a different structure, and full version and execution histories are not imported.
Before planning a migration: Contact Vansah to confirm migration availability and the scope for your Jira space. If Zephyr Essentials is not listed in the migration tool, confirm the next steps with Vansah.
Test case fields
In Zephyr Essentials | In Vansah |
Name | Headline |
Objective | Description |
Precondition | Precondition |
Status | Test case status, matched by name or created when needed. |
Priority | Jira priority, using the priority mapping selected for the migration. |
Owner | Test case owner. |
Component and labels | Component and labels. |
Estimated run time | Estimated Time. |
Folder | A linked Test Folder in the migrated folder structure. |
Linked Jira issues | Linked Jira work items. |
Review priority and execution-result mappings before starting. For example, confirm which Vansah result should be used for each Zephyr execution status.
Test scripts and images
Script type | What is imported |
Step-by-step | Step descriptions, test data, and expected results. |
Plain text | The test script text. |
BDD / Gherkin | The behavior-based script text. |
Embedded images in supported descriptions, preconditions, and scripts are processed for migration. Check them after import to confirm that they display correctly.
Separate file attachments are not migrated. An image embedded in a description or script is different from a file attached to a test case. Keep any separate files you still need available for manual transfer.
Cycles and execution results
When cycles and executions are included, a Zephyr Test Cycle is represented by a Vansah Test Folder and a Standard Test Plan. The folder organizes the linked test cases, and the plan holds the migrated round of testing.
Execution information | What to expect in Vansah |
Execution result | The latest overall result is imported using your result mapping. Earlier executions are not imported. |
Execution key | Vansah creates a new Test Run key. The original Zephyr execution key is not retained. |
Execution date | The source execution’s actual end date is used as the tested date. This does not transfer the full execution timeline. |
Executed by | The source tester is used when their account can be matched. Check the tester after migration. |
Assigned to | Cycle execution assignments are used for linked cases in the migrated plan when the account can be matched. |
Release and environment | Available values are used for results imported against the migrated folder. Review these separately from the plan’s Run Setup. |
Cycle dates | Available planned start and end dates are used for the migrated plan. |
If a tester or assignee cannot be matched, the migration user may be used instead. Review assignments before your team starts testing.
The original per-step execution results, actual-result comments, and execution defects are not transferred as a detailed execution history. The migrated overall result should not be treated as evidence that the original step-level record has been preserved.
Versions and information that is not migrated
The migration imports the current test case information returned by the source system. It does not recreate the test case’s version history or all previous revisions.
Zephyr test case version history and earlier revisions.
Full execution history; only the latest executions are requested.
Zephyr Test Plans and their original iterations.
Zephyr custom fields and web links.
Separate test case file attachments.
Original execution keys, actual time spent, and the source Manual/Automation execution-type setting.
Vansah supports its own Test Plan iterations and Jira custom fields, but those features do not mean the corresponding Zephyr history or custom-field values are automatically migrated.
Review the migration before using the imported data
Compare the migration summary with the expected test cases, folders, cycles, and latest results for the Jira space.
Open sample cases of each script type. Check the headline, description, precondition, steps, expected results, labels, priority, and owner.
Check embedded images, folder placement, and links to Jira work items.
Open migrated Test Plans and Test Runs. Confirm the overall result, tested date, tester, and assignments.
Record anything that needs manual transfer, including separate attachments and information outside the migration scope.
For ongoing use, see Understanding Test Plans.