If you’re moving off Xray, this guide covers what carries over, how to run the import, and what’s genuinely different once your team is on Qase.
What comes across
There are two ways to move, and they carry different amounts.
The in-app import brings test cases, steps, and priority from an XML export.
The Xray migration tool reads Xray Cloud over its API and also brings your folder tree, test executions and their results, and attachments. It works with Xray Cloud only, not Xray Server or Data Center.
Importing test cases from an XML export
Export your Tests from Xray as XML — from the Test Repository, or from a saved Jira filter of your Test issues, using Xray’s export action.
In Qase, open Import Data, choose Xray as the source type, and upload the file. See Import Test Cases for the full walkthrough.
Check case counts and step formatting against Xray before you retire it.
Migrating everything with the migration tool
The Xray migration tool runs on your own machine. It works in three stages — extract, transform, load — so a failed load can be re-run without fetching from Xray again. Test plans, test sets, and preconditions are not migrated; its README lists exactly what carries over.
Follow the Prerequisites, Install and Configure sections of the Xray migration tool README. You need Python 3.11 or newer and credentials for both sides.
Validate your configuration before anything is written, then do a dry run: it reads everything and writes nothing to Qase.
Run the migration, then read the migration report it prints at the end. It lists everything that was skipped or degraded, with the reason.
Stuck, or want us to run the migration for you? Email [email protected]. A fully managed migration, including adapting the tool to your data, is available as a paid service.
What’s different in Qase
No Jira seat required for viewers. Xray confines test data to Jira, so every stakeholder who wants to see a result needs a Jira license. Qase is a standalone workspace with a lower-cost collaborator seat for anyone who only needs to view runs and comment.
Jira integration stays for defects and requirements, you just lose the requirement that every viewer has a Jira seat.
Managing test structure doesn’t need Jira admin permissions — suites, fields, and workflows live in Qase directly.
Want the fuller feature-by-feature comparison? See Qase vs. Xray.
Questions about your migration? Contact support or use the in-app chat.