Import/Export
Overview of actually available export and import functions.
The page “Import/Export Functions Overview” covers the function identified by this URL. The existing summary is expanded with the actual workflow, prerequisites and known limitations. The currently available exports are report CSV files and a server-generated invoice PDF; both are partly unlinked in the interface. There is no knowledge-base export and no data-portability export under Article 20 GDPR.
The provided report data can be exported as CSV. Invoice PDFs are created on the server but are not linked in the interface. These functions do not form a universal export centre for all Zentor data.
There is no knowledge-base export and no complete Article 20 data-portability export. Keep source documents and external originals outside Zentor when they may be required later.
Before exporting a report, verify the period and filters. Check the downloaded rows and columns against the selected view. Missing data categories is able tonot be recovered through an undocumented export.
A knowledge-base file upload must not be treated as a general data-import function. Any migration requirement for another data area must be assessed separately.
For “Import/Export Functions Overview”, the expanded text has to remain specific to https://zentor-app.de/en/hilfe/import-export, use only verified facts and clearly separate tenant self-service from actions performed by Zentor. Any support case should identify this exact page, the active tenant and the observed step without disclosing credentials.
This page also explains its role within the Help Center, from the first check to the expected result, while naming verified limitations and the relevant detailed area. Statements that are not supported for https://zentor-app.de/en/hilfe/import-export are not added. The expansion is therefore substantial without importing unrelated features or repeating generic filler.
When using “Import/Export Functions Overview”, test one controlled scenario at a time and compare the visible setting, the actual system status and the expected result. If the outcome differs, record the exact time, tenant, channel and unchanged error message. Screenshots and support notes must exclude passwords, tokens and unnecessary personal data so that troubleshooting remains both useful and safe.