Before planning a Zephyr migration, confirm the available migration path with Vansah. Zephyr is not currently listed in the source-tool selector in Plugin Migrations. Older screenshots showing that option and a Jira API token field do not describe the current setup.
Confirm the migration path
Identify the exact Zephyr product and hosting option you use. Zephyr products can store and expose test data differently.
List the Jira spaces and data you need to move, such as cases, scripts, folders, plans, cycles, execution results, and attachments.
Contact Vansah to confirm availability, supported data, mappings, access requirements, and how the migration should be started.
Agree on a review approach before moving your full testing scope.
See Start a Test Management Tool Migration to Vansah for the current migration entry point. Do not choose another source tool just to continue through the wizard.
Prepare for the agreed workflow
Confirm that your administrator can access the source data and the destination Jira spaces.
Review how source cases, versions, folders, requirements, and results will map to Vansah.
Identify data or configuration that needs a separate process rather than assuming everything will transfer.
Keep credentials private and provide them only through the agreed migration workflow. The current migration service uses your signed-in Jira authorization rather than the older Jira-token setup.
If you only need to bring across case content, discuss whether CSV or Excel Test Case import fits your needs. A file import should not be assumed to preserve complete Zephyr history or configuration.
Review an existing migration job
Open Migration History in Vansah.
Find the job for the correct source tool and Jira space. Check both ongoing and historical migrations.
Open the job’s More menu and choose View Progress where available.
Review each data category and any error information. A completed category does not mean every category has finished.
The retained screenshot shows the View Progress action in an earlier layout.
Verify the migrated data
After the job finishes, compare the agreed source scope with the data visible in Vansah. Open representative cases and scripts, check folder and work item links, and review any plans and execution results included in the agreed migration.
Record missing or mismatched items and contact Vansah before restarting or deleting a job. A retry or deletion can affect existing migration work. Check Migration History even if no notification email arrives. See Why Vansah Requests an Email During Migration.