If you’re moving your test cases off TestRail, 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, suite hierarchy, steps, and priority from an XML export. It takes a few minutes and suits a team that only needs its test library.
The TestRail migration tool reads TestRail over its API and also brings test runs and results, attachments, custom fields, shared steps, milestones, configurations, and users. It suits a team that wants its execution history too.
Importing test cases from an XML export
In TestRail, export each Test Suite as XML from the Test Cases view. XML keeps the nested suite structure, which is why it’s the better choice over CSV for TestRail specifically.
In Qase, open Import Data, choose TestRail as the source type, and upload the file. See Import Test Cases for the full walkthrough.
Check suite nesting and case counts against your TestRail project before you retire it.
Migrating everything with the migration tool
The TestRail migration tool is free for every paying and trialing Qase customer. It runs on your own machine and works with TestRail Cloud and TestRail Server or Data Center. Its README lists exactly what carries over and what does not — read the coverage table and known limitations before you plan the move.
Follow the Prerequisites, Install and Configure sections of the TestRail 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
Collaborator seats. TestRail bills every named user the same price. Qase has a lower-cost collaborator seat for anyone who only needs to view runs and comment, not write cases.
Requirements traceability and QQL are built in, so coverage and release-readiness reporting don’t need a separate export step.
One workspace, not one license per project.
Want the fuller feature-by-feature comparison? See Qase vs. TestRail.
Questions about your migration? Contact support or use the in-app chat.