Skip to main content
Import test cases from external tools, and export them for backup, migration, or offline use.

​
Import

Only organization Owners and Admins can import test cases. Open the Import Test Cases dialog from either:
  • + New → Import CSV / JSON in the header
  • The Import CSV / JSON card on the empty No test cases yet screen

​
Supported formats

​
Import limits

An import that would take the project past its plan’s test case limit is rejected before it starts. Split a larger export into batches and import them one at a time.

​
Templates

Click Sample to download a JSON or CSV template to properly map test cases and their fields before importing. Templates show the expected field names, hierarchy structure, and data types so your import maps correctly on the first attempt.

​
CSV import flow

  1. Upload: Drag-and-drop or browse to select a .csv file. TestDino detects whether it is a TestDino or TestRail export from its columns.
  2. Map Columns: Map each CSV column to a TestDino field. Columns are matched by name; review them with the All, To review, Mapped, and Skipped filters and the row preview. A column must be mapped to Title to continue.
  3. Configure: Choose how to handle duplicates, then click Start import. Suites come from your file; rows without a suite name go to Unassigned.
CSV Import Wizard showing CSV/JSON tabs, source radio (TestDino/TestRail/Other CSV), template download, and file drop zone
RecommendationUse JSON for flexible import: it preserves the full suite hierarchy, steps, tags, and all metadata with no manual mapping. For faster test creation, use the TestDino MCP Server to create and manage test cases directly from your IDE.

​
JSON import flow

  1. Upload. Drag and drop or browse to select a .json file, then choose the source type such as TestDino or Testmo. Use Preview to review the contents before continuing.
  2. Configure & Import. Review detected suites and test cases, configure duplicate handling options, then start the import.
JSON import preserves suite hierarchy, test steps, tags, classifications, automation fields, custom fields, releases, manual runs, and sessions from the source export. JSON Import dialog after upload showing file name, test case count, suite count, suite list, and Validated ready to import status

​
Duplicate Handling

Before importing, choose how to handle test cases that already exist with the same title. The default is to skip them. CSV and JSON imports label the options differently. Skip duplicates is the default and the safest choice for re-importing the same file.

​
Export

Export is available on the Team and Enterprise plans. Click the Export button in the Test Cases header to open the format dropdown. 3 options are available.

​
Export selected test cases

Export includes the test cases in the current view: the open suite, your search, and your filters, up to 10,000 test cases per export. To export only a subset, tick checkboxes to select cases first; see Bulk Export for the per-selection flow. An Exporting badge shows in the header while the export is prepared. Export dropdown in the Test Cases header showing Export JSON, JSON with Attachments, and Export CSV options
TipUse JSON export for full-fidelity backups and migration. Use CSV export when you need to open test cases in a spreadsheet or import into a non-TestDino tool.

Bulk Actions

Select test cases before exporting

Concepts & Settings

Test case fields, structure, and project settings

Overview

Test Management capabilities and navigation
Last modified on September 29, 2026