> For the complete documentation index, see [llms.txt](https://docs.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pakk.io/data-and-integrations/data-import-and-export/export/csv-conventions.md).

# CSV Conventions

Here are some notes about conventions we use in our CSV file exports and imports.

This is probably the most important part of this article and crucial to making your life with CSVs easier - don't skip over it!

* Wrap your complex text fields with double speech marks (`"` ), especially if they themselves contain a comma. Most other exporting systems, including Pakk, will do this for you by default.
* Use `TRUE` or `FALSE` for checkbox-type fields (Boolean, in tech speak).
* "Simple" list fields (like numbers, checkbox-type, text or reference identifiers) are represented as a comma-separated list, e.g. if you wanted to enter a list of "content tags" for a product, the field might read `cooking,recipes,vegan`. Remember not to include spaces and to wrap with speech marks (see above).
* More complex, "composite" fields (basically fields that have sub-fields, like an address) are represented with "dot notation" - e.g. `address.recipient`, `address.phone`, `address.phone` etc.
* Required fields (for import) are marked with an asterisk `*` before the column header -e.g. `*email`. You don't have to remove that asterisk when re-importing data - the system is clever enough to ignore it.
* Non-importable fields - i.e. fields that can be exported but not imported, are marked with an exclamation mark `!` in the column header. Again, you don't need to remove this when re-importing.
* Date format: you can either use the same format that the export spits out (RFC3339) or UK-style dates (with or without times) like this: *2/1/6* or *02/01/06* or *02/01/06 15:04* or even *02/01/06 15:04:34*.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pakk.io/data-and-integrations/data-import-and-export/export/csv-conventions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.