RunwayCal

CSV Import

Preview the rows. Confirm what enters RunwayCal.

Import supported Team, Tools, or Deals records from a structured CSV template. RunwayCal validates the file before it writes, shows errors and warnings by row, and waits for explicit confirmation before valid records are created.

Start freeSee the workflow
Input
One structured CSV
Review
Errors and warnings before write
Destinations
Team, Tools, or Deals
Conceptual workflowReview before write
  1. 01TemplateRequired headers
  2. 02PreviewErrors + warnings
  3. 03ConfirmExplicit action
  4. 04RecordsCreated + skipped
Nothing is written before this point
Conceptual explanation only. This sequence describes the supported import contract and does not present invented product data.

Supported destinations

Choose the records first. Then use the matching template.

CSV Import is not a universal spreadsheet mapper. It begins inside one supported destination and uses that destination's expected schema. Extra columns do not replace missing required headers.

  1. 01

    Team

    Create supported team records from the Team CSV template.

  2. 02

    Tools

    Create supported tool and subscription records from the Tools template.

  3. 03

    Deals

    Create supported deal records from the Deals CSV template.

Import workflow

Upload, preview, then confirm.

The review step is part of the product, not a promise that every row is accepted. The file is held in a temporary preview session while the user decides whether to confirm the import.

  1. 01
    Upload

    Start from the destination

    Open CSV Import from Team, Tools, or Deals. Download that destination's template, keep the required headers, and select one .csv file up to 1 MB and 200 rows.

  2. 02
    Preview

    Read the row-level result

    RunwayCal parses the file and previews supported fields with row errors and warnings. Missing values, invalid dates, numbers, categories, statuses, and billing values are surfaced before confirmation.

  3. 03
    Confirm

    Create only after review

    Confirmation writes valid rows to the chosen destination. Invalid rows stay skipped and are reported. The result separates records created, rows skipped, and remaining errors.

Validation boundary

A warning asks for attention. An error keeps the row out.

The preview can flag an existing record name as a warning while field errors identify rows that cannot be created. Valid rows may still be confirmed, and the result makes the created, skipped, and error counts explicit.

Re-importing the same file uses stable row identity to avoid recreating rows already written from that file. This is a narrow replay safeguard, not a broad claim that RunwayCal finds every duplicate across unrelated files.

File
One .csv, up to 1 MB
Rows
Up to 200 per import
Destinations
Team, Tools, or Deals
Encoding
UTF-8 with Latin-1 fallback
Headers
Destination template required
Write
Explicit confirmation

Product evidence

The evidence should show a real CSV preview, not the document Upload flow.

The legacy image belongs to a different product. A current CSV-specific capture is reserved below so the page does not manufacture a mapping or validation interface.

Current capture required

CSV Import: preview and validation

Capture the current destination-specific preview with representative valid rows, field errors or existing-name warnings, the skip-errors control, and the explicit confirmation action.

public/product/csv-import-preview.png

Product boundary

Structured import, not open-ended data transformation.

CSV Import moves supported records into one named destination. Upload and AI Import is a separate product for supported document extraction, while integrations remain separate connection paths.

  • No arbitrary column-mapping screen
  • No AI extraction step
  • No multi-file batch
  • No Cash Commitments destination
  • No live accounting or bank connection
  • No rollback or import-history promise

Connected context

CSV Import handles structured rows for three destinations. Document extraction, operating review, and runway interpretation remain distinct workflows.

CSV Import

Review the rows before they become records.

Start with the matching template, resolve what the preview surfaces, and confirm only when the destination and row result are clear.

Start free