Skip to main content
Already have a spreadsheet of past incidents or failure reports? Migrate them to FTS in minutes using CSV import.

Preparing your CSV

Create a CSV file with the following columns (all optional except title):
ColumnTypeExampleNotes
titleStringConnector burn failureRequired; max 200 characters
bodyStringDetailed incident descriptionMax 5000 characters
tagsStringconnector,hardware,batchComma-separated; no spaces
created_atISO 86012025-12-15T10:30:00ZOptional; defaults to import date
statusStringresolvedOptional: open, resolved, in-progress
severityNumber2Optional: 1 (low) to 5 (critical)
attachment_urlsURLhttps://example.com/photo.jpgOptional; one URL per row
Keep file size under 50 MB. If you have more data, split into multiple CSV files and import separately.

CSV import process

1

Prepare your CSV file

Follow the format above. Save as .csv (UTF-8 encoding recommended).
2

Go to Import

In your workspace, click Tools (bottom of sidebar) → Import Data. You’ll see the import dialog.
3

Upload your CSV

Click Choose File and select your CSV. FTS will preview the first 5 rows to validate format.
If column names don’t match exactly, FTS will ask you to map them manually before proceeding.
4

Validate & map fields

Review the preview. If columns are misaligned:
  • Click each column header
  • Select the corresponding FTS field (or “Skip”)
  • Click Apply Mapping
5

Confirm import

FTS shows a summary: “Ready to import 247 cases.” Click Import to begin.During import, FTS validates each row:
  • Duplicate titles are flagged (same title + same tags)
  • Missing required fields are reported
  • Attachment URLs are checked for accessibility
Click Resolve Issues if errors appear, or skip flagged rows.
6

Review imported cases

After import completes, all cases appear in your Cases list with a blue “imported” badge. You can edit or tag them further.

Handling duplicates

If FTS detects a duplicate (same title + tags already in workspace):
  • Merge: Combine the two cases (new data overwrites old)
  • Rename: Append a suffix (e.g., “Connector failure v2”) and import as new
  • Skip: Don’t import this row
Choose per-row in the Resolve Issues view.
The import is transactional—if critical errors occur, no cases are added and you can re-upload after fixing your CSV.

Bulk attachment import

For files (photos, logs, PDFs):
  1. Create a folder on your web server (e.g., https://example.com/fts-imports/)
  2. Upload all attachments there
  3. In your CSV, add URLs: https://example.com/fts-imports/photo_batch_2847.jpg
FTS fetches each URL during import. Large files (>100 MB) may time out—split into smaller chunks.

Post-import cleanup

After import, spend 15–30 minutes reviewing:
  • Add missing tags for discoverability
  • Fix formatting inconsistencies
  • Update statuses to reflect current state
  • Invite team members to review and comment

Create your first case

Data export

Integrations