Yven Help

Importing your client book

Already keeping clients in a spreadsheet? You don’t have to retype any of it. The CSV importer takes a single file and turns each row into a client (and, where present, a site and a service) in your registry. It’s a guided, four-step flow with a preview before anything is written. Find it under Settings → Data → Import.

What a row contains

One row describes one service for one client. Repeat a client across rows to give them several services – Yven reuses the existing client rather than creating duplicates. A handy starting point is the sample CSV you can download from the import wizard; its columns are:

Column What it is
Client Name (required) The client this row belongs to.
Company, Email, Website Client contact details (used when the client is first created).
Asset Type Domain & DNS, Hosting, CDN, SSL, Email, CMS, CMS Plugin, Framework, Database, Code Repository, CI/CD, Payment Processing, E-Commerce, Analytics, Advertising, SEO, CRM, File Storage, Backup, Monitoring, Auth/Identity, or Other – see Services for the full list. Anything unrecognised imports as Other rather than being skipped.
Label (required) A short name for the service (for example, the domain name).
Provider, Account Who the service is with, and the account identifier.
Renewal Date, Renewal Cost When it renews and what it costs (left blank = not tracked).
Paid By me_rebilled, me_absorbed, or client_direct.
Managed By me, client, or third_party.

See Services for what each of those fields means.

The four steps

  1. Upload – choose your .csv file (up to 2 MB). Yven reads the header row and shows you the columns it found.
  2. Map columns – Yven auto-matches your headers to its fields. Check the guesses and fix any it got wrong. You must map at least Client name and Label; everything else is optional.
  3. Preview – see exactly what will be created, split into rows that will import and rows that will be skipped (with the reason). If your dates use slashes, pick whether they’re day/month/year or month/day/year so they’re read correctly.
  4. Import – commit the valid rows. You’ll get a summary of what was created.

Skipped rows

Nothing partial is ever written: a row either imports cleanly or is skipped with a reason (a missing client name, an unrecognised type, an unreadable date…). You can download the skipped rows as their own CSV, fix them in your spreadsheet, and re-import just those – the importer won’t duplicate the clients that already came in.

Where to next


Was this helpful, or did we miss something? Let us know.