Documentation Data Import
Detailed guide

Data Import

Controlled bulk CSV import for seeding a new workspace or refreshing existing data across settings, catalog, people, projects, and commercial records.

Data Import is the bulk-change entry point for the workspace. It exists for structured, previewable, reversible-by-threshold updates rather than ad hoc mass editing, so large data movements stay safe and auditable.

Open demo page Back to overview
Quick summary Step by step Guardrails Troubleshooting Related workflows

Quick summary

  • Download the entity's sample CSV and shape your file to match its columns before uploading.
  • Run Test changes first to catch structural and data errors without touching live data.
  • Choose Update for incremental refreshes and reserve Overwrite for a deliberate full replace.
  • Set the rollback threshold to 0 when the file must import completely or not at all.
  • Check the import history status and error detail after every real import.

Put it into practice

  1. Select the entity tab that matches the data you are loading. Each tab has its own template, columns, mode behaviour, and history, so getting this right first avoids importing into the wrong place.

    InteractionsData Import page: click the correct entity tab (for example Projects, Clients, or Service Catalog).

  2. Download the sample CSV and compare its columns against your source file. Match required columns exactly before you upload anything.

    InteractionsGet the template card: click Download sample CSV and align your file to the shown columns.

  3. Choose the CSV file and pick the import mode deliberately. Use Update to add and refresh by name, and only use Overwrite when you intend to delete and replace all existing records for that entity.

    InteractionsUpload card: select the CSV file, then choose Update or Overwrite mode.

  4. Set the rollback threshold to control tolerance for bad rows. Use 0 for all-or-nothing, or a small percentage to allow a few known-bad rows without failing the whole batch.

    InteractionsUpload card: set the Rollback threshold value.

  5. Run Test changes first. Preview validates the file and reports errors without saving, so you can fix the source before committing.

    InteractionsUpload card: click Test changes and read the validation result.
    Open workflow: Upload Import File

  6. When the preview is clean, run Import Data to commit. Confirm the Overwrite warning if you chose that mode, since it removes existing records first.

    InteractionsUpload card: click Import Data and confirm the modal if prompted.

  7. Review the import history row and then verify the affected records in their destination pages to confirm the data landed as expected.

    InteractionsImport history: check Status and error detail, then open Projects, Clients, or Catalog to spot-check imported rows.
    Open workflow: Projects

What to review

Entity tabs

The import type selector across the top: Settings, Service Catalog, Proposal Groups, Expense Categories, Clients, Roles, Users, Projects, Estimates, Quotes, Invoices, Timesheets, Expenses, Year Goals, and Calculator Goals. Each tab has its own template, columns, and history.

Get the template card

The 'Download sample CSV' action and the list of expected columns (required columns are marked). Start here so your file matches exactly what the importer expects.

CSV file chooser

The upload input that accepts a .csv file prepared from the template for the selected entity.

Import mode

Update adds new records and refreshes existing ones matched by name; Overwrite deletes all existing data for that entity first, then imports. Overwrite is destructive and asks for confirmation.

Rollback threshold

The percentage of row errors allowed before the whole import is rolled back. Set it to 0 to make the import all-or-nothing. Preview never saves changes and ignores this setting.

Test changes and Import Data actions

Test changes runs a preview that validates without saving; Import Data commits the import. Overwrite mode shows a confirmation modal before proceeding.

Import history

The right-hand log of recent imports showing Date, File, Mode, By (who ran it), Rows (success/total), and Status (Success, Test, Partial, or Failed), with expandable per-row error detail.

See guide: Upload Import File

Guardrails

  • CSV structure and entity-specific rules must validate before data is committed; run Test changes so errors surface without saving.
  • Overwrite mode deletes all existing records for the entity before importing, so a wrong file can wipe good data. Preview and confirm before using it.
  • The rollback threshold decides whether a partially bad file is committed or rolled back, so set it consciously rather than leaving it at a default you did not check.
  • Data Import is admin-only because a single import can change large parts of the workspace at once.
  • Because imports can overwrite people, pricing, and commercial records, access should be limited to trusted administrators.

If it starts drifting

  • If an import fails, fix the first reported structural error before revisiting the rest of the file; later errors often cascade from it.
  • If the file is rejected outright, re-download the template and compare headers directly rather than guessing which column is wrong.
  • If the status shows Partial, open the expandable error list to see exactly which rows failed and why before re-running.
  • If imported data is missing, confirm you were on the intended entity tab and that Overwrite did not remove records you expected to keep.