Importing and Exporting Data

Most list pages share one import/export workflow. Export and import build on the same field definitions per entity, so the field picker, translated labels, automatic column matching, and validation all fit together — a file you export in data mode is ready to be imported again.

Three areas have specialized flows instead: Contacts (address books need matching, organization links, and vCard support), Bank Transactions (bank files need account matching and deduplication), and Accounting Exports (bookkeeping packages are generated from journal entries, not list fields).

List page

current filters

Export

format · mode · fields

File

CSV · XLSX · JSON

Import

mapping · preview

your data in Einblickexportimportthe exchange file

Where you find it

Supported list pages have Export and Import in the header actions.
Import is available on Absences, Buildings, Contacts, Equipment, Events, Festivals, Materials, Organizations, Reports, Tasks, Tools, Vehicles, and Work Times.
Export is available more broadly, including Projects, Inquiries, Quotes, Invoices, Incoming Invoices, and Work Orders.
On Contacts, the Import action opens the directory import instead of the generic column-mapping sheet.
Bank Transactions has Import file for OFX and CSV bank exports. That flow previews new, updated, duplicate, and skipped transactions and can create a manual bank account when it sees a new own IBAN.
Accounting Exports is the finance handoff for your bookkeeper — see below.

Export workflow

Open Export on a supported list page.
Pick the format (CSV, XLSX, or JSON) and the mode:
- Readable — translated headers, formatted dates, display labels.
- Data — raw field keys, raw values, and relation IDs, made for reimport.
Adjust filters, fields, field order, related data, and sorting.
Start the export and download the file.

The export sheet starts from the current table filters, so you export exactly what the view shows — or widen the filters first. Archived rows are hidden by default; flip the archive toggle in the table toolbar before exporting if they should be included.

Formats at a glance

Format	Readable mode	Data mode	Notes
`CSV`	✓	—	always a flat, single table
`XLSX`	✓	✓	related data becomes extra sheets
`JSON`	✓	✓	related data becomes a `relatedData` object; data mode adds an `_einblick` envelope so the importer recognizes the file

Related data is available for invoices, quotes, and work orders (their positions), organizations (linked contacts and bank details), and festivals (festival days). In readable mode it's optional; in data mode it's included automatically.

Import workflow

Open Import on a supported list page.
Upload a CSV, XLSX, XLS, or JSON file — up to 10 MB and 50,000 rows. If the file has multiple sheets, pick one.
Review the column mapping. Einblick matches columns by field key, translated labels, and common synonyms across all supported languages first, then falls back to fuzzy matches — which are marked so you can double-check them. Any column can be remapped or ignored, and a preview shows the first parsed rows. Under Default values, review or add values for fields that have no mapped column; a mapped column always wins.
Continue to the preview. It shows which rows will be created, updated, skipped, or rejected, including values supplied by Default values. If rows match existing records, choose whether to fill only empty fields, overwrite fields that have an imported value, skip the matches, or import them as new records.
Start the import and watch progress in the same sheet. Rows are written in batches; Cancel import stops the remaining batches, but records already created or updated keep those changes.

Good to know:

Generic imports create new records and can update detected matches. Fill in missing details is the safe default and never overwrites stored values; the preview offers the other duplicate strategies before anything is written. Only the first 5,000 existing records are checked, and the preview warns when that limit applies.
Default values apply only to newly created records and never change a matched existing record. Required defaults can be changed but not removed. Blank rows remain skipped instead of becoming records made only from defaults.
Each import targets one table. Multi-sheet files let you pick a sheet, not recreate parent-child trees in one step — import each sheet from its matching feature page.
Number parsing follows the active interface language, including grouping and decimal separators: for example, 1,234.56 in English, 1.234,56 in German, and 1 234,56 in Czech.
System and computed fields are excluded from the mapping. Supported file and image fields accept public HTTP(S) links: after you explicitly confirm that you trust the sources, Einblick downloads supported images and common documents into the Workspace, up to 25 MB per file. A failed download is reported on its row, but does not discard the rest of that record.

Contact directory imports

The Contacts import is built for address books rather than table reimport:

Sources: the browser's system contact picker (where available), .vcf/.vcard, CSV, XLSX, XLS, and JSON.
Common contact headers, vCard fields, and browser contact fields are normalized into contact and organization data. A row only needs some identity — a name, nickname, email, or phone number — first and last name are not individually required.
Rows are prepared as ready, review, or skipped before anything is written. Ready rows can create contacts or organizations, fill empty fields on exact matches, and create contact-organization links; ambiguous rows are left untouched.
The result reports created, updated, linked, skipped, and failed rows plus warnings, separately.

Accounting exports

Accounting Exports generates bookkeeping packages from journal data instead of list fields.

Configure provider, account chart, tax mappings, document inclusion, and partner numbers in Workspace Settings → Accounting.
In Accounting Exports, pick a month and review row count, warnings, blocking issues, and sample postings before generating. Blocking issues must be resolved first — their actions jump straight to tax mappings, partner numbers, or the source record.
Postings can come from paid invoices, paid supplier invoices, active financial entries, categorized bank transactions, synced Stripe balance transactions or payouts, asset depreciation or disposals, and inventory movements.
The generated BMD ZIP contains bookings, source documents (when enabled), manifest.json, README.txt, optional account master data, and an anlagenspiegel_<period>.csv asset schedule. Each export keeps its sequence number, period, downloads, and a Mark sent action.
Provider settings can be prepared for multiple providers, but package generation currently supports BMD.

Best format for reimport

Use Data mode to move data between Workspaces, archive raw records, or prepare a later reimport — field keys then match directly on import, independent of language.
XLSX and JSON are lossless; use CSV when you want a flat file for spreadsheet work or manual review.