Skip to content

Tenant export format

A full export holds all the data of one tenant in one zip file. A Posto platform administrator starts the export. The download link works for 7 days after the export is done.

The zip comes from one snapshot of the database. All files show the tenant at the same moment.

File Contents
manifest.json The format version, the database migrations, the tenant, the export time, and each table with its file, row count and columns
tables/<table>.csv One file for each table of the tenant, for example tables/sales_invoice.csv
users.csv The members of the tenant: id, username, name, email
documents/<type>/<number>.pdf Each document as a PDF, as the ERP prints it
README.txt A short description of these files, in Macedonian and English
{
"format": 1,
"migrations": { "count": 42, "last": "…" },
"tenant": { "id": "…", "slug": "acme", "name": "Acme Trade" },
"exportedAt": "2026-11-13T16:00:00.000Z",
"tables": [
{
"name": "sales_invoice",
"file": "tables/sales_invoice.csv",
"rows": 120,
"columns": [
{ "name": "id", "type": "uuid" },
{ "name": "created_at", "type": "timestamp with time zone" }
]
}
],
"users": { "file": "users.csv", "rows": 3 },
"documents": [{ "type": "sales.invoices", "count": 120 }],
"leftOut": { "tables": { "api_key": { "reason": "…", "setUpAgain": "…" } }, "columns": { "mail_settings.smtp_password": { "reason": "…", "setUpAgain": "…" } } }
}
Member Contents
format The version of the zip format. It is 1. The import refuses another version.
migrations The number of database migrations and the name of the last one
tenant The id, slug and name of the tenant
exportedAt The export time, ISO 8601 in UTC
tables Each table: its name, its CSV file, its row count and its columns with their PostgreSQL types. The columns are in the order of the CSV file.
users The file and the row count of users.csv
documents The PDF count for each document type
leftOut The tables and the columns that the export leaves out. Each has the reason, and some say what to set up again.

Each CSV file follows RFC 4180:

  • The first row has the column names.
  • Each value is in double quotes. A double quote in a value is two double quotes.
  • An empty field without quotes is NULL.
  • An empty field in quotes ("") is an empty text.
  • Dates are ISO 8601 (2026-11-13). Times are in UTC.
  • Intervals are ISO 8601. Decimal numbers are exact.
  • JSON values and arrays use the text format of PostgreSQL.

Example:

"id","uid","name","note","created_at"
"01a19771-6749-7ba4-bd20-c6aa74b70184","A1","Item 1",,"2026-11-13 16:00:00+00"
"01a19771-672a-78b9-a4e9-0c07a26a6eae","A2","Item 2","","2026-11-13 16:05:00+00"

In the first row, note is NULL. In the second row, note is an empty text.

A CSV file holds only the rows of the tenant. It also holds the deleted rows that the database still keeps.

Users are global in Posto: one user can be a member of more than one tenant. So the export has no users table. users.csv has the members of the tenant:

"id","username","name","email"
"9832316d-f9e4-4c5f-a4b3-bd7c90ca2139","ana","Ana Petrovska","ana@example.com"

users.csv has no passwords. The users of service API keys and server clients are not in it.

Each document is in documents/<type>/<number>.pdf. <type> is the document type, for example sales.invoices or finance.journals. <number> is the document number. A document without a number, or with a number that repeats, takes its ID in the file name.

The bills of the PoS have no PDF. They are only in the CSV files.

The export holds no secrets. After a move to another server, set these up again:

Left out Set up again
API keys and their users Make new API keys and give them to the integrations.
Server clients and their users Register them again and give the integrations the new secrets.
PoS device sign-ins Each PoS signs in again.
E-invoice certificates Upload each certificate again.
The SMTP password of the mail settings Enter it again in the mail settings.

Passwords, sessions and tokens are not in the export. manifest.json lists each left-out table and column in leftOut.