Importing your customer data via CSV
The field-mapping guide for CSV imports — required columns, optional fields, handling duplicates, and validation errors.
Importing accounts via CSV
Admin Console → Integrations & Data → Quick Import walks you through a mapped CSV import.
Steps
- Choose what you're importing (accounts, contacts, or a custom object) and upload your CSV. The importer previews the first rows.
- Map columns. Match your CSV headers to Velsano fields. For accounts, name is required; everything else — ARR, renewal date, owner email, lifecycle stage, custom fields — is optional but recommended. The importer auto-maps obvious matches.
- Set a match key. Rows are matched on an external ID or name, so re-importing updates existing records instead of creating duplicates.
- Validate. Bad rows (invalid dates, unknown picklist values, missing required fields) are flagged before anything is written — nothing commits until you confirm.
After import
Health scores recalculate for imported accounts so you're not left staring at a blank portfolio. If you imported usage or contract data too, give the nightly jobs a cycle to roll everything up.
Tip
For large or recurring loads, prefer a connector (Admin Console → Integrations & Data → Connectors) over manual CSV — it re-syncs on a schedule.
Related: *Connectors & Data Hub* · *Importing data (admin)*