If you’re moving your test cases off Azure Test Plans, 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 cases from Azure Test Plans as CSV — open a plan, then use the export action on the suite (or the Test Plans REST API for larger sets).
In Qase, open Import Data, choose Azure DevOps (ADO) as the source type, and upload the file.
Check case counts and step formatting against Azure Test Plans 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
No separate access tier to buy. Test Plans is a paid add-on tier on top of your Azure DevOps org. Qase is priced per seat, with a lower-cost collaborator seat for anyone who only needs to view runs and comment, and no Azure DevOps org membership required.
Not tied to one issue tracker. Qase integrates with Jira, GitHub, GitLab, and Azure DevOps side by side, so switching (or running more than one) doesn’t mean rebuilding your test data.
Dedicated test analytics and QQL search, instead of building reports in Azure Analytics views.
Questions about your migration? Contact support or use the in-app chat.