Use Plugin Migrations to import Xray Cloud Test Cases and Test Case Folders into Vansah in the same Jira space. The migration connects to Xray and Jira directly; you do not need to prepare a CSV file.
Before you begin
Sign in as a Jira administrator and make sure you can administer the Jira space being migrated.
Install Vansah and enable it for the Jira space.
The destination Jira space must have no Vansah Test Cases on its board or in its Recycle Bin. If it already contains data, contact Vansah to plan the migration before changing or removing that data.
Migrate one Jira space at a time. Complete or resolve an earlier migration before starting another.
Keep Xray available until you have checked the imported content in Vansah.
Prepare your credentials
Have the following credentials ready for the migration form.
Credential | What you need |
Xray client ID and client secret | A matching pair from an Xray Cloud API key with access to the source data. See Xray’s API key guide. |
Jira API token | A valid token for your Atlassian account. Use the Jira token link in the form to manage your tokens. |
Vansah API token | A token with access to the selected Jira space and permission to import Test Cases and create Test Folders. See Creating a Vansah API Token. |
Atlassian account email | If Vansah cannot retrieve your account email, enter it when prompted. It must match the account used for the Jira API token. |
What is imported?
Xray content | How it appears in Vansah |
Test details | Test Case headline, description, labels, priority, reporter as owner, components, and matching or newly created Test Case statuses. |
Manual tests | Test steps, test data, and expected results. |
Generic tests | A Plain Text test script. |
Gherkin tests | A BDD test script. |
Test Repository folders | Test Folders under Xray Test Folders, preserving the folder hierarchy. |
Linked preconditions | Precondition summaries and descriptions are added to the Test Case’s precondition content. |
Embedded attachments | Files referenced in imported descriptions and steps are copied where they are available and accessible. Check them after migration. |
For example, an Xray Test with the key QA-123 is imported as the Vansah Test Case QA-C123. Called tests in manual scripts are expanded into steps, so review their step order and content after migration.
This migration flow imports Test Cases and Test Case Folders. Plan separately for Test Plans, Test Sets, execution history, and requirement links.
Start the migration
Open Plugin Migrations
In Jira, select Apps > Vansah.
Open the Settings menu using the gear icon.
Select Plugin Migrations.
Select Xray and your Jira space
Choose Xray from the Plugin list and select Next.
Select the Jira space you want to migrate. The wizard accepts one space per migration.
Select Next.
Validate your credentials
Enter the Xray client ID and client secret, Jira API token, and Vansah API token.
If prompted, enter your Atlassian account email.
Select Validate.
Resolve any validation errors, then select Next.
Preview and confirm
On the review screen, select Preview beside your Jira space to check the source Test Case count.
Confirm that you selected the correct space.
Select Confirm to start importing. Vansah opens Migration History.
Check the migration
Open Settings > Migration History to follow progress.
Check that the migration and its Test Cases and Test Case Folders entries reach DONE.
Review any available logs if the migration fails or reports a problem.
Open Vansah in the migrated Jira space. Compare Test Case counts and check representative scripts, preconditions, labels, statuses, folder paths, and embedded files.
Re-create the requirement links and other content you need that falls outside this migration flow.
Resolve common problems
Problem | What to check |
Plugin Migrations is unavailable | You need Jira administrator permission. You also need administrator permission for the Jira space you select. |
Credentials fail validation | Check that the Xray client ID and secret belong together, the Jira token matches the account email, and the Vansah token can access the selected space. |
The destination contains Test Cases | The migration requires an empty Vansah Test Case board and Recycle Bin in that space. Contact Vansah if you need help preserving existing data. |
An earlier migration prevents a new one | Review its status in Migration History. Wait for an active migration to finish, or review the failure and contact Vansah before choosing recovery actions. |
Important: Deleting a migration can remove the Vansah Test Cases and Test Folders it imported. Review the confirmation carefully; use Migration History and its logs to investigate a problem first.