Every migration (TestRail API, TestRail CSV/XML, or a generic CSV) runs a Fidelity Report at the Preview step, before a single row is written. If something can’t map cleanly — an unmapped priority, a dropped custom field, an unrecognized column — you see it, with an exact count, first.
| Qmatrix | Typical importer | |
|---|---|---|
| Shows what will be dropped before you import | ✓ | ✕ |
| Per-field mapping/default counts, not just a pass/fail | ✓ | ✕ |
| Re-running an import updates existing cases instead of duplicating them | ✓ | ✕ |
| One-click rollback window | 14 days | none |
| Full error & warning log, downloadable | ✓ | ✕ |
Before you click Import, Qmatrix scans every case, priority, type, and column against what it can actually represent. Anything that will be defaulted or dropped is listed with an exact affected-item count — not a vague "some data may not transfer" disclaimer.
Every imported case is tagged with its source system’s ID. Re-running the same import updates those cases in place instead of creating duplicates, so you can fix a mapping and re-run without cleanup.
If an import doesn’t look right after the fact, undo it from the migration wizard — no support ticket, no manual deletion. The window is 14 days, long enough to notice a problem during a normal sprint or UAT cycle.
Anything that failed outright (not just partial-fidelity items) is logged per row and downloadable as CSV, so nothing silently vanishes.
No "trust us." Every fidelity number in this guarantee comes from the same report you’ll see on your own import.
Start a migration