Two routes, one mapping
File export and API access use the same field mapping. Anyone starting with CSV and later switching to the gateway does not reconfigure.
← All integrations
Migration & switching Reads data
otris
From otris privacy, contract and corporate into isidaten
otris builds privacy, contract, corporate, risk, policy and register on one shared platform: documentsOS. Records are called folders there, their types folder types, and the field names are configured per customer installation. That is exactly where blanket imports fail. The connector therefore takes two routes: the file import reads the export as CSV or as an Excel workbook with one sheet per entity type, the API import pulls the data live via the documentsOS REST gateway. Both use the same mapping logic, and both end in a preview before anything is committed.
Vendor: otris software AG · www.otris.de
What is synchronized automatically
- Processing activities from otris privacy
- Contracts and deadlines from otris contract
- Risks and policies from otris risk and policy
- Further folder types via manual assignment
Your benefits
Field names may differ
Because otris installations name their own fields, the connector works with candidate lists for the usual German and English labels and pre-fills the mapping from them. Every row can be corrected.
Nothing is imported unasked
Unknown folder types are skipped rather than guessed. otris installations contain many customer-specific workflow folders that have no place in an ISMS.
The file route is the sturdier one
The REST gateway is not present in every installation and requires a DOCUMENTS API licence. Where it is missing or differs, the export gets you there reliably. We say so upfront, not afterwards.
Connect otris with isidaten
We show you the connector live in your own environment – non-binding and free of charge.