If you’re moving off Zephyr Squad or Zephyr Scale, 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. Qase’s importer supports Zephyr Squad and Zephyr Scale as a single source type. Custom fields and attachment data need a separate pass.
How to migrate
Export your test case library as XML: in Zephyr Squad, from the Test Case Library search results; in Zephyr Scale, from the Test Cases view.
In Qase, open Import Data, choose Zephyr Squad/Scale as the source type, and upload the file. See Import Test Cases for the full walkthrough.
Check case counts and step formatting against Zephyr 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. Zephyr lives inside Jira, so every stakeholder who wants to see a test result needs a Jira license plus the Zephyr add-on. Qase is a standalone workspace with a lower-cost collaborator seat for anyone who only needs to view runs and comment.
Jira integration stays, you keep the two-way sync for defects and requirements, you just lose the requirement that every viewer has a Jira seat.
Reporting isn’t limited by Jira’s issue data model, so coverage and run history dashboards don’t need to be built around Jira fields.
Want the fuller feature-by-feature comparison? See Qase vs. Zephyr.
Questions about your migration? Contact support or use the in-app chat.