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
Test cases, steps, and priority map directly. Custom fields and attachment data need a separate pass, they’re best handled with our team’s help for larger repositories.
How to migrate
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 attachments, custom field data, or execution history too? Reach out to our team and we’ll help plan it.
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.