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