Skip to content
PRESHaiPRESHaiPRESHos Platform

CSV import

Settings import batch-creates CRM objects and work items from a CSV file. It is the bulk path where the workspace pages are the single-row path: same records, same validation, no per-row clicking.

Open in product: preshos.com/settings/import

What it covers

Section titled “What it covers”
  • CRM objects: the records behind the CRM workspace pages — companies, contacts, deals, and related rows. See Objects for the object groups and Sales for where the rows land.
  • Work items: the tracked work behind Work items, typed by Work Item Types.
  • Custom fields travel with the row: values for tenant-defined fields on the target object are accepted where the object accepts them. See Custom Fields.

How a run works

Section titled “How a run works”
  1. Pick the target. Choose the object or work-item type the rows belong to. One file, one target — do not mix companies and work items in a single CSV.
  2. Upload the CSV. The header row names the incoming columns. Keep the file to the columns the target accepts; extra columns are a mapping question, not data.
  3. Map columns to fields. Confirm each CSV column lands on the intended field, including custom fields and owner references. An unmapped column does not import — review the mapping before running.
  4. Run and read the result. The run reports created rows plus per-row failures with reasons. Fix the failed rows in the CSV and re-run only those; do not re-upload the rows that already landed.

Working rules

Section titled “Working rules”
  • Small file first. Prove the mapping on a handful of rows before sending the full file — a mapping mistake at ten rows is a correction, at ten thousand it is cleanup.
  • Owners resolve to tenant members, not free text. If an owner value does not resolve, the row fails rather than inventing a member. Membership truth lives under People.
  • Imports write through the same validation as the workspace pages. A row the workspace would reject fails here too — read the per-row reason and fix the source data.
  • Treat the product UI as the source of truth for file-size limits, accepted encodings, and whether a target object supports import yet. Targets this page does not name are not promised.

What next

Section titled “What next”