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
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. Qase’s importer supports Zephyr Squad and Zephyr Scale as a single source type.
A Zephyr migration tool reads Zephyr over its API and also brings your folder tree, test cycles and executions, and attachments. There is one tool per Zephyr product, listed below.
Importing test cases from an XML export
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 everything with a migration tool
Each Zephyr product has a different API, so pick the tool that matches yours:
Your Zephyr | Tool |
Zephyr Scale Cloud | |
Zephyr Essential, the Jira Cloud app v10 and later, formerly Zephyr Squad | |
Zephyr Enterprise, self-hosted |
Not sure which you have? If your test cases appear in Jira as issues with their own keys, you are on classic Zephyr Squad, which none of these tools covers — use the XML import above. If they live in a Zephyr panel with their own folder tree, you are on Zephyr Essential.
Every tool runs on your own machine. On Zephyr Essential, attachments are an opt-in extra step, because Zephyr’s API does not hand over the files themselves — the tool’s README explains the trade-offs.
Follow the Prerequisites, Install and Configure sections of your tool’s 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. 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.