If you’re moving your test cases off PractiTest, 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 Test Library from PractiTest as CSV — from the Test Library view, or via PractiTest’s REST API for larger sets.
In Qase, open Import Data, choose PractiTest as the source type, and upload the file.
Check case counts and step formatting against PractiTest 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
A flatter workspace. PractiTest organizes work through Test Sets and Cycles above your test library; Qase’s filter-first repository gets you to your first run with less setup.
Collaborator seats for anyone who only needs visibility into results, not a full seat.
AI test case generation is built in, not a separate add-on.
Want the fuller feature-by-feature comparison? See Qase vs. PractiTest.
Questions about your migration? Contact support or use the in-app chat.