Export data

Pour :Administrateur

Once your exploration is built and the preview matches your need, you can export the results in three formats: XLSX (Excel), PDF Table or PDF Cards. Each format answers a different use case.

Overview of the 3 formats

Format	Main use case	Row limit	Typical use
XLSX (Excel)	Analysis, reprocessing, accounting	50,000 rows	Accounting export, segmentation, cross-reference with another tool
PDF Table	Quick printing of a list	500 rows	Service table, printed visual check
PDF Cards	Physical file per entity	500 rows	Registrant cards, donor cards, event file

General procedure

1. 1

   Build or open the exploration

   Open the view to export, or create it from scratch. Check that the preview displays the expected columns and scope.

2. 2

   Check the number of rows

   The counter at the bottom of the table shows the total number of rows. Check it respects the format limit you want to use (50,000 for XLSX, 500 for PDFs).

   If you exceed: add more restrictive filters (for example on the date) to reduce the scope.

3. 3

   Click « Export »

   The button is in the workshop's action bar, at the top of the preview.

4. 4

   Choose the format

   Select XLSX, PDF Table or PDF Cards in the dropdown menu.

5. 5

   Launch the export and retrieve the file

   The export is generated in a few seconds (proportional to the row volume) and the file is downloaded automatically by your browser.

XLSX (Excel)

The default and most versatile format. To prefer for any analysis, reprocessing or integration with another tool (Excel, Google Sheets, accounting software).

Characteristics

• .xlsx format openable in Excel, Google Sheets, LibreOffice Calc, Apple Numbers
• Auto-width: column width adjusts automatically to content
• Header row formatted at the top
• Excel filters enabled to sort/filter in the exported file
• Types respected: dates are Excel dates (sortable, filterable), numbers are numbers (computable)

Specific behavior for « many » relations

If your view contains a « many to one » relation (for example payments of a contact), Unisoft unpacks the relation: one row per child, with the parent's columns repeated.

Example on a Contacts view with Payments relation:

Contact	Email	Payment date	Amount
David Cohen	david.cohen@exemple-unisoft.org	01/12/2026	€50
David Cohen	david.cohen@exemple-unisoft.org	02/03/2026	€100
David Cohen	david.cohen@exemple-unisoft.org	03/17/2026	€75
Sarah Lévy	sarah.levy@exemple-unisoft.org	01/14/2026	€200

Contact David Cohen appears on 3 rows because he has 3 payments. It's the ideal format for making pivot tables in Excel.

ℹ

Good to know

If you want one row per contact without unpacking, don't check the columns of the Payments relation. You can instead use a computed field (for example « Total amount received ») if available on the entity.

Limit

• Maximum 50,000 rows per export.
• Beyond that, you get a message inviting you to reduce the scope.

⚠

No async export in V1

In V1, the export is synchronous: you wait for generation in your browser. For very large exports (beyond 50,000 rows), there's no asynchronous queue yet. Slice your view by periods (month by month, quarter by quarter) to stay under the limit.

PDF Table

A PDF in A4 landscape format, with your view shown as a classic table. Ideal for a quick print or a share by email to someone who doesn't have access to Excel.

Characteristics

• .pdf format universally readable
• A4 landscape: maximizes the available width for columns
• Headers repeated on each page to ease reading
• Page numbering in the footer
• Organization logo and name in the header (per your configuration)

When to use it

• Give a printed list to a team member during an event
• Prepare a visual check document of an operation
• Send a summary by email to a community president who just wants to look, not reprocess

Limit

• Maximum 500 rows (hard cap).
• Beyond that, you have to filter more precisely.

⚠

Too many columns = hard to read

The A4 landscape format allows comfortable display of 6 to 10 columns depending on their width. Beyond that, the text becomes too small to read. If your view has many fields, prefer the XLSX export.

PDF Cards

A PDF where each entity is on its own page, presented as a card (two columns: label / value). Ideal for producing a physical file with one card per contact, per payment, per submission…

Characteristics

• .pdf format
• One page = one entity (one contact, one payment, one submission…)
• Field label on the left, value on the right on two columns
• All fields checked in the view appear on the card
• Organization logo and name in the header

When to use it

• Print a registration card per participant at an event
• Produce a physical donor file for archiving
• Prepare contact cards for a welcome team on a mobilization day

Limit

• Maximum 500 rows (= 500 pages in the generated PDF).
• For very large populations, export rather as XLSX and generate the cards via another tool.

Choosing the right format — recap

Your need	Recommended format
Prepare an accounting export	XLSX
Segment a population for a follow-up	XLSX
Cross-reference with another tool (Excel, Sheets)	XLSX
Print a list to scan quickly	PDF Table
Send a readable summary to a leader	PDF Table
Produce a file with one card per contact	PDF Cards
Print registration cards	PDF Cards

V1 limits — to know

⚠

No automatic scheduling

You cannot (in V1) schedule a recurring automatic export (for example « send me this export every Monday at 8 AM »). You have to restart the export manually each time.

⚠

No threshold alert

Nor is there an automatic alert when a view exceeds a threshold (for example « notify me if more than 10 payments are in error »). This feature is planned for a future version.

⚠

Export limited to 50,000 rows (XLSX) or 500 (PDF)

If your view exceeds, slice by periods (month, quarter…) and concatenate the files manually after download.

Going further

• Create an exploration — the complete procedure
• Save and share a view — reuse a view over time
• Filters and sorts — refine the scope before exporting