Migrate From qTest to TestMu AI Test Manager in One Click

Why Migration Was the Blocker

Manual test case migration fails the same way every time:

• CSV exports flatten your folder tree - the hierarchy collapses into a single column that someone rebuilds by hand. Six months later, nobody can find anything.
• Custom dropdowns arrive as plain text - the values survive, but the constraints and the reporting built on them do not.
• Attachments do not export at all - downloading and re-uploading them means touching every test case, one at a time.
• Jira traceability simply breaks - the links that were hardest to establish are the first thing lost.

So migration projects sit in the backlog forever, and teams keep paying for a tool they have already decided to leave. One-click migration removes that specific problem. It is also the step that stalls most shortlists of qTest alternatives, long after the replacement has been chosen.

Start Migrating in 2 Steps

• Log in to TestMu AI, open Test Manager > Projects, click Import data, and select qTest. Enter your qTest instance URL and API token. Credentials are validated before anything runs.
• Pick one or more projects and click Start Migration. It runs in the background, survives page reloads, and emails you on completion. Migrated projects appear tagged qTest Migrated.

One thing to know: the migration covers test design data. Execution history, meaning runs, results, and defects, stays in qTest, so keep that accessible if you need it for audits. The migration guide covers prerequisites, scope, and troubleshooting in full.

qTest is the fourth tool with a one-click path into Test Manager, alongside TestRail, X-Ray, and Zephyr Scale.

What One Click Migration Does

The migration reads your qTest projects through the qTest API and rebuilds them inside Test Manager, structure and all:

• Folder hierarchy preserved - the qTest module and folder tree is recreated with the same ordering, so nobody has to relearn where things live.
• Custom fields created automatically - dropdowns, multi-selects, user fields, and checkboxes are detected and created at the org level, with required-field flags intact.
• Attachments carried over - files at the test case and step level are pulled from qTest and stored in TestMu AI. Inline images inside step content are re-uploaded with refreshed links so nothing renders broken.
• Jira links kept - if your Jira instance is integrated with TestMu AI, linked requirements on test cases carry over.
• Traceability back to source - original qTest IDs are stored as external IDs and tags, so every migrated case can be traced to where it came from.
• Read-only on the qTest side - your source data is never modified. You can validate everything in Test Manager before committing to anything.

In the migrated repository above, the nested folder path survives on every one of the 10,063 test cases, and each case carries two identifiers: its new Test Manager ID and the original source ID as a tag beside the title. That pairing is what makes the migration auditable months later, without a mapping spreadsheet somebody has to keep alive.

Note: Migrate a real qTest project today and evaluate TestMu AI against your actual test cases, not sample data. The migration is read-only, so nothing in qTest changes. Try it now

Why Choose TestMu AI Over qTest

Migration answers how to move. Here is why teams make the move, on the capabilities that matter most once your test cases arrive. Every qTest column entry below reflects what Tricentis states on its own live product pages as of August 2026.

For the full feature-by-feature and pricing breakdown, see the TestMu AI vs qTest comparison.

Summing Up

The hardest part of leaving qTest was never deciding to leave. It was the migration project nobody wanted to own. That project is now a background job: connect, select, and review the results when the email arrives, with your source data untouched the whole way through.

If your test cases have been stuck in qTest because moving them felt like a quarter of manual work, that reason is gone. Log in to Test Manager and open Import data to see your qTest library inside TestMu AI, with the migration guide open alongside it for prerequisites and troubleshooting.

If you are rethinking process at the same time as tooling, the test management fundamentals are a good place to start once your cases have landed, and agentic test management covers what the agent stack does with them afterwards.