# Make CSV Tulip user import possible (and improve export?)

**URL:** https://community.tulip.co/t/make-csv-tulip-user-import-possible-and-improve-export/16419
**Category:** Product Suggestions
**Tags:** users, export-to-csv, user, csv, import
**Created:** [June 12, 2026, 8:42am UTC](https://community.tulip.co/t/make-csv-tulip-user-import-possible-and-improve-export/16419 "2026-06-12T08:42:32Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![fti](https://avatars.discourse-cdn.com/v4/letter/f/fbc32d/32.png) [@fti](https://community.tulip.co/u/fti)
#### Post date: [June 12, 2026, 8:42am UTC](https://community.tulip.co/t/make-csv-tulip-user-import-possible-and-improve-export/16419/1 "2026-06-12T08:42:32Z")

</div>

Greetings.

I’ve recently been working with a table containing users. I wanted to fill this table with a test dataset to evaluate some app behavior under more realistic conditions. However, I noticed that for columns of type **User** :

- Exporting to CSV simply adds the user’s full name in the CSV (which is ambiguous if two users share the same name),
- and importing users via CSV seems to be impossible.

I think it would be good if:

- An exported user CSV value also contained the Tulip user ID to guarantee unicity.
- A user could be imported using the Tulip user ID.

Both of these needs could be fulfilled if, for example, the user was represented as a CSV value with a format such as `<full-name> (<tulip-user-id>)`, e.g.: `John Doe (xip7DXdLOJDgo4Iio)`.

What do you think?