Migrate to Qualflare
Move to Qualflare from TestRail, Qase, Testmo or Allure TestOps by importing their exports, or run it alongside Zephyr or Xray. What moves and what stays.
Last updated
Qualflare imports test cases from TestRail, Qase, Testmo and Allure TestOps export files of up to 20 MB. It has no importer for Zephyr or Xray, so with those you run Qualflare alongside. Automated results move separately, through the qf CLI.
Migration guides
Pick the guide for the tool you're moving from:
Migrate from TestRail
Import a TestRail CSV or XML export: sections become suites, and steps keep their expected results.
Migrate from Qase
Import a Qase CSV, JSON or XML export: JSON and XML keep nested suites, and steps keep their data.
Migrate from Testmo
Import a Testmo CSV export: folders become suites, with one step per case or a list of steps.
Migrate from Allure TestOps
Import an Allure TestOps CSV export with nested scenario steps, and keep your Allure adapters for results.
Use Qualflare alongside Zephyr or Xray
No importer exists: keep your manual tests where they are and upload automated results with qf.
What each tool can import
Qualflare's Import reads the export files of four tools:
| Tool | Files | Suites come from | Case state |
|---|---|---|---|
| TestRail | CSV, XML | Sections, as a Parent > Child path | Draft |
| Qase | CSV, JSON, XML | Suites; JSON and XML keep the path | Kept when it matches a Qualflare state |
| Testmo | CSV | Folders, as a path | Kept when it matches a Qualflare state |
| Allure TestOps | CSV | Suite labels, else epic, feature and story | Kept when it matches a Qualflare state |
| Zephyr, Xray | None: run Qualflare alongside | — | — |
Qualflare doesn't import generic CSV or spreadsheet files, or its own export.
What moves and what stays
- Moves: suites, test cases and their steps. An expected result becomes its own Expected Result step, and preconditions become a Precondition step where the export has them. Priority and test type map to Qualflare's values.
- Stays in the old tool: runs and results, attachments, tags, custom fields, test plans, milestones and users.
Qualflare suites don't nest, so a nested section or folder becomes one suite whose name holds the path, such as API > Authentication.
Before you start
Editor+ · project (requires the Editor role or higher in the project)- Import is on every plan. It adds to the project you open Browse in, so create the project first.
- Imported suites and cases count toward your workspace's limits, 10 test suites and 200 test cases on Starter: every section path, suite or folder in the export becomes one suite. See What happens at a limit.
- One file holds up to 1,000 cases in 200 suites. Export a larger project in parts, a few suites or sections at a time. See Limits.
- Importing never changes or deletes what a project already has: a case whose name already exists in its suite is skipped.
Plan your migration
- Import your test case library into each project with the guide for your tool.
- Upload automated results from CI with
qf <identifier> collect: each upload becomes a launch (CI/CD integration). A result joins an imported case only when its suite and case names match; otherwise the upload creates an automated case, and its suite if no suite has that name. If a result that joins an imported case includes steps, they replace the case's imported steps (Steps on matched cases). - If your tests write Allure results, keep the adapters and upload the results directory (Upload Allure results).
- Recreate your test plans and milestones, then invite your team.
Related
- Guides: Import and export test cases · Create and edit test cases
- Reference: Test suites and Browse · Plans and limits · Glossary: test suite
- CLI/API: Upload results with qf collect
Tutorial: run a manual regression cycle
Run a manual regression cycle in Qualflare: write cases with steps, save them as a test plan, run it in the Test Wizard, then finalize it and file defects.
Migrate from TestRail
Move test cases from TestRail to Qualflare with a CSV or XML export: how sections become suites, which fields map, and what stays in TestRail.