Migrate from TestRail: bring cases onto the thread

Moving off TestRail is usually less about rewriting every case and more about where verification evidence lives. The goal is to bring cases onto the same thread as the requirements they verify in traceunified — not to lose the library your QA team already built.

What to export from TestRail

1. Test cases — title, steps (action / expected), priority, type, references, custom fields — as CSV or Excel.
2. Suites / sections — preserve hierarchy if your export supports it; otherwise recreate folders in the destination after import.
3. Historical runs (optional) — many teams keep TestRail read-only for past evidence and migrate the library forward; decide with QA and quality.
4. Jira / requirement IDs — export any external keys you use today so you can re-link after import.

Import into traceunified

Test cases come in through the same import path as other tabular work, with field mapping so steps and metadata land on your test item type.

1. Start an import and upload the CSV or Excel export.
2. Set the Import Destination (project folder / suite location).
3. Open Field Mapping — map title, steps, expected results, priority, type, and any custom columns to Target Fields. Leave unused columns unmapped.
4. Enable Import Traceability Links when the sheet carries requirement or risk IDs in link columns; otherwise plan a structured link pass after import.
5. Preview, then commit one project’s suite first.

Concepts and UI detail for mapping/preview: Import requirements (same Import Center pattern) and ReqIF & field mapping. Then prove live coverage and a sample signed run before expanding.

Cutover pattern

1. Map fields before committing a production import.
2. Link each case to the requirement it verifies (and risk it mitigates) — on import if IDs align, or in a cleanup pass.
3. Parallel run: TestRail remains the system of record for in-flight runs for one release; new cases and formal coverage move to traceunified.
4. Retire TestRail when coverage views and evidence match your QMS bar. Confirm you can export again from Export / reports.

Validation checklist

• Case count and critical suites accounted for
• Steps and expected results intact for a sample of high-risk tests
• Requirement-to-test links for a known subsystem
• Suspect-on-change exercised after an upstream edit
• Part 11 / audit path exercised on a controlled run (if in scope)
• Export path out confirmed

Related reading

• TestRail alternatives
• traceunified vs TestRail
• TestRail alternative
• Tests module
• Import requirements