Moving from another TMS
You send an export, we run a trial import on your project, then a full import checked by case count. A few thousand cases usually move within 1 day.
How the move goes
We take the first steps together with you. A few thousand cases usually move within 1 day.
You send an export
A file from TestRail, Zephyr, Xray, Qase or Excel. We tell you what moves one to one, what goes into project custom fields and what has to be filled in by hand.
We run a trial import on your project
We move part of the base into a separate project. You open a dozen cases and tell us what to fix in the mapping.
Full import, checked by case count
After the upload the system returns the number of imported and failed cases with the list, so the check is done on numbers, not by eye.
We set up roles, SSO and the first test plan
We create projects, roles and members, connect SSO sign-in and build the first plan from the migrated cases. From then on the old system is no longer needed.
What we move
TestRail, Zephyr, Xray, Qase, TestLink, CSV and Excel. You pick the source system when you upload the file, so its columns are parsed by its own layout.
TestRail
Export the project to CSV, Excel or XML. Choose TestRail as the source on upload and the columns are read by its layout.
Zephyr
Export to CSV or Excel. Action, test data and expected result stay three separate step fields instead of one glued paragraph.
Xray
Export to CSV, Excel or XML. A case comes over with its list of steps, preconditions and priority.
Qase.io and TestLink
Their own export formats are parsed directly, with no spreadsheet in between: JSON and XML.
CSV and Excel
If the base lives in a spreadsheet rather than a tracker, we move the spreadsheet: columns are mapped to case fields.
File size
Up to 50 MB the file is imported straight away. Between 50 and 100 MB it goes to a background job with a visible status. Larger files are split.
How the fields land
Most fields have a direct counterpart. Anything without one goes into project custom fields instead of being dropped.
- Title and description
- Move across one to one, together with the case description.
- Preconditions and postconditions
- Kept as separate fields on the case. Repeating ones are later pulled out into shared preconditions.
- Steps
- Every step keeps three fields: action, test data and expected result.
- Priority, type, severity
- Values are matched to CommIT TMS lists: priority, type, severity, layer and case status.
- Labels
- Become tags, which is how you find cases once the base runs into thousands of records.
- Fields we do not have
- We add a project custom field of the right type and move the values into it.
What changes after the move
Verifiable differences only. Everything listed works in the current version of the product.
The base stays yours
Export in 6 formats at any time: CSV, Excel, XML, JSON, HTML and PDF, with the suite hierarchy preserved.
Contract and invoicing
A contract and an invoice for your company. Write to sales for terms.
Can run in your perimeter
The same application deploys inside your infrastructure when the data must not leave the network.
AI writes the cases
Paste a ticket or a piece of a spec up to 10,000 characters and get cases with preconditions, steps and expected results. The tester makes the final call.
Send the export, we will look at your base
From the file we tell you what moves automatically and how long the move takes. The trial import runs on your project, not on demo data. Or start on your own: import is available right after sign-up.
30 minutes online with a CommIT expert: we walk you through the product and answer questions about your process