Skip to content
Docs

Migration from Qase

Welcome!

In this tutorial you will export your cases from Qase as a CSV file, import that file, and check that everything works correctly. Qase and Testomat.io store same things, so a migration is simple.

Export from Qase, import into Testomat.io, then check the result

Export from Qase

Section titled “Export from Qase”

First, get your test cases out of Qase as a file.

  1. Open your project in Qase.
  2. Export your test cases as a CSV file.
  3. Save the file on your computer.

The export option in a Qase project, with CSV selected

Open the file and check the first row. It should hold column names like Title and Folder - that is how Testomat.io knows what each column means.

Import into Testomat.io

Section titled “Import into Testomat.io”

Now you upload a CSV file.

  1. Open your project and go to the Tests tab.
  2. In menu (...), click Import from other TMS and the Imports window will open.
  3. Click Import.
  4. Choose Import from CSV. Import tests from CSV/XLSX sidebar opens on the right.

The Import from other TMS button on the Tests tab of a new project

Next, in the Import tests from CSV/XLSX sidebar:

  1. Choose Qase from the dropdown.
  2. Select the CSV file you exported.
  3. Click Create.

Choosing Qase as the source and selecting the exported CSV file

After Testomat.io reads the file, your test cases appear on the Tests page.

You do not have to rebuild anything: you picked Qase in the dropdown, Testomat.io knows how your file is built. Your tests are in the same folders they were in Qase, and each test keeps its steps and expected results.

If this doesn’t work

  • The import fails with an error. A missing header row is the most common cause.
  • Your folders are flat. Confirm you picked Qase in the dropdown - not another format.
  • Something is still off. Contact support.

Export your CSV, check the headers, import it, and check the result

Something missing or in the wrong place? Fix it in your CSV file and import again. That is much faster than editing tests one by one.

Next steps

Section titled “Next steps”